Re: [Veritas-bu] big issue with netbackup upgrade; any insight?

I'm assuming you have multiple hostnames defined for the Master/Media servers, one per interface ? If so, welcome to the fun word of EMM aliases. =)

# nbemmcmd -machinealias -help
NBEMMCMD, Version:6.0MP5(20060530)
Help requested.
Usage:
nbemmcmd -machinealias [-brief]
    [-addalias -alias <string> -machinename <string>]
    [-deletealias -alias <string>]
    [-deleteallaliases -machinename <string>]
    [-getaliases -machinename <string>]
    -machinetype <api | app_cluster | cluster | master | media | ndmp >
Command completed successfully.

I've seen this kind of thing when the Media Servers in particular have multiple interefaces and are attempting communication over a different one than normal. You basically just need to add an alias to authorize that interface.

So if your alternate interface is myhost-backup on your media server, then you'd run:

nbemmcmd -machinealias -addalias -alias myhost-backup -machinename myhost -machinetype media

Then you can use the 'getaliases' option to list out what you've currently got defined and make sure all your interfaces are listed.

Hope that helps.

John Nardello

From: veritas-bu-bounces AT mailman.eng.auburn DOT edu [mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of rascal
Sent: Tuesday, March 11, 2008 8:38 AM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] big issue with netbackup upgrade; any insight?

Good morning/afternoon/evening all,

     So I have run into a fun, fun issue with my netbackup upgrade. Here are the details:

1. mix environment; primarily AIX5xxx boxes, master/media servers, all have multiple NIC interfaces (pub/private/backup)
2. going from NB5MP5 to NB651
3. procedure went like so:
     a. stop services
     b. upgrade environment
     c. run nbpushdata and note errors (go back and fix in nb5 if required)
     d. patch
     e. start services
     f. push client
     g. test backups/restores

     So here is what is interesting.

1. Hot catalogs fail; here is an error:
03/09/2008 11:00:20 - begin Catalog Backup
03/09/2008 11:00:24 - Error bpbackupdb (pid=5779600) jmcomm_RequestMultipleResources() failed with stat = 800
03/09/2008 11:00:24 - Error bpbackupdb (pid=5779600) NBJM returned an extended error status: resource request failed (800)
03/09/2008 11:00:24 - end Catalog Backup; elapsed time 0:00:04
03/09/2008 11:00:25 - Error bpbackupdb (pid=5779600) Offline catalog backup to media id XXXXXX FAILED
03/09/2008 11:00:22 - requesting resource XXXXXX
03/09/2008 11:00:22 - Error nbjm (pid=1810436) NBU status: 800, EMM status: The host is not defined in EMM
An extended error status has been encountered, check detailed status (252)

2. Restores to different locations other than local server:

03/11/2008 09:09:25 - begin Restore
03/11/2008 09:09:30 - number of images required: 1
03/11/2008 09:09:30 - media needed: XXXXXX
03/11/2008 09:10:09 - restoring from image XXXXXXXX_1191236706
03/11/2008 09:10:13 - connecting
03/11/2008 09:10:16 - connected; connect time: 0:00:00
03/11/2008 09:10:17 - Error bptm (pid=4772066) NBJM returned an extended error status: resource request failed (800)
03/11/2008 09:10:15 - requesting resource XXXXXX
03/11/2008 09:10:15 - Error nbjm (pid=5107866) NBU status: 800, EMM status: The host is not defined in EMM
03/11/2008 09:10:15 - Error nbjm (pid=5107866) NBU status: 800, EMM status: The host is not defined in EMM
03/11/2008 09:10:18 - Error bptm (pid=1904656) The following files/folders were not restored:
03/11/2008 09:10:22 - Error bptm (pid=1904656) more than 10 files were not restored, remaining ones are shown in the progress log.
03/11/2008 09:10:23 - restored from image XXXXXXXX_1191236706; restore time: 0:00:14
03/11/2008 09:10:25 - Warning bprd (pid=5132452) Restore must be resumed prior to first image expiration on Sun Sep 29 07:05:06 EDT 2013
03/11/2008 09:10:26 - end Restore; elapsed time 0:01:01
the restore failed to recover the requested files (5)

So here I sit, trying to figure out what the issue is that I am experiencing but I can't seem to get it nailed to anything in particular. It seems that it is only happening on the upgrades though; these same boxes can be just installed with 6.5.1 (no upgrade) and it works fine. Anyone else see this? Anyone else run into the emm 800 errors?

Matthew MCP, MCSA, MCTS, OCA
rascal1981 AT gmail DOT com

Define Trouble:
Why did you apply THAT patch??....

_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu