Archive is archive. There is no "incremental" archive. The difference with
backup is that each archive is on its own.
You can use backup for files until they need to be kept as Alex proposed
but you may need to adjust retonly to less than 60 days (for their
mgmtclass).
If you prefer to use only archive create separate mgmtclasses - for the
first days (when you keep the files) with low retension and for real
archiving with delete and normal retension. At least one of them will have
to be made with -archmc option.
This has the drawback that if you perform seven archives before archive
with deletion you will get seven copies.
When the eight (with delete) is made when the first can expire (or little
bit later) and quickly others will expire too. During that time you will
have a backup to copypool and at least two copies will be there.
Zlatko Krastev
IT Consultant
Jack McKinney <jackmc-adsm AT LORENTZ DOT COM> on 08.10.2001 21:38:22
Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
cc:
Subject: Archiving without deleting???
I want to archive files on the TSM server so that it is safe to delete
them on the workstation. For example, I rotate my syslogs everyday to a
file in /var/log/OLD/ named after the date (e.g., messages.20011008).
I might need these files for the first several days that I have them,
but not after that. What I would like to do is to exclude /var/log/.../*
from backups, and then run a 'dsmc archive /var/log/OLD/ -subdir=yes' to
archive them.
The problem is that if I do this, any files that are already archived
but that still live in the filesystem are stored twice in the storage pool,
even though the file has not changed!
I don't want to use HSM for this. Currently, I run backups from
/etc/daily with 'dsmc incremental'. I'd like to follow this with
'dsmc archive' to archive the various directories that I want archived
as above. However, I don't want to re-archive files that are already
there. I also do not want to use the -deletefiles option to dsmc,
because I may want those files for the first several days after they
are archived.
In the case of the log rotation, I can script this to only archive
the current files as I rotate them out. However, if the TSM server is
down at the time /etc/daily runs, and I forget or don't notice in the
root mail, then I'll miss the fact that I don't have backups of these
files. Also, there are some files that don't fit this pattern that I
want archived this way.
Currently, my only thought is to create a virtual mount point for
the directory, and then create a new management class and copygroup
in which the only copy of a file is kept indefinitely (I have to check
to see if that is possible, or if I have to settle for 9999 days).
Is there a magic paragraph in the manual I am missing whereby I
can specify an option to dsmc that says to not re-archive files???
--
"Master knows everthing except Jack McKinney
"Master knows everthing except Jack McKinney
combination to safe" jackmc AT lorentz DOT com
1024D/D68F2C07 4096g/38AEF076 http://www.lorentz.com
2002 Chicago Cubs magic number: 163
|
