Solved!
Go to SolutionRetention Lock Governance MTree needs to be deleted
Hello,
is there any way to delete a Data Domain Mtree which is protected with Retention Lock Governance?
There are files in this folder which have set the retention with the touch command.
Tried to reduce the retention to 12 hours, but always get permission denied error.
#########################################################################################################
C:\Users\*>c:\windows\system32\touch.exe -a -t 111120002015 "\\Cifs-Share\rl_old$\backupexec\IMG000001\File.dll"
c:\windows\system32\touch.exe: \\Cifs-Share\rl_old$\backupexec\IMG000001\File.dll: Permission denied
#########################################################################################################
I migrated the Mtree to a new Data Domain system and so don´t need it on this system. But there are other production files on it, so I can´t run a filsys delete.
So I wonder if there is any other way to get rid of this Mtree.
Hi All,
Please refer to the below FAQ for all retention lock questions.
Data Domain: Retention Lock Frequently Asked Questions
Thanks you!
Conor
andikovaci
1 Message
0
1
Posted January 26th, 2024 09:55
I have the same problem on Data Domain Data Domain OS 7.10.1.15-1078832
I try with:
mtree retention-lock revertBut this didn't work
I change the date on Data Domain. Set the time manual and set the date to the date of the expired retention.
In this situation I'm able to delete the backup.
Later set the correct date.(edited)
Druehl1
2 Intern
•
223 Posts
4832
1
Posted November 13th, 2015 08:00
How to Remove
Retention Locked Files
SYMPTOMS
"Permission denied"message when attempting to remove files that are under a Retention Lock period.APPLIES TO
PURPOSE
Although the Retention Lock feature is designed to expressly prevent removal of locked files through the duration of the Retention period, there may arise occasions when it is necessary to override the Retention Lock. This article provides instructions to do so.
CAUSE
By design, files under a Retention Lock cannot normally be removed within their specified retention period.
SOLUTION
The following example walks through the process of reverting the retention-lock on a file and its subsequent removal.
Note that retention lock must be currently enabled for the process below to work. If it was previously enabled, but currently disabled, you may need to re-enable retention lock before proceeding.
Also note that because the revert is a recursive process, it has to operate on each single file or directory, therefore may take a long time if there is a large number of files.
Assume a directory mounted from a Data Domain system with two files in it, and Retention Lock enabled. Note that this example uses an NFS mount, but CIFS can also be used.
# pwd/nfs_mount/backup/ret-lock-test# ls -altotal 1drwxr--r-- 2 root root 232 Apr 2 22:04 .drwxr-xr-x 3 root root 157 Apr 2 21:09 ..-rw-r--r-- 1 root root 0 Jan 1 2013 test-locked-file-rw-r--r-- 1 root root 0 Jan 1 2013 test-locked-file2Now we’ll attempt to remove one of the files.
# rm ./test-locked-filerm: remove write-protected regular empty file `./test-locked-file'? yesrm: cannot remove `./test-locked-file': Permission denied# ls -altotal 1drwxr--r-- 2 root root 232 Apr 2 22:04 .drwxr-xr-x 3 root root 157 Apr 2 21:09 ..-rw-r--r-- 1 root root 0 Jan 1 2013 test-locked-file-rw-r--r-- 1 root root 0 Jan 1 2013 test-locked-file2The system correctly refuses to allow the file to be removed due to the retention lock. Note that even though the error is a generic "Permission denied," in this instance it is due to the Retention Lock.
Logging onto the Data Domain system using an administrator account, we can verify the existence and settings for the Retention Lock feature, as follows (note that /data/col1/backup is the directory containing the relevant files on the Data Domain system):
sysadmin@DD670# mtree retention-lock show min-retention-period mtree /data/col1/backupRetention-lock min-retention-period of mtree /data/col1/backup is: 50 days.sysadmin@DD670# mtree retention-lock show max-retention-period mtree /data/col1/backupRetention-lock max-retention-period of mtree /data/col1/backup is: 900 days.In order to allow removal of the file, we must revert the retention lock, as follows:
sysadmin@UK-DD670# mtree retention-lock revert "/data/col1/backup/ret-lock-test/test-locked-file"The 'mtree retention-lock revert' command removes retention-lock on this path therebymaking it unprotected.Are you sure? (yes|no|?) [no]: yesok, proceeding.Please enter sysadmin password to confirm 'mtree retention-lock revert':Message from syslogd@UK-DD670 at Mon Apr 2 22:18:47 2012 ...UK-DD670 ddfs[4324]: ALERT: MSG-SFS-00036: The command to reset retention was invokedon /data/col1/backup/ret-lock-test/test-locked-fileNow we can successfully remove the file:
# rm ./test-locked-file# ls -altotal 1drwxr--r-- 2 root root 167 Apr 2 22:19 .drwxr-xr-x 3 root root 157 Apr 2 21:09 ..-rw-r--r-- 1 root root 0 Jan 1 2013 test-locked-file2However, note that the Retention Lock feature is still in place for other files in the directory (and elsewhere on the Data Domain system).
# rm ./test-locked-file2rm: remove write-protected regular empty file `./test-locked-file2'? yesrm: cannot remove `./test-locked-file2': Permission denied# ls -altotal 1drwxr--r-- 2 root root 167 Apr 2 22:19 .drwxr-xr-x 3 root root 157 Apr 2 21:09 ..-rw-r--r-- 1 root root 0 Jan 1 2013 test-locked-file2WARNING: If the "
mtree retention-lock revert" command is applied to a directory, it will recursively remove the retention-lock for the directory and all files and sub-directories within the directory. This is very useful, but always be certain that the parameters used in the command match the desired results.