Re: Any way to avoid full backup of data relocated on TSM client file system??

2010-05-31 Thread Gary Bowers
Rick, If memory serves right ( and that is always questionable) that is exactly what used to happen at one point. I believe that Unix systems still do this, but I would have to test it again. The metadata for a file is stored in the TSM database. At least it was until Active Directory made

Re: Any way to avoid full backup of data relocated on TSM client file system??

2010-05-28 Thread Rick Adamson
Steve, Yes that is an option but also would have consequences in a restore/recovery situation. The clusters are where the company's user home and group directories live, hence permissions are somewhat granular to say the least. In a recovery situation they would be lost or at a minimum restored

Re: Any way to avoid full backup of data relocated on TSM client file system??

2010-05-28 Thread Huebner,Andy,FORT WORTH,IT
Have they considered the use of groups? Once the group has access they can add or remove users as needed. I understand that the home directories will have the user instead of a group, but anything that affects the whole tree or a large part should be a group. One thing we have done in the past

Re: Any way to avoid full backup of data relocated on TSM client file system??

2010-05-27 Thread Ben Bullock
I have had that problem also in the past and found no suitable way to get around it. We considered just not backing up the ACLs, but that was deemed unacceptable, so we just had to grin and bear it. As I understand it, the ACLs are actually part of the Windows files, so there is no way to

Any way to avoid full backup of data relocated on TSM client file system??

2010-05-26 Thread Rick Adamson
We have an operations and security team that is constantly either moving client data or changing a file spaces inheritable ACL's, which in turn results in the next backup recognizing this as changed or new data and backing it up again. This results in wasted storage and reduces the retention