I am planning our backup strategy in a mixed enviroment (Windows File Server, Linux Samba Server, MS desktops). The target is to use such backup which for dektops uses shared folders as mapped drives on windows server. On windows server there are several data partitions which should be backup-ed to the Linux file server. One mapped backup device on SAMBA should be synchronized with the windows data partitions.
Since this is a big collection of data (200-300GB) it is not a good idea to copy all the data again and again each day. This is why I am trying to use robocopy instead of Windows Backup utility on MSW Server. (I am used to use rsync for this on my Linux servers).
Because I would like to investigate thoroughly whether the built in Windows Backup on MS Windows Server is capable of such tasks, I list here the pros and contras for robocopy. I don't have much experience with the windows built-in backup capabilities and I don't want to use something what would not do its job correctly.
- I would like to backup only the new data, i.e. incremental backup to not to send 300G of data each day on network
- If there is a problem with the connection (in the middle of the backup process) or some other problem (windows cannot read some files) robocopy should continue to backup if the network is back and skip files that it can not access
- Do the copy whether there is some user loged in or not
- Possibility to simply check wheter the update is correct - check the file tree in the backup storage (no need to unpack archives, backups). It gives a good feedback about wheter the backup is working correctly
- Log the process of backup, where I can look later for reasons of possible problems that may have appear
These are the main advantages which robocopy gives me. I would like to know whether it is possible to do this with the built in Windows Server Backup utility.
Further, I have one problem with robocopy. I created a .bat script which is scheduled in the windows server for everyday execution. The problem is that the script is executed only when a user is logged in. If the user is not logged in the mapped shared drive is not connected (Z: in my case). So it cannot access the backup target directory. I found this suggestion on google:
NET USE Z: //LINUX/BACKUP \USER:Remoteuser
This should be inserted before the robocopy command (this should connect the network-drive). It didn't work - I don't know why. I tried the same command on cmd.exe where it worked. (although I had to disconnect the actual alive connection first which is automatically used at logon)
As a matter of fact it is also not a good solution. because if the user is logged in it shows error that the drive is already connected - that it cannot be connected multiple times or with multiple users. I am confused about the way the windows scheduler works. :( Is it possible to do backup with acceptable functionality??