When running a backup with Veritas System Recovery (VSR) the machine hangs immediately after backup starts
Article ID: 100019785
Updated On:
Resolution
A hang may occur when running backups for several different reasons such as low disk space, disk fragmentation, disk errors, backup of non-vss aware database applications, or backup destination. Hangs typically occur during the first 5% of the backup during the snapshot phase.
Perform the following steps to troubleshoot a hang:
1) Verify there is free space available on the backup destination and the machine being backed up. The lack of contiguous free space on the disk interferes with Backup Exec System Recovery's ability to maintain the snapshot. Defragment the drive(s) and then rerun the backup.
2) If backing up multiple drives, run backup of each drive independently to isolate if one drive is causing the issue.
3) A common test to verify drive issues exist is to run a backup choosing the advanced option to "Ignore Bad Sectors During Copy". If the backup completes successfully, then there are potential hardware issues which usually are resolved by running CHKDSK /r /f.
Perform the following steps to run CHKDSK:
a) Goto Start / Run and type CMD to open a command prompt window.
b) At the command prompt type CHKDSK /r /f
Note - CHKDSK cannot lock the current drives while Windows is running
c) Answer Y to schedule the process to run on the next reboot
d) After the CHKDSK had finished, reboot into Windows and rerun the backup in Veritas System Recovery.
Note: Selecting "Ignore bad sectors during copy" will bypass any sectors on the disk that contain errors that may cause the job to hang. While most drives do not have bad sectors, the potential for such problems increases over the lifetime of the hard disk. This is not a workaround and drive errors should be addressed.
4) If backing up non Volume Shadow Copy Service (VSS) compliant database applications, services must be stopped in order for snapshot to occur. Backup Exec System Recovery uses the VSS framework to quiesce a database. Batch files can be implemented in the backup job to stop and start these services.
Note - Microsoft SQL versions prior to 2005, Oracle, and Sybase are not VSS-aware.
5) Perform a Clean Boot .
Run MSCONFIG.EXE
-Services TAB: Check box 'Hide ALL Microsoft Services'. Then select: 'Disable All' for all services.
-Startup TAB: Select 'Disable All' for all startup applications.
6) Reboot and rerun the backup. If successful, 3rd party application is conflicting with the backup.
7) Verify the backup destination is online and has adequate disk space to store the recovery points.
Issue/Introduction
When running a backup with Veritas System Recovery (VSR) the machine hangs immediately after backup starts
Was this article helpful?
Yes
No
Powered by
