Forum Discussion

Merv's avatar
Merv
Level 6
16 years ago
Solved

Netbackup for enterprise vault - error code 112 when backing up vaultstore

Hi all, I'm having a problem getting the EV agent for netbackup working backing a SQL db(monitoring db) works ok but not the enterprise vault store. I get exit code error 112 no files specified in the file list. I suspect it's something to do with the backup LAN as the EV server has a different hostname on the backup LAN. There are lots of errors in the bpresolver logs about hostname - will post the logs later. Hopefully someone has some exp with the EV agent and cab tell how to get it to work with a Backup LAN
7.1.x and Earlier
Backup and Recovery
NetBackup
  • Merv's avatar
    Merv
    16 years ago
    Hi Bill/Bob, FYI. Managed to get this resolved. It wasn't MSXML6 the bpresolver logs were giving errors with gethostbyname errors or name resolution issues. I re-ran the job on production LAN I.e. By specifying the production LAN hostname and it ran successfully. After checking through the backup LAN setup realised that the client could not resolve it's own backup LAN hostname. The master server could but since the NBU EV agent spawned multiple jobs (seems like initiated by client) after the main policy is run the client resolution issues happens. Had to add the backup LAN hostname to the hosts file on the EV server which should br standard practise anyway else client run jobs will fail.

3 Replies

Sort By
  • Stumpr2's avatar
    Stumpr2
    Level 6
    16 years ago
    STATUS CODE 112: When backing up Enterprise Vault using the NetBackup Enterprise Vault agent backups fails with status 112 and with message "MSXML not found" in the bpresolver log
    http://support.veritas.com/docs/328431

    Exact Error Message
    Registry Key for MSXML6 not found.

     
    Details:
    ERROR MESSAGE/CODE:
    Status Code 112:  no files specified in the file list
     

    TROUBLESHOOTING:
     
    Extract from the bpresolver log:
     
    10:33:51.249 [8478.5492] <2> DebugLog(): INF - evFileSystem::isMSXMLInstalled: Registry Key for MSXML6 not found. Seems that MSXML6 is not installed.. Exiting......
     
    SOLUTION:
     
    In order to use the NetBackup Enterprise Vault Agent as a pre-requisite Microsoft Core XML Services (MSXML6) 6.0 needs to be installed on the Enterprise Vault server. You can download MSXML6 from the Microsoft Web site:  http://www.microsoft.com/downloads/details.aspx?FamilyID=993c0bcf-3bcf-4009-be21-27e85e1857b1&displaylang=en
     
  • Merv's avatar
    Merv
    Level 6
    16 years ago
    Hi Bill/Bob, FYI. Managed to get this resolved. It wasn't MSXML6 the bpresolver logs were giving errors with gethostbyname errors or name resolution issues. I re-ran the job on production LAN I.e. By specifying the production LAN hostname and it ran successfully. After checking through the backup LAN setup realised that the client could not resolve it's own backup LAN hostname. The master server could but since the NBU EV agent spawned multiple jobs (seems like initiated by client) after the main policy is run the client resolution issues happens. Had to add the backup LAN hostname to the hosts file on the EV server which should br standard practise anyway else client run jobs will fail.