Only Backup-to-disc with Backup-Exec 2014 SP2

[steinmannr]

Hi,

we are running Backup Exec 2014 SP2 on a Windows 2008 R2 SP1 Server. On this server 2 backup-systems are running. One is Backup Exec and the other one is Data Protection Manager 2010 (DPM). The DPM is doing synchronisations and restore points during the week and ALL Backup-to-tape jobs during the weekend. Backup Exec is only used for Backup-to-disc jobs of our Exchange-Server twice a day from Monday till Friday. The tape-device is a HP Autoloader. The loader uses a current HP-driver.

Using Backup Exec 2012 both jobs worked fine. Even after a reboot Backup Exec did not connect to the Autoloader.

After the Update to 2014 after each reboot Backup Exec connects to the Autoloader. For this reason DPM cannot run the backup-to-tape job. DPM shows the Autoloader as offline.

Symantec-Support is not able to find a solution. Their last suggestion was to set the Autoloader to disabled and inactive. But we already tried that and it didn't work. The last workaround was to stop all Backup Exec services, set them to disabled and reboot the server. In this situation DPM could connect to the autoloader and the backup-to-tape jobs ran. Later we had to set the Backup-Exec services to enabled and reboot the server again to run the backup-to-disc jobs during the week.

We need a configuration for Backup exec which ensures that Backup Exec does not search for tape drives even after a reboot of the whole server.

Does anybody here has an idea?

Thanks in advance.

Ruediger

[CraigV]

...running 2 different backup vendor applications on the same server isn't really recommended, basically due to the issue you have. they will fight for hardware resources.

If BE starts up first it's going to grab the tape library and prevent DPM from doing so.

I would recommend putting in a delay to the BE services starting up and see if this allows DPM to start up its services and grab a lock on the library. Set this to 5 or 10 minutes for instance.

Thanks!

[steinmannr]

That's very similar to way we already tried. As long as we don't open Symantec console every thing is fine. The backup exec jobs are working fine and DPM still is connected to autoloader. After opening Symantec console connection between DPM and autoloader is lost.

Thanks for your help but it seems that this software is not able to keep hands off the autoloader.

[CraigV]

...try disabling the device within BE itself.

Thanks!

[steinmannr]

We already tried that. Symantec still blocks DPM from connecting to autoloader. Only when device is deleted in Symantec, DPM can connect. But after next reboot it the same problem.

[CraigV]

...only 2 choices here then:

1. Log a call with Symantec to see if there is a way to block BE from accessing the library;

2. Choose 1 of the applications to do all the work instead of having 2.

Thanks!

[steinmannr]

Already had a call with Symantec. They don't have a solution to stop Backup Exec from accessing the autoloader.

We cannot stop using DPM cause of the catalogues we need for possible restores.

We will test a competitive product for BackupExec.

Thanks for your support.

[steinmannr]

Does anybody has instructions for uninstall Backup Exec 2014? I'm justing reading lots of discussions on symantec.com about uninstalling Backup Exec 2010 or 2012. Some of them had to uninstall manually.

Thanks in advance

[CraigV]

...there used to ba a manual uninstallation document, but this was removed. If you find the steps, you do so at your own risk.

You need to contact Symantec when it comes to manually uninstalling BE. Otherwise Add/Remove Programs is the only other way.

Thanks!

[maurijo]

Just move DPM to another server and keep it for restore purposes until the retention of the data is past. Start using backup exec for all your backup needs. (Or move backup exec since that is easier in your situation)

Having both programs on one server is asking for issues...

[steinmannr]

We decided to install an additional virtuel Server and install backup exec there to continue our backup. The current backup exec 2014 installation will than be uninstalled and version 2012 we be installed again. We hope that will work ;-))

We think the case can be closed now cause there seems to be no solution from symantec.

Thanks for your support.

[pkh]

Accessing a tape drive from a virtual media server is not supported

[steinmannr · Accepted solution]

Once again.

WE DON'T WANT TO WRITE DATA ON A TAPE DRIVE WITH SYMANTEC SOFTWARE.

We are using now an additional virtual server and it is working.

[CraigV]

...not sure why shouting with CAPS, but you sorted it out which is good.

Thanks!