ADSM-L

"saving" tapes (or management's ideas...)

1999-01-25 12:20:59
Subject: "saving" tapes (or management's ideas...)
From: Zvi Bar-Deroma <zvika AT AESERV.TECHNION.AC DOT IL>
Date: Mon, 25 Jan 1999 19:20:59 +0200
I am currently involved in the painful process of trying to convince
the "powers to be" to spend $$$ for "backup h/w"  and I need some advice.

We are running ADSM on an AIX machine to backup the computers in our
department (we are a technical university). We have a 3570-B12 (that's
2 drives and 19 cartridges), and that is almost full. We don't have a
copy pool, and don't archive (well - got 1cartridge dedicated for that
just so I could get the feeling of how it works, but it's not in production
for the users).

We had a policy of 60 days + 2 versions is file exists and 90 days/1 version
for deleted files. The only action approved to me when we choked on space
was to lower these values to 30/2 vers. (exists) and 60/1 (deleted), and
we more or less saved the space of 1 cart (around 10.5GB).

I requested to get a 3575, make it our primary backup pool and create
a copy pool on it, and dedicate the 3570 to an acrhive pool + db backup.

The enthousiasm was very small to my request, and I was asked to check the
option of minimizing the files on the backup media, by having (some of) them
on other/cheaper media, such as on CD-Rs, sort of HSM from tape to other
backup media. As far as I know there's no such possibility with ADSM,
and I was therefore asked to check for the possibility that files untouched
for 1 year (for example) would be deleted from backup and sent to some
archive. Is this possible under ADSM ?
I guess I could do a find old_untouched_files >> my_adsm_exclud file,
and then the files will be expired, and I could archive them....

A few questions about that (mad, IMHO) idea:

1. What will  the expected performance penalty be when performing incrementals
   with exclude lists of tens of thousand files (upto, around 150,000 on
   my major client, the NFS server which is also the ADSM server) ?

2. Any "simple" way to make sure, that if a file's changed, its status will
   be changed from "no backup, once archived" back to "normal" backup ?

3. Do you know of any very cheap storage solutions (fully automated, we can't
   do it manually for lack of manpower) that is available to work with ADSM
   (cheap = relatively to 3570/3575 solution).

4. Any ideas on how to approach the problem ? Other solutions ?

I would appreciate your input.


Regards,
/Zvika



~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
I cherish the environment - this message was composed with 100% recycled bits.

Zvika Bar-Deroma
Systems and Network manager                       Phone: (+972)-4-829-2706
Faculty of Aerospace Engineering,                 Fax  : (+972)-4-823-1848
Technion                                          Home phone:
Haifa 32000                                              (+972)-4-823-5562
Israel

Internet      :   zvika AT aeserv.technion.ac DOT il
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
<Prev in Thread] Current Thread [Next in Thread>