Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Catalog Backup - unsuccessful

Created: 19 Dec 2012 • Updated: 22 Dec 2012 | 22 comments
jawad_butt's picture
This issue has been solved. See solution.

Hey all, I need help with doing a backup of the catalog and not sure where the problem is. There is no where that I can look at (or know) that would tell me what to do to fix it.

I have NBU 7.5 on Windows 2008 R2. Running a Master and a separate Media server. I can run full successful backups of file system jobs without problems but when i try to run the backup job for Catalog, it fails with error: none of the requested files were backed up(2). I have rebooted the server and created the policy a few times. I am trying to backup the catalog to C:\BackupDirectory (Disaster Recovery) with domain credentials but it doesnt seem to work.

 

I am also attaching the dpdbm log that (i dont think) really gives much info that i can go off of. This is all that i can see that says error.
 

excerpt:
15:43:04.391 [3524.3380] <4> bsa_comm_w_bkar: Wait for bkar END file / BEGIN file message.
15:43:07.495 [3524.2880] <16> serverResponse: ERR - server exited with status 25: cannot connect on socket
15:43:07.495 [3524.2880] <16> CreateNewImage: ERR - serverResponse() failed
15:43:08.447 [3524.3380] <16> bsa_a_backup_completed: ERR - thread <2880> backup failed: 25 <cannot connect on socket>
15:43:09.461 [3524.3380] <4> ASA_XBSA_file_backup: All backup jobs have failed.
15:43:09.461 [3524.3380] <16> do_online_nbdb_backup: Error backing up files in C:\Program Files\Veritas\NetBackupDB\staging
15:43:09.461 [3524.3380] <4> do_online_nbdb_backup: Setting NB-Full keyword in vxdbms.conf
15:43:09.461 [3524.3380] <4> do_online_nbdb_backup: Setting empty backup policy and schedule in vxdbms.conf
 

 

