Hello,
I would do some tests to see how quickly you are able to migrate from the
diskpool with single or multiple migration processes, and also to see how
quickly your diskpools fill up, and take it from there. The only other thing
I would be aware of is the size of the files being backed up - TSM will only
migrate the file once it has finished backing up, and 6 / 7 clients sending
2GB+ files will fill up a smaller stgpool before migration kicks in.
Matt.
>-----Original Message-----
>From: Gerard M Hanway [mailto:[EMAIL PROTECTED]]
>Sent: 24 October 2000 03:54:PM
>To: [EMAIL 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 NT
>servers(colocated) and one of 4GB for the OS/2 servers(non
>colocated). HIMIG is
>set to 80% on the large pool and usually results is migration
>starting between 2
>and 3am each morning and completing around 9am.
>
>However the storage people have just been in touch wanting to
>know what I am
>doing with so much disc in the large pool. Basically they want
>30gb back leaving
>leaving me with just 15gb. I suspect that things should
>continue to work just
>with migration kicking it a lot earlier however I would
>welcome opinions.
>
>Is there a recommended ratio of disk pool size to amount of
>data backed up. What
>ratio do most people use. Are there quantifable performance
>impacts in running
>migration at the same time as backups. I do know from
>experience that with
>migration starting significantly earlier I can expect a lot of
>additional tape
>mounts. But it might be argued so what.
>Are there any other gotcha's
>
>Gerard
>
>
>
>
>**********************************************************************
>This document is strictly confidential and is intended for use by
> the addressee unless otherwise indicated.
>
>Allied Irish Banks
>**********************************************************************
>
