The TSM server admin needs to be aware and in contol of what is happening in the TSM environment. It sounds like you may be running unrestricted client registration and client polling for backups. So the first thing I would do is make sure that no client can be registered without having good estimate of initial backup and likely change rate. I would also switch to schedmode prompted, so you can contol the flow of clients backing up to the diskpools over your backup window. The ideal is that you should have diskpool large enough to hold complete night's backup. If this is a problem then you need to trigger migration at a low threshold to ensure that diskpool always has enough space to receive your large databases.
Michelle Wiedeman <[EMAIL PROTECTED]> on 12/16/2002 02:14:11 PM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: (bcc: John Naylor/HAV/SSE) Subject: extra diskpool or seperate network? ********************************************************************** The information in this E-Mail is confidential and may be legally privileged. It may not represent the views of Scottish and Southern Energy plc. It is intended solely for the addressees. Access to this E-Mail by anyone else is unauthorised. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Any unauthorised recipient should advise the sender immediately of the error in transmission. Scottish Hydro-Electric, Southern Electric, SWALEC and S+S are trading names of the Scottish and Southern Energy Group. **********************************************************************
hi all, to start with the details: tsmserver=adsm3.1 os = aix4.3.3 ML 10 clients: 4 aix 4.3.3 servers with progress databases running. (aprox. backup each night 300GB) My problem: the databases seem to fail a lot on diskpool space problems in backup, this is due to the ever changing suroundings here. new costumers create new tsm clients. The surroundings change so much and so often that its undoable to keep track of the diskpool and tapepool size (when to enlarge etc.) The costumer is now fed up with it and wants a solution for this problem, now they are our biggest clients so this is important to us. I came up with two solutions. 1. I create a seperate diskpool for these clients to write to. 2. I create a seperate network (SAN) to the tsmserver for these four clients, with their own diskpoolspace. 3. I create a policy with the priority option on 1 or 2 Now my question to you is which of the above is best? and why? thnx a lot mi�helle