Full Error Log:
Lines 96 - 99
15:41:29.012 [3524.3380] <2> logconnections: BPDBM ACCEPT FROM 192.168.231.70.50251 TO 192.168.231.70.13721 fd = 568
15:41:29.012 [3524.3380] <2> bpdbm: VERBOSE = 0
15:41:29.012 [3524.3380] <8> vnet_check_vxss_server_magic: [vnet_vxss_helper.c:495] VxSS magic 1041669 0xfe505
15:41:29.028 [3524.3380] <8> vnet_check_vxss_server_magic: [vnet_vxss_helper.c:496] remote_vxss 160 0xa0
15:41:29.028 [3524.3380] <8> vnet_check_vxss_server_magic: [vnet_vxss_helper.c:538] Ignoring VxSS authentication 2 0x2
15:41:29.028 [3524.3380] <2> image_db: Q_IMAGE_CATALOG_BACKUP
15:41:29.028 [3524.3380] <2> ReadVxDBMS_ConfFile: Acquiring mutex
15:41:29.028 [3524.3380] <2> ReadVxDBMS_ConfFile: Acquiring read lock on C:\Program Files\Veritas\NetBackupDB\data\vxdbms_conf.lock
15:41:29.028 [3524.3380] <2> ReadVxDBMS_ConfFile: Acquired read lock on C:\Program Files\Veritas\NetBackupDB\data\vxdbms_conf.lock successfully with fd (464)
15:41:29.028 [3524.3380] <2> ReadVxDBMS_ConfFile: unlocking on fd (464) for C:\Program Files\Veritas\NetBackupDB\data\vxdbms_conf.lock
15:41:29.028 [3524.3380] <2> ReadVxDBMS_ConfFile: Releasing mutex
15:41:29.231 [3524.3380] <4> do_online_nbdb_backup: VXDBMS_NBDB_BACKUP_OWNER = YES - ASA online backup is included
15:41:29.231 [3524.3380] <2> ReadVxDBMS_ConfFile: Acquiring mutex
15:41:29.246 [3524.3380] <2> ReadVxDBMS_ConfFile: Acquiring read lock on C:\Program Files\Veritas\NetBackupDB\data\vxdbms_conf.lock
15:41:29.246 [3524.3380] <2> ReadVxDBMS_ConfFile: Acquired read lock on C:\Program Files\Veritas\NetBackupDB\data\vxdbms_conf.lock successfully with fd (568)
15:41:29.246 [3524.3380] <2> ReadVxDBMS_ConfFile: unlocking on fd (568) for C:\Program Files\Veritas\NetBackupDB\data\vxdbms_conf.lock
15:41:29.246 [3524.3380] <2> ReadVxDBMS_ConfFile: Releasing mutex
15:41:29.246 [3524.3380] <2> ReadVxDBMS_ConfFile: Acquiring mutex
15:41:29.246 [3524.3380] <2> ReadVxDBMS_ConfFile: Acquiring read lock on C:\Program Files\Veritas\NetBackupDB\data\vxdbms_conf.lock
15:41:29.246 [3524.3380] <2> ReadVxDBMS_ConfFile: Acquired read lock on C:\Program Files\Veritas\NetBackupDB\data\vxdbms_conf.lock successfully with fd (568)
15:41:29.246 [3524.3380] <2> ReadVxDBMS_ConfFile: unlocking on fd (568) for C:\Program Files\Veritas\NetBackupDB\data\vxdbms_conf.lock
15:41:29.246 [3524.3380] <2> ReadVxDBMS_ConfFile: Releasing mutex
15:41:29.246 [3524.3380] <2> ReadVxDBMS_ConfFile: Acquiring mutex
15:41:29.246 [3524.3380] <2> ReadVxDBMS_ConfFile: Acquiring read lock on C:\Program Files\Veritas\NetBackupDB\data\vxdbms_conf.lock
15:41:29.246 [3524.3380] <2> ReadVxDBMS_ConfFile: Acquired read lock on C:\Program Files\Veritas\NetBackupDB\data\vxdbms_conf.lock successfully with fd (568)
15:41:29.246 [3524.3380] <2> ReadVxDBMS_ConfFile: unlocking on fd (568) for C:\Program Files\Veritas\NetBackupDB\data\vxdbms_conf.lock
15:41:29.246 [3524.3380] <2> ReadVxDBMS_ConfFile: Releasing mutex
15:41:29.246 [3524.3380] <2> ReadVxDBMS_ConfFile: Acquiring mutex
15:41:29.246 [3524.3380] <2> ReadVxDBMS_ConfFile: Acquiring read lock on C:\Program Files\Veritas\NetBackupDB\data\vxdbms_conf.lock
15:41:29.246 [3524.3380] <2> ReadVxDBMS_ConfFile: Acquired read lock on C:\Program Files\Veritas\NetBackupDB\data\vxdbms_conf.lock successfully with fd (568)
15:41:29.246 [3524.3380] <2> ReadVxDBMS_ConfFile: unlocking on fd (568) for C:\Program Files\Veritas\NetBackupDB\data\vxdbms_conf.lock
15:41:29.246 [3524.3380] <2> ReadVxDBMS_ConfFile: Releasing mutex
15:41:29.262 [3524.3380] <2> ReadVxDBMS_ConfFile: Acquiring mutex
15:41:29.262 [3524.3380] <2> ReadVxDBMS_ConfFile: Acquiring read lock on C:\Program Files\Veritas\NetBackupDB\data\vxdbms_conf.lock
15:41:29.262 [3524.3380] <2> ReadVxDBMS_ConfFile: Acquired read lock on C:\Program Files\Veritas\NetBackupDB\data\vxdbms_conf.lock successfully with fd (568)
15:41:29.262 [3524.3380] <2> ReadVxDBMS_ConfFile: unlocking on fd (568) for C:\Program Files\Veritas\NetBackupDB\data\vxdbms_conf.lock
15:41:29.262 [3524.3380] <2> ReadVxDBMS_ConfFile: Releasing mutex
15:41:29.262 [3524.3380] <4> empty_staging_dir: Emptying staging directory:  C:\Program Files\Veritas\NetBackupDB\staging
15:41:29.293 [3524.3380] <4> open_terminate_event: Created terminate event:"Global\NetBackup Terminate Event, pid: 3524"
15:41:29.309 [3524.3380] <2> job_connect: SO_KEEPALIVE set on socket 588 for client nbmaster.contoso.com
15:41:29.309 [3524.3380] <2> logconnections: BPJOBD CONNECT FROM 192.168.231.70.50252 TO 192.168.231.70.13723 fd = 588
15:41:29.309 [3524.3380] <2> job_authenticate_connection: ignoring VxSS authentication check for now...
15:41:29.324 [3524.3380] <2> job_connect: Connected to the host nbmaster.contoso.com contype 53 jobid <0> socket <588>
15:41:29.324 [3524.3380] <2> job_connect: Connected on port 50252
15:41:29.340 [3524.3380] <4> startStagingJob: staging relational database files for catalog backup
15:41:29.340 [3524.3380] <4> do_online_nbdb_backup: staging NBAZDB backup to C:\Program Files\Veritas\NetBackupDB\staging
15:41:29.434 [3524.3380] <4> backup_dbspaces: Executing:  backup database directory 'C:\Program Files\Veritas\NetBackupDB\staging' wait before start with checkpoint log no copy transaction log truncate;
15:41:30.682 [3524.3380] <4> do_online_nbdb_backup: done staging NBAZDB backup to C:\Program Files\Veritas\NetBackupDB\staging
15:41:30.682 [3524.3380] <4> do_online_nbdb_backup: Online backup of NBAZDB successful
15:41:30.682 [3524.3380] <4> do_online_nbdb_backup: Server nbmaster.contoso.com, Policy HotBackup, Schedule Full, parentJobID 140
15:41:30.682 [3524.3380] <4> do_online_nbdb_backup: staging NBDB backup to C:\Program Files\Veritas\NetBackupDB\staging
15:41:30.728 [3524.3380] <4> backup_dbspaces: Executing:  backup database directory 'C:\Program Files\Veritas\NetBackupDB\staging' wait before start with checkpoint log no copy transaction log truncate;
15:42:03.754 [3524.3380] <4> do_online_nbdb_backup: done staging NBDB backup to C:\Program Files\Veritas\NetBackupDB\staging
15:42:03.754 [3524.3380] <4> do_online_nbdb_backup: Backup checkpoint at Wed Dec 19 15:42:03 2012
15:42:03.754 [3524.3380] <4> do_online_nbdb_backup: Online backup of NBDB successful at Wed Dec 19 15:42:03 2012
15:42:03.754 [3524.3380] <4> do_online_nbdb_backup: Server nbmaster.contoso.com, Policy HotBackup, Schedule Full, parentJobID 140
15:42:03.754 [3524.3380] <4> do_online_nbdb_backup: Setting backup policy:HotBackup and schedule type:0, in vxdbms.conf file.
15:42:03.754 [3524.3380] <4> SaveVxDBMS_Conf: Entering
15:42:03.754 [3524.3380] <2> SaveVxDBMS_Conf: Acquiring mutex
15:42:03.754 [3524.3380] <2> SaveVxDBMS_Conf: Acquiring write lock on C:\Program Files\Veritas\NetBackupDB\data\vxdbms_conf.lock
15:42:03.754 [3524.3380] <2> SaveVxDBMS_Conf: Acquired write lock on C:\Program Files\Veritas\NetBackupDB\data\vxdbms_conf.lock successfully with fd (616)
15:42:03.754 [3524.3380] <2> SaveVxDBMS_Conf: unlocking on fd (616) for C:\Program Files\Veritas\NetBackupDB\data\vxdbms_conf.lock
15:42:03.754 [3524.3380] <2> SaveVxDBMS_Conf: Releasing mutex
15:42:03.769 [3524.3380] <4> do_online_nbdb_backup: Backing up 16 database files
15:42:03.769 [3524.3380] <4> do_online_nbdb_backup: File 0:  C:\Program Files\Veritas\NetBackupDB\staging\DARS_DATA.db
15:42:03.769 [3524.3380] <4> do_online_nbdb_backup: File 1:  C:\Program Files\Veritas\NetBackupDB\staging\DARS_INDEX.db
15:42:03.769 [3524.3380] <4> do_online_nbdb_backup: File 2:  C:\Program Files\Veritas\NetBackupDB\staging\DBM_DATA.db
15:42:03.769 [3524.3380] <4> do_online_nbdb_backup: File 3:  C:\Program Files\Veritas\NetBackupDB\staging\DBM_INDEX.db
15:42:03.769 [3524.3380] <4> do_online_nbdb_backup: File 4:  C:\Program Files\Veritas\NetBackupDB\staging\EMM_DATA.db
15:42:03.769 [3524.3380] <4> do_online_nbdb_backup: File 5:  C:\Program Files\Veritas\NetBackupDB\staging\EMM_INDEX.db
15:42:03.769 [3524.3380] <4> do_online_nbdb_backup: File 6:  C:\Program Files\Veritas\NetBackupDB\staging\JOBD_DATA.db
15:42:03.769 [3524.3380] <4> do_online_nbdb_backup: File 7:  C:\Program Files\Veritas\NetBackupDB\staging\NBAZDB.db
15:42:03.769 [3524.3380] <4> do_online_nbdb_backup: File 8:  C:\Program Files\Veritas\NetBackupDB\staging\NBAZDB.log.1
15:42:03.769 [3524.3380] <4> do_online_nbdb_backup: File 9:  C:\Program Files\Veritas\NetBackupDB\staging\NBDB.db
15:42:03.769 [3524.3380] <4> do_online_nbdb_backup: File 10:  C:\Program Files\Veritas\NetBackupDB\staging\NBDB.log.1
15:42:03.785 [3524.3380] <4> do_online_nbdb_backup: File 11:  C:\Program Files\Veritas\NetBackupDB\staging\SEARCH_DATA.db
15:42:03.785 [3524.3380] <4> do_online_nbdb_backup: File 12:  C:\Program Files\Veritas\NetBackupDB\staging\SEARCH_INDEX.db
15:42:03.785 [3524.3380] <4> do_online_nbdb_backup: File 13:  C:\Program Files\Veritas\NetBackupDB\staging\databases.conf
15:42:03.785 [3524.3380] <4> do_online_nbdb_backup: File 14:  C:\Program Files\Veritas\NetBackupDB\staging\server.conf
15:42:03.785 [3524.3380] <4> do_online_nbdb_backup: File 15:  C:\Program Files\Veritas\NetBackupDB\staging\vxdbms.conf
15:42:03.785 [3524.3380] <4> do_online_nbdb_backup: DOING_HOT_CATALOG_BACKUP is: YES
15:42:03.800 [3524.3380] <2> logconnections: BPRD CONNECT FROM 192.168.231.70.50253 TO 192.168.231.70.13720 fd = 624
15:42:03.800 [3524.3380] <8> vnet_check_vxss_client_magic_with_info: [vnet_vxss_helper.c:871] Ignoring VxSS authentication 2 0x2
15:42:04.112 [3524.3380] <2> logconnections: BPRD CONNECT FROM 192.168.231.70.50254 TO 192.168.231.70.13720 fd = 624
15:42:04.112 [3524.3380] <8> vnet_check_vxss_client_magic_with_info: [vnet_vxss_helper.c:871] Ignoring VxSS authentication 2 0x2
15:42:04.612 [3524.2880] <2> logconnections: BPRD CONNECT FROM 192.168.231.70.50255 TO 192.168.231.70.13720 fd = 632
15:42:04.612 [3524.2880] <8> vnet_check_vxss_client_magic_with_info: [vnet_vxss_helper.c:871] Ignoring VxSS authentication 2 0x2
15:42:05.314 [3484.3832] <2> logconnections: BPDBM ACCEPT FROM 192.168.231.70.50256 TO 192.168.231.70.13721 fd = 476
15:42:05.329 [3484.3832] <2> bpdbm: VERBOSE = 0
15:42:05.329 [3484.3832] <8> vnet_check_vxss_server_magic: [vnet_vxss_helper.c:495] VxSS magic 1041669 0xfe505
15:42:05.329 [3484.3832] <8> vnet_check_vxss_server_magic: [vnet_vxss_helper.c:496] remote_vxss 84 0x54
15:42:05.329 [3484.3832] <8> vnet_check_vxss_server_magic: [vnet_vxss_helper.c:538] Ignoring VxSS authentication 2 0x2
15:42:05.329 [3484.3832] <2> image_db: Q_IMAGE_GET_CCNAME
15:42:05.360 [3484.3832] <2> LOCAL CLASS_ATT_DEFS: Product ID = 6
15:43:04.391 [3524.3380] <4> bsa_comm_w_bkar: Wait for bkar END file / BEGIN file message.
15:43:07.495 [3524.2880] <16> serverResponse: ERR - server exited with status 25: cannot connect on socket
15:43:07.495 [3524.2880] <16> CreateNewImage: ERR - serverResponse() failed
15:43:08.447 [3524.3380] <16> bsa_a_backup_completed: ERR - thread <2880> backup failed: 25 <cannot connect on socket>
15:43:09.461 [3524.3380] <4> ASA_XBSA_file_backup: All backup jobs have failed.
15:43:09.461 [3524.3380] <16> do_online_nbdb_backup: Error backing up files in C:\Program Files\Veritas\NetBackupDB\staging
15:43:09.461 [3524.3380] <4> do_online_nbdb_backup: Setting NB-Full keyword in vxdbms.conf
15:43:09.461 [3524.3380] <4> do_online_nbdb_backup: Setting empty backup policy and schedule in vxdbms.conf
15:43:09.461 [3524.3380] <4> SaveVxDBMS_Conf: Entering
15:43:09.461 [3524.3380] <2> SaveVxDBMS_Conf: Acquiring mutex
15:43:09.461 [3524.3380] <2> SaveVxDBMS_Conf: Acquiring write lock on C:\Program Files\Veritas\NetBackupDB\data\vxdbms_conf.lock
15:43:09.461 [3524.3380] <2> SaveVxDBMS_Conf: Acquired write lock on C:\Program Files\Veritas\NetBackupDB\data\vxdbms_conf.lock successfully with fd (616)
15:43:09.461 [3524.3380] <2> SaveVxDBMS_Conf: unlocking on fd (616) for C:\Program Files\Veritas\NetBackupDB\data\vxdbms_conf.lock
15:43:09.461 [3524.3380] <2> SaveVxDBMS_Conf: Releasing mutex
15:43:09.492 [3524.3380] <2> job_monitoring_exex: ACK disconnect
15:43:09.492 [3524.3380] <2> job_disconnect: Disconnected
15:43:09.492 [3524.3380] <2> ReadVxDBMS_ConfFile: Acquiring mutex
15:43:09.492 [3524.3380] <2> ReadVxDBMS_ConfFile: Acquiring read lock on C:\Program Files\Veritas\NetBackupDB\data\vxdbms_conf.lock
15:43:09.492 [3524.3380] <2> ReadVxDBMS_ConfFile: Acquired read lock on C:\Program Files\Veritas\NetBackupDB\data\vxdbms_conf.lock successfully with fd (588)
15:43:09.492 [3524.3380] <2> ReadVxDBMS_ConfFile: unlocking on fd (588) for C:\Program Files\Veritas\NetBackupDB\data\vxdbms_conf.lock
15:43:09.492 [3524.3380] <2> ReadVxDBMS_ConfFile: Releasing mutex
15:43:09.492 [3524.3380] <4> GetServerCacheSettings: Entering.
15:43:09.492 [3524.3380] <4> GetServerCacheSettings: Exiting with rc = 0
15:43:09.492 [3524.3380] <4> apply_tlog: Executing C:\Program Files\Veritas\NetBackupDB\Win64\dbsrv11 -qs -qw  "C:\Program Files\Veritas\NetBackupDB\staging\NBAZDB.db" -ds "C:\Program Files\Veritas\NetBackupDB\staging" -a "C:\Program Files\Veritas\NetBackupDB\staging\NBAZDB.log.1" -c 100M -ch 1024M -cl 100M
15:43:11.192 [3524.3380] <4> NBDBsystem: Command exited with status: 0
15:43:11.192 [3524.3380] <4> apply_tlog: Deleted log C:\Program Files\Veritas\NetBackupDB\staging\NBAZDB.log.1
15:43:11.192 [3524.3380] <2> ReadVxDBMS_ConfFile: Acquiring mutex
15:43:11.192 [3524.3380] <2> ReadVxDBMS_ConfFile: Acquiring read lock on C:\Program Files\Veritas\NetBackupDB\data\vxdbms_conf.lock
15:43:11.192 [3524.3380] <2> ReadVxDBMS_ConfFile: Acquired read lock on C:\Program Files\Veritas\NetBackupDB\data\vxdbms_conf.lock successfully with fd (568)
15:43:11.192 [3524.3380] <2> ReadVxDBMS_ConfFile: unlocking on fd (568) for C:\Program Files\Veritas\NetBackupDB\data\vxdbms_conf.lock
15:43:11.192 [3524.3380] <2> ReadVxDBMS_ConfFile: Releasing mutex
15:43:11.192 [3524.3380] <4> GetServerCacheSettings: Entering.
15:43:11.208 [3524.3380] <4> GetServerCacheSettings: Exiting with rc = 0
15:43:11.208 [3524.3380] <4> apply_tlog: Executing C:\Program Files\Veritas\NetBackupDB\Win64\dbsrv11 -qs -qw  "C:\Program Files\Veritas\NetBackupDB\staging\NBDB.db" -ds "C:\Program Files\Veritas\NetBackupDB\staging" -a "C:\Program Files\Veritas\NetBackupDB\staging\NBDB.log.1" -c 100M -ch 1024M -cl 100M
15:43:13.127 [3524.3380] <4> NBDBsystem: Command exited with status: 0
15:43:13.142 [3524.3380] <4> apply_tlog: Deleted log C:\Program Files\Veritas\NetBackupDB\staging\NBDB.log.1
15:43:13.142 [3524.3380] <16> ImageCatalogBackup::executeQuery: exec_asa_database_backup() failed (2)
15:43:13.158 [3524.3380] <4> jmcomm_UpdateActionStatus: Sending status: 2 back to parent JobID: 140
15:43:13.189 [3524.3380] <2> Orb::init: Enabling ORBNativeCharCodeSet UTF-8(Orb.cpp:594)
15:43:13.189 [3524.3380] <2> Orb::init: Created anon service name: NB_3524_1337705567(Orb.cpp:697)
15:43:13.189 [3524.3380] <2> Orb::init: endpointvalue is : pbxiop://1556:NB_3524_1337705567(Orb.cpp:714)
15:43:13.189 [3524.3380] <2> Orb::init: initializing ORB Default_DAEMON_Orb with: Unknown -ORBSvcConfDirective "-ORBDottedDecimalAddresses 0" -ORBSvcConfDirective "static Resource_Factory '-ORBNativeCharCodeSet UTF-8'" -ORBSvcConfDirective "static PBXIOP_Factory '-enable_keepalive'" -ORBSvcConfDirective "static EndpointSelectorFactory ''" -ORBSvcConfDirective "static Resource_Factory '-ORBProtocolFactory PBXIOP_Factory'" -ORBSvcConfDirective "static Resource_Factory '-ORBProtocolFactory IIOP_Factory'" -ORBDefaultInitRef '' -ORBSvcConfDirective "static PBXIOP_Evaluator_Factory '-orb Default_DAEMON_Orb'" -ORBSvcConfDirective "static Resource_Factory '-ORBConnectionCacheMax 1024 '" -ORBEndpoint pbxiop://1556:NB_3524_1337705567 -ORBSvcConf nul -ORBSvcConfDirective "static Server_Strategy_Factory '-ORBMaxRecvGIOPPayloadSize 268435456'"(Orb.cpp:825)
15:43:13.205 [3524.3380] <2> Orb::init: caching EndpointSelectorFactory(Orb.cpp:840)
15:43:13.298 [3524.3380] <2> jmcomm_UpdateActionStatus: returning

 

