ADSM-L

Re: More Management Class Questions

2015-10-04 18:08:47
Subject: Re: More Management Class Questions
From: Jerry Lawson at ASUPO
To: INTERNET.OWNERAD at SNADGATE
Date: 4/11/97 9:46AM
When you say the only good copy was deleted, how did you determine this?  Did
you go to view and select "Show active and inactive files" first?  Remember
that if you do not do this, ADSM only shows the current active file.  This
does not mean that the other inactive copies don't exist - they just aren't
displayed.  As you show the management class info below, and your description
of what happened, you should have had a copy of the file prior to the
corruption.  If  it doesn't show up when you select "active and Inactive",
then there is a problem somewhere.....

Jerry Lawson
jlawson AT thehartford DOT com


______________________________ Reply Separator _________________________________
Subject: More Management Class Questions
Author:  INTERNET.OWNERAD at SNADGATE
Date:    4/11/97 8:36 AM


--- Message Part 1.1: Text Body Part ------------------------------
While we are on the subject, has anyone developed a technique for
While we are on the subject, has anyone developed a technique for
maintaining multiple (>1) ONLY versions for files that STILL EXIST.  I have
a server who backs up data to a management class with the following
characteristics:

          Versions Data Exists: 7
         Versions Data Deleted: 2
         Retain Extra Versions: 30
           Retain Only Version: 30
                     Copy Mode: Modified
            Copy Serialization: Shared Static
                Copy Frequency: 0

Earlier this week, a client corrupted a file that had not been modified for
90 days.  The file was still valid and ADSM backed up the "corrupted" copy
that evening, EXPIRING THE ONLY GOOD COPY.  The client discovered that the
file corrupted the next morning and requested that it be restored to the
previous version.  We were very embarrassed to not be able to meet this
very reasonable request.  Note that had the file been deleted instead of
corrupted, we would have had 2 copies from which to restore.  Fortunately
for us this was not a business critical file.  However, this does point
does a very real exposure that we had not previously considered.  We could
keep 7 copies for an UNLIMITED amount of time but this policy change
applied to several hundred clients would create a significant increase in
resource utilization both for the database and the associated storage
pools.  What I really need is a option to specify multiple ONLY files.
Have I overlooked something?

> Date:    Thu, 10 Apr 1997 08:42:23 -0400
> From:    Andrew Raibeck <storman AT US.IBM DOT COM>
> Subject: Re: Plea for Clarification of example in AIX Admin Guide
>
>Classification:
>Prologue:
 >Epilogue:
>
>As long as the file exists on the client, the active version is always the
most
>recent version. If/when the file is backed up again, the pre-existing
active
>version becomes inactive, and the new version becomes the active version.
Thus,
>as you've already surmised, the "VEREXISTS=5" is correct.
>
>If you delete the file from the client, then run another incremental
backup,
>ADSM detects that the file no longer exists on the client and changes the
>active version to inactive. Also at this time, the VERDELETED and RETONLY
>options go into effect. Thus if the goal is to retain up to 3 inactive
versions
>when the original file is deleted, the VERDELETED should be set to 3. So
I'd
>say that the example is wrong in this case.
>
>Andy Raibeck
>ADSM Level 2 Support

DanC
=============================================
Daniel G. Crouse
Mainstar Software Corporation
Email:  Dan.Crouse AT Transquest DOT com
Vmail:  800-233-6838
Voice:  404-714-5754
   Fax:  770-682-7739
=============================================




--- Message part 1.2: PCDATA --------------------------------------
 ==> Message part  1.2 is a PCDATA file that has been sent separately.
 ==> Message part  1.2 is a PCDATA file that has been sent separately.
 ==> Subject:       More Management Class Questions

 ==> Document Name: AT000411081248
<Prev in Thread] Current Thread [Next in Thread>