How to troubleshoot NetBackup 7.1 duplication to remote master feature?

Article:HOWTO42477  |  Created: 2011-02-26  |  Updated: 2011-02-26  |  Article URL http://www.symantec.com/docs/HOWTO42477
Article Type
How To



This document provides a list of debug logs and commands useful while troubleshooting duplication to master feature. Duplication to remote master feature is also known as automatic image replication.

Debug logs at the source domain

Unless otherwise specified, the debug logs are located in the following directory
 
/usr/openv/netbackup/logs/<log_dir_name> on UNIX/Linux hosts
Install_Path\Veritas\Netbackup\logs\<log_dir_name>  on Windows hosts

Enterprise Media Manager server(usually the master server)
 
log_dir_name = nbemm: Components logged that are relevant to duplication to remote master are  DSM, nbemm, DAL. These components show the activities on the Storage Lifecycle Policy (SLP) work list and disk volume objects
 
Master server
 
log_dir_name = admin: This will show the nbreplicate jobs for duplication to remote master
log_dir_name = nbstserv: Duplication Manager (OID 226) shows SLP workflow for replication
log_dir_name = bpdbm: This log shows catalog activity for images
 
Media server
 
log_dir_name = bpdm: This log shows replication control job
log_dir_name = bptm: This log shows image copy and fragment creation
 
 
Debug logs at the target domain
 
Enterprise Media Manager server(usually the master server)
 
log_dir_name = nbemm: Components logged that are relevant to duplication to remote master are  DSM, nbemm, REM, DAL. These components show the activities on the Storage Lifecycle Policy (SLP) work list and disk volume objects
 
Master server
 
log_dir_name = admin: This will show the bpimport jobs for replication
log_dir_name = nbstserv: Import Manager (OID 369) shows SLP workflow for replication
log_dir_name = bpdbm: This log shows catalog activity for images
 
Media server
 
log_dir_name = bpdm: This log shows import
log_dir_name = nbrmms: This log shows the storage server replication events
 
 
Commands for debugging
 
The nbstlutil command line utility is enhanced to report on various copy types. The copy type for duplicate to remote master is 'replica'. The replica copies have no fragments as they are considered virtual copies in source domain. You cannot restore from such copies at the source domain. Similarly the copy type of 'import' represents images imported at the target site.
 
nbstlutil list –copy_type backup|duplicate|snapshot|replica|import]
 
 
The repllist subcommand lists all the replica destination records
 
nbstlutil repllist […]
 
The pendimplist subcommand lists all images in the pending import state. This means that a replication event was received but the import has not successfully imported yet. NetBackup target domain will not import anything with a backup time in the future. It stays pending until the backup time has passed. This is to account for situations where master server clocks are at different time zones.
 
nbstlutil pendimplist […]
 
 
nbemmcmd uses remote_master as a new host type to associate replication target with a remote master
 
 nbemmcmd -addhost [...] -machinetype remote_master  
 
 
Import status codes from bpdm
 
 
Automatic import jobs at the target domain either succeed with status 0 or fail with status 191. In case of status 191, detailed job status will have more clues. The following new error codes from bpdm propagated detailed job status will indicate a configuration errors related to duplication to remote master feature.
 
Status 1532: Import failed because the imported image specifies an SLP name which does not exist
Status 1533: Import failed because the imported image data class is different than the SLP data class
Status 1534: Import failed because the imported image specifies an SLP name with no Import destination
Status 1535: Import failed because the imported image backup id conflicts with an existing image
 
NetBackup Problems Report
NetBackup Problems report on target domain provides useful information regarding automatic image import failures. The problems report can also be generated from bperror command line.  


Article URL http://www.symantec.com/docs/HOWTO42477


Terms of use for this information are found in Legal Notices