Forum Discussion

Cedeguill's avatar
Cedeguill
Level 4
8 years ago

Catalog Fail get status 2520

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.

7.6
7.7
Windows Server 2008
  • Cedeguill's avatar
    Cedeguill
    7 years ago

    Hello,

    We have updated to version 7.7.3 and the catalago has finished ok.

     

    thanks for your comments

     

     

26 Replies

Sort By
    • Will_Restore's avatar
      Will_Restore
      Level 6
      8 years ago

      Windows 2008, NBU 7.6.1 both out-of-date.  Please update OS and NetBackup ASAP.  

    • Cedeguill's avatar
      Cedeguill
      Level 4
      8 years ago

      Hello Will,

      Yes I know. but the catalog fail immediately when start the backup.

       

  • Marianne's avatar
    Marianne
    Level 6
    8 years ago

    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?

    • Cedeguill's avatar
      Cedeguill
      Level 4
      8 years ago

      The last backup was... 06/26/2017.

      The others backups by clients its OK.

      The nbemm is running.

       

      • Thiago_Ribeiro's avatar
        Thiago_Ribeiro
        Moderator
        8 years ago

        Hi,

        As Marianne said, Did you check it?

        Have you checked the partitition where NBU is installed for available space?

         

        Regards,

         

        Thiago

  • mph999's avatar
    mph999
    Level 6
    8 years ago

    There is a specific db validate log, I think that is the one that will be needed.

    Hopefully, it's set up the same in Windows as Unix, so lets give this a go.

    The log location should be :

    C:\Program Files\Veritas\NetBackupDB\log\dbvalid-connection.log

    It is enabled via a touch file:

    Create this empty file (make sure Windows doesn't add some suffix to the filename)

    C:\Program Files\Veritas\NetBackupDB\VRTS_NBDB_DBVALID_LOGS

    You can add further detail by increasing the log level for BPDBM, this can be done in the GUI, Host Properties.

     

    • Marianne's avatar
      Marianne
      Level 6
      8 years ago
      Maybe mph999 can help to interpret this...
      I see the following in bpdbm log:

      16:57:15.360 [5572.42908] <2> image_db: Q_IMAGE_CATALOG_BACKUP
      16:57:15.360 [5572.42908] <2> read_legacy_touch_file: Found E:\NetBackupDB\data\vxdbms.conf; requested from (vxdbms_conf.cpp.1528).
      16:57:15.407 [5572.42908] <16> ImageCatalogBackup::executeQuery: ManageLockFile(D:\Program Files\Veritas\NetBackup\bin\catbackup.lock) failed to set lock
      16:57:15.423 [5572.42908] <16> DbmOdbcConnect::commitTransaction: (-1) Cannot commit since transaction was never initiated
      16:57:15.438 [5572.42908] <4> jmcomm_UpdateActionStatus: Sending status: 2520 back to parent JobID: 0
      16:57:15.438 [5572.42908] <16> jmcomm_UpdateActionStatus: Invalid Parmeter
      16:57:15.438 [5572.42908] <2> jmcomm_UpdateActionStatus: returning
      16:57:15.438 [5572.42908] <16> image_db: error sending status back to jobmgr for job 0: 20
      16:57:15.438 [5572.42908] <2> process_request: request complete: exit status 2520 Cannot trigger current catalog backup; another catalog backup in progress; query type: 160

      Is there a leftover lock file (D:\Program Files\Veritas\NetBackup\bin\catbackup.lock) in place from a previous failed catalog backup?
      And this is causing the last message saying that another catalog backup is already in progress?
      • mph999's avatar
        mph999
        Level 6
        8 years ago

        I think we could stop NBU processes and remove the file - certainly the messages make it look like it could be an issue, but looking in the code it seems that the lock file is used by 'other processes, to prevent certain operations'  during a catalog backup, as opposed to stopping another catalog backup running.

        Also, the nbdb_backup –online failed, which is unrelated to the lock file.  So whilst not impossible that the lock file is an issue, it doesn’t appear to be, although it needs to be removed.

        I would set up the db validate log as explained above, and then in <install>\veritas\netbackup\bin run NbDbAdmin (should be a GUI) and run a full DB validate.  When you logintop NbDbAdmin, the passwd should be nbusql

        Let's then see what is in the validate log.