I never had success with Safepoint. I was able to follow the instructions by nicktee55 and use rsync but the speed was slow. Being more comfortable in DOS than linux I decided to go with a batch file to handle my backups. I have a decent PC running windows 10 as a Plex server that is on all the time so letting it do backups is simple.
This is what I did:
1 created a new folder - C:\BackupFiles
2 created a new text file called backup.txt
3 opened backup.txt and entered this text: (no carriage return in the robocopy lines -wordwrap)
rem robocopy [source] [destination] /[switches]
rem /copy:dt copies dates and timestamps of originals
rem /fft needed because ext3 and ntfs timestamps are different
rem /e includes all directories including empty ones
rem replace /e with /mir to make destination an exact copy *** will delete files on destination ***
rem /np no progress percents in log file
rem /log+:[filename] appends backup info to log file
rem /r:[n] number of retries per file - default is 1,000,000
rem /w:[n] time to wait between retries
rem you need /r because the job will never finish if you hit an error with 1,000,000 retries
robocopy \\MCMname\share1name \\DestDeviceName\share1BUname /copy:dt /e /fft /np /r:3 /w:30 /log+:c:\BackupFiles\backuplog.txt
robocopy \\MCMname\share2name \\DestDeviceName\share1BUname /copy:dt /e /fft /np /r:3 /w:30 /log+:c:\BackupFiles\backuplog.txt
4 saved the text file
5 renamed the text file backup.bat (you need to have Windows display filename extensions to do this)
6 used Windows Task Scheduler to run the backup.bat file everyday at 2:01 am
(Don’t want it running twice on a DST change day)
7 had an ice cold vodka gimlet - hold the lime and syrup
This runs great and the speed is about 10x faster than I was getting using rsync. The backuplog.txt file gets appended each time it runs. You can get a replacement log file each day by removing the ‘+’ in the /log switch.
I made a separate file that I can run with the /mir switch that will clean up any deletes I made in the source. Be careful with the /mir switch because anything not in the source will be deleted from the destination. You may not need the /copy:dt or /fft switches depending on your drives. I had to add them because one of my destination drives is a USB drive formatted as NTFS.
As with anything test this out thoroughly with a small directory and see how file changes are handled. You can also use this to back up to your MCM by putting it in the destination of the robocopy command. If you have spaces in the folder names of your source or destination you will need quotes around the source and/or destination.
This worked perfectly for me because my PC is on 24/7, YMMV.