Backup exec job stuck at 0 bytes

[gmoolenaar]

Hi,

I need some help.  We are using v10d of backup exec and we have one system where we cannot start the backup.

The backup are set to write to Backup-to-Disk Folders on an internal drive

If we submit the job, it seems to create the backupfile and then stalls.  We have deselected the prescan function and still the backup sits on 0 bytes.  We also cannot cancel this job, which kill the backup processes.

If I ran a test run of the backup job, it reports it fails with error code:

Final error: 0xe0008703 - Job failed running its test run. See logfile for details.

just Errorcode -536836349

I have tried:

1. reformatting the backup drive.
2. backup up the data to another drive on the same system
3. reinstalling the package
4. removing all registry keys prior to the reinstallation
5. backing up a single file
6. dropping and recreating the database

Figured it may have been a fault with the configuration however, a catalog/inventory/erase of the backup file works ok (even thou its only 2KB)

Any help would be much appreciated.  Thanks in advance.

[AmolB]

What version of OS or what kind of data you are trying to backup?

Do you see any unattended alerts in the BE console?

The backup in question has it ever worked in past?

[CraigV]

...have you turned on Advanced Open File Option and retried the backup?

Any AV perhaps scanning the BE services on the server in question? If so, put in an exclusion for them (beremote.exe if a remote server)...

Thanks!

[VJware]

Try creating a new backup job and ensure the "Test run" option is deselected.

As you are backing up to a disk, set the backup to overwrite and not append.
 

[gmoolenaar]

Hi guys, thanks for the responses

Its a windows 2003 server and the backup had been working successfully for years.  We also have 700+ servers with the exactly the same configuration and have never had this issue before(and not been able to resolve it).

The server is basically a F&P with a couple of applications running on the server.

If I create a new backup.  The job stays in the prescan mode.  If i disable "Display progress indicators for backup jobs" then its load the B2D file and stays on 0 bytes, until the job eventually times out.  Even if i create a new job trying to backup a single file only.

Our 2nd level team who were working on the issue prior to us, have replaced the B2D disk and I can see no errors in the RAID logs.

The media is set to overwrite, i have also retired all media to ensure a new file is created

Gary

[Laurie_Downey]

I would advise checking the event viewer by expanding Windows Logs and highlighting “Application” and also checking “System” events for a better idea of what might be occurring. You also might want to confirm there is not any anti-virus or a firewall blocking the connection to the remote server.

Have you considered upgrading your version of Backup Exec? The 10d version has already reached its EOL, and the BE 2014 is a much more stable version. If you are considering an upgrade please review the product compatibility, to ensure your environment meets any requirements prior to starting the upgrade process.

Backup Exec 2014 - where to find manuals, videos and compatibility information: http://www.symantec.com/docs/TECH216587

Backup Exec 2014: Step By Step guide to download and install the program: http://www.symantec.com/docs/TECH218012  

Backup Exec 2014 Software Compatibility List: http://www.symantec.com/docs/TECH217478

Backup Exec 2014 Hardware Compatibility List: http://www.symantec.com/docs/TECH214803

Backup Exec Product EOL Dates: http://www.symantec.com/business/support/index?page=releasedetails&key=15047#

[gmoolenaar]

Thanks for the information, however management have not indicated they are prepared to upgrade at this stage.

There is also nothing in the event logs relating to why the backupexec has not actually started to backup files.

[maurijo]

I never used this old version of BE but if there is SGmon then I would run that during the job and check the logs. If you don't have any error to go on this will be hard to fix.

[Laurie_Downey]

I would also advise what VJware has already recommended for you earlier in the thread:

"Try creating a new backup job and ensure the "Test run" option is deselected"