Joyce, you're not anywhere different than everyone else at one time or
another...
If you wish you may set up a new domain... if it makes sense to group all
those differently across a domain.
I've set my domains by operating systems and/or major applications (so I
have stuff like UNIX domains but also have a SAP domain where unix boxes
running SAP go... I also have NT domains but I also have an EXCHANGE domain
which has NT Exchange servers)
You may get the results you desire by making a new (non-default) management
class and binding the required data to it within the "include/exclude" list
Ok, for a little assistance on the poop...
versions data exists is how many backup versions you wish to keep for up to
"retain extra versions" number of days...
so where you've set versions data exists to 9999 once a "inactive" version
becomes 30 days old ("retain extra versions" days old) it will still be
purged from ADSM/TSM ! so if the data changes daily you'll have 30 copies,
if it changes every other day you'll have 15 copies, etc...
YIKES ! yep, that's the way it works... well, the last time I sat and
pushed backups to a test box, reset dates, pushed more data, reset dates,
and did this a heck of a lot to simulate many days going by.
so hope this helps...
later,
Dwight
> ----------
> From: Joyce Woods[SMTP:Joyce.Woods AT ITPMS DOT COM]
> Reply To: ADSM: Dist Stor Manager
> Sent: Monday, July 24, 2000 8:19 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Backup copy group
>
> Hi Fellow ADSM'ers.
>
> I ran into a big problem. I totally misunderstood the backup copy group
> parameters. I have almost all of my backups within one copy group. This
> is bad
> !@!! And the reason I now know this......is because a file that I thought
> would
> be out there to be restored.........was not. So here is my dilemma. Some
> servers we only need to keep 6 versions of. But some......(that contain
> data
> files which change everyday), we need to keep for 30 days. Do I need to
> set up
> a new policy domain, policy set, mgmt class and copy group.........????
> And if
> anyone has any documentation or really understands all theses parameters
> in the
> copy group. I sure would appreciate the input. I am so tired of feeling
> like
> an idiot.
>
>
>
> Policy Domain Name
> FILESYS
> Policy Set Name
> ACTIVE
> Mgmt Class Name
>
> FILESYS_MC
> Copy Group Name
> STANDARD
> Versions Data Exists
> 9999
> This used to be 6
> Versions Data Deleted
> 2
> This
> used to be 1
> Retain Extra Versions
> 30
> Retain Only Version
> 90
> Copy Mode
> MODIFIED
> Copy Serialization
>
> SHRSTATIC
> Copy Frequency
> 0
> Copy Destination
> DISKPOOL
> Last Update Date/Time
>
> 2000-07-17
> 18:23:32.000000
> Last Update by (administrator)
> JWOODS
> Managing profile
>
|
