How would I find that out? We're not even doing monthly backups yet - just
trying to see the impending impact.
>From what I've read here so far:
Much much more database usage
(Obviously) much more tape usage
I guess I'm just trying to deal with a TSM deployment that needs to be
rebuilt in order to handle this operation. Our database is on a 15gig
partition with no chance of extending that. We'll have to purchase two more
drives and move it to those drives, which'll entail MOVING the database
(this scares me...)
- mike
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Steve Harris
Sent: Thursday, July 15, 2004 7:53 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Thoughts on Monthly Archives
Gordon,
I've though of doing this in the past, but, if we postulate a random daily
change rate, then the chances of a particular file being changed in any one
month are
at 1% , 1-(0.99**30), or about .25
at 2%, 1-(0.98**30) , or about .45
at 3%, 1-(0.97**30), or about .60 (Please feel free to correct my maths
if I'm wrong - probability was never my strong point)
Now, of course its often the same files which change day after day, so real
experience should be better than this, but at the time, I decided that the
overhead of mainitianing two TSMs (and two clients per node) wasn't worth
the benefit, and went with archives.
Can I ask what rate of change you are seeing on your monthly backups?
Thanks
Steve
Steve Harris
AIX and TSM Admin
Queensland Health, Brisbane Australia
>>> gordon.woodward AT DB DOT COM 16/07/2004 11:22:20 >>>
We use to do full Monthly archives of all our important data on our servers
but our TSM database was growing too rapidly, especially when we have to
retain our backups for 7 years. What we ended up doing is registering a
whole new alternate set of nodes specifically for Monthly backups and now
just run incrementals. Our database doesn't grow as rapidly anymore and we
don't chew through as many tapes.
I'm thinking of now creating a second TSM instance and have that running
exclusively for our monthly backups to take the load off our day to day
operations.
Gordon Woodward
Wintel Server Support
mbantz AT RSINC DOT COM
Sent by: To:
ADSM-L AT VM.MARIST DOT EDU
[email protected]. cc:
EDU Subject: Thoughts on Monthly
Archives
16/07/2004 07:00
AM
Please respond to
ADSM-L
We are implementing the following:
Monthly FULL backups, saved for 4 years for document retention purposes.
Backupsets are not viable, as a restore would be a pain. So it looks like
we're going to do this with archives. My idea is to create another storage
pool with it's own media, another domain with it's own management class (we
really need only one: save 1 version of this file for 4 years), and remove
that media once the archive runs.
Anyone care to comment on if this is the best, easiest, way to do this? Or
comment on what to expect with things like tape usage and database size?
We're currently at 57% of a 12gig database.
Thanks in advance!!!
Mike Bantz
Systems Administrator
--
This e-mail may contain confidential and/or privileged information. If you
are not the intended recipient (or have received this e-mail in error)
please notify the sender immediately and destroy this e-mail. Any
unauthorized copying, disclosure or distribution of the material in this
e-mail is strictly forbidden.
****************************************************************************
*******
This email, including any attachments sent with it, is confidential and for
the sole use of the intended recipient(s). This confidentiality is not
waived or lost, if you receive it and you are not the intended recipient(s),
or if it is transmitted/received in error.
Any unauthorised use, alteration, disclosure, distribution or review of this
email is prohibited. It may be subject to a statutory duty of
confidentiality if it relates to health service matters.
If you are not the intended recipient(s), or if you have received this email
in error, you are asked to immediately notify the sender by telephone or by
return email. You should also delete this email and destroy any hard copies
produced.
****************************************************************************
*******
|
