ADSM-L

Re: Archiving conundrum

2005-05-10 08:22:13
Subject: Re: Archiving conundrum
From: Jonathan Kaufman <jkaufman AT FOOTLOCKER DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Tue, 10 May 2005 07:20:24 -0500
If you are using a unix client you can create a seperate servername stanza
that references an include/execlude that uses the 7year archive (and one
that uses the 1 year archive in a diferent stanza), if you are using a
window client you will have to use a different opt file to accomplish the
same effect.

You can specify the servername on unix using -se={servername} and on
windows you can use the -optfile={optfile} on your command line

I've used such tricks in the scheduler to accomplish running "special"
archives without having to change anything on the regular backups.

YMMV

Jonathan Kaufman








Troy Frank <Troy.Frank AT UWMF.WISC DOT EDU>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
05/09/2005 04:56 PM
Please respond to "ADSM: Dist Stor Manager"



        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        Archiving conundrum



We are planning on implementing archives soon, and some of it I'm not sure
how to accomplish.

- We currently have no archives, and our backup retention policy is 60
copies for 60 days.

- Ideally, we want to get a 1-year archive every 60 days, and a 7-year
archive once a year.

- The archives will contain the same dataset that the backups normally
get.

- Our database size is currently ~ 12GB.  Active data is currently 75% of
total.  I took this to
  mean that active data occupies ~ 9GB of the database.  I used that as my
assumed growth
  for each archive (ie. the database will grow 9GB for each archive).  Is
that a good assumption?

For defining the scope of the archives, I was going to use the current
client option sets that are already setup.  I planned on just duplicating
each Include statement with an equivalent include.archive.  The problem
with this is that you can only specify one management class after the
statement.  So I could associate the include.archive statement with either
the 7-yr policy, or the 1-yr policy, but not both.  Even if I could, it
wouldn't have a way to pick which MC to use on which day.  I definitely
don't want to have to edit every cloptset before each archive, with the
correct management class.

I've got separate schedules setup for 7yr & 1yr, but I'm ok with the fact
that I'll probably have to manually enable/disable them when necessary. In
short, any suggestions on how to pull this mess together would be
appreciated.



Troy Frank
Network Services
University of Wisconsin Medical Foundation
608.829.5384

Confidentiality Notice follows:

The information in this message (and the documents attached to it, if any)
is confidential and may be legally privileged. It is intended solely for
the addressee. Access to this message by anyone else is unauthorized. If
you are not the intended recipient, any disclosure, copying, distribution
or any action taken, or omitted to be taken in reliance on it is
prohibited and may be unlawful. If you have received this message in
error, please delete all electronic copies of this message (and the
documents attached to it, if any), destroy any hard copies you may have
created and notify me immediately by replying to this email. Thank you.

<Prev in Thread] Current Thread [Next in Thread>