That depends on the backup mode you use. You can revirew your bottleneck statistics to determine the slowest component.Is 70MB/s reasonable?
If you specified a repository as source and some other job has put some data there then your backup to tape job will pull all new data as well. Also full backups of those 18VMs could grow in size.How can it process 3.7TB and ask for a second tape when the previous job to disk was 3.3TB?
Depends on how many of other backup jobs are pointing to that repository. If none then you can use the whole repository as source.Should I have the tape job setup to duplicate from backup job or from StoreOnce repository?
Switching to "Backup repository" source will make your job to pull the whole repo, so your backup to tape may get only bigger, not smaller.I'm testing it right now again but I switch the backup files to "backup repositories" instead of backup job...not sure if that would make a difference or not.
In other words you say that you had 18 VMs backed up to repository and the resulting .vbk file was 3.3 TB in size whereas Backup To Tape Job that used Backup Job as a source has demanded 3.7 Tb and no other backups were made since the only backup job run that had produced 3.3 Tb file, is that correct?only 1 backup job to that repository. But the job that ran on the weekend wasn't from the repository but backup job that completed with 3.3TB...shouldn't it duplicate to tape be the same size? that's what is confusing that the tape ran until 3.7TB and asked for a second tape.
Users browsing this forum: No registered users and 1 guest