Hi Steve!
Now what if an extra filespace is created in the sharedvg? You will have to
modify your backup script. This is something we don't want, because that's
something that will most likely be forgotten in the daily practice.
So, what I would like to know is, how do you automate this? Is building your
own scripts (using the utilities Jeroen mentioned) the only (and best?)
solution?
Kindest regards,
Eric van Loon
KLM Royal Dutch Airlines
-----Original Message-----
From: Steve Harris [mailto:Steve_Harris AT HEALTH.QLD.GOV DOT AU]
Sent: Wednesday, April 21, 2004 10:00
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Exclude on AIX (part 2)
Eric,
Use another client node for shared data - we have one per app in the
cluster.
It fails over with the app and has domain statements that restrict it to
back up just its own filesystems. Use the PASSWDDIR option to keep the
encrypted password with the data. You will need to implement domain
statements for the nodes that backup the non-shared portions of your
cluster.
In our case if the app lives on filesystems /p201, /p202 etc...
We have a /p201/app/tsm directory containing app_dsm.opt and TSM.PWD and the
logs
The app_dsm.opt file looks like
SERVERNAME BLAH
DOMAIN /p201 /p202 (in our case /p203 and /p204 exist but are the Database
filespaces for this app)
DATEFORMAT 2
and we have the same dsm.sys on all servers in the cluster
SErvername BLAH
nodename blah
COMMmethod TCPip
tcpclientaddress Blah
HTTPPORT 1611
PASSWDDIR /p201/app/tsm
PasswordAccess generate
schedmode prompted
managedservices schedule webclient
errorlogname /p201/app/tsm/dsmerror.log
errorlogretention 7
schedlogname /p201/app/tsm/dsmsched.log
schedlogretention 7
We just increment the HTTPPort by one for each new app we define
Startup scripts run dsmcad -optfile=/p201/app/tsm/app_dsm.opt.
This currently is running well on sun/veritas. In the past we ran it in an
AIX/hacmp environment that never made it into production.
HTH
Steve
Steve Harris
AIX and TSM Admin
Queensland Health, Brisbane Australia
>>> Eric-van.Loon AT KLM DOT COM 21/04/2004 17:34:45 >>>
Hi *SM-ers!
Ok, I understand that include.fs is not available on AIX, so that will make
things more difficult.
Let me first explain what our AIX guys try to accomplish, maybe we are
trying to re-invent the wheel.
We are trying to create a standard backup solution for our HACMP clusters.
To put is simple: we want to backup all filesystems which are part of the
sharedvg. We would like to create a standard script, which can be used on
all HACMP nodes.
How do other people solve this?
Thank you very much for your reply in advance!
Kindest regards,
Eric van Loon
KLM Royal Dutch Airlines
-----Original Message-----
From: Richard Sims [mailto:rbs AT BU DOT EDU]
Sent: Tuesday, April 20, 2004 16:16
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Exclude on AIX
>Hi Richard!
>Thank you very much for your reply!
>We don't use server defined include-excludes, so that's not the problem.
>We currently tried the following:
>
>exclude.fs *
>include.fs /home
>include.fs /usr
>
>Backup now finishes in 1 second. I've had them issue a q inclexcl which
>shows the correct statements and when they start the GUI, you can see that
>no filespaces are listed through the backup window. That explains why
backup
>finishes so quickly, but it's still not what we want to accomplish...
But your backups now run so much faster! :-)
Checking the Unix client manual, I find no such "Include.FS" option, so what
you probably want to do is "Include /home/.../*".
Would that Query Inclexcl flagged such things.
Richard
**********************************************************************
For information, services and offers, please visit our web site:
http://www.klm.com. This e-mail and any attachment may contain confidential
and privileged material intended for the addressee only. If you are not the
addressee, you are notified that no part of the e-mail or any attachment may
be disclosed, copied or distributed, and that any other action related to
this e-mail or attachment is strictly prohibited, and may be unlawful. If
you have received this e-mail by error, please notify the sender immediately
by return e-mail, and delete this message. Koninklijke Luchtvaart
Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be
liable for the incorrect or incomplete transmission of this e-mail or any
attachments, nor responsible for any delay in receipt.
**********************************************************************
****************************************************************************
*******
This email, including any attachments sent with it, is confidential and for
the sole use of the intended recipient(s). This confidentiality is not
waived or lost, if you receive it and you are not the intended recipient(s),
or if it is transmitted/received in error.
Any unauthorised use, alteration, disclosure, distribution or review of this
email is prohibited. It may be subject to a statutory duty of
confidentiality if it relates to health service matters.
If you are not the intended recipient(s), or if you have received this email
in error, you are asked to immediately notify the sender by telephone or by
return email. You should also delete this email and destroy any hard copies
produced.
****************************************************************************
*******
|
