Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

934

March 22nd, 2017 12:00

Setting "atime" when Retention Lock is not installed ?

I’m working with a customer to move Centera data to a Data Domain CIFS.  Retention lock is NOT installed and enabled on the DD Mtree.  This is a newly created Mtree and CIFS share and is the first CIFS on this DD in the environment.

I am trying to set the "atime" (lastaccessedtime) on files programmatically but it does not work on the DD CIFS.  Setting the atime in the future is an industry standard way to set retention.

I've run some simple tests using Windows RoboCopy with the "/COPY:DAT" settings to preserve file attributes and times.  That fails to preserve atime (lastasccesstime) as well.

Does anyone know if DD “Retention lock” would be required on a DD CIFS just to modify the atime on a file ?

After doing some more research I've found that some OSes disable atime tracking by default.  Does DDOS do this and if so how would it be enabled ?

DD is running DDOS 5.7.

Any help would be greatly appreciated

Jay R.

5 Practitioner

 • 

274.2K Posts

March 24th, 2017 05:00

I can answer my own question now...

I've been told by support that "atime" maintenance is only available when "Retention lock" is installed.

Jay R.

19 Posts

March 24th, 2017 07:00

just to add there are two license options for retention lock.  governance and compliance.  the latter is stricter and probably more expensive.

-e

No Events found!

Top