Hi everybody,
Oh, well, this could be posted in the other thread, too:
Subject: Re: AFS backup/restore using ADSM
Mitch wanted to know:
> Out of curiosity is anyone backing up their AFS setup using vos dump
> for fulls and vos dump -t for incrementals, rather than using the AFS
> backup commands?
Yesss. I consider it working better that the butc (or if you have
ADSM/TSM buta) solution because I can control the dump logic myself.
Plus that I never was found of butc's interactive character.
We dump volumes to file and my last full home volume ended up in
a file:
H.haba.backup.00000000.20000927
When I then do an incremental tonight it will end up in a file
H.haba.backup.20000927.20000930
You folks in the US might be a bit puzzled about the date convention,
but here in Sweden we write dates like YYYY-MM-DD anyway. Makes
sorting easy as a charm. ls H.haba.backup.00000000.* | sort | tail -1
gives the most recent full backup. But then what to do with that load
of files? Earlier (as in until 2 months ago) we just dumped them into
a HSM filesystem (Cray DMF) which migrated them to tape automatically.
Then we dumped them to a scratch disk from where we did an archive to
the TSM server. That solution has been used by Stacken (as in
stacken.kth.se) a long time. For us it lasted some weeks and then we
moved on to eliminate the scratch disk. Today we use a homemade TSM
solution which makes use of the API so we directly can stream the data
from the vos dump pipe into TSM. To retrieve we use standard dsmc. Why
not HSM any more? Soon we will be without the HSM on the Cray because
the Cray has come to end of life (contact me if you want to buy a full
J90). I do not trust the TSM/HSM solution to be used for this purpose,
because we have a lot of problems with the HSM part of TSM.
I wrote a load of shell scripts which look at each volume and dump it
only if it has been changed or if the most recent full dump is older
that 2 month. But this depends of course on your policy. Then I wrote
more scripts to clean out old backups (the older the cleaner). If you
need such a script depends on your policy and the amount of money you
got :-) This gives me the possibility to have different keep policies
on different types of volumes. We keep our home (H.*) volumes longer
for example.
We do not use the file backup solution for TSM/AFS because it requires
the backup process to run as system:administrator to be sure to be able
to read all files.
Harald.
PS: That's hoew it look like when I use TSM to find my backups:
goby# dsmc query archive /scratch/H.haba.backup.\*
Tivoli Storage Manager
Command Line Backup Client Interface - Version 3, Release 7, Level 2.0
(C) Copyright IBM Corporation, 1990, 2000, All Rights Reserved.
Node Name: AFSBACKUP.PDC.KTH.SE
Session established with server BIGBLUE: AIX-RS/6000
Server Version 3, Release 7, Level 3.0
Server date/time: 09/30/00 13:30:24 Last access: 09/30/00 13:30:13
Size Archive Date - Time File - Expires on - Description
---- ------------------- -------------------------------
API 243,964 K 09/27/00 19:18:05 /scratch/H.haba.backup.00000000.20000927
Never
API 243,966 K 09/28/00 19:25:07 /scratch/H.haba.backup.20000927.20000928
Never
API 243,968 K 09/29/00 16:34:13 /scratch/H.haba.backup.20000927.20000929
Never
