The above mentioned error is generated during a restore operation of DLO client data which is created by another user.

For example:
1. Create a folder named 'test' on a workstation. Assign full control rights to the Domain Users group on this folder so that Domain Users can Delete, Add, and Modify files in this folder.
2. On the DLO console, create a backup selection to back up the 'test' folder. Configure DLO to back up data of two users 'user1' and 'user2'
3. Log in with 'user1' on the workstation and create files in this folder. These files will be backed on the Network User Data Folder (NUDF)
4. Log in with 'user2' on the same workstation. Files created by 'user1' will be backed up on the NUDF for the 'user2' also.
5. From the DLO console Restore tab, expand the data backed up for 'user2' and select a file for restore. The restore job will be submitted on the console (Figure 1)

Figure 1

 

6. On the workstation, open the DLO client. There will be a confirmation message that the file already exists, do you want to overwrite? Click Yes (Figure 2)

Figure 2

 

7. After clicking Yes, the restore shows completed with error and ' 0' files restored. The log file shows the error:
 

"Restore - C:\foldername\restore.txt was not restored. This security ID may not be assigned as the owner of this object.   http://eventlookup.veritas.com/eventlookup/EventLookup.jhtml?EvtID=V-139-35840-20130 " (Figure 3)
 

Figure 3

 

The same error is generated when trying to restore from the DLO Client workstation when the user is logged in as 'user2'


Note:
1. Administrators can restore files to other workstations but not to the original one.
2. Files can be restored using redirection to alternate computers (on the media server).
3. Logging in as 'user2' on another workstation and redirecting the restore to this workstation will allow files to be restored.


This is a security feature of the Backup Exec Desktop and Laptop Option and is working as designed.