Networker

Re: [Networker] Cluster backup problems

2004-01-21 15:05:57
Subject: Re: [Networker] Cluster backup problems
From: "Faidherbe, Thierry" <thierry.faidherbe AT HP DOT COM>
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Date: Wed, 21 Jan 2004 21:05:42 +0100
Joel,

In the definition of each virtual client, look for backup command.
Fill with "save -c <virtual client name>".

Networker will then fill info of the backup of each virtual client
to the corresponding CFI index and not anymore to the
cfi of the physical member. 

Have fun,

Thierry





Kind regards - Bien cordialement - Vriendelijke groeten,

Thierry FAIDHERBE

HP Service - Storage Division
Tru64 Unix and Legato EBS Consultant
                                   
 *********       *********   HEWLETT - PACKARD
 *******    h      *******   1 Rue de l'aeronef/Luchtschipstraat
 ******    h        ******   1140 Bruxelles/Brussel/Brussels
 *****    hhhh  pppp *****   
 *****   h  h  p  p  *****   100/102 Blv de la Woluwe/Woluwedal
 *****  h  h  pppp   *****   1200 Bruxelles/Brussel/Brussels
 ******      p      ******   BELGIUM
 *******    p      *******                              
 *********       *********   Phone :    +32 (0)2  / 729.85.42   
                             Mobile :   +32 (0)498/  94.60.85 
                             Fax :      +32 (0)2  / 729.88.30   
     I  N  V  E  N  T        Email :    thierry.faidherbe AT hp DOT com
                             Internet : http://www.hp.com/ 
________________________________________________________________________

MOBISTAR SA/NV 

SYSTEM Team Charleroi, Mermoz 2 Phone : +32 (0)2  / 745.75.81  
Avenue Jean Mermoz, 32          Fax :   +32 (0)2  / 745.89.56  
6041 GOSSELIES                  Email : tfhaidhe AT mail.mobistar DOT be
BELGIUM                         Web :   http://www.mobistar.be/
________________________________________________________________________

 

-----Original Message-----
From: Legato NetWorker discussion [mailto:NETWORKER AT LISTMAIL.TEMPLE DOT EDU]
On Behalf Of Joel Fisher
Sent: mercredi 21 janvier 2004 20:47
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Subject: [Networker] Cluster backup problems

Hey All,
 
Server: E450/Solaris 2.6/Solstice Backup 6.1.3(with patch to allow 7.0
clients)
Cluster: 2 Compq server/W2K3/MS Cluster/Networker 7.0 client
 
Below is how our cluster is configured:
 
physicalnode1   C:\
                D:\
                SYSTEM STATE:\
                SYSTEM FILES:\ 
physicalnode2   C:\
                D:\
                SYSTEM STATE:\
                SYSTEM FILES:\
virtualnode1    Q:\ (quorum)
virtualnode2    H:\
                J:\
virtualnode3    K:\
                L:\
                D:\volumes\data1
virtualnode4    M:\
                N:\
                D:\volumes\data2
                D:\volumes\data3
 
Everything was working correct... all the virtual nodes using their own
indexes etc... until we added the D:\volumes\data* mounted volumes.
Then I started getting the below messages.
 
--- Unsuccessful Save Sets ---
* virtualnode3.nt.wfubmc.edu:d:volumesdata1 1 retry attempted
* virtualnode3.nt.wfubmc.edu:d:volumesdata1 nsrexec: authtype nsrexec
* virtualnode3.nt.wfubmc.edu:d:volumesdata1 savefs: path d:volumesdata1
by default belongs to client physicalnode1.medctr.ad.wfubmc.edu and NOT
client virtualnode3.nt.wfubmc.edu!
* virtualnode3.nt.wfubmc.edu:d:volumesdata1 savefs: Searching for
NetWorker bin 'pathownerignore' file.
* virtualnode3.nt.wfubmc.edu:d:volumesdata1 savefs: Disallowing
sched-save for integrity reasons - no 'pathownerignore' file.
* virtualnode3.nt.wfubmc.edu:d:volumesdata1 savefs: nothing to save
savefs virtualnode3.nt.wfubmc.edu: failed.
--- Successful Save Sets ---
 
We can get the backups to "work" if I create the pathownerignore file in
the ..\nsr\bin directory, but that then causes the backup to use the
index of the physicalnode the volume is on rather than the index of the
virtualnode.  Which will cause problems when the cluster is failed over.
Is that how it's supposed to work?  Is there something special that
needs to be configured for mounted volumes?  Anyone else have a similar
config working properly?
 
One this I thought what strange is that in the error message it uses
d:volumesdata1 rather than d:\volumes\data1.  I'm not sure if this is an
indication of where the problem is, but it seems strange.
 
Thanks in advance,
 
Joel
 

--
Note: To sign off this list, send a "signoff networker" command via
email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

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