Hi Serge -
I have version 3.7.2 at my server, soon to upgrade to 4.11 - Anyway, I
thought that when an archive was created, it has to go out to the client,
thus, it would put some burden on the client and network, or am I missing
something? I want to implement archiving, but this is one of the problems
that I am facing. I know backupsets are generated at the server end, but I
am not pleased as to the way it needs to be done. For instance, it is not
real easy to retrieve them. If I am only doing a filespace that is say 5
gigs, then it uses a whole tape and I cannot use the tape anymore. These
are just to mention a few.
Therefore, I have been looking at archiving - but I have been looking at 2
things - 1, the size of my database will probably grow at a super fast rate
as we need to keep archives on a monthly basis for 7 years and 2, the
network traffic. If I am looking at something wrong, someone please tell
me. Thanks
-----Original Message-----
From: Serge Gaudet/EIG [mailto:[EMAIL PROTECTED]]
Sent: Friday, November 03, 2000 12:55 PM
To: [EMAIL PROTECTED]
Subject: Re: retention
RECLAIM does not address the issue. It only prevents the TSM server from
moving the active copies around to help reduce the number of tapes the pool
uses following an inventory expiration process (and is an option of the
storage pool configuration should you want to change it.... More info: Do
an "help update stg" on your admin interface).
What you want to do, the way you stated it, is set the REUSEDELAY=360 (also
a parameter of the storage pool configuration). However, I don't think
that is what you REALLY want to do. You should establish an ARCHIVE policy
for your environment, and start using the archival process instead. At TSM
3.7+, the archives are generated and handled at the TSM server. Both the
client and network don't get additionally burdened by this process.
Food for thought: The REUSEDELAY=360 will get you to spend $$$$$ in tapes
since you will not going to be able to recall ANY tapes freed up by
reclamation for at least a year for this pool...
Serge Gaudet, CMI
Consultant
"Talafous,
John G." To: [EMAIL PROTECTED]
<Talafous@TIM cc:
KEN.COM> Subject: Re: retension
Sent by:
"ADSM: Dist
Stor Manager"
<[EMAIL PROTECTED]
RIST.EDU>
03/11/2000
12:31 PM
Please
respond to
"ADSM: Dist
Stor Manager"
The quickest way that comes to my mind is to keep the RECLAIM percent at
100
for copypoolextra.
But, why do it anyway?
John G. Talafous IS Technical Principal
The Timken Company Phone: (330)-471-3390
P.O. Box 6927 Fax : (330)-471-4034
1835 Dueber Ave. S.W.
Canton, Ohio USA 44706-0927
[EMAIL PROTECTED] http://www.timken.com/
-----Original Message-----
From: Shekhar Dhotre [mailto:[EMAIL PROTECTED]]
Sent: Thursday, November 02, 2000 11:36 AM
To: [EMAIL PROTECTED]
Subject: retension
Hi all,
I have defined a extra copypool named copypoolextra other than tapepool
and
copypool ,
i want to set 360 days retension on this copypool , what is the command or
reference Book ?
Thnaks in advance
