Hi
So, I can have two nodenames pointing to one tsm sever i.e. pointing to the
same tcpserveraddress? In my example I assume I would want to do the
following.
SErvername DOMSRV1
Nodename DOMSRV1
COMMmethod TCPip
TCPPort 1500
TCPServeraddress tsmbackup
passwordaccess generate
schedlogname
/opt/tivoli/tsm/client/ba/log/domsrv1_sched.log
errorlogname
/opt/tivoli/tsm/client/ba/log/domsrv1_error.log
SErvername DOMSRV1_ARCHIVE
Nodename DOMSRV1_ARCHIVE
COMMmethod TCPip
TCPPort 1500
TCPServeraddress tsmbackup
passwordaccess generate
schedlogname
/opt/tivoli/tsm/client/ba/log/domsrv1_archive_sched.log
errorlogname
/opt/tivoli/tsm/client/ba/log/domsrv1_arch_error.log
Will the TSM Server see this as two seperate clients? I'm wondering what I
would see from a filesystem point of view.
Also, when I come to do a restore, how do I connect to a specific
nodename?
Sorry for all the question.
Farren
|-----------------------------+-------------------------------------------|
| "Hooft, Jeroen" | |
| <[email protected]| |
| OM> | To|
| Sent by: "ADSM: Dist Stor | [email protected]|
| Manager" | ARIST.EDU |
| <ADSM-L AT VM.MARIST DOT EDU> |
cc|
| | |
| 27/01/2006 15:36 | Subject|
| | Re: |
| Please respond to | [ADSM-L] |
| "ADSM: Dist Stor | Domino |
| Manager" | Client |
| <ADSM-L AT VM.MARIST DOT EDU> | question
|
| | |
| | |
| | |
| | |
| | |
| | |
|-----------------------------+-------------------------------------------|
Don't know the location of this mechanism in the manuals, but here is an
example for AIX.
The idea is that the same notes-system makes the backups using different
nodenames.
The idea is to have to different dsm.opt files. 1 for the normal and 1 for
the longtime backups.
In the dsm.sys file you will need a server entry for both dsm.opt files.
dsm.sys
SERVERNAME DOMSRV1
NODENAME DOMSRV1
tcpadd xxx
etc...
SERVERNAME DOMSRV1_ARCHIVE
NODENAME DOMSRV1_ARCHIVE
tcpadd xxx
etc..
For the regular backups a reference to the default dsm.opt is made
export DSMI_CONFIG=/path/dsm.opt
For the long term archival, you refer before the backup to the other
dsm.opt
export DSMI_CONFIG=/path/dsm_archive.opt
Regards Jeroen
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
Farren Minns
Sent: vrijdag 27 januari 2006 16:22
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Domino Client question
Hi all
Can anyone tell me where I find information on setting up a client with two
different node names etc. I'm looking in the BA client manual but not
finding anything that looks relevant.
Many thanks
Farren
|-----------------------------+-------------------------------------------|
| Del Hoobler | |
| <hoobler AT US.IBM DOT COM> |
|
| Sent by: "ADSM: Dist Stor | To|
| Manager" | [email protected]|
| <ADSM-L AT VM.MARIST DOT EDU> | ARIST.EDU
|
| | cc|
| 26/01/2006 16:06 | |
| | Subject|
| Please respond to | Re: |
| "ADSM: Dist Stor | [ADSM-L] |
| Manager" | Domino |
| <ADSM-L AT VM.MARIST DOT EDU> | Client
|
| | question |
| | |
| | |
| | |
| | |
| | |
| | |
|-----------------------------+-------------------------------------------|
Hi Farren,
For long-term archival, you should still use the
Data Protection for Domino client because you want to
make sure that the databases being backed up have
full integrity.
Many customers accomplish this by setting up a
secondary TSM NODENAME like DOMSRV1_ARCHIVE and
perform a monthly Data Protection for Domino backup
using a different nodename with different
policy setting to meet their longterm archival needs.
Another thing you can look at is IBM DB2 CommonStore for Lotus Domino:
http://www-306.ibm.com/software/data/commonstore/lotus/
Thanks,
Del
----------------------------------------------------
Del Hoobler
Tivoli Storage Manager Development
IBM Corporation
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 01/26/2006
10:56:41 AM:
> Hi Del
>
> OK, that all makes sense, but in this case where we are doing full
backups
> every weekend, and if we wanted to keep data for a year (at least) we
are
> going to end up with 52 full copies of the db in backup. Which again
leads
> me to think that the domino client may not be the best tool for long
term
> archive storage of data. Would I be right in thinking this, or is this
the
> way things are generally done with domino databases?
>
> All the best
>
> Farren
######################################################################
The information contained in this e-mail and any subsequent
correspondence is private and confidential and intended solely
for the named recipient(s). If you are not a named recipient,
you must not copy, distribute, or disseminate the information,
open any attachment, or take any action in reliance on it. If you
have received the e-mail in error, please notify the sender and delete
the e-mail.
Any views or opinions expressed in this e-mail are those of the
individual sender, unless otherwise stated. Although this e-mail has
been scanned for viruses you should rely on your own virus check, as
the sender accepts no liability for any damage arising out of any bug
or virus infection.
######################################################################
######################################################################
The information contained in this e-mail and any subsequent
correspondence is private and confidential and intended solely
for the named recipient(s). If you are not a named recipient,
you must not copy, distribute, or disseminate the information,
open any attachment, or take any action in reliance on it. If you
have received the e-mail in error, please notify the sender and delete
the e-mail.
Any views or opinions expressed in this e-mail are those of the
individual sender, unless otherwise stated. Although this e-mail has
been scanned for viruses you should rely on your own virus check, as
the sender accepts no liability for any damage arising out of any bug
or virus infection.
######################################################################
|
