Determining the Status of a Migration Running in the Background (4225592)

Yes, this can be done. This is more of a workaround method that should achieve the same results.

For this method to work users must:

1. create a new batch file for the job list, and store it in a commonly accessible area on the file system.

2. Give this job list the same name as the one that is, or will be, running in the background.

 [After the main job is running in the background, the new job file can be opened in any users instance of Content Matrix.]

3. When the new job is opened, users will be given a snapshot view of the job in progress (this is not a real-time update).

For example, let's say that a job file called "Big Job" is running in the background, and another user wants to determine the progress for this job. They would create a new Job file, and call it "Big Job" to match the existing (running) job and then place that file in a commonly accessible area on the file system. Next, they would open this new job file (the copy) in their instance of Content Matrix. This should give the user a snapshot view of the original "Big Job" migration, in process, as it continues to run in the background.

Users can use this method to quickly determine how far along the migration is, and it's status.