![]() ![]() ![]() I have no real issue, because the file still gets copied and I have my Backup. I might add that it shows as a fail quite rightly as I have "Verify Copy" enabled and the files have changed from initial check to copy (as they are fluid live files). ![]() This makes sense because it fails on the VM's. Where I have an issue is that Sync-Back Reports a Failure on the App Drive Backups. I back up my Main Server Array to the Backup Server Daily (Incremental Backup, no Delete). I take a mirror of the Flash and App Drive (of both Servers) to my Main Server Array Daily, Weekly and Monthly. I have a well thought out backup strategy. However I have another one now Given the topic was so broad, it seemed to feel right to keep going with this thread.Īs can be seen from the attached screen shot. a neat way to do it, since it doesn't require a separate computer.Īs I note above, I solved the initial issue which was the driver of this thread. My setup runs SyncBack from a separate Windows box that's always on => I believe Daniel has his set up to run from a Windows VM that's on his primary server. You can also create an icon that will load SyncBack and automatically run the profile by simply appending the name of the profile to the end of the command line. Or, even easier, you can set SyncBack to run the "Backup Now" profile at a scheduled time on whatever days you want (daily, weekly, monthly, every-other-day, etc. So in SyncBack you simply point to "Backup Now" and click Run. perhaps name "Backup Now" => and it would include all of the profiles I just listed above. ![]() You can then create a "Group" profile to do it all. You would then create backup profiles for each. As an example, suppose you have shares named Movies, TV Shows, Music, System Backups, and Personal Data. So I simply have one profile for each share, and they're all set up with the same set of options. It's very easy to configure it to do exactly what you want to achieve with the backup. It can be a backup only a synchronization between two locations and you can choose whether the backup should mirror the source or should retain files that were previously backed up but are no longer on the source. If you're familiar with SyncBack, you create "profiles" that define the source, the destination, and a LOT of options about how you want the backup or sync to work. Mine is basically the same => I have a SyncBack profile for each share and simply back it up to the backup server. ![]()
0 Comments
Leave a Reply. |