I don't want to disagree with the 'large enough for 1 nights dump'
rule of thumb but that's just it: its a rule of thumb.
I thinks in terms of utilizing resources to the 100% level.
(except that there needs to be breathing room for things like restores)
First off:
GET A COMMITTMENT from those
migrating it.
Otherwise, you have to copy from tape to tape rather than from disk to tape.
(Of course, even after migrating one must backup the tape to tape pool to be
sure you get everything!)
Any optimum diskpool size will depend on how much data you normally receive
on any given day. With 700
rives.
just things I've run into
later,
Dwight
-Original Message-
From: Gerard M Hanway [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, October 24, 2000 9:54 AM
To: [EMAIL PROTECTED]
Subject: Optimum diskpool size
I look after the companies TSM environment. Approx 700 servers back up an
IL PROTECTED]
>Subject: Optimum diskpool size
>
>
>I look after the companies TSM environment. Approx 700 servers
>back up an
>average of 60-70gb per night. The ADSM server runs on OS/390
>with 500 OS/2 and
>200 NT clients. I have 2 primary disk pools, one of 45GB for the N
I look after the companies TSM environment. Approx 700 servers back up an
average of 60-70gb per night. The ADSM server runs on OS/390 with 500 OS/2 and
200 NT clients. I have 2 primary disk pools, one of 45GB for the NT
servers(colocated) and one of 4GB for the OS/2 servers(non colocated). HIMIG
