07-05-2011 02:46 PM
Hi all,
Sometimes the answer gets here quicker than via support so I thought I should ask it here as well.
I need to reverse the path etc. for a bunch of of .dvs files (long story why I need this).
From the saveset table there are three columns that look like it could be the ticket.
IdTransaction, IdChecksumLow, IdChecksumHigh
The problem is that I need someone to confirm this and if the first character of IdChecksumLow is the last character for Month-Day in the path ?
E.g. it looks like this:
IdTransaction, IdChecksumLow, IdChecksumHigh
70679494-FDA9-842F-1F0E-CBC7EA0A0EF1, 19517753, 2011070
70689298-121F-7081-A250-6BAC9C36AFD1, 19517768, 2011070
So if I take the last column it would translate to 2011\07-0?
The questionmark seems to be the first character of the checksumlow (by studying pre EV9 entries), which would mean 2011\07-01\
Then get rid of all the "-" charcters of the IdTransaction, take the first character for the next subfolder, the the next three for the folder after that.
So
2011\07-01\7\067\70679494FDA9842F1F0ECBC7EA0A0EF1
And
2011\07-01\7\068\70689298121F7081A2506BAC9C36AFD1
Looks correct from the partition point of view the problem is if I can use the checksumlow for this (as described above).
Also if there is a smarter way to get the path and saveset even better (no the physical file structure doesn't work :) )
Solved! Go to Solution.
07-06-2011 09:08 AM
all you need is ArchivedDate and idTransaction, i promise!
07-05-2011 06:34 PM
just modify the following query i wrote ages ago
https://www-secure.symantec.com/connect/forums/dvs-file-name-70-version#comment-5449481
07-05-2011 09:57 PM
07-06-2011 02:51 AM
Thanks JW2, as always :)
Can you confirm if the first character in the IdChecksumLow column is the last digit for the "day" part of the path ?
Not sure if that is what you meant by "correct" in the second post :)
07-06-2011 07:16 AM
OK So!!!
The way its calculating it is!
ArchivedDate~idDateTime~Z~idTransaction
201107069961508~201106082150450000~Z~90A732262A7CB691832CBE16CC6B1E91
So it would be
E:\Enterprise Vault Stores\Ptn1\YYYY\MM-DD\X\Y\[itemName]
YYYY = Year from the ArchivedDate
MM-DD = Month and Day from the ArchivedDate
X = First letter of the Transaction ID
Y = Second Two letters from the Transaction ID
So based on the above example it would be
E:\Enterprise Vault Stores\Ptn1\2011\07-06\9\0A\ <--- that would be the location
07-06-2011 08:20 AM
JW2,
I know how EV do it when it archives an item.
The problem (or I'm just being stupid) is that if you look in the Saveset table and compare the idChecksumHigh and idChecksumLow columns it's not really stored in that way in the database (meaning in regard to the complete saveset string that you posted).
As per my example above:
idTransaction = 70689298-121F-7081-A250-6BAC9C36AFD1
idChecksumLow = 19517768
idChecksumHigh = 2011070
So if you look at idChecksumHigh it contain everything except the last number, so 2011\07-0x
Now the question is if the first character of idChecksumLow is the last digit for the 2011\07-01 information.
Or if I need to look/use something else.
The number of characters match and as far as I can see it matches the example you posted above, would just like to get that little piece confirmed....if possible :)
07-06-2011 09:08 AM
all you need is ArchivedDate and idTransaction, i promise!
07-06-2011 09:34 AM
Right JW2, didn't see the forrest for all the trees :)
Will use the archived date column instead of messing with the checksum columns.
Should work :)
Cheers.