No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


Tapes Are not Automatically Replaced after Data Is Backed Up to the VTL3605 by Using the Netbackup

Publication Date:  2012-07-19 Views:  413 Downloads:  0

Issue Description

Backups are properly running in LAN-based mode. When one hard disk is used up, the NetBackup does not automatically replace the hard disk.

Alarm Information


Handling Process

Step 1  Uninstall Microsoft iSCSI-initiator 2.05 and install Microsoft iSCSI-initiator 2.08. Then, restart the backup server.
Step 2  Run Microsoft iSCSI-initiator 2.08 and rebuild an iSCSI link between the backup server and VTL engine.
1. If no link is displayed on the target, click Refresh.
2. Select an existing link and click log on.
3. The NetBackup drive is in the down state and Drive Path is in the MISSING_Path state.
Step 3  Check whether the tape driver on the hardware management is loaded. If no, run the NetBackup installation CD-ROM to reinstall the tape driver
Run \nbu_installpath\netbackup\bin\bpdown.exe and
\nbu_installpath\netbackup\bin\bpup.exe to restart the NetBackup service to normalize the NetBackup drive.
Step 4  When a backup uses up a tape and generates a NetBackup error with error code 84, the tape is frozen and data is not completely written onto the tape. Restart the backup and the NetBackup selects another tape for backup. Then, the data is completely backed up to the tape.
You are advised not to unfreeze the tape that fails backup. Otherwise, the NetBackup considers it a normal tape and may select it for use.
The data backed up before the error code is displayed can be restored. The data backed up when the error code is displayed cannot be restored.

Root Cause

The backup server used at the deployment site is Microsoft iSCSI-initiator 2.05.


Persuade costumers to install Microsoft iSCSI-Initiator 2.08 instead of Microsoft iSCSI-Initiator 2.05 when the VTL3605 is being deployed at the deployment site.