07-05-2017 06:15 AM - edited 07-05-2017 06:15 AM
Hello,
We have the problem of catalog, which at the beginning fails me with error 2520. At the moment I have not made any resolution.
Job detail:
07/02/2017 14:10:04 - Info nbjm (pid=53420) starting backup job (jobid=1048379) for client g300603cl005, policy CSD_BR_NBU_CAT, schedule Diario_Full
07/02/2017 14:10:04 - Info nbjm (pid=53420) requesting CATALOG_BACKUP_RESOURCE resources from RB for backup job (jobid=1048379, request id:{CF79AD2E-2679-4DE9-9BC0-2F3BD95FEDB0})
07/02/2017 14:10:04 - requesting resource g300603cl005.NBU_CATALOG.MAXJOBS
07/02/2017 14:10:05 - granted resource g300603cl005.NBU_CATALOG.MAXJOBS
07/02/2017 14:10:05 - estimated 0 kbytes needed
07/02/2017 14:10:05 - begin Parent Job
07/02/2017 14:10:05 - begin Catalog Backup: Start Notify Script
07/02/2017 14:10:05 - Info RUNCMD (pid=21672) started
07/02/2017 14:10:05 - Info RUNCMD (pid=21672) exiting with status: 0
Operation Status: 0
07/02/2017 14:10:05 - end Catalog Backup: Start Notify Script; elapsed time 0:00:00
07/02/2017 14:10:05 - begin Catalog Backup: Database Manager Query
Operation Status: 2520
07/02/2017 14:10:06 - end Catalog Backup: Database Manager Query; elapsed time 0:00:01
07/02/2017 14:10:06 - begin Catalog Backup: Stop On Error
Operation Status: 0
07/02/2017 14:10:06 - end Catalog Backup: Stop On Error; elapsed time 0:00:00
07/02/2017 14:10:06 - begin Catalog Backup: End Notify Script
07/02/2017 14:10:06 - Info RUNCMD (pid=14736) started
07/02/2017 14:10:06 - Info RUNCMD (pid=14736) exiting with status: 0
Operation Status: 0
07/02/2017 14:10:06 - end Catalog Backup: End Notify Script; elapsed time 0:00:00
Operation Status: 2520
07/02/2017 14:10:06 - end Parent Job; elapsed time 0:00:01
Failed to get status code information (2520)
Can you helpme about solution?
Enviroment:
Windows 2008, NBU 7.6.1.
Regards.
Solved! Go to Solution.
07-20-2017 12:37 PM
Hello,
We have updated to version 7.7.3 and the catalago has finished ok.
thanks for your comments
07-05-2017 07:26 AM
2520 not found in Status Codes guide
https://www.veritas.com/support/en_US/article.000004304
Check Windows Event Viewer for possible clues.
07-05-2017 07:31 AM
Windows 2008, NBU 7.6.1 both out-of-date. Please update OS and NetBackup ASAP.
07-05-2017 07:38 AM
When last did a catalog backup work?
What about other backups in the environment? Still working or not?
Yes, status code 2520 does not appear in any NBU documentation.
The actual error is this:
Failed to get status code information
This means that something is very wrong - to the extend that NBU cannot determine the actual error/problem.
Is EMM running? And other NBU services/processes?
Have you checked the partitition where NBU is installed for available space?
07-05-2017 07:42 AM
Hello Will,
Yes I know. but the catalog fail immediately when start the backup.
07-05-2017 07:50 AM
The last backup was... 06/26/2017.
The others backups by clients its OK.
The nbemm is running.
07-05-2017 08:03 AM
Hi,
As @Marianne said, Did you check it?
Have you checked the partitition where NBU is installed for available space?
Regards,
Thiago
07-05-2017 12:34 PM
Hello,
Yes we cherk the space and its ok.
We restart the nbu service and the catalog show this logs:
07/05/2017 16:25:27 - Info bpdbm (pid=42624) staging relational database files for catalog backup
07/05/2017 16:25:27 - Info bpdbm (pid=42624) staging NBAZDB backup to E:\NetBackupDB\staging
07/05/2017 16:25:27 - Info bpdbm (pid=42624) done staging NBAZDB backup to E:\NetBackupDB\staging
07/05/2017 16:25:27 - Info bpdbm (pid=42624) staging NBDB backup to E:\NetBackupDB\staging
07/05/2017 16:25:37 - Error bpdbm (pid=42624) error staging NBDB backup to E:\NetBackupDB\staging
and finished with status 1.
Regards.
07-05-2017 11:24 PM
Try:
C:\Program Files\Veritas\NetBackup\bin\nbdb_backup -online <some dir>
You need to create <some dir> first, and from memory it needs to be empty.
This will run, but should hopefully show some error. Please post up the results.
07-06-2017 08:01 AM
Hello,
I run the command and the result is:
D:\Program Files\Veritas\NetBackup\bin>nbdb_backup -online D:\nbdblog
Online backup of database to D:\nbdblog failed.
D:\Program Files\Veritas\NetBackup\bin>
D:\Program Files\Veritas\NetBackup\bin>
Regards.
07-06-2017 09:37 AM - edited 07-06-2017 09:44 AM
Check the Event Viewer ??
You should see things like
SQLAnywhere: Opening dbspace 'EMM_DATA' in file 'D:\nbdblog\EMM_DATA.db' for database 'NBDB'
07-06-2017 12:10 PM
Hi,
No i can´t see this message.
After I ran that command the catalog started to fail for status 2 ...what's up with that?
07/06/2017 16:01:55 - Info bpdbm (pid=12120) staging relational database files for catalog backup
07/06/2017 16:01:55 - Info bpdbm (pid=12120) staging NBAZDB backup to E:\NetBackupDB\staging
07/06/2017 16:01:55 - Info bpdbm (pid=12120) done staging NBAZDB backup to E:\NetBackupDB\staging
07/06/2017 16:01:55 - Info bpdbm (pid=12120) staging NBDB backup to E:\NetBackupDB\staging
07/06/2017 16:02:05 - Info bpdbm (pid=12120) done staging NBDB backup to E:\NetBackupDB\staging
07/06/2017 16:05:24 - Info bpdbm (pid=12120) validating NBAZDB backup in E:\NetBackupDB\staging
07/06/2017 16:05:27 - Info bpdbm (pid=12120) done validating NBAZDB backup in E:\NetBackupDB\staging
07/06/2017 16:05:27 - Info bpdbm (pid=12120) validating NBDB backup in E:\NetBackupDB\staging
07/06/2017 16:05:27 - Error bpdbm (pid=12120) error validating NBDB backup in E:\NetBackupDB\staging.
none of the requested files were backed up (2)
before the them finished with status 1..
07-06-2017 12:16 PM
Hi @Cedeguill,
Did you already check this article?
https://www.veritas.com/support/en_US/article.000017498
Regards,
Thiago
07-07-2017 12:36 AM
If the above advice does not fix your issue, you will need logs to troubleshoot.
The first one I would look at is server.log in <install-path>\veritas\netbackupDB\log directory.
The next one is bpdbm log. This folder does not exist by default and must be created under <install-path>\veritas\netbackup\logs, followed by restart of NBU.
If you want to upload logs for us to have a look at, please copy to .txt files (e.g. server.txt, bpdbm.txt) and then attach.
Please schedule NBU upgrade as a matter of urgency - you cannot log a call with Support with your EOSL version.
07-07-2017 05:31 AM
Hello @Marianne,
I'm going to take out the logs that you indicate, since the technical note did not work.
Yes, the update is scheduled, but first we want to run the catalog for security since it has almost two weeks with the failure.
Regards.
07-07-2017 08:55 AM
Attach the server.log. I can not restart services since there are backups running
07-07-2017 09:23 AM
07-07-2017 09:26 AM
FYI
07-07-2017 09:39 AM
07-07-2017 10:05 AM
The logs will be sent shortly. We are scheduling an early update.
The backup of E: \ NetBackupDB \ staging \ DARS_DATA.db ends OK, what is failing is staging.