If you need any other information that would be helpful in getting this issue resolved, i'll be happy to provide. please let me know what you think i can do to get the catalog backups going.

Comments 22 CommentsJump to latest comment

Marianne's picture

Please show us your policy config.

From cmd on master (remember to open with 'Run As Administrator' if UAC is enabled)
cd <install-path>\veritas\netbackup\bin\admincmd
bppllist <policy-name> -U

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

jawad_butt's picture

 Followign is the output...

------------------------------------------------------------

Policy Name:       HotBackup

  Policy Type:         NBU-Catalog
  Active:              yes
  Effective date:      12/19/2012 14:17:34
  Mult. Data Streams:  no
  Client Encrypt:      no
  Checkpoint:          no
  Policy Priority:     0
  Max Jobs/Policy:     1
  Disaster Recovery:   0
  Collect BMR info:    no
  Residence:           (specific storage unit not required)
  Volume Pool:         CatalogBackup
  Server Group:        *ANY*
  Keyword:             (none specified)
  Data Classification:       -
  Residence is Storage Lifecycle Policy:    no
  Application Discovery:      no
  Discovery Lifetime:      0 seconds
ASC Application and attributes: (none defined)

  Granular Restore Info:  no
  Ignore Client Direct:  no
Enable Metadata Indexing:  no
Index server name:  NULL
  Use Accelerator:  no
  HW/OS/Client:  PC-x64        Windows2008   nbmaster.contoso.com

  Include:  CATALOG_DRIVEN_BACKUP

  Schedule:              Full
    Type:                Full Backup
    Frequency:           every 7 days
    Maximum MPX:         1
    Synthetic:           0
    Checksum Change Detection: 0
    PFI Recovery:        0
    Retention Level:     1 (2 weeks)
    Number Copies:       1
    Fail on Error:       0
    Residence:           (specific storage unit not required)
    Volume Pool:         (same as policy volume pool)
    Server Group:        (same as specified for policy)
    Residence is Storage Lifecycle Policy:         0
    Schedule indexing:     0
    Daily Windows:
          Sunday     00:00:00  -->  Sunday     24:00:00
          Monday     00:00:00  -->  Monday     24:00:00
          Tuesday    00:00:00  -->  Tuesday    24:00:00
          Wednesday  00:00:00  -->  Wednesday  24:00:00
          Thursday   00:00:00  -->  Thursday   24:00:00
          Friday     00:00:00  -->  Friday     24:00:00
          Saturday   00:00:00  -->  Saturday   24:00:00

  Schedule:              Differential-Inc
    Type:                Differential Incremental Backup
    Frequency:           every 1 day
    Maximum MPX:         1
    Synthetic:           0
    Checksum Change Detection: 0
    PFI Recovery:        0
    Retention Level:     1 (2 weeks)
    Number Copies:       1
    Fail on Error:       0
    Residence:           (specific storage unit not required)
    Volume Pool:         (same as policy volume pool)
    Server Group:        (same as specified for policy)
    Residence is Storage Lifecycle Policy:         0
    Schedule indexing:     0
    Daily Windows:
          Sunday     00:00:00  -->  Sunday     24:00:00
          Monday     00:00:00  -->  Monday     24:00:00
          Tuesday    00:00:00  -->  Tuesday    24:00:00
          Wednesday  00:00:00  -->  Wednesday  24:00:00
          Thursday   00:00:00  -->  Thursday   24:00:00
          Friday     00:00:00  -->  Friday     24:00:00
          Saturday   00:00:00  -->  Saturday   24:00:00

