Change Dedupe Store Immutability setting?

Question

Hi, 
 I'm testing out using DP's Dedupe stores for the first time on a standalone VM. I've given the VM an E drive pointing to a specific VMware datastore, on a standalone backup only storage array. I then used DP 23.4 panels to create a new Dedupe store, and it worked just fine, test backups ran, and some scheduled. But then I noticed the media delete jobs which kick in to delete old backups was not working due to immutability settings on the Dedupe Store: 
 Immutability period of the medium abc is not completed 
 Reading up on immutability the default is 10 days for a new Dedupe Store. But going through the panels again in the DP GUI I could not see anywhere where I could have set this timeframe. Checking the DPDUtils commands on the VM itself, there are no commands to change an existing Dedupe Store immutability settings. Is my only option to delete the test store, and then use the DPDUtils command to create the store with the -i setting for immutability, and then the panels to point to the store and use it? 
 Thanks, 
 Andy

Koen Verbelen · Accepted Answer

I can confirm that changing the "immutabilityPeriod" in the store's xml file works and also it seems to be the only possible way. As said you could request an enhancement for this to get it implemented in DPDUtils and/or the GUI. 
 I also want to stress that this period is set store-wide. So for any object in the store, already existing or new ones, the period will be modified to the new value that is set.

Koen Verbelen · Answer

The only place I have seen so far is in the configuration file for the store in /opt/omni/sdfs/etc/sdfs or Program Files\OmniBack\sdfs\etc. In the xml file you can find "immutabilityPeriod="10"". It looks like this is something that should be added to CLI and GUI. It may be worth a new post on Idea Exchange .

Koen Verbelen · Answer

Hi Andy, 
 
 I was confused for a moment as I didn't see that message. But that's because I usually use the omnimm CLI command to erase expired media. When running it from the GUI, I was able to reproduce that popup message and most likely you see it because of this global parameter: 
 # DeleteUnprotectedMediaMinimumAge=seconds 
 # default: 86400 # Determines what is the minimum age of the medium to be deleted # by omnimm -delete_unprotected_media. # If a medium age is lower than this value (from time of # creation), then it is skipped by omnimm. 
 
 While it's a good idea to keep some delay here, it doesn't need to be a full day. Maybe you can set it to 3600 seconds or something like that. For testing purposes, I typically set it to 10 seconds in my test environment. 
 
 I also wrote a document about this some time ago: 
 Support Tip: Why is my B2D medium not deleted while it is unprotected? 
 
 And yet another one which you may find interesting: 
 Support Tip: Why are immutable media purged from the Internal DataBase?

Menu

Data Protector Discussions

Verified Answers

Change Dedupe Store Immutability setting?

Top Replies

Verified Answer

Resources