How has the archive manager changed to content without changes and to content?

Question

I check the following documentation and slightly distort the information about how the archive manager checks for content changes.

http://sdllivecontent.sdl.com/LiveContent/content/en-US/SDL_ArchiveManager_10SP2/concept_756FB4CA97E94AE9836229E605A06CAD

Scenario:

• I have component A with related components to reference component B, C, D.
• On my page A we will add component A with template A and
  publish page A.
• Publish Archive Manager processes this file and saves the version to the archiver database.
• Subsequent content updates are performed on any of the components B, C, D.

When we republish page A, does Archive Manager process it as a new copy? Right now, we are seeing this for some updates, and we are not seeing it for some updates.

We want some clarification on the document below.

• Republic (no change) - When a page is republished, the Archive Manager checks to see if the contents of the page and / or its artifacts have really changed. If neither the content, nor the page or its artifacts have changed, a new version of the record was created to indicate that the resource was reissued, but the content itself was not tightened.

• Republication (content changed) - when a page is republished and its content has changed, a new version of the record and a new record for its contents are created.

How does Archive Manager check if its artifacts have changed? Does it check components A, B, C, D and page A?

Any clarification would be helpful.

Answer 1

Archive archiving occurs at the Tridion content deployment stage and does not return to Content Manager.

The archiver determines which presentation components are deployed by looking at the instructions that Publisher puts in the transport package. But as far as I remember (it was time), it uses only the actual web page to determine if the Components have been changed.