I haven’t used it for some years now, but the old Domino client used to store
two entries for each client, one for the data and one for the permissions. It
would probably go against the TSM (Hate the new name!) philosophy to store any
client data in the database, but this case might be a reason
Hi Hans,
I've been snagged by this on many occasions myself. The worst time was when 40
TB of data had to get backed up again because a system admin made a simple
permission change at the root directory.
I agree with you that since TSM now uses DB2 for its database, it should be
able to handl
That’s correct.
It’s possible to skip the permissions, but as a previous sysadmin that had to
restore permissions from backup, I’d advised against that.
Sent from my iPhone using IBM Verse
On Nov 22, 2017, 9:14:08 AM, bull...@gmail.com wrote:
From: bull...@gmail.com
To: ADS
Hi Marc.
So it is not theoretically possible to isolate the permission part and keep
that versioned in the TSM database? Is there any other way to avoid the
problem mentioned(dedup would take care of the doubling of backup data but
is not applicable to our setup).
Hans Chr.
On Wed, Nov 22, 2017
Hi Hans,
File permissions are part of the file, on the filesystem, they are stored
inside the file. When backed up, the whole file is backed up, which
includes the permissions. The permissions are not stored in the server
database. That's why the entire file is backed up. It would be different
When our customers changes permissions on their file servers there is total
chaos with new full backup of everything and no practical method to get rid
of the extra backup data. I think our customers should be able to do this
without paying twice as much for their backups.
>From what I have heard
