Geoff and Tab,
This is best solved at the Domino side.
Geoff, it looks to me like your Domino people are trying to make you use
your disk rather than buying some more of their own.
Caveat: I was once mooted to assist with Domino Admin here and did the
Install and Maintenance courses at V5, but I have *never* administered it
in anger.
Domino's great strength is distributed database updates. To solve the
backup problem satisfactorily for both parties, set up another domino
server. This can be on an existing Domino box, the TSM box or even hew
hardware. Create a replica of the database in question with push
replication from the primary server to this new "backup" server. Once the
initial replication is complete, schedule a push replication from primary
to backup at appropriate frequency.
When you need to do your TSM backups,
either take down the backup server (or maybe just close that database) and
backup the underlying files
or backup with TSM for Notes so that you can restore individual items
The primary server continues to run completely uninterrupted and you get a
clean backup. The next replication after the backup server comes back on
line will catch up any missed entries.
Talk to your people about it.
Regards
Steve Harris
AIX/ADSM/Oracle/HACMP Guy
The Wesley Hospital, Brisbane Australia.
Tab Trepagnier <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 11/10/2000
06:57:47
Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:
Fax to:
Subject: Re: Notes/Domino Agent again
Gill,
We are trying to find ways of dealing with R5 also. One thought: can you
ARCHIVE the "critical" database with a 1 day expiration?
Our experience backing up Notes DBs with ADSM 3.1 and Notes R4 hasn't been
good.
We have a hub/spoke Notes arrangement and all backups are done from the
hub. It
probably has 500 databases on it. With the amount of data flowing from
that
server to the ADSM server, on occasion a network packet would get dropped
and
the session would restart. Normally on an incremental, the job will pick
up
where it left off. But not with Notes because the background indexer has
already touched all the DBs that were backed up during the previous pass.
When
the ADSM client does its compare, it sees the DB file has changed from a
few
minutes ago, and starts again from the beginning!
We are currently using the Notes Agent for our R4 databases and have
resorted to
scripts that kill the R5 service prior to incremental backup. That's the
only
way that we know to take the indexer out of the picture. Then we restart
the
service at the conclusion of the backup.
I would have to blow a gasket if my management insisted on incremental
backups
of all those DBs for the reasons I cited earlier.
As an aside, you also wrote:
"This is just a matter of people not setting up their Outlook correctly. It
can do a lot of things, even though it's a Microsoft product, you just need
to take the time to set it up properly. If they would take the time the
list
wouldn't get them and neither would we."
Notes has that feature also, and in fact, (I think) I've told my Notes
client to
NOT send "out of office" replies to the list. Please let me know if I've
goofed
up.
Good luck.
Tab Trepagnier
Laitram Corporation
"Gill, Geoffrey L." <[EMAIL PROTECTED]> on 10/10/2000 03:19:19 PM
Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc: (bcc: Tab Trepagnier/Corporation/Laitram/US)
Subject: Notes/Domino Agent again
Ok, so I got out of this meeting after saying my peace and everyone wants
to
know why I'm being such an @#$ $^&%. Honestly I don't care, if people tell
me something doesn't work but can't prove where, it just tells me they
don't
like it.
Since the box is not R5 we can't use the new version, and since they don't
want to use the old one they'll be backing up an open database, with lots
of
users probably accessing the database during the day. They expect it to be
usable if they need to do a restore. When I said there is no guarantee the
backup will be any good I got a bunch of looks like, how can that be
possible.
Enough of that and here is a question. For now we will be backing up only 1
database at about 1.2GB, until someone else feels like they have a mission
critical database that needs to be backed up every 5 minutes. I'm guessing
the only way to get hourly backups between 6am and 6pm Monday to Friday is
to run a schedule in at on that box. Unless someone else knows a better way
to do that???
Is it possible to "NOT" have this data go to tape and just be purged off
the
disk pools? Since a regularly nightly backup runs at 9PM I'd rather not
have
ADSM track those files. What could I run in a script, at say about 8 PM?
Those disks should be empty of files since I "ONLY" have notes going to
their "own DPOOL" and they don't start backups till 9PM. But if not, is it
possible to run a delete on just that file(S)? I'd also rather not create
another node/domain/management class/whatever whatever..... I just want
backups on disk to be deleted at the end of the day, but I doubt I'll be
able to get all of them since ADSM will be doing it's thing during that
same
time frame. At 11:30 ADSM migrates to tape so some of those files are bound
to get moved, and the rest happens earlier in the morning.... Am I correct?
Versions is set to 45 for them, believe it or not, that's a heck of a lot
of
data.
Help is always appreciated...
Thanks,
Geoff Gill
NT Systems Support Engineer
SAIC
Computer Systems Group
E-Mail: [EMAIL PROTECTED]
Phone: (858) 826-4062
Pager: (888) 997-9614
===========================================
This email message has been swept by
MIMESweeper at The Wesley Hospital - Australia
Although this email has been scanned for Viruses please
ensure that due care is taken and correct virus management
procedures are maintained.
===========================================
