We have an AIX HACMP cluster made of 2 physical node running each one a
ressource (ip address + disks).
Physical node : hn291 & hn292
Ressource name : hn491 & hn492
We have a backup running each night on both physical and ressource name
with an "all" saveset.
So,
For the physical node backup, legato backups the local disks. It doesn't
backup the SAN disks.
For the ressource name, legato backups the SAN disks. It doesn't backup
the local disks.
How does legato know which particular filesystem belong to the physical or
the ressource?
I'm asking this question because legato is wrong on a particular
filesystem. I can't backup it under the ressource name but i can under the
physical name.
So, for now, as long as my cluster is in its normal state,i've a backup
... but if my physical node crash, my backup will be KO (unless i made
some manual change in legato).
Here is the log:
NetWorker savegroup: (alert) DWHBCV completed, Total 2 client(s), 1
Failed, 1 Succeeded. Please see group completion details for more
information.
Failed: hn491
Succeeded: hn291
Start time: Thu Mar 19 08:58:44 2009
End time: Thu Mar 19 09:01:48 2009
--- Never Started Save Sets ---
savegrp: hn491:/crelan/exp/ora_data1/dwh/data save was never started
* Probe job had unrecoverable failure(s), this job is being abandoned.
savegrp: hn491:/crelan/exp/ora_data1/dwh/index save was never started
* Probe job had unrecoverable failure(s), this job is being abandoned.
--- Unsuccessful Save Sets ---
* hn491:Probe 7198:savefs: path /crelan/exp/ora_data1/dwh/index by default
belongs to client hn291 and NOT client hn491!
* hn491:Probe Searching for NetWorker bin 'pathownerignore' file.
* hn491:Probe 7199:savefs: Disallowing sched-save for integrity reasons -
no 'pathownerignore' file.
* hn491:Probe 7198:savefs: path /crelan/exp/ora_data1/dwh/data by default
belongs to client hn291 and NOT client hn491!
* hn491:Probe 7199:savefs: Disallowing sched-save for integrity reasons -
no 'pathownerignore' file.
* hn491:Probe 7184:savefs: nothing to save
* hn491:Probe savefs hn491: failed.
* <ERROR> : Failed with error(s)
--- Successful Save Sets ---
* hn291:Probe savefs hn291: succeeded.
hn291: /crelan/exp/ora_data1/dwh/data level=incr, 0 KB 00:02:59 0
files
hn291: /crelan/exp/ora_data1/dwh/index level=incr, 0 KB 00:02:59 0
files
hn600.crelan.be: index:hn291 level=9, 611 KB 00:00:01 37
files
hn600.crelan.be: index:hn491 level=9, 17 MB 00:03:02 24
files
_____________________________________________________
This email and any attached files are confidential and may be legally
privileged.If you are not the intended recipient, any disclosure, reproduction,
copying, distribution, or other dissemination or use of this communication is
strictly prohibited. If you have received this transmission in error please
notify the sender immediately and then delete this email.Email transmission
cannot be guaranteed to be secure or error free as information could be
intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain
viruses. The sender therefore is in no way liable for any errors or omissions
in the content of this message, which may arise as a result of email
transmission. If verification is required, please request a hard copy.
Please bear in mind that the content of any email leaving and entering the
recipient network
will be verified against viruses, spam and unsuitable content in accordance
with the recipient
policies and regulations. Halted messages will therefore be destroyed without
any further
notice.LBK.
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
|