In the Task Settings enter the following: (See picture for a schedule set to run every sunday). Name it “PostgreSQL Backup” with the user root, and set the schedule to how frequent you want it to back up. To do this simply head back into the Task Scheduler in the control panel of the DSM, and Create a new Scheduled Task as a User-defined script. Within the pgAdmin program there IS an option to create backups manually, but a much safer option is to schedule backups within the DSM Task Scheduler for a more consistent backup routine. If you’ve made it this far then congratulations, you’re done and everything is ready to be used! However, there’s still one final (optional, but recommended) step to schedule automatic backups of the postgres databases. Su – postgres -c “pg_ctl -m fast restart” is to apply all changes. The cp command reoplaces the internal pg_hba.conf file with the one stored on the network drive. The sed command is to make sure the listen_addresses from before are always set to “ 127.0.0.1, 192.168.1.115“. Su – postgres -c “pg_ctl -m fast restart” In the Task Settings, enter the following in the Run command: In the general settings give your task a name: “postgresql” and set the user to root. To do this go to the DSM and open up the Control Panel in the Task Scheduler tab.Ĭhoose the option Create: Triggered Task: User-defined script. Now that we have access to our config file within a network drive it’s time to create a script within DSM to keep them in sync after system updates. The finishing touches are going to be on the DSM site. That was the final step of SSH, so you may now close the SSH client. txt file, and create a new folder called “psql-backup”. conf file appear in the folder it means the command succeded.ĭelete the. Note: If your path has spaces in it, surround the filepath with quotation marks.Ĭp “/etc/postgresql/pg_hba.conf” “/volume1/System/PostgreSQL/pg_hba.conf” Now use the following command to copy over the. You should now see a file path showing up something like this: “/volume1/System/PostgreSQL/pg_hba.txt”. Once the file is created go back to your SSH client and enter the following: This is in order to be able to verify the folder location within the system, as it may vary depending on how it’s configured. Locate the folder and create a text file named “pg_hba.txt”. In order to prevent this we need to use a network directory where we can store our modified pg_hba.conf file to keep it in sync with the system.Įarlier in this tutorial I advised you to create a PostgreSQL folder on a Shared Drive.
#Synology install idrive update
TimeZone = to the way Synology DSM was setup, everytime there’s a new update or change in the DSM system it resets all internal configuration files. # Following parameters will be modified dynamically Ident_file = ‘/etc/postgresql/pg_nf’Įxternal_pid_file = ‘/run/postgresql/postmaster.pid’ Access the Shared folder on an external computer, and create a directory called ‘PostgreSQL’.ġ92.168.1.115 – sed -i ‘6s/127.0.0.1/*’ cat /etc/postgresql/nf In this folder we will store the postgresql configuration file, aswell as automatically backup the SQL databases. I would also recommend you to create an additional shared folder within your Synology named ‘System’. Set the type to Source Port, Protocol TCP and type in Port: 5432 Hit edit and then Create in the new window. Enter the Security submenu and the tab ‘Firewall’. The system is also required to allow source port 5432 through the firewall. Go into the submenu “Terminal & SNMP” and enable SSH. Here are some of the packages that use postgres:Īccess the Synology server and enter the control panels. Keep in mind that you don’t actually need to use the packages, but they might have to be Running (TBD). Make sure you atleast have one package installed and running that already utilises PostgreSQL – this is due to some weird limitation set by Synology. Before postgresql can be accessed there are some preparations required within the Synology DSM:
0 kommentar(er)
