www.mass.dk

Sharing what I know...

  • Increase font size
  • Default font size
  • Decrease font size
Welcome to the Frontpage

Status 196 with open backup windows

Thursday, 25 September 2008 20:42 administrator
Print PDF

 

Yet another issue found in Netbackup 6.5.2. multi streamed backup with frequency set to >50 weeks (exact number not yet found) fails with status code 196 seconds after start-up, even with backup windows still open for hours.

Root cause: Not known.

Workaround: Disable multi streams or lower frequency.

Permanent fix: nbpem version 6 or Netbackup patch 6.5.3

Platform:  Linux only.

 

Last Updated on Sunday, 21 December 2008 17:52
 

Status code 13 during catalog restore in a cluster..

Wednesday, 17 September 2008 14:48 administrator
Print PDF

 

There is a limitation in the code when a catalog restore / recovery is performed on a clustered Netbackup installation. Any recovery of the catalog will exit with a status 13 - "

Failed to recover NBDB on {xyz} (13)”.

Root cause: During catalog restore, data is placed in  /opt/VRTSnbu/db/staging but the recovery process looks in /usr/openv/db/staging.

Workaround: Create symbolic link from /usr/openv/db/staging to /opt/VRTSnbu/db/staging.

Permanent fix: estimated for 6.5.4

Platform: Confirmed for Linux and Solaris.

 

 

Last Updated on Thursday, 02 October 2008 16:28
 

Unable to delete chritical policies in Netbackup.

Friday, 19 September 2008 10:57 administrator
Print PDF

 Deleting critical policies from the Netbackup catalog backup using the java gui (windows or *nix) fails. They seem to have been deleted - but pressing refresh will make them re-appear. The issue have been discover in Netbackup 6.5.2 but may exist in earlier versions.

Root cause: Not known.

Workaround: Use bpadm to delete critical policies.

Permanent fix: EEB for bpplcatdrinfo

Platform:  Linux

Last Updated on Monday, 20 October 2008 14:34
 


Page 5 of 5