How do I go about running a "full archive" on each box such that it gets everything on each drive? Can I use "?:*.*" as my filespec?
An archive won't work for the TDP agents, either. You can't use backupsets for TDP data. Sure, you can generate a backupset for a node/filespace that contains TDP data, but the TDP agent does not understand restoring from a backupset. I had a client with this type of requirement and what we did was to backup each server each month under a different nodename that was registered in a domain where the policy was to keep inactive versions for a year. And to make sure that it was always a FULL backup and not an incremental over last month, the copygroups specified MODE=ABSOLUTE. Be warned that your TSM database will grow a lot! I would very much like to use an ARCHIVE for this, but haven't figured out how to make it do all drives without having to code them in a command script or in the OBJECT= for the schedule. Bill Boyer "Some days you're the bug, some days you're the windshield" - ?? -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Stapleton, Mark Sent: Tuesday, September 13, 2005 5:35 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: generate full backup using backupsets From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Kurt Beyers >Due to SLA agreements a full backup should be taken every month that is >stored offsite for a year. Of course this does not match with the >principles 'incremental forever' and the versioning defined in the >management classes. > >I guess that a full backup can be created from the backups already >residing in the primary storage pool using a backupset. > >Would such a setup be feasible for 75 clients (load on the TSM server, >required time to generate the backupsets, ...)? Can it be used for >backups from a TDP too? Any howto's for the creation of a backupset? A suggestion: Run a full archive of 3 clients each day for a month, so that you can spread out the 75 full backups. Set your archive management class to keep any given archive for a year. Send those archives to a (small) disk pool which in turn is migrated to an archive tape pool. Once a month check those archive tapes out and vault them. After a full 12 months in the vault, that month's tapes can come to the TSM server as scratch tapes. -- Mark Stapleton ([EMAIL PROTECTED]) IBM Certified Advanced Deployment Professional Tivoli Storage Management Solutions 2005 IBM Certified Advanced Technical Expert (CATE) AIX Office 262.521.5627
