ryanbe
asked on
Linux Server Backup Guidance
Hi folks
Just looking for some guidance on backing up a linux server regularly.
The server I have will be a very stable state ubuntu running postgresql and Odoo ERP services.
What I currently plan to do is:
1. Have cron job that runs dump for my postgresql databases.
2. Then cron runs tar to backup specific directories (including database dumps) to a local backup folder, then copies them to an external drive.
3. When a restore is needed, I manually extract the files from external drive tar to a temporary folder on the target recovery machine. This machine is already setup identically to the server, e.g. running ubuntu, postgresql, and odoo.
4. Copy needed files to appropriate folders (probably automate this).
5. Restore database dumps.
6. Enjoy running business on new Server? Profit?
Any advice please? Am wiling to spend significant money if there's a much easier/better way anyone can suggest? e.g. Acronis.
Just looking for some guidance on backing up a linux server regularly.
The server I have will be a very stable state ubuntu running postgresql and Odoo ERP services.
What I currently plan to do is:
1. Have cron job that runs dump for my postgresql databases.
2. Then cron runs tar to backup specific directories (including database dumps) to a local backup folder, then copies them to an external drive.
3. When a restore is needed, I manually extract the files from external drive tar to a temporary folder on the target recovery machine. This machine is already setup identically to the server, e.g. running ubuntu, postgresql, and odoo.
4. Copy needed files to appropriate folders (probably automate this).
5. Restore database dumps.
6. Enjoy running business on new Server? Profit?
Any advice please? Am wiling to spend significant money if there's a much easier/better way anyone can suggest? e.g. Acronis.
If you already have two systems on hand with one "ready" to take over, why not look at having the second as a hot standby or better a functional load balance/......
Have a look at PostgreSQL replication or clustering.
http://wiki.postgresql.org/wiki/Replication%2C_Clustering%2C_and_Connection_Pooling
..........
Note your backups/DR should still be done just in case both .......... Fail
Have a look at PostgreSQL replication or clustering.
http://wiki.postgresql.org/wiki/Replication%2C_Clustering%2C_and_Connection_Pooling
..........
Note your backups/DR should still be done just in case both .......... Fail
ASKER
Hi arnold
That might be an option for later but for now am confident a single server will be able to handle the load. A one-off few hours downtime is OK should the server fail. Just want to keep things as simple as possible initially. Also I would like the backup server to be off-site. Acronis backup to the cloud is looking like a nice neat 'hands-free' solution.
I guess it's just a matter of developing a backup/restore procedure and testing and practicing it.
That might be an option for later but for now am confident a single server will be able to handle the load. A one-off few hours downtime is OK should the server fail. Just want to keep things as simple as possible initially. Also I would like the backup server to be off-site. Acronis backup to the cloud is looking like a nice neat 'hands-free' solution.
I guess it's just a matter of developing a backup/restore procedure and testing and practicing it.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER