If you want to maintain all the schedules that go with the correct node with the correct drive letters for his 75 nodes.... And when an admin adds a drive to a node without letting you know? Or removes one and now your schedules fail because D:\*.* doesn't exist? Whose fault does that end up being when they can't restore the data you said you were archiving for them?
And if your requirements are that you be able to BMR a box to a monthly state, archive is out of the question. I would sooner use archive, don't get me wrong, but there's just not a DOMAIN that you can specify to archive and have it pick up everything in that DOMAIN. Like backup. With changes when those pesky admins change things and don't communicate it back to you. 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 9:53 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 William Boyer >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. ...and the problem with that is...? -- 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
