This is a problem for NTFS because the amount of metadata associated with an
object is more than you can put into the TSM database. Thus, TSM puts it into
the storage pool, along with the object. What this means is that when the meta
changes, the object has to be backed up again. This is not
Share perms are stored in the registry, so backed up with a system state
backup. If all the files are getting backed up again he must have changed
the filesystem perms too.
On Mon, 11 May 2015 22:13 Paul Zarnowski p...@cornell.edu wrote:
This is a problem for NTFS because the amount of
One of our TSM servers is in the process of backing up a large part of the
contents of a Windows 2008 file server. I contacted the system administrator.
He told me that he had changed share permissions but not security permissions,
and did not expect all the files in the share to be backed up.
Hello
From my experience changing share permission will force tsm to backup all
the data once more. A solution we used in the past was to assign groups
instead of users to shares.
Changes to group membership is behind the scenes in AD, and is not picked
up by TSM at the client level.
On Mon,
,
_
email: ron.delaw...@us.ibm.com
From: Steven Langdale steven.langd...@gmail.com
To: ADSM-L@VM.MARIST.EDU
Date: 05/11/15 14:54
Subject:Re: [ADSM-L] Share permission changes
Sent by:ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU
Share perms