Catalog Disaster Recovery Configuration:
  Email Address:   (none specified)
  Disk Path:       C:\BackupCatalog
  User Name:       contoso\adminjb
  Pass Word:       xxxx
  Critical policy: (none specified)

 

RonCaplinger's picture

It looks like you are using your master server to back itself up to itself, which I think is the problem.  I think it is using VSS to try to do a snapshot of the drive where the catalog is located (C:), but then it can't write to that drive because it is snapped.

If I'm wrong, please correct me!

If i'm right, why would you store your catalog backup on the root drive of the master server?  If that drive fails, you've lost your catalog AND the backup. Assuming you have space on your media server, back the data up there instead.

jawad_butt's picture

I changed the backups but might have to restart the services. Without restarting the srvices and moving the backup to E: drive, i still am getting the same error.

i'll keep you posted.

Marianne's picture

Your Storage Unit is set to 'Any Avalailable':

 Residence:           (specific storage unit not required)
 Volume Pool:         CatalogBackup

Best to select a specific Storage Unit. If it is a Media Manager SU, ensure that you have tapes available in CatalogBackup or in Scratch pool. The Storage Unit is where the actual backup is written.

Disaster Recovery location is where small DR-file is written with information about Catalog Backup when successful. This DR-file needs to be written to a drive letter other than the one where NBU installation and catalogs reside.

