Hi Todd! > I based the increase in DB size on the "600k of database space per object stored by TSM" rule. If I remember it correctly, it's 600 bytes, not 600Kb. Kindest regards, Eric van Loon KLM Royal Dutch Airlines
-----Original Message----- From: Todd Lundstedt [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 30, 2002 16:18 To: [EMAIL PROTECTED] Subject: Minimizing Database Utilization TSM 4.2.1.7 running on AIX 4.3.3 Database is 8GB, 66.2% utilized. DBVols are on an ESS shark. We have an application server that the admins would like to backup on the TSM server. The problem is, after I analyzed the backup needs of this one server, my database would grow an additional 300GB, and increase in size an additional 50-100MB each day (in actuality, it may be an additional 66% growth because I can't recall if I calculated my copy storage pool needs). They have a folder on this server (NT4.0 running a PACS system, by Fujimed, I think) that contain over 240K+ files, each file in it's own folder (so 240K+ folders) each uniquely named, never changing, and almost all of the files less than 1K in data size. There are other similar folders on this server that would significantly increase the size of the database, but not as much as this one folder. I based the increase in DB size on the "600k of database space per object stored by TSM" rule. I told the admin there would be no way I could back that data up unless he created a zip file (or something similar) of all those directories/files first. He is looking into this possibility. Is there any other way to do this without increasing the size of my database more than the size of the files being backed up (what is that... 3 million times more?)? Thanks in advance for your help. Todd Lundstedt Technical Specialist Via Christi Information Management Services [EMAIL PROTECTED] ********************************************************************** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. **********************************************************************
