ADSM-L

Re: [ADSM-L] Journaling database retaining upon reboot?

2008-07-09 14:27:01
Subject: Re: [ADSM-L] Journaling database retaining upon reboot?
From: "Bell, Charles (Chip)" <Chip.Bell AT BHSALA DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Wed, 9 Jul 2008 13:25:39 -0500
Does that plan apply, considering (something I don't think I mentioned) that
only the most recent numerical mount point is getting changed data? Most of
the other mount point backups are getting few to no files changed. A
co-worker and I were discussing a similar script...

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Richard Sims
Sent: Wednesday, July 09, 2008 1:03 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Journaling database retaining upon reboot?

On Jul 9, 2008, at 1:48 PM, Bell, Charles (Chip) wrote:

> ... The application (an imaging app) on the host machine writes to a
> mount point until reaching a 80% utilized threshold, and then begins
> writing
> to the next numerical mount point. Last February, they started with
> mount
> point 1, and now they are on 12. ...

I would approach a situation like this on a logical basis...
In that the app is doing the Mad Hatter's Tea Party thing (abandon the
current position and move on to the next clean place at the table), I
would have the backup initiate from a script on the client, which
would run a backup of only the latest volume, and there use Incrbydate
in that the list of Active files is pointless in a case like this.
You could run an infrequent, staggered Incremental of the earlier
volumes if you felt compelled, just in case.  Repeatedly running a
backup scan against static volumes is just waste.

    Richard Sims

-----------------------------------------
Confidentiality Notice:
The information contained in this email message is privileged and
confidential information and intended only for the use of the
individual or entity named in the address. If you are not the
intended recipient, you are hereby notified that any dissemination,
distribution, or copying of this information is strictly
prohibited. If you received this information in error, please
notify the sender and delete this information from your computer
and retain no copies of any of this information.