How to share a tape library between two backup solutions?

[zoltank]

I have both Veeam and Symantec Backup Exec installed on the same server. Backup Exec runs the tape library, backs up the few physical servers we have, and writes Veeam backups to tape to send off site. However, since I installed Veeam v.7 it keeps loading its own tape drivers, which are then conflicting with the Backup Exec drivers and keeping Backup Exec from working. Even when I delete the tape library from Veeam it just adds it back again. Could someone please tell me how I can prevent Veeam from ever even trying to load drivers for the tape library?

I've already opened case #00438411.

[zoltank]

Or, if Veeam is not installing drivers, then prevent it from looking for and trying to access tape devices.

[foggy]

There's no way to stop Veeam B&R to autodetect and lock tape devices other than stopping its services. Do you have an ability to install v7 on another server to avoid these conflicts?

[zoltank]

So Veeam locks the tape device as well?

As much as it sucks, it looks like I'll need to downgrade Veeam to keep this from happening.

[foggy]

I've just talked to R&D and there's actually a way to prevent this, at least partially. By default, Veeam B&R performs tape devices rescan each 30 seconds, which makes it temporarily (for the duration of the rescan operation) lock the device. You can increase the rescan interval by setting it to extremely high value so that rescan never occur after Veeam B&R is started (so basically rescan will be performed on each Veeam B&R service start only, allowing you to successfully use BE the rest of the time).

The interval can be set via the following registry key (value in seconds):

Code: Select all

ChangerElementFillCompletionTimeoutSec
DWORD

[zoltank]

That sounds like it would work pretty well. Would you please tell me where the registry key is supposed to go?

[foggy]

It's in the standard HKLM\SOFTWARE\VeeaM\Veeam Backup and Replication hive. And don't forget to restart the backup service after creating the key.

[zoltank]

So far this seems to be doing the trick.

[foggy]

Glad to hear, thanks for confirming. Probably the next version will allow to disable the rescan operation completely.

[zoltank]

So far this change is working very well. I'll check back again in 10 days.

[zoltank]

Still working well without issue.

[zoltank]

Just checking back in one more time. The fix is still working really well, and I consider this problem resolved.

[namiko78]

I am also having this issue. Is it possible to address this in a patch, so it can be fully disabled?
Thanks

[Dima P.]

Steven,

Have you tried to modify the registry key as it was mentioned before?

[namiko78]

Yes, but veeam still tries to access the tape drive on startup, which messes up symantec and causes the jobs to lock up. It would be better if i could simply disable.

[veremin]

Hi, Steven. I'm wondering whether you restarted the corresponding service one the said key was implemented. Thanks.

[namiko78]

I did. Just starting the service is enough to cause the symantec jobs to lock up.

[foggy]

There will be a registry key available in patch 2 that will disable the rescan operation completely.

[namiko78]

Great. Any ETA on that?

[foggy]

November, according to the latest Anton's estimate.

[namiko78]

just to confirm i have this registry entry correct, it needs to go under:
HKEY_LOCAL_MACHINE\SOFTWARE\VeeaM\Veeam Backup and Replication
DWORD ChangerElementFillCompletionTimeoutSec
and the maximum value, in decimal

that right?

Thanks

[foggy]

Correct. AFAIK, the maximum you could set is 2 to the power of 32, should be enough.

[namiko78]

This fix isn't working for me. Symantec jobs hang randomely, it's as if veeam is still scanning. I'm thinking the easiest thing now would be to move veeam to a VM, and install the repository agent on my physical server (where symantec lives) but i'm wondering if the repo agent will also scan for tapes? Do you know?

Maybe i should open a ticket, because i have questions on how to move the catalogue, and restore the jobs themselves. I know there is a config backup that veeam does.

[veremin]

No, it won’t. Only devices that are connected to backup management server are scanned and recognized by VB&R. Thanks.

[foggy]

Maybe i should open a ticket, because i have questions on how to move the catalogue, and restore the jobs themselves. I know there is a config backup that veeam does.

Yes, you can utilize backup configuration functionality to move your Veeam B&R server to another machine.

[veremin]

This fix isn't working for me.

Under certain circumstances the said regkey doesn’t solve the issue. As mentioned above, the current behavior should be fixed in the patch#2. Thanks.

[namiko78]

I've moved it to a VM and it's working normally now.

[foggy]

Glad you've worked around that limitation, without the need to downgrade.

[namiko78]

One great thing about v7, our 60+ production server backup went from almost 6 hrs to 1.5 hrs. lovin' the parallel processing.

[Titou]

Hello
I have Backup Exec associated with an HP Autoloader and also Veeam for Backup on hard disk on the same server.
When Veeam 7 was available, I'm saying it was the opportunity to replace some of jobs Backup Exec on tape by jobs Veeam on Tape.
I did some tests and the results are not good : I have to play with services of Backup Exec when I have to do some operations on tape with Veeam : that's ok.
The backup jobs on tape seems to be ok but when I want to restore, I have error message.
Someone said me : no Backup Exec and Veeam on the same server if you want to to backup/restore on tape.
Who knows please ?
Thanks
Titou