Forum Discussion

susindran_surul's avatar
11 years ago

Catalog Backup getting failed after upgrade from 7.5.0.4 to 7.6.0.2

Hi Team,

My catalog backup getting failed after upgrade from 7.5.0.4 to 7.6.0.2.All other backup running fine but this catalog backup getting failed.I could see below logs on bpdbm before fails.

Please help on here.

10:29:53.951 [6809] <2> DbmOdbcConnect::setIsolationLevel: (-7) Isolation Level=<32> (SNAPSHOT)
10:29:53.952 [6809] <2> DbmOdbcConnect::beginTransaction: (-7) transaction started
10:29:53.952 [6809] <16> ImageCatalogBackup::executeQuery: failed to execute /usr/openv/netbackup/bin/bpbackup -i -p Test-Catalog -h master -t 35 -pop 5436071 -s Full -cbustart 0 -cbuend 1403578455 -w (13)
10:29:53.952 [6809] <2> DbmOdbcView::DbmOdbcView: (-7.17) Executing "SELECT @@SPID" Bindings <>
10:29:53.953 [6809] <2> DbmOdbcView::DbmOdbcView: SQL_SUCCESS
10:29:53.954 [6809] <2> DbmOdbcView::DbmOdbcView: (-7.17) ConnectionId = '10953'
10:29:53.954 [6809] <2> DbmOdbcConnect::set_connection_id: -7 -> 10953
10:29:53.954 [6809] <2> DbmOdbcView::DbmOdbcView: (10953.17) Created
10:29:53.954 [6809] <2> update_DBM_Image: Entering
10:29:53.954 [6809] <2> update_DBM_Image: (10953.17) Executing "UPDATE DBM_Main.DBM_Image SET Expiration = 1403605793 WHERE ImageKey = ?" Bindings <1624269>
10:29:53.965 [6809] <2> update_DBM_Image: SQL_SUCCESS
10:29:53.965 [6809] <2> update_DBM_Image: Success executing (ImageKey = 1624269) (0)
10:29:53.966 [6809] <2> exec_catalog_DR_protection: Entering
10:29:53.966 [6809] <2> exec_catalog_DR_protection: classname=Test-Catalog, fqDRImagePath=<NULL>, status=13
10:29:53.966 [6809] <2> read_catdrinfo: ?
10:29:53.967 [6809] <2> read_catdrinfo_file: ?
10:29:53.981 [6809] <2> read_catdrinfo_file: EMAIL xx@xx.com
10:29:53.981 [6809] <2> read_catdrinfo_file: PATH /opt/openv/DR
10:29:53.981 [6809] <2> read_catdrinfo_file: FLAGS 0
10:29:53.981 [6809] <2> exec_catalog_DR_protection: Sending DR image info via email
10:29:53.981 [6809] <2> generate_DR_file_and_send_mail: Entering
10:29:53.986 [6809] <2> generate_DR_report: Entering, copynum:0, subject:, fqfilePath:, updateExistingDR:0, reportFP:1
10:29:53.987 [6809] <2> send_DR_report: Entering
10:29:53.988 [6809] <2> OpenSendmailPipe: /usr/lib/sendmail -t >/dev/null 2>/dev/null
10:29:53.990 [6809] <16> send_mail2: fopen() failed (2)
10:29:54.121 [6809] <4> db_error_add_to_file: Could not send DR report
10:29:54.121 [6809] <16> generate_DR_file_and_send_mail: Could not send DR report
10:29:54.122 [6809] <16> exec_catalog_DR_protection: Failed to send DR image to xx@xx.com (0)

10:29:54.122 [6809] <2> ImageCatalogBackup::executeQuery: Deleting /usr/openv/netbackup/db/images/master/1403000000/Test-Catalog_1403578455_FULL
10:29:54.124 [6809] <2> ImageCatalogBackup::executeQuery: Deleting /usr/openv/netbackup/db/images/master/1403000000/Test-Catalog_1403578132_FULL
10:29:54.125 [6809] <2> ~DbmLockFile: Successfully release lockfile /usr/openv/netbackup/bin/catbackup.lock file descriptor 7
10:29:54.125 [6809] <2> ImageCatalogBackup::~ImageCatalogBackup: Exiting

 

Thanks,

Susi.S

 

  • So, incorrect symbolic link, pointing to itself instead of a folder. Seems someone wanted to ensure that all possible names for RAC nodes will save image files in the same folder, but created the link incorrectly. From what I see, the link should be directly under images folder, gbsRAC -> gbsdb-bkp. I cannot tell you why this is only causing an issue now. Simply delete this link.

13 Replies