ADSM-L

Re: symbolic links

2006-07-13 12:51:55
Subject: Re: symbolic links
From: Alexander Lazarevich <alazarev AT ITG.UIUC DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Thu, 13 Jul 2006 11:51:13 -0500
I added "archsymlinkasfile=no" to dsm.opt and that seems to fix the
problem. So we are good. And yes, TSM linux client I'm using (5.1.7) does
follow and backup symlinks by default, so if you've got recursive links,
the backup will fail. So the fix is that option. At least that works for
us right now.

Alex

On Thu, 13 Jul 2006, Richard Sims wrote:

Alex -

It is the case that the client OS environment is screwed up, and that
the client administrator needs to fix it...which is to say that this
is not a TSM problem.

(However, the TSM documentation on symbolic links is conflicting: In
the Unix client manual it says, "During a backup operation,
symbolic links are never followed".  In IBM Technote 1117280 it says,
"TSM is designed to backup the symbolic links and their associated
object. ... TSM will attempt to follow the link to the actual object."

Your experience proves that the client manual is wrong.  In any case,
the client file system needs owner attention.  The only TSM
alternative is to Exclude problem areas in a file system.

 Richard Sims

On Jul 13, 2006, at 10:40 AM, Alexander Lazarevich wrote:

TSM 5.3.1 server on windows 2K server. TSM client 5.1.7 on RHEL4-
AS. The
client has some recursive symbolic links, and whenever the client
backs
up, the server tries to backup every directory within the sym link,
which
is infinite and the backup dies.

Is there a flag to ignore backups of sym links? I searched the list
back a
couple of years, one other person asked, but no answer. I also
checked the
install readme, and it only mentions how to restore an object within a
symlink, not to avoid backing then up alltogether.

Thanks for your time,

Alex

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