Looking for new off-site backup for a Dedicated Linux Server

Started by kpripper, Jul 01, 2022, 06:50 AM

Previous topic - Next topic

kpripperTopic starter

I am looking for a reliable off-site backup option for my dedicated Linux server. I am currently using BackupRun with their R1soft software, but I had a scare a month ago. I tried to restore a client's database, and I wasn't successful. Fortunately, I had another local backup, but I no longer have confidence in BackupRun and I have my doubts about R1soft. I have about 1.2TB on the server.

I need to be able to restore individual files and/or databases. Ideally I'd like to be able to do a bare-metal restore as well, but with a cloud service that could take forever. I know that some services will FedEx a hard drive if there is a catastrophic failure. But I'm more concerned about getting a daily total server backup that permits restoration of a single file.

Some searches turn up companies like iDrive, but most of the large and cheaper backup options don't seem to support Linux servers.

I even considered just getting another cheap dedicated server and mirroring. Is that a reasonable option?


I have been using Duplicity software to make "incremental forever" backups of Ubuntu-based VPS's for almost 10 years now, with the following Duplicity parameters:
--timeout 120
--num-retries 12
--backend-retry-delay 90

I use B2 as the cloud object storage but I use S3 as the interface as it is more reliable with Duplicity (new versions sometimes don't work with B2 interface).

Only "trick", for easier database recovery, has been a mysqldump just before I start Duplicity each night.


In my experience the best option for you is to use an app like Jetbackup. First, choose a high-capacity Bare-metal server.
Then install the Jetbackup application on your main server and set how you want your data to be backed up.

However, it is not fair that you blame R1soft. R1soft is still a stable application. If you installed R1soft correctly, no problems will arise.


The programs that you use are popular, then reliable. I don't believe that R1soft is somehow not reliable. Check again if you have installed the necessary files correctly. If something is still wrong, contact the software support service.


I can recommend CrashPlan. It has many backup options. There are such options: copies in a folder, copies in another network computer, you can also in a friend's computer or on your CrashPlan backup server. The main thing is to find a friend with a lot of free hard disk space, and you will be able to get your files absolutely free of charge right from home.


Backups on another server
After you have made a backup on the local server, copy the backup to the remote webserver. If you have a qa server, backup your production and restore it to the qa server. You should probably set aside a dedicated server with plenty of backup storage space. If you have a dedicated backup webserver, you can even initiate a backup from a dedicated remote server and you don't need to keep a copy of the backup on the local server.

To back up a DB, I prefer to take a backup on a local server and copy it to a remote server. So the database backup is in two different locations. If you lose one backup, you will have another one. Also, if a database fails on a local server, it can be quickly and easily restored from a backup located on the same server, instead of copying the backup from a remote webserver to a local server and restoring it.

Note: use mysqldump, mysqlcopy for MySQL database backup, pg_dump psql for PostgreSQL database backup and RMAN for Oracle database backup.

 Tape backup
If you don't have a dedicated backup server to keep copies of all your backups, implement a tape backup solution and store all your backups on tape. Tape backup is slow. Therefore, first make a backup on a local webserver and copy it to tape after business hours or on weekends. The advantage of backing up to tape is that the backups are easily portable and you can move the backup to any location.

 Backup at a remote website
You can do all of the above and still get in trouble when disaster strikes. If the local server, the backup server, and the tape backup are in the same physical location, you could lose all data in the event of a disaster. Therefore, it is important that you store your backups off website.

You can have a backup data center where all your mission-critical applications in the primary data center are synchronized with the emergency data center (or at least keep a copy of the backup tape in a remote location). Don't physically change tapes and store them in the same datacenter, which is useless during a disaster recovery scenario.