- AFAIK, no. You can specify which volumes to be used for backupset generation but they cannot be reused without overwrite. Will this be resolved in next version(s) is another question. - I do not know why you are not satisfied by the command line. If you look at Andrew Raibeck's signature - "The command line is your friend". And I can confirm this is true for me. However some of Tivoli Enterprise products have tasks which can be done only through GUI but not CLI. And this is nearly impossible to automate. - What is your problem with backups during archive? Is it time constrain, lack of bandwidth, tape drives occupation, etc. ? If this is a technical problem the list can help you. But if it needs more resources then it is for managers and purchasing department.
Zlatko Krastev IT Consultant Joe Cascanette <[EMAIL PROTECTED]> on 30.11.2001 17:46:21 Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject: Re: Large TSM database due to no. of files and versions Is it possible to assign a group of tapes to hold a group of backup sets?. I have 5 servers that I am creating backup sets on a daily basis (collocation is turned on, and I have 10 drives, so the creation time frame is pretty fast). But can I bundle all these servers onto a few tapes? My over all goal (when Tivoli fixes the backup set option and adds the ability to drill down the backup set with the gui) is to use backup sets in place of monthly archives. I don't know about anyone else, but I am unable to perform my daily backups during an archive weekend. Changing to Backup Sets will fix this problem. Joe Cascanette The Cumis Group Limited -----Original Message----- From: Zlatko Krastev/ACIT [mailto:[EMAIL PROTECTED]] Sent: Friday, November 30, 2001 8:54 AM To: [EMAIL PROTECTED] Subject: Re: Large TSM database due to no. of files and versions If your users want to be able to restore *EVERY* version created during the month you need VERExists=NOLimit and VERDeleted=NOLimit. And with backupset generation on the first day (or night ;-) of a month you can keep RETExtra=31 (hey friends, some months are longer `-) and RETOnly=31 (or more). And just the backupset retension to be 366 days (remember Y2k `-). But the backupsets are treated as single object in TSM DB and do not occupy too much. Backupsets occupy separate volumes and do not mess with other backups/archives for this and other nodes. So backupsets generation will improve restore time of other nodes (slightly) and this node (much, much more). And creation of archives is done with all archived data traversing the net again ! Zlatko Krastev IT Consultant Kilchenmann Timo <[EMAIL PROTECTED]> on 26.11.2001 16:02:45 Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject: Large TSM database due to no. of files and versions Dear all, We have the following problem: We are backing up some large Novell servers (more than 1 million files per Server). The users want to be able to restore every version of a file 30 days back and every version of a file at the end of a month 12 months back. In order to meet these requirements at least partly we set the backup management class as follows: Versions Data Exists: 10 Versions Data Deleted: 5 Retain Extra Versions: 366 Retain Only Version: 366 Because of these settings, the TSM database grew to 15 GB in the last 6 months and is growing fast even further. Restore performance is bad for these servers as well. Is there a possibility / idea to get over this apart from using archives? Is it possible to create archives (not backupsets) from existing data on the TSM server? Any idea is welcome! Eurodis Schweiz AG Data Division Timo Kilchenmann Systems Engineer ----------------------------------------------------------- Timo Kilchenmann E-Mail [EMAIL PROTECTED] Eurodis Schweiz AG Phone +41 1 843 34 91 (direct) Bahnstrasse 58/60 or +41 1 843 32 32 CH-8105 Regensdorf Telefax +41 1 843 34 24 Switzerland Mobile +41 79 417 43 55 http://www.eurodis.ch -----------------------------------------------------------
