Oooooh!

That there be alot of versions son. I don't think I want the sorted story
behind that.

anyway, I would consider changing a few things, but to answer your question
I would bind each drive to a management class in the dsm.opt file with a
line like this:
INCLUDE \\machinename\C$\...\* USERDATACLASS
INCLUDE \\machinename\D$\...\* DEFAULTCLASS

this should bind the respective drives/volumes to their appropriate
management class.

We do this on our Exchange server backups so that the Exchange DB's don't
intermingle with the regular data on the c & d drives and have their own
tapepools.

C
__________________________________________________
Cris Robinson
Sr. Technical Analyst
Enterprise Storage Management / TSM (ADSM)
Liberty Mutual Insurance
Portsmouth, New Hampshire
603.431.8400.54837
mailto:cris.robinson AT libertymutual DOT com

Stolen quote of the week:
"A computer is almost human - except that it does not blame its mistakes on
another computer. "

        -----Original Message-----
        From:   Richard Cowen [SMTP:richard.cowen AT VTMEDNET DOT ORG]
        Sent:   Wednesday, March 22, 2000 10:33 AM
        To:     ADSM-L AT VM.MARIST DOT EDU
        Subject:        NT client, mgmt classes, C: vs D:

        Here is what we have:

        A bunch of NT clients with C: and D: drives to backup.

        Here is what we do now:

        Weekends, we archive the D drives, just to speed recovery.
        Weekends, we "selective backup" the C drives.
        Weeknights, we incremental both C and D with a single scheduled
"incremental".

        Here are our mgmtclasses:

        adsm> q copyg windowsnt_server defaultpolicy userdataclass type=back
f=d

                    Policy Domain Name: WINDOWSNT_SERVER
                       Policy Set Name: DEFAULTPOLICY
                       Mgmt Class Name: USERDATACLASS
                       Copy Group Name: STANDARD
                       Copy Group Type: Backup
                  Versions Data Exists: 9,999
                 Versions Data Deleted: 9,999
                 Retain Extra Versions: 735
                   Retain Only Version: 735
                             Copy Mode: Modified
                    Copy Serialization: Shared Dynamic
                        Copy Frequency: 0
                      Copy Destination: BACKUPPOOL
        Last Update by (administrator): M178079
                 Last Update Date/Time: 01/30/98   10:09:18
                      Managing profile:


        adsm> q copyg windowsnt_server defaultpolicy defaultclass type=back
f=d
        Session established with server ADSM: AIX-RS/6000
          Server Version 3, Release 1, Level 2.42
          Server date/time: 03/22/00   10:12:46  Last access: 03/22/00
09:32:23


                    Policy Domain Name: WINDOWSNT_SERVER
                       Policy Set Name: DEFAULTPOLICY
                       Mgmt Class Name: DEFAULTCLASS
                       Copy Group Name: STANDARD
                       Copy Group Type: Backup
                  Versions Data Exists: 4
                 Versions Data Deleted: 2
                 Retain Extra Versions: No Limit
                   Retain Only Version: 366
                             Copy Mode: Modified
                    Copy Serialization: Shared Dynamic
                        Copy Frequency: 0
                      Copy Destination: BACKUPPOOL
        Last Update by (administrator): M178079
                 Last Update Date/Time: 01/30/98   10:06:11
                      Managing profile:



        The problem:

        We are keeping all the C drives' directories for 2 years (735
days.), or 104 copies of every directory.  (Using the longest retention
mgmtclass.)

        If I code a DIRMC in the options file, it will apply to both C drive
and D drive directories, rebinding all the D drives to a much shorter term
mgmtclass (matching the defaultclass.)  Will expiration actually delete the
older directories (type=backup), or will the type=arch rule apply and keep
the directories as long as there are files below them?

        How do you treat the C drives and D drives differently, with a
minimum of schedules, etc?


        ps. I know you can have a -OPTFILE on a command, but that requires
doubling the schedules and doubling the maintenance of the dsm.opt files.
(Or client option sets.)

        pps. I also know you can't put a -DIRMC on a command line, or I
wouldn't be posting this email.

        ppps. I am considering changing the weekend selective backup of the
C drives to be archives....


        --
        Richard