D]>
07/19/2004 12:45 PM
Please respond to "ADSM: Dist Stor Manager"
To: [EMAIL PROTECTED]
cc:
Subject: Re: Thoughts on Monthly Archives
> For us, it is the beginning of the Sarbanes-Oxley overhaul. I ask those
same
> questio
Thanks for your input Andy, yes these are all valid points.
The requirement that we have is to be able to go back to the time of a decision and
have available all pertinent information so that the same decision could be made
again. I don't know who the optimist was who wrote the requirement, b
nt for more
disk space is one of the 'dumb idea' entries.
Good Luck -
Tom Kauffman
NIBCO, Inc
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf
> Of Andrew Raibeck
> Sent: Monday, July 19, 2004 12:58 PM
> To: [EMAIL PROT
Raibeck
Sent: Monday, July 19, 2004 11:58 AM
To: [EMAIL PROTECTED]
Subject: Re: Thoughts on Monthly Archives
> I haven't read the SBO requirements, but from our internal auditors,
> it
looks
> like we need to have a good business
> best efforts to keep readable for whatever retenti
> I haven't read the SBO requirements, but from our internal auditors, it
looks
> like we need to have a good business
> best efforts to keep readable for whatever retention period we
publicize.
>
> In working with older tape technology in storing archive tapes, we found
> that 20% of the tapes wer
;
>
> Andrew Raibeck <[EMAIL PROTECTED]>
> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
> 07/19/2004 11:25 AM
> Please respond to "ADSM: Dist Stor Manager"
>
>
> To:[EMAIL PROTECTED]
> cc:
> Subje
that is what the federal regulators requried.
-Original Message-
From: Shannon Bach [mailto:[EMAIL PROTECTED]
Sent: Monday, July 19, 2004 12:09 PM
To: [EMAIL PROTECTED]
Subject: Re: Thoughts on Monthly Archives
For us, it is the beginning of the Sarbanes-Oxley overhaul. I ask those
same ques
004 11:25 AM
Please respond to "ADSM: Dist Stor Manager"
To: [EMAIL PROTECTED]
cc:
Subject: Re: Thoughts on Monthly Archives
Some considerations for long-term archive:
- Much of today's data, as it is used from day to day, exis
Some considerations for long-term archive:
- Much of today's data, as it is used from day to day, exists in some
product-specific format. If you were to retrieve that data, say, 10 years
from now, would you have software capable of reading that data?
- Even if you archive the software, will opera
==> In article <[EMAIL PROTECTED]>, Steve Harris <[EMAIL PROTECTED]> writes:
> There was another management requirement that all production servers be
> backed up in full once per year and that snapshot be kept "forever" - there
> is no reasoning with this, its one of those stupid mandates that ap
.QLD.GOV.AUTo: [EMAIL PROTECTED]
Sent by: cc:
[EMAIL PROTECTED] Subject: Re: Thoughts on Monthly
Archives
U
16/07/2004 11:53 AM
Allen,
Your post got me thinking as to just why I decided what I did ― and now I remember :)
There was another management requirement that all production servers be backed up in
full once per year and that snapshot be kept "forever" - there is no reasoning with
this, its one of those stupid
ECTED]
Subject: Re: Thoughts on Monthly Archives
If you keep the tapes "outside the system", what do you do when there is an
opportunity to change tape technology in 5 years?
How do you migrate that data to new tapes?
[RC]
"Dwight Cook"
To:[EMAIL PROTECTED]
Sent by: "ADSM: Dist cc:
Stor Manager" Subject: Re: Thoughts on Monthly
Archives
<[EMAIL PROTECTED]
>
07/15/2004 05:22
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On
Behalf Of Mike Bantz
>I *love* that TSM is so flexible and I hate that I get to
>agonize and debate
>any changes to it for that very reason. We've been bitten
>really hard in the
>past due to poor planning, so I'm trying to plan for my n
g, so I'm trying to plan for my next 4-7 years now.
:-)
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: Friday, July 16, 2004 10:08 AM
To: [EMAIL PROTECTED]
Subject: Re: Thoughts on Monthly Archives
==> In article <
==> In article <[EMAIL PROTECTED]>, Mike Bantz <[EMAIL PROTECTED]> writes:
> How would I find that out? We're not even doing monthly backups yet - just
> trying to see the impending impact.
Count your incremental size over a series of days, and you'll have a measure
of the instantaneous change r
==> In article <[EMAIL PROTECTED]>, Steve Harris <[EMAIL PROTECTED]> writes:
> 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)
I think yo
--Original Message-
From: Mike Bantz [mailto:[EMAIL PROTECTED]
Sent: Friday, July 16, 2004 7:40 AM
To: [EMAIL PROTECTED]
Subject: Re: Thoughts on Monthly Archives
How would I find that out? We're not even doing monthly backups yet - just
trying to see the impending impact.
>From what I&#
M: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Steve Harris
Sent: Thursday, July 15, 2004 7:53 PM
To: [EMAIL PROTECTED]
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 par
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 t
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 j
Dist Stor cc
Manager"
<[EMAIL PROTECTED] Subject
.EDU>
>>personally I don't like to keep any archived data in an active TSM server
environment that has a retention value of more than 370 days
Can I ask why? This seems like an **awfully** short time...
- mike
one thought...
for clients that require the monthly 4 year archives...
register alternate nodes by the name of _exp
push any data required for long term retention (in the form of either
backups or archives or both) using the client _exp
export that node
remove from environment...
doesn't tak
25 matches
Mail list logo
