So we just upgraded our dev environment top 8.0sp5 in preperation for our prod upgrade and our checkpoint xml files are always starting at the begining and not picking up where the last run left off. I contacted support about this and this is what I was told, "The reason why the checkpoint file always start the same is because always scans from the begging of the archive point, until it finds the last archived file (this is one of the sections in the XML file). " That seems completely wrong from what my understanding of checkpoint archiving is, the discription that suppport stated is the way it worked before checkpoint archiving right?. Isn't it supposed to pick up where it left off without having to rescan everything? what am I missing here?
Indeed, the point of FSA check point so that if the archiving is interupted then it will kick off where it left off and doesn't have to scan from the beginning again. Make sure the xml file is not corrupted and vault service account has full permissions to the file and location of the xml file.
The permissions are good and the xml file have been run multiple times and always starts in the same place. The main thing that I wanted to confrim was that what I was told by support was incorrect, it should not rescan each time but pick up where it left off. I guess I may have to call support back and get another person to look at it.
Thanks for the input guys, so I ran the task again this morning and just looked at the xml and now it seems to be working. The question that I have is why? Dose it have to run some sort of initial scan of the intire volume before it updates? hmmm the good news is that it works but nothing changed...