If backup still fails, please let us know how many jobs are generated and show us ALL text in Details tab of all of these jobs.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

jawad_butt's picture

So, I selected a specific Media (Disk SU) and disabled Indexing on the E: drive. Restarted NBU services (BPDOWN/BPUP) and then tried the Catalog Backup again..same result (error 2). Following is what i see in the job:

12/19/2012 10:44:04 PM - Info bpdbm(pid=4136) staging relational database files for catalog backup     
12/19/2012 10:44:04 PM - Info bpdbm(pid=4136) staging NBAZDB backup to C:\Program Files\Veritas\NetBackupDB\staging      
12/19/2012 10:44:05 PM - Info bpdbm(pid=4136) done staging NBAZDB backup to C:\Program Files\Veritas\NetBackupDB\staging     
12/19/2012 10:44:05 PM - Info bpdbm(pid=4136) staging NBDB backup to C:\Program Files\Veritas\NetBackupDB\staging      
12/19/2012 10:44:38 PM - Info bpdbm(pid=4136) done staging NBDB backup to C:\Program Files\Veritas\NetBackupDB\staging     
none of the requested files were backed up(2)

When i run the job, there are two jobs that are created, one is parent, second is child. Child dies first with the log up above. Parent dies with the following log in the details pane of the job:

12/19/2012 11:35:45 PM - Info nbjm(pid=3472) starting backup job (jobid=226) for client nbmaster.contoso.com, policy HotBackup, schedule Full 
12/19/2012 11:35:45 PM - Info nbjm(pid=3472) requesting CATALOG_BACKUP_RESOURCE resources from RB for backup job (jobid=226, request id:{38A019C1-6A71-4B99-9FB2-088D608E000E}) 
12/19/2012 11:35:45 PM - requesting resource nbmaster.contoso.com.NBU_CATALOG.MAXJOBS
12/19/2012 11:35:45 PM - granted resource nbmaster.contoso.com.NBU_CATALOG.MAXJOBS
12/19/2012 11:35:45 PM - estimated 0 Kbytes needed
12/19/2012 11:35:45 PM - begin Parent Job
12/19/2012 11:35:45 PM - begin Catalog Backup, Start Notify Script
12/19/2012 11:35:46 PM - Info RUNCMD(pid=2384) started           
12/19/2012 11:35:46 PM - Info RUNCMD(pid=2384) exiting with status: 0        
Status 0
12/19/2012 11:35:46 PM - end Catalog Backup, Start Notify Script; elapsed time: 00:00:01
12/19/2012 11:35:46 PM - begin Catalog Backup, DBM Query
Status 2
12/19/2012 11:37:31 PM - end Catalog Backup, DBM Query; elapsed time: 00:01:45
12/19/2012 11:37:31 PM - begin Catalog Backup, Stop On Error
Status 0
12/19/2012 11:37:31 PM - end Catalog Backup, Stop On Error; elapsed time: 00:00:00
12/19/2012 11:37:31 PM - begin Catalog Backup, End Notify Script
12/19/2012 11:37:31 PM - Info RUNCMD(pid=4764) started           
12/19/2012 11:37:32 PM - Info RUNCMD(pid=4764) exiting with status: 0        
Status 0
12/19/2012 11:37:32 PM - end Catalog Backup, End Notify Script; elapsed time: 00:00:01
Status 2
12/19/2012 11:37:32 PM - end Parent Job; elapsed time: 00:01:47
none of the requested files were backed up(2)

 

