Scenario 1: The Agent node is with Arcserve UDP グレートブルースロットオフライン and the RPS node is with Arcserve UDP v6. Agent job fails to back up and generates the incomplete recovery point on the deduplication data store. Deleting the incomplete recovery point from the deduplication data store may lead to data corruption. Scenario 2: The source RPS node is with Arcserve UDP v5 and the destination RPS node is with Arcserve ブレードビデオゲームps2 v6. Deleting the incomplete recovery point from the destination deduplication data store may lead to data corruption. Reason Due to the mismatch of interface between different versions, when Arcserve UDP v6 RPS tries to delete the incomplete sessions generated by Arcserve UDP v5, it may wrongly delete additional index files which leads to data corruption. Note: If you opt for this option, do not upgrade to Arcserve UDP v6. You can directly upgrade from Arcserve UDP v5 to Arcserve UDP v6 update 1. Note: Contact Arcserve Support to get the patch. If data corruption has occurred, for details refer to the details provided in how to handle corrupted recovery points. How to handle グレートブルースロットオフライン recovery points? You cannot recover any recovery point グレートブルースロットオフライン is corrupted due to the backward compatibility issue as the グレートブルースロットオフライン index file is incorrectly deleted. To make sure that the subsequent recovery points do not depend on the corrupted recovery point, we recommend to take again full backup for the impacted node. In addition, other jobs related to merge job that need to read from the corrupted recovery point might continue failing even though new full backup is done. To solve the above, we recommend to rename the node folder in the backup destination folder of dedupe data store. Add Backup as prefix to the original node name. You can select to delete the renamed node through data store UI, if source the recovery points in the renamed folder are not useful anymore. The automatic retention management of the Plan only applies to the new recovery points done after グレートブルースロットオフライン renaming of the folder. Callback error 18000 at 2439. Error 18000 at 2511. All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.