I am checking the following documentation and looking for little bit more information on How archive manager checks for content changes.
http://sdllivecontent.sdl.com/LiveContent/content/en-US/SDL_ArchiveManager_10SP2/concept_756FB4CA97E94AE9836229E605A06CAD
Scenario:
When we re-publish Page A, does Archive Manager process it as a new copy ? Right now, we see it for some updates and we do not see it for some updates.
We want to get some clarification on the below documented.
Republication (content unchanged) — When the page is republished, the Archive Manager checks to see whether the content of the page and/or its artifacts has actually changed. If neither the contents of the page nor its artifacts have changed, a new version of the record is created to indicate the resource has been republished, but the content itself is not rearchived.
Republication (content changed) — when the page is republished, and its content has changed, a new version of the record is created and a new entry for its content created.
How does Archive Manager checks whether its artifacts changed or not? Does it check Componet A, B, C , D and Page A ?
Any clarification will be helpful.
File verification is the process of using an algorithm for verifying the integrity of a computer file, usually by checksum. This can be done by comparing two files bit-by-bit, but requires two copies of the same file, and may miss systematic corruptions which might occur to both files.
Open Windows Explorer, navigate to the file or folder you want to monitor. Right-click the folder and select Properties. In the Properties window, go to the Security tab and select Advanced. After that select Auditing tab and click Add.
How often to perform checks depends on many factors including the type of storage, how well it is maintained, and how often it is being used. As a general guideline, checking data tapes might be done annually and checking hard drive based systems might be done every six months.
Archive Manager's archiving happens in Tridion's content deployment phase and it doesn't reach back to the Content Manager.
The archiver determines which Component Presentations are being deployed by looking at the instructions that the Publisher put into the transport package. But as far as I remember (it's been a while) it only uses the actual web page to determine whether the Components have been changed.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With