Doug,

  You have hit upon a sore subject that has been hashed out on the ADSM
forum before.  However, no ideal solution has been forthcoming.  If you
have any desire to view the discussion thread, the listserv can send you
archives.  It was a rather interesting discussion.  Suffice to say that
many of us have the need you spoke of and desire ADSM to support it.

The only real recommendation that came out of the thread was to view your
customer specs that drive this need and make absolutely certain that ADSM's
current storage management constructs cannot meet your needs.  Otherwise,
you need to perform a trick like you described.  Options for this are to
run 2 client tasks on the client end or run a task to either rename the
filespaces or the node at the server end.   (Have two nodes or two sets of
filespaces and swap them for the monthly run).

I regret not having better news.

Good Luck,
  Dan T.


----------
> From: Doug Thorneycroft <dthorneycroft AT lacsd DOT org>
> From: Doug Thorneycroft <dthorneycroft AT lacsd DOT org>
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Any ideas on how to perform a monthly incremental in addition
toa daily?
> Date: Friday, August 01, 1997 3:03 PM
>
> I've been asking around for any ideas on how to perform a montly
> incremental backup. Here's the situation. . .
>
> We currently run a daily incremental with a retention of 3 versions for
> 30 days.
>
> In addition to this we would like to perform a monthly backup (12
> versions for 365 days.
>
> The problem is that we don't have enough time to perform a full backup
> or archive, and ADSM doesn't support an incremental archive.
>
> So far the best solution we have heard is to regester a second client
> for each server (with a different node name) and use it to run an
> incremental once a month.
>
> Does anyone have a better idea?
>
> Note: What we would really like to see is a command that would set a
> retention period of 365 days for all active version currently in
> storage. This would allow us to perform what we want at the database
> level, and not require any backup processing at all.
>
> P.S. I accidently sent this message to the command server earlier..
> sorry.