Using fileinfo -d to correct audit enforcement dates

My Vault Audit report is telling me that I have a whole bunch of files loaded in a given month, but those files are actually from many different months.  What is wrong?

Here is my audit report:
 
MonthTotal PagesLicence 
1/1/201391309010ok 
2/1/20131991064ok 
3/1/20132017668ok 
4/1/20132031012ok 
5/1/20132055535ok 
6/1/20132091846ok 
7/1/20132122206ok 
8/1/20132154281ok

 


Notice all the files loaded in 1/1/2013.  But the report is listing files from 2012 in that month:
 
File NameFile DateError
20121217125952-gstarpce-ps-1c766c4ea3e7224badec14d26ccbbf60.drp1/3/20130
20121214092319-gstarpce-ps-c56df88e6b758a46ae1e8a733debc5e9.drp1/3/20130
20121213155148-gesspcefr-ps-bc241c76c7b7bb48952b414fa9655918.drp1/3/20130
20121213154608-gessenpce-ps-a307fe526e36804e8a4d1d4b4ca3372c.drp1/3/20130
20121213132140-simplex-ps-dacc26cc23b2034a869b58724092fba4.drp1/3/20130
20121210124604-gws-ps-68d65641e7c21241ae70c9b695e692b0.drp1/3/20130
20121212085921-gstarpce-ps-c997ec84b743ff4db7bde31e21d99bc8.drp1/3/20130
20121207094948-gstarpce-ps-6c943a60b3fee04880a8711c0dae21b1.drp1/3/20130
20121206132031-gstarpce-ps-c8a4c4a9cb9ebf47b52639b7bdc78c49.drp1/3/20130
20121206101150-gstarpce-ps-263667b00609f34397d3996c9463306b.drp1/3/20130
20121205140031-gstarpce-ps-cab41791f8b5b04aa9ec221f88d9b791.drp1/3/20130
20121205082938-gstarpce-ps-2dabcae1895f4345a8a9dc75f7c99c14.drp1/3/20130
20121204105420-gstarpce-ps-8c74f42c9dea1a49b8a88aeed168a9b8.drp1/3/20130
20121203082404-gesspcefr-ps-96a52e38e8942947811cf52280550573.drp1/3/20130
20121203081852-gessenpce-ps-0bc2de447e693948bc48b6cb28fff2b4.drp1/3/20130
20121130094102-gstarpce-ps-e2cd8824ca79b94280545da5a221179c.drp1/3/20130
20121126094228-gstarpce-ps-01fd596fd5a82345a7cba83270d8f4b8.drp1/3/20130
20121126085211-gstarpce-ps-32d65daf39708e4ba1698712f2bb1f19.drp1/3/20130
20121126080126-gstarpce-ps-9cacee0bcb325c43af2797d31de39b4e.drp1/3/20130
20121120224317-gstarpce-ps-8c93ee9b8719394ab8a182ae6ede658f.drp1/3/20130
20121120110921-gstarpce-ps-2a353fef59a5814991d86afe95a6caf3.drp1/3/20130
20121116140759-gstarpce-ps-bbfcd73a8e72b64da3d3f6a31caee398.drp1/3/20130
20121114143857-gesspcefr-ps-2b8fec1a5abe8a42955c0aad4c697943.drp1/3/20130
20121114143059-gessenpce-ps-e0def602f4744946b5bbf10ff8e45280.drp1/3/20130
20121114131308-gstarpce-ps-5e320fdf3229ae4f86bc79a2c18c4468.drp1/3/20130








The audit report normally goes off of the file creation / modification date to determine what month to count the file under for license purposes.

If the Vault server has been moved to another PC, it is possible that when the files were copied the file creation/modification dates changes, causing the Vault audit to now consider them in a new/different/wrong month.

In order to correct this, you need to run the fileinfo -d command against each file, as follows:

fileinfo <filename> -d  

i.e.,

fileinfo 20121114131308-gstarpce-ps-5e320fdf3229ae4f86bc79a2c18c4468.drp -d

Running with the -d flag will cause Vault to reassign the date to whatever is listed in the filename.  (In this case 20121114.)

Note that this will not work if the DRP isn't already using the YYYYDDMM naming convention.

Once you've done this to all the affected files, you can re-run the audit report and get better results.
UPDATED:  September 25, 2017