That's great.
Thanks as always to all who have given me some pointers.
Farren
|-+---|
| Helder Garcia | |
| <[EMAIL PROTECTED]> |
You can use "-servername" option of dsmc, like
./dsmc -servername=DOMSRV1_ARCHIVE
Servername option should be the name given by "SERVERNAME" stanza on
your dsm.sys, it may be different of nodename.
Or, you can make use of two option files:
---
dsm.opt (content):
servername DOMSRV1
---
My student Solaris Domino servers have 19-stanzas / node names/definitions
(for 6-Domino instances) in /usr/bin/dsm.sys. 1-OS backup, 6-Daily
Incremental, 6-Weekly Selective, 6-Archive Logs !
Farren Minns <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager"
01/27/2006 11:20 AM
Please respon
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
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
Farren,
All you need to do is follow the instructions for setting up a client node
and just give it a different name and a different dsm.opt file. So for
example you already have abcdefg as a node name with a opt file called
dsm.opt. Create a second client called abcdefg1 with an opt file called
d
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 Ho
Thanks again Del
That does sound like a better way forward, but can someone point me in the
right direction of information on how to configure two TSM clients
(nodenames), on one machine. This is not something I am familiar with? I'll
start browsing the manuals I have anyway but first hand experie
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
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 lon
Check "Retextra" option on copygroup too.
On 1/26/06, Farren Minns <[EMAIL PROTECTED]> wrote:
> Hi all
>
> A user is trying to restore a lotus domino database on a Windows NT server,
> and when we look at active/inactive files, there are only five (we do full
> backups every weekend). So, my quest
Ok, so now I know why we are only seeing the 5 files. But this has lead
management to ask if this system of backing data up is really the best way
forward. Sadly for me I wasn't involved in the set-up of the domino clients
or the nature of the data being backed up, so I had no way of knowing there
Hi Farren,
Right. RETEXTRA says how long to keep the "inactive" versions.
If you want to keep your database backups based on time,
(which many customers do for Domino and Exchange, for example),
you should set VEREXISTS to Nolimit and VERDELETED to Nolimit,
and set the RETEXTRA and RETONLY to the
Aaah, does the 'retextra' option override the 'versions data exists'? The
'retextra' for the default backup copy group is 30 and the 'versions data
exists' is set to 7. But I assume if the databases are only backed up fully
each week, there would never be any more than 4-5 active/inactive copies?
Hi Farren,
Look in the DSM.OPT file for Data Protection for Domino.
Are there any INCLUDE statements that are binding the backups to
a different management class?
If not, check to see what the default management class is for the
Data Protection for Domino NODENAME. It may have a different
default
15 matches
Mail list logo
