Thanks :-)

The exports don't expire :-) That's the fun.... It's the backup that does
the expiration....
So if you import a node, you will get all the data you import, after a
backup the active data could go to inactive and/or expire.
But i guess you only want to import the data to restore it and want to get
rid of it after the restore, so if you don't merge the import, you can
simply delete the imported filespaces after the restore.... so expiration
and mc's are out of the question...

You can use export node's if you want to "backup" a selection of nodes, but
i suggest to use export server if you want to "backup" all the nodes, that's
much more simple... But that's only if you can put the whole set of tapes
back in the library of course....

Regards,
Maurice van 't Loo

----- Original Message -----
From: "Kurt Beyers" <Kurt.Beyers AT DOLMEN DOT BE>
To: <ADSM-L AT VM.MARIST DOT EDU>
Sent: Wednesday, September 14, 2005 4:18 PM
Subject: Re: [ADSM-L] generate full backup using backupsets


Thanks for the feedback so far.

An archive is out of question due to the 'schedule maintenance' that would
be required as William pointed out and due to the bandwith anyway.

But the 'export node' mentioned by Maurice is a possibility that I will try
out further. A good suggestion tht I didn't think yet of.

What happens if the data on the export expires in the TSM database due to
the management class it is bound to. Can it still be imported and bound to a
new management class?

best regards,
Kurt

________________________________

Van: ADSM: Dist Stor Manager namens William Boyer
Verzonden: wo 14/09/2005 13:13
Aan: ADSM-L AT VM.MARIST DOT EDU
Onderwerp: Re: [ADSM-L] generate full backup using backupsets



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:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Stapleton, Mark
Sent: Tuesday, September 13, 2005 9:53 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: generate full backup using backupsets

From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] 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 (stapleton AT berbee DOT com)
IBM Certified Advanced Deployment Professional
  Tivoli Storage Management Solutions 2005 IBM Certified Advanced Technical
Expert (CATE) AIX Office 262.521.5627