Networker

Re: [Networker] URGENT NMSAP backup error

2010-04-01 09:46:26
Subject: Re: [Networker] URGENT NMSAP backup error
From: Mario Behring <mariobehring AT YAHOO DOT COM>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Thu, 1 Apr 2010 06:43:43 -0700
I didn´t change anything on Media Pool properties....but I w
Hi Tim,

I didn´t change anything on Media Pool properties....but I went there anyway to 
check...the only things marked there are in the Target Device subwindow....and 
both are Tape drives from the DELL 132-T jukebox that is connected to the 
StgNode (bkptempo03).

All other subwindows are clear....Data Source - Clientes, Save Sets and 
Levels....Target Media also clear....

Should the tapes from the other jukebox be marked as well? For the index backup 
I mean....the other jukebox (DELL TL-4000) is connected to the NW Server 
(bkptempo02)....could that be the error??

Mario





________________________________
From: Tim Mooney <Tim.Mooney AT NDSU DOT EDU>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Sent: Wed, March 31, 2010 8:11:50 PM
Subject: Re: [Networker] URGENT NMSAP backup error

In regard to: [Networker] URGENT NMSAP backup error, Mario Behring said (at...:

> I am getting the following error when trying to execute a Schedule on a
> Module for SAP with Oracle 4.0 agent:
>
> 1 retry attempted
> brbackup exited with error status 2.
>
> (pid = 676) (date = 03/31/2010 01:28:14 PM) Backup Failed.
> (pid = 676) (date = 03/31/2010 01:28:14 PM) Refer to BRBACKUP's 
> /oracle/PRD/sapbackup/becxgqmd.fnf log for details.
>
> saptempoprd.tempopar.intranet:index 1 retry attempted
> saptempoprd.tempopar.intranet:index 39077:save: error, no matching devices 
> for save of client `bkptempo02'; check storage nodes, devices or pools
> saptempoprd.tempopar.intranet:index
> saptempoprd.tempopar.intranet:index 5777:save: Cannot open save session with 
> bkptempo02

Have you made any modifications to your devices or pools recently?  There
are a few things that can cause this, but one very common reason is that
a NetWorker administrator changes what levels of backups a particular
pool will accept, and inadvertently makes it so that there are no
pools that a backup can use, because one or more levels are not allowed
by the pool.

> Please note this....saptempoprd is the hostname of the NMSAP
> agent....and bkptempo02 is the NW Server....so, I don?t know why the
> error message says "no matching devices for save of client
> 'bkptempo02'..."

When a typical savegrp runs, all of the clients in that group do their
backups.  After each client completes, the NetWorker client file index
for that client is backed up.  Since this is stored on the server, when
that backup takes place it's actually the backup server that is the
"client".

> The NMSAP configuration
>
> What could be wrong? This schedule used to work....

You or someone else with NetWorker administrator access probably made
a change to the "pools" configuration.  There are other settings that
might cause this, but pools is the usual culprit.

Look at the pools (launch NMC, then launch NetWorker Administrator, then
select the "Media" icon and highlight the "Media Pools" entry).  Find the
pool that is accept the remainder of your Oracle/SAP data.  Examine the
properties for that pool.

Look closely at the settings on the "Selection Criteria" tab.  Is there
anything that's "checked"?  Anything you've changed recently?

Tim
-- 
Tim Mooney                                            Tim.Mooney AT ndsu DOT edu
Enterprise Computing & Infrastructure                  701-231-1076 (Voice)
Room 242-J6, IACC Building                             701-231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
[email protected] you have any problems with this list. 
You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER





To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

<Prev in Thread] Current Thread [Next in Thread>