Not to mention that you'd have to do this on a copy pool, as this is for DR
reasons. Also assuming that this copy pool will be offsite. So you'll be
sending volumes offsite daily with very few files on them. Which, if your
reclaim threshold is set to a normal 60%, will cause the tapes to be
reclaimed the moment they're ejected to go offsite. Which will cause you
to use the same number of tapes again, one per filespace.
Now, at the DR site, you have to have at least the same number of tape
drives available as filespaces to make this work. Fairly expensive for a
single client restore, not practical for multiple clients, who will also
want tape drives.
The best thing I've found, through my experience, is to take periodic "full
backups" (I do archives), then, at the DR site, restore (retrieve) that
backup, then pull the incremental backups since then. Using a normal copy
pool (no collocation), and staggering the days of the "full" backup, you
can keep the clients from fighting for tapes and keep your drives at
maximum utilization, as well as reducing the number of tapes mounted to
restore a client.
Nick Cassimatis
[EMAIL PROTECTED]
Today is the tomorrow of yesterday.
Doug Thorneycroft
<dthorneycroft@la To: [EMAIL PROTECTED]
csd.org> cc:
Sent by: "ADSM: Subject: Re: TSM Client Acceptor
Service
Dist Stor
Manager"
<[EMAIL PROTECTED]
.EDU>
02/12/2002 04:08
PM
Please respond to
"dthorneycroft@la
csd.org"
Look up colocation in the administrator guide. You set colocation
at the sequential storagepool, not at the client.
Setting colocation to filespace will have a big impact on your tape
usage and processing, so be sure to read everything in the guide first.
-----Original Message-----
From: Adams, Matt (US - Hermitage) [SMTP:[EMAIL PROTECTED]]
Sent: Tuesday, February 12, 2002 12:58 PM
To: [EMAIL PROTECTED]
Subject: TSM Client Acceptor Service
Hi...
I am wanting to configure one of our larger file servers to have
collocation
by filespace to make DR recovery faster. The easiest thing that comes to
mind is to have separate nodenames for each filespace(logical drive). So I
guess I will have to have a separate backup schedule per nodename,
therefore
separate option files and separate services to manage the schedules, logs
etc. I am new to setting up and using the Client Acceptor service. I used
the wizard to setup and it seemed straight forward. I was able to use
different service names, option files, log files etc.
My question is, do I use the same Client Acceptor Name as it is prompted
during the setup wizard so that it manages all the services?? How do I
know
that it is working?? I am assuming it could handle backup schedules at the
same time?? (If I wanted all the backups for this machine to kick off at
the
same time?)
Is there an easier way to accomplish this??
Thanks,
Matt
- This message (including any attachments) contains confidential
information
intended for a specific individual and purpose, and is protected by law. -
If you are not the intended recipient, you should delete this message and
are hereby notified that any disclosure, copying, or distribution of this
message, or the taking of any action based on it, is strictly prohibited.
