Change in order for the TSM6.3 Restore process of WORM enabled File system

Issue:
IBM TSM (non NDMP) is used to take backup of WORMed/Retained file, it backs up file content and also backs up the Xattr “ibrix.virtual.retention_state” along with the value of the Xattr. Now, when IBM TSM restores a retained/WORMed file on a retention enabled Ibrix Filesystem , it does the setting of the Xattr “ibrix.virtual.retention_state” before restoring the file data. This makes the file read-only and IBM TSM is not able to write the data on the file. As a result the restore fails. However it is working fine as expected with ISVs

Background:

Typically in a retention enabled ibrix filesystem, the File Extended Attribute(Xattr) “ibrix.virtual.retention_state” represents the retention/WORM metadata of the file, i.e whether the file is WORMed or Retained , Retention Period etc. A non-WORMed / non-Retained file will not have this Xattr. This Xattr is listable and the data of the Xattr can be extracted/set using normal VFS interface.

Tested Configuration:
1. TSM 6.3 with Non-NDMP backup
2. RHEL 5.5 (Tikanga)

Potential/logical Solution:
If the restore needs to be successful IBM TSM needs to restore the file data first and then should set the Xattr “ibrix.virtual.retention_state”. This is the error we get in TSM logs : ANS4004E Error processing '/fs1/dir2/file2': destination file or directory is write locked

Other information:
But when restoring(non NDMP) the file TSM does the following, in the following sequence is observed based on the logs
1. Create the file.
2. Set the backed up Xattr of the file.
3. Restore the File Data.

Please note, restoring a retained/WORMed file (on a Retention Enable Ibrix Filesystem) to the original location when the original file is existing is not possible , as the original file is read-only. This is expected behavior. The normal use case is that the restore is done to a different location OR the original file does not exist in the original location. The restore should get back the File Data and also its retention metadata i.e the Xattr “ibrix.virtual.retention_state” (WORMed/Retained whichever is valid ).

Please also note, In a retention enabled Ibrix Filesystem when the Xattr “ibrix.virtual.retention_state” is set, the file becomes read-only (WORMed/Retained whichever is valid).