[3157] in Release_7.7_team
Re: ext3 TSM backup problems
daemon@ATHENA.MIT.EDU (Alex T Prengel)
Sat Feb 23 14:06:55 2002
Message-Id: <200202231903.OAA01098@astrophel.mit.edu>
To: amb@MIT.EDU, anger@MIT.EDU, davek@MIT.EDU, stasik@MIT.EDU
cc: alexp@MIT.EDU, ops@MIT.EDU, release-team@MIT.EDU, wccf-dist@bcs.MIT.EDU,
linux-help@MIT.EDU
Date: Sat, 23 Feb 2002 14:03:39 -0500
From: Alex T Prengel <alexp@MIT.EDU>
I've made progress on the Linux TSM backup problem-
A work-around reported on the Net, adding a line
Virtualmountpoint /
to one of TSM's configuration files, seems to work, but only for the
dsmc command-line client, not the dsm GUI. I've seem conflicting
advice as to which of the two config files, dsm.opt or dsm.sys, this
should go in. The manual says dsm.sys, but this is the system-wide
one that users can't normally edit when using the manual backup
clients- I'm reluctant to chance this globally in case there are
other, unforseem consequences (dsm.sys is common to all platforms, for
one thing).
Fortunately, it seemed to not matter- I put it in the local dsm.sys that
scheduled backup users have (this one can be edited- it's file
/var/local/tsm/current/dsm.sys), and on my next scheduled backup files
that had changed recently were being backed up (as noted in the log file-
while the problem was occurring, the scheduled backup log file showed no
file transfers). Although I haven't yet had a chance to try restoring these
backed-up files I think this will work.
For manual backup, I put this line in file ~/dsm_backup/dsm.opt (users can't
edit dsm.sys when doing manual backups). In this case I found that the
command line dsmc client worked for both backup and restore, but not the
dsm gui- I wrote a new file, backed it up with "dsmc selective", deleted
the original, restored it with "dsmc restore", and it was restored.
If this holds up, it may be enough of a work-around that we needn't expend
further efforts on this (the vendor is working on an ext3-capable client
now, release expected in late March). It would help if someone else could
verify my results before we announce it publicly- I only have one test
machine, and I've only done limited testing.
Alex
