Consider then setting up the policy indicating how many version to keep
(and if you want to restore to any day, a full month back, you'd have to
make that 31), then enabling collocation (for 1 separate storage pool that
all the nodes that a full restore is expected to happen can use) (and in
your case, it sounds like a certainty), so all the files go to a minimum
set of tapes (helping making the restore time its smallest possible). That
would be a better startup for a solution that doing a daily selective.
With the above suggestion, you would at least would insure only the
necessary (updated files) get transferred over your network (avoiding
possible flooding, and possible backup window over-run), and reduce the
number of tapes you need to keep the exact same data. (TSM knows what
files it needs to restore when you tell it to what day you want to get back
to). [not to mention reduce your total tape expenditure - doubling your
saving since all that data gets copied for your offsite vaulting]
I usually sit down with the user, and try to establish what his real needs
are, probably just needs a few version of each files, and an archival
process (and the archival process runs at the TSM server.... [assuming 3.7+
release] and so not getting transferred over the network each day) and it's
probably the better solution than doing a selective as suggested.
I hope I didn't offend you. I believed my comment would be humorous for
those that know *SM... and at the same time trigger what you did: you to
provide more details. I would not have left my comments unanswered either
had I been in your shoes.
I hope my comments help you discover the better solution for your
environment.
Best Regards,
Serge Gaudet, CMI
Consultant
"MC Matt Cooper
(2838)" To: [EMAIL PROTECTED]
<Matt.Cooper@AMGREE cc:
TINGS.COM> Subject: Re: how is a weekly FULL
bkup scheduled?
Sent by: "ADSM:
Dist Stor Manager"
<[EMAIL PROTECTED]
DU>
31/10/2000 11:54 AM
Please respond to
"ADSM: Dist Stor
Manager"
Why is this so strange? I need the data for many servers for a months
worth
of data. I have to be able to restore to any date they (user) says. We
keep the tapes offsite and exercise our DR plan yearly. I will be
restoring
whole servers. Not a file here and there. I would think a full backup and
a year of incrementals could get a little ugly.
Matt
-----Original Message-----
From: Serge Gaudet/EIG [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, October 31, 2000 11:00 AM
To: [EMAIL PROTECTED]
Subject: Re: how is a weekly FULL bkup scheduled?
It's gotta be a tape stress test in progress..... or a validation of the
reclamation process....
I don't know anyone in their right mind who would want to do such a
thing...
...but then again, it could be just to satisfy a paranoid ex-arcserv like
client user!
Serge Gaudet, CMI
"Couldn't help the wise crack - Have a great day"
Larry Way
<Larry.Way@TR To: [EMAIL PROTECTED]
W.COM> cc:
Sent by: Subject: Re: how is a weekly
FULL bkup scheduled?
"ADSM: Dist
Stor Manager"
<[EMAIL PROTECTED]
RIST.EDU>
31/10/2000
10:49 AM
Please
respond to
"ADSM: Dist
Stor Manager"
My question to you is why would you want to ?
>>> [EMAIL PROTECTED] 10/31/00 07:37AM >>>
Check "selective" backups.
"[EMAIL PROTECTED]/P=Internet/A= /C=us" on 10/31/2000
10:32:55 AM
Please respond to "[EMAIL PROTECTED]/P=Internet/A= /C=us" @
X400
To: "[EMAIL PROTECTED]/P=Internet/A= /C=us" @ X400
cc:
Subject: how is a weekly FULL bkup scheduled?
Hello,
I am trying to figure out how to set up a scheduled job that will
do
a Full backup every weekend of a client. I will be running daily
incrementals and will have the POLICY set to keep 4 copies of the backup.
I
just don't see how to get the client to do a full backup after the intial
has been done. What am I missing?
Matt
