Mike you don't have to move your database to enlarge it. if you add disk space you can create new volumes and then you just extend the database over these new volumes to gain the extra space that you need.
Ie: in our case we had to increase our database from 10 GB to 20 GB so this is what we did. Database Volumes Volume Name (Copy 1) Volume Name (Copy 2) Volume Name (Copy 3) E:\DB1.DSM F:\DB1.DSM E:\DB2.DSM F:\DB2.DSM Hope this helps your comfort zone a bit. Also with our system because we are a banking system we have to do monthly archives and retain them for 7 years by law, so we have a separate policy for archive pools and we move these out when they are full to a shelf in our server room. This is working well for us as it does not take up all the slots in the library with archived tapes. The only downside to this is when you do a retrieve you have to watch for TSM asking for specific tapes to be put in from the shelf and then make sure to move them back out again after the retrieve process. A bit more work but it's not been bad. Tammy Schellenberg Systems Administrator, MCP Prospera Credit Union email: [EMAIL PROTECTED] DID: 604-864-6578 -----Original Message----- From: Mike Bantz [mailto:[EMAIL PROTECTED] Sent: Friday, July 16, 2004 7:40 AM To: [EMAIL PROTECTED] Subject: Re: Thoughts on Monthly Archives How would I find that out? We're not even doing monthly backups yet - just trying to see the impending impact. >From what I've read here so far: Much much more database usage (Obviously) much more tape usage I guess I'm just trying to deal with a TSM deployment that needs to be rebuilt in order to handle this operation. Our database is on a 15gig partition with no chance of extending that. We'll have to purchase two more drives and move it to those drives, which'll entail MOVING the database (this scares me...) - mike -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Steve Harris Sent: Thursday, July 15, 2004 7:53 PM To: [EMAIL PROTECTED] Subject: Re: Thoughts on Monthly Archives Gordon, I've though of doing this in the past, but, if we postulate a random daily change rate, then the chances of a particular file being changed in any one month are at 1% , 1-(0.99**30), or about .25 at 2%, 1-(0.98**30) , or about .45 at 3%, 1-(0.97**30), or about .60 (Please feel free to correct my maths if I'm wrong - probability was never my strong point) Now, of course its often the same files which change day after day, so real experience should be better than this, but at the time, I decided that the overhead of mainitianing two TSMs (and two clients per node) wasn't worth the benefit, and went with archives. Can I ask what rate of change you are seeing on your monthly backups? Thanks Steve Steve Harris AIX and TSM Admin Queensland Health, Brisbane Australia >>> [EMAIL PROTECTED] 16/07/2004 11:22:20 >>> We use to do full Monthly archives of all our important data on our servers but our TSM database was growing too rapidly, especially when we have to retain our backups for 7 years. What we ended up doing is registering a whole new alternate set of nodes specifically for Monthly backups and now just run incrementals. Our database doesn't grow as rapidly anymore and we don't chew through as many tapes. I'm thinking of now creating a second TSM instance and have that running exclusively for our monthly backups to take the load off our day to day operations. Gordon Woodward Wintel Server Support [EMAIL PROTECTED] Sent by: To: [EMAIL PROTECTED] [EMAIL PROTECTED] cc: EDU Subject: Thoughts on Monthly Archives 16/07/2004 07:00 AM Please respond to ADSM-L We are implementing the following: Monthly FULL backups, saved for 4 years for document retention purposes. Backupsets are not viable, as a restore would be a pain. So it looks like we're going to do this with archives. My idea is to create another storage pool with it's own media, another domain with it's own management class (we really need only one: save 1 version of this file for 4 years), and remove that media once the archive runs. Anyone care to comment on if this is the best, easiest, way to do this? Or comment on what to expect with things like tape usage and database size? We're currently at 57% of a 12gig database. Thanks in advance!!! Mike Bantz Systems Administrator -- This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. **************************************************************************** ******* This email, including any attachments sent with it, is confidential and for the sole use of the intended recipient(s). This confidentiality is not waived or lost, if you receive it and you are not the intended recipient(s), or if it is transmitted/received in error. Any unauthorised use, alteration, disclosure, distribution or review of this email is prohibited. It may be subject to a statutory duty of confidentiality if it relates to health service matters. If you are not the intended recipient(s), or if you have received this email in error, you are asked to immediately notify the sender by telephone or by return email. You should also delete this email and destroy any hard copies produced. **************************************************************************** ******* This email and any files transmitted with it are confidential and are intended solely for the use of the individual or entity to whom they are addressed. If you are not the original recipient or the person responsible for delivering the email to the intended recipient, be advised that you have received this email in error, and that any use, dissemination, forwarding, printing, or copying of this email is strictly prohibited. If you receive this email in error, please immediately notify the sender. Please note that this financial institution neither accepts nor discloses confidential member account information via email. This includes password related inquiries, financial transaction instructions and address changes.
