I have spent rar too much time this past week reviewing and updating the backup procedures on my development workstation. In the past, I was:
- Using Acronis to backup the files on drives C, D to drive Z.
- Using Syncback to occasionally copy Videos, Music and Photos to an SMB share on a Synology DS209J.
- Using the Synology DS209J as a media server.
The challenges I faced:
- Acronis has failed in the past, so I need to either trust it again or dump it.
- The Synology server is embarassingly slow. File copying is slow, and videos occasionally stutter.
- I’m concerned about SMB shares being trashed by a possible Cryptowall virus.
- Am a bit low on disk space in areas.
Hardware changes made:
- Replace the Synology with a CentOS 7 VM running on an existing ESXi server, and install Plex on it.
- Add a 4TB WD Red drive to the ESXi server, create a 4TB ext4 volume and attach it to the CentOS VM.
- Replace an existing 10/100 ethernet switch with a 10/100/1000 ethernet switch.
Functionality to test:
- Disk and file backups with incremental and block level support for extra large files.
- Cataloging of the backups.
- Directory/file synchronization.
- Cloud and SFTP support.
- Syncback (I have been using Syncback free)
- Acronis Backup/Recovery (I already own this)
- Acronis True Image
It slowly dawned on me that when performing occasional full backups with Syncback, what I really wanted to do was to perform file synchronization. In this case, I didn’t want incrementals or the ability to restore an old version. I just wanted a source and destination synchronization of my media directories. It also turns out that dedicated backup software such as Acronis or Cloudberry don’t really support that functionality. So, let’s look at each of the packages I tried.
There are several versions of this product, and Syncback free has allowed me to backup across SMB shares without any problems in the past.
It does not support block level backups, which I felt were important with the number of Virtual Machines I’m using.
In order to Synchronize to the CentOS server via the more secure SFTP, I needed to purchase Syncback Pro (and not SE).
Being about same price, the block level support of Syncovery put it ahead of Syncback Pro.
This product costs about the same as Syncback Pro, but does support block level backups, as well as file/directory synchronization.
I ended up buying a copy of this to use strictly for synchronization with the new media server. Maybe I’ll use it for full backups down the road once it gains my trust. I’m not there yet.
I already own this product, so I spent time determining if I wanted to continue using it or replace it with an alternate. After significant testing, I decided to update it and use it for backups. One of the main reasons was that using the catalog for file recovery was easier to use than the alternatives.
Acronis True Image
This package had great reviews, however the simplistic interface was not for me. I ditched it early on.
This product performs backups to various local and Cloud services and worked very well. I have a client that uses it and it’s a good product. In order for me to purchase Cloudberry, Acronis Backup/Recovery had to fail in some significant fashion and the only weakness I could see with Acronis (other than the fact that it’s huge), was that the version of Acronis I own does not support Cloud Services. Fortunately for me, that was not a requirement and as a result, Cloudberry was off the table.
Acronis now performs custom daily/weekly backups of drive C and drive D to drive Z as well as to the CentOS server via SFTP. One of the advantages of the custom configuration is that I can tell it to purge old backups when the destination drive gets full. At 4TB, that should take a while.
Syncovery synchronizes the Photo, Music and Video directories to the CentOS server via SFTP for use by the Plex media server. It also does so at a MUCH faster clip with the new gigabit switch.
Oh, and I’m also running Crashplan as a backup of last resort. When it comes to backups, you can never have too many.