Archived Case Migration
1. If we're moving to Pega Cloud and have previously archived case data in a repo, is there a process for ensuring the archive cases are searchable and retrievable in the new cloud system? Would this be handled automatically by the pyArchival_ReIndexer Job Scheduler?
2. In a disaster recovery situation, what would happen if the archival process ran on the DR system and attempted to archive a case that had already been archived? This assumes the repo is accessible from both the primary and DR system.
Thanks -Ryan
Accepted Solution
Updated: 15 Oct 2024 16:24 EDT
Pegasystems Inc.
GB
1. there is a process for ensuring that archived cases are searchable and retrievable in the new Pega Cloud system. The pyArchival_ReIndexer Job Scheduler is designed to fix corrupted Elasticsearch indexes, which can help in making archived cases searchable. However, it is important to ensure that the archived cases are properly indexed into Elasticsearch as part of the archival process. The indexing of copied cases into Elasticsearch is a crucial step to ensure they are searchable in the new system.
2. In a disaster recovery situation, if the archival process runs on the DR system and attempts to archive a case that has already been archived, the system should ideally recognize that the case has already been archived and avoid duplicating the archival process. The pyPegaArchiverUsingPipeline job uses a crawler to identify eligible cases for archiving, and it should validate the resolution of all subcases before copying them to the secondary storage repository. This validation step should help prevent re-archiving of cases that have already been archived.
⚠ This is a GenAI-powered tool. All generated answers require validation against the provided references.
The Case archiving and data expunging processes
Archived Case Search in 8.3 Cloud
1. there is a process for ensuring that archived cases are searchable and retrievable in the new Pega Cloud system. The pyArchival_ReIndexer Job Scheduler is designed to fix corrupted Elasticsearch indexes, which can help in making archived cases searchable. However, it is important to ensure that the archived cases are properly indexed into Elasticsearch as part of the archival process. The indexing of copied cases into Elasticsearch is a crucial step to ensure they are searchable in the new system.
2. In a disaster recovery situation, if the archival process runs on the DR system and attempts to archive a case that has already been archived, the system should ideally recognize that the case has already been archived and avoid duplicating the archival process. The pyPegaArchiverUsingPipeline job uses a crawler to identify eligible cases for archiving, and it should validate the resolution of all subcases before copying them to the secondary storage repository. This validation step should help prevent re-archiving of cases that have already been archived.
⚠ This is a GenAI-powered tool. All generated answers require validation against the provided references.
The Case archiving and data expunging processes
Archived Case Search in 8.3 Cloud
How to access Pega cloud storage after Archive and Purge the Pega cloud application case types data.
Secondary storage repository for archived data