Really not sure what i am doing wrong... it is straight forward and should be able to back itself up on E: drive (30GB size empty).

dpdbm logs are the same as noted above in previous posts. no change. 

Marianne's picture

Please copy bpdbm log to bpdbm.txt and upload entire file as File attachment.

Difficult to say with small extracts.

PS. Hopefully you have a patched version of 7.5? 7.5.0.3 or 7.5.0.4?

 

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

jawad_butt's picture

I am attaching the file with this message...

I do not have the patches installed... i have a clean install from the 7.5 CD. At the bottom of the log file, you'll see the errors mentioned in my previous posts.

Also, instead of 2 jobs, i am getting 3 jobs created for the process. Second process (that does not seem to do anything) goes through succesfully but the main one does not.

Attaching the screenshots from the Activity Monitor.

AttachmentSize
122012.txt 6.2 MB
NBUScreenShots.docx 134.5 KB
mph999's picture

What does this do:

Create a dir eg E:\cat_test

Run

nbdb_backup -online E:\cat_test

Martin

 

Regards,  Martin
 
Setting Logs in NetBackup:
http://www.symantec.com/docs/TECH75805
 
jawad_butt's picture

Tried that and this is what i get in the command line:

Online backup of database to E:\cat_test successful.

When i browse to the folder E:\Cat_test, there are a bunch of files

E:\cat_test>dir /b
DARS_DATA.db
DARS_INDEX.db
databases.conf
DBM_DATA.db
DBM_INDEX.db
EMM_DATA.db
EMM_INDEX.db
JOBD_DATA.db
NBAZDB.db
NBAZDB.log
NBDB.db
NBDB.log
SEARCH_DATA.db
SEARCH_INDEX.db
server.conf
vxdbms.conf

Marianne's picture

I see something strange in the beginning of your bpdbm log file:

 

bpdbm: NBMASTER is not the primary server nbmaster.contoso.com...exiting

and then when it fails:

 

09:21:43.289 [4344.776] <16> ConnectionCache::close_i: Handle [2324] not found in our cache
09:21:53.881 [1380.1732] <16> serverResponse: ERR - server exited with status 25: cannot connect on socket
09:21:53.881 [1380.1732] <16> CreateNewImage: ERR - serverResponse() failed
09:21:53.928 [1380.808] <16> bsa_a_backup_completed: ERR - thread <1732> backup failed: 25 <cannot connect on socket>

Please show us output of all of the following:

bpclntcmd -self

nbemmcmd -listhosts -verbose
nbemmcmd -getemmserver

bpgetconfig -M NBMASTER |findstr SERVER

 

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

jawad_butt's picture

I am attaching the output from all the commands. Please let me know what you thinkk. thank you,

 

EDIT: BTW: All Firewalls are turned off.. for all profiles.

AttachmentSize
output.txt 3.01 KB
Marianne's picture

I don't see anything wrong with any of the output.

The NBMASTER vs nbmaster.contoso.com stuff that I saw in the beginning of the file is probably a red herring.

All I can suggest at this point in time is to patch the master to 7.5.0.4. There were just too many issues with unpatched 7.5.

Maybe Martin has some idea?

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

mph999's picture

Funnily enough I was just looking ...

Can't see anything obvious as the cause - I certainly go with patching first and see if that resolves.

Martin

 

Regards,  Martin
 
Setting Logs in NetBackup:
http://www.symantec.com/docs/TECH75805
 
jawad_butt's picture

Followed your suggestion..
Upgraded all systems (Master, Media, Clients) to 7.5.0.4. Restarted all the systems.

Created a new CatalogBackup policy... Started the job, failed with the same message (none of the requested files were backed up(2)

I am attaching a screenshot of the activity monitor as well as the log file of today. Any configuratino that i might have missed?

 

bpdbjobs.png
AttachmentSize
122112.txt 2.36 MB
jawad_butt's picture

I dont know if this would help any.. but, i get the attached error everytime i try to do a manual backup from BAR within Master server.

error25.png
mph999's picture

Hmm, anything in the bprd log ?

There are no magic settings for this sort of issue.

If, you have a server with a OS install, and then put NBU on te top, things should 'just work'.

If they don't we have to consider what could be causing the issue, this includes NBU itself and the OS and anything else we can think of.

We then have to decide in what order to consider things.

We've looked already at nbemmcmd outputs which looked ok, and partially eliminates this part of NBU as the cause, we could also look in the DB table directly, but not yet, as I don;t think this is the most likely cause.

Could of questions.

Apart from installing NBU, has anything else been installed, eg, anti-virus 

Anything changed apart from the default os install, for eample, do you have multiple interfaces ?

I'd also run 

nbdna -phase 2  on the master, this might show something, of if not, will eliminate a few other things.

Martin

 

Regards,  Martin
 
Setting Logs in NetBackup:
http://www.symantec.com/docs/TECH75805
 
Marianne's picture

Master is certainly having an issue connecting to itself.

I am out of ideas. We are obviously overlooking something... 

Please log a call with Symantec Support.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

jawad_butt's picture

This was installed on a Clean OS in VM environment with single interfaces on each system. nbdna comes up as unrecognized app.

jawad_butt's picture

This thing didnt go anywhere.. after a little troubleshooting i stopped getting results from nbemmcmd -getemmserver (CORBA)... Giving up... Deleting VMs and starting up again. Thank you all for your input and help...

Issues that I have had could have something to do with the "virtual" environment and NIC. Also, it could have been something to do with NAT'd network. I'm closing this thread with a big thank you.

mph999's picture

Hmm, NAT is not supported with NBU, it can work, but can be very very troublesome.

CORBA issues are network related, we had 25s and as Marianne pointed out, the master is having trouble talking to itself, which is pointing more and more to something outside NBU casung this, or at least contributing to it, which was my first thought, although I didn't say so ... )

Proving EMM is correct (the bits we looked at of yours looked fine) and there are no incorrect entries (unlikely on a new system) I'm struggling to think of a reason where NBU could cause this, after all, we only use the network provided to us, we don't control it.

As you will understand, when looking at an issue you have to consider the most likely cause, there's no point spending hours looking where the issue is least likely to be and I do think that it this case, starting again is the correct way forward.

I suggest that you progress without NAT, if nothing else to confirm NBU works, keep it simple and all that.  then if you must, see what happens with NAT (which I don't recommend as it's not supported).

Regards,

Martin

 

Regards,  Martin
 
Setting Logs in NetBackup:
http://www.symantec.com/docs/TECH75805
 
SOLUTION
jawad_butt's picture

Well.. I had an idea that NAT or something with the networking might be an issue but since everything was pingable and accessible, i didnt really give a lot of thought into it... it was definitely in the back of my head (which is why i wrote that in my last post) :)

So, I re-created the Server 2008 r2 servers, did all the updates, installed NBU without 7.5.0.4 update and ran the catalog backups (after initial configuration of course). What do you know, it all goes through... get 5 jobs craeted and all were successful.

Thank you again for all your time, blaming the NAT'd stuff for the cause and finishing with this thread :)

Laters,