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.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=