How about creating a new primary pool and copy pool set. When nearly
all of the data has expire out of the original set, move the remaining
data from the old primary pool to the new primary pool and backup to the
new copy pool. Let the expiration reduce amount of data to copy.
If you define a
Hi guys, can any one tell me what client version to install on hp-ux
B.10.20.
As tsm client version 3.7 and above available in tsm ftp site are only
for hp-unix 11 and above say 11.x.
With Best Regards,
Sandeep Jain
** Legal Disclaimer
Hello Sandeep
I believe that client version 3.1 was the last client level that works on hp/ux
10.20. There was a thread model change in the client which was not supported on
hp/ux 10.20.
We have one last 10.20 client on a tsm 5.2 server.
len
-Original Message-
From: ADSM: Dist
Hi len ,
Oh! So that is very old version. So this must be last stable
version for hp-unix 10.20. so at urs end is it working fine, what backup
are u performing on this server ? have u any TDP installed or doing B/A
client backup.
With Best Regards,
Sandeep Jain
100gb is still way too small.
Your basic problem is that every day you will have 1TB of data arriving,
and you've got to put it somewhere. What you want to avoid is having
anything in your TSM server that will slow down the backup. The optimal
size is, of course, 1TB. This figure comes from the
Roger,
The 100 GB was the size for one volume in the disk storage pool and not the
total size. So you end up with 10 volumes for each TB disk pool.
Kurt
Van: ADSM: Dist Stor Manager namens Roger Deschner
Verzonden: za 3/12/2005 19:57
Aan:
