AW: synthetic fullbackup
Hi, thanks a lot for your tips. With all of your mentioned hints we go to the right direction. But I think that there is still room for doing it better (VERITAS for ex. has to de-DUPLEX their tapes after the backup_process to be able for an acceptable fast restore). Our envir: - TSM Server: 4.2.2.3 on zOS 1.2 (we plan to migrate to TSM 5.1) - STGPool(s): virtual tapes (Virtual Storage Manager from STK) - we are backing up to tape (if all ACTIVE versions are on disk, the problem of scattered versions may be not serious for restores (?)) remarks for MOVE NODEDATA: I think ALL versions are moved - we need quite a lot of storage if we maintain many versions. thanks very much werner -Ursprüngliche Nachricht- Von: Halvorsen Geirr Gulbrand [mailto:[EMAIL PROTECTED]] Gesendet am: Mittwoch, 18. Dezember 2002 14:44 An: [EMAIL PROTECTED] Betreff: Re: synthetic fullbackup Hi Werner, we might need some clearifying of your setup. What is your server version? Are you backing up to tape, or disk? Generally I can say this: If you are running TSM v. 5.x you have the possibility to use MOVE NODEDATA, which moves data for one node to another storagepool (from tape to disk), and then start your restore from the diskpool. It may sound strange, because you move the data twice, but often, you have a delay between the time you decide to restore, until you actually start the restore (f.ex. in a disaster recovery situation, where you have to get new hardware, install OS + TSM client software, before you start the restore). In this interval, you can start to move data from tape to disk, and the subsequent restore will be alot faster. The other possibility is to use collocation by filespace. Different filespaces from the same server will be collocated on different tapes, enabling you to simultaneously start a restore for each filespace. This helps reducing restore times. Third option is using backupsets, which can be created just for active files. Then you will have all active files on one volume. Others may also have an opinion on best approach to solve this. I have just pointed out some of TSM's features. Rgds. Geirr Halvorsen -Original Message- From: Schwarz Werner [mailto:[EMAIL PROTECTED]] Sent: 18. december 2002 14:08 To: [EMAIL PROTECTED] Subject: synthetic fullbackup We are looking for a solution for the following problem: During a restore of a whole TSM-client we found that the needed ACTIVE backup_versions were heavy scattered around our virtual tape-volumes. This was the main reason for an unacceptable long restore-time. Disk as a primary STGPool is too expensive. Now we are looking for methods to 'cluster together' all active backup_versions per node without backing up the whole TSM-client every night (like VERITAS NetbackUp). Ideally the full_backup should be done in the TSM-server (starting with an initial full_backup, then combining the full_backup and the incrementals from next run to build the next synthetic full_backup and so on). We already have activated COLLOCATE. Has anybody good ideas? thanks, werner
AW: synthetic fullbackup
Hi Richard thanks for your hints. We still hope on a solution that makes us happy. The idea with BackupSet is theoretically the closest one. But I heard from people with experince, that (i) its not so easy to restore a client with the newest backupversions and (ii) we have the time-problem moved to the process GENERATE BACKUPSET (collect/consolidate all newest versions). Regards, werner -Ursprüngliche Nachricht- Von: Richard Sims [mailto:[EMAIL PROTECTED]] Gesendet am: Mittwoch, 18. Dezember 2002 15:21 An: [EMAIL PROTECTED] Betreff: Re: synthetic fullbackup We are looking for a solution for the following problem: During a restore of a whole TSM-client we found that the needed ACTIVE backup_versions were heavy scattered around our virtual tape-volumes. This was the main reason for an unacceptable long restore-time... Werner - As Geirr said, Backupsets are the optimal solution but, as all solutions, will require extra processing time. Another approach is to exploit the often-unexploited MIGDelay value, on the primary tape storage pool. Try to match that value to your dominant Copy Group retention value, and migrate older files to a next, tape storage pool, and let reclamation naturally bring bring newer files closer together. This should get inactive versions out of the way. The cost is extra tape data movement. There is no ideal solution. Opportune full backups (weekend?) will get you closest to what you want. Richard Sims, BU
Re: AW: synthetic fullbackup
How about using the Policy Domain to schedule a backup every so often. We are thinking of doing this and changing the Copy Mode (in the Backup Copy Group) to Absolute causing the backup to be a full and this will bring the node date closer for faster restores. Thank You, Bill Rosette Data Center/IS/Papa Johns International WWJD Schwarz Werner Werner.Schwarz@BTo: [EMAIL PROTECTED] EDAG.CH cc: Sent by: ADSM: Subject: AW: synthetic fullbackup Dist Stor Manager [EMAIL PROTECTED] .EDU 12/18/2002 10:09 AM Please respond to ADSM: Dist Stor Manager Hi Richard thanks for your hints. We still hope on a solution that makes us happy. The idea with BackupSet is theoretically the closest one. But I heard from people with experince, that (i) its not so easy to restore a client with the newest backupversions and (ii) we have the time-problem moved to the process GENERATE BACKUPSET (collect/consolidate all newest versions). Regards, werner -Ursprüngliche Nachricht- Von: Richard Sims [mailto:[EMAIL PROTECTED]] Gesendet am: Mittwoch, 18. Dezember 2002 15:21 An: [EMAIL PROTECTED] Betreff: Re: synthetic fullbackup We are looking for a solution for the following problem: During a restore of a whole TSM-client we found that the needed ACTIVE backup_versions were heavy scattered around our virtual tape-volumes. This was the main reason for an unacceptable long restore-time... Werner - As Geirr said, Backupsets are the optimal solution but, as all solutions, will require extra processing time. Another approach is to exploit the often-unexploited MIGDelay value, on the primary tape storage pool. Try to match that value to your dominant Copy Group retention value, and migrate older files to a next, tape storage pool, and let reclamation naturally bring bring newer files closer together. This should get inactive versions out of the way. The cost is extra tape data movement. There is no ideal solution. Opportune full backups (weekend?) will get you closest to what you want. Richard Sims, BU
