Aller au contenu principal

Permissions for .tib Files Causing the Backup to Appear Corrupt

Thread needs solution

Hello,

I have been experiencing an issue for a while now, and browsing the forums hasn't seemed to provide an answer, so I am here to ask it myself.

A while back, I started noticing my incremental backups were not running as scheduled. I tried to manually run the backup, and got an error message stating that the backup was unable to be opened, and was most likely corrupt. (paraphrasing, of course.) I knew the backup wasn't corrupt because I had validated it before, so I did some digging. I went into the location where the backups are stored, and found out that the latest .tib file in the archive listed having permission access to an unknown account called S-1-5-21-3445504233-682657791-4132911926-100. No other accounts were listed. I check the previous file, and saw that the SYSTEM account had full control. I added the SYSTEM account to the most recent .tib file's permissions, giving it full control, and then the backup opened without a problem.

So apparently there is some sort of permission issue going on with both my incremental backups. Does anyone know how I can fix this? Every time the scheduled incremental backup runs, I have to manually go into the file location, open the latest .tib file, and add the SYSTEM account with full control for the backup to be considered valid, not corrupt.

Any insight would be greatly appreciated.

Thanks,
JW

0 Users found this helpful

If the permissions on your backup files are inherited from the folder or drive that contains them, the permissions on the folder/drive and its propagations to the files/folder below it need to be corrected. You can also set explicit permissions on a folder and remove the inherited permissions, if you wish. If this is a external drive that has been moved from one system to another, the user rights on the different systems could be a problem. The unkown account is probably from another computer or a deleted user account on the computer itself, and should not be removed from the permissions if it is from another system, as it will be needed there when re-attached.