- Posts: 6
- Liked: 1 time
- Joined: Jun 22, 2016 11:58 am
- Full Name: Jesper Pedersen
Currently the bottleneck is my san box running on ethernet and the LTO-6 technology. I will replace my LTO device with LTO9 when is comes available.
While this is no big issue for the tape backup it self, it is for my regular backup process, as it is placed on hold while the tape backup is running.
Are there any guide on how to have Tape Backup copy the files it needs to a temporary location and backup from there, and allow my other backup jobs to run on the main repository?
- Posts: 188
- Liked: 25 times
- Joined: May 21, 2013 9:08 pm
- Full Name: Alan Wells
We have HP servers for storage in our HQ and DR facilities which are FC connected to our SANs and also FC connected to Quantum i80 tape libraries. There are 4 LTO6 drives in each library.
Even before the upgrade it took me quite some time to get all my full backups out to tape. We start doing synthetic full backups on Thursday nights and stagger the jobs through Sunday night.
I have been finding some tape jobs just stuck and running forever without completing. One of them ran over 50 hours this last weekend. Once that happens no other jobs run and everything is stopped.
I just had to kill another job just now as it was just sitting there for 10 hours when it should have completed super fast for the small amount of data it represented. Once I killed it other tape jobs started up.
- Posts: 60
- Liked: 14 times
- Joined: Jun 25, 2015 12:59 am
- Full Name: Rick Boynton
Backing up to tape is very slow, as you know. How can we simply back up existing full and incremental files instead of new ones that come along? We also have backup copy jobs that copy the backup files to our DR site. As you gave the recommendation above to use backup copy jobs as the source; would those also cause the problem where Veeam sees changes in the source backup files as well?
Users browsing this forum: Bing [Bot] and 9 guests