v.Eremin wrote:If 3-party application can't copy files produced by backup copy job due to locks or something, it stands to reason to utilize additional backup job, instead of backup copy one, that is pointed to remote repository and let software archive to tapes the resulting backup files. Thanks.
albertwt wrote:Craig, Thanks for sharing your strategy and plan here.
FYI: I'm also in the same situation as yours, having Veeam Backup Copy repository in remote site and then the files written to the tape using Symantec Backup Exec 15. So it is Disk (First Veeam Backup in DC) to Disk (Backup Copy to Remote Site) to tape(Tape library attached to the same Veeam Backup Copy repository server).
The problem is that using the Forward incremental, the .VIB files directory most of the time is failed to be written to the tape by Symantec, and Symantec now blame Veeam for "holding" the files during the backup copy job, therefore the Writing to tape process has never been succeesful 100% ever since I upgrade Veeam to v8.0
So I'm interested to know what's your strategy here to ensure that the files can be written o tape by 3rd party application not using Veeam.
Users browsing this forum: No registered users and 1 guest