This chapter describes error handling and possible failures that may occur during migration, and includes the following information:
DIVAmigrate performs error handling based on following process:
If the configured number of request failures occur sequentially, the migration job attempts to switch to another Migration Destination. The job is paused if there are no other destinations.
After failing for the configured number of request attempts for a destination, the migration job switches to another destination. DIVAmigrate then attempts to process the job using the new destination until the configured number of requests fails sequentially. If this attempt also fails, DIVAmigrate attempts to switch to the next destination (if any exist). After all destinations have been exhausted, the job will pause (if no more destinations exist).
The only exception to this rule is failed requests due to a too many running requests error; these requests are always retried.
In general DIVAmigrate does not retry migration for objects. DIVAmigrate stores the error codes for each object, and moves on to next object requiring migration. You can rerun the migration job later, and it only affects new objects on the source, and those that failed during the previous run; objects successfully migrated the first time are not retried when you rerun the failed job.
This section describes specific failure scenarios, actions by DIVAmigrate to resolve the failure, and suggested actions for you.
Table 4-1 DIVAmigrate Failure Scenarios and Resolutions
| Failure | DIVAmigrate Action | Suggested User Action |
|---|---|---|
|
DIVAmigrate lost the connection to the DIVArchive Manager. |
Tries to reconnect until connection is restored. |
If the Manager is offline or not running, then restart the Manager. If DIVAmigrate cannot connect to the Manager, you can identify it because new migration jobs stay too long in the Submitted state, and do not change to the Pending state. You can also check the DIVAmigrate Logs. At this point you should investigate common problems with the connection. |
|
DIVAmigrate cannot connect to the Manager Database. |
Retry the connection three times every 10 seconds; if not successful then quit. |
You must investigate and resolve common database connectivity issues, and then restart the DIVAmigrate service. |
|
The environment where DIVAmigrate is running fails. |
After restart, DIVAmigrate checks the status of each job in the database. If they are not expired, it continues their processing. Otherwise, DIVAmigrate recreates their migration plan and resumes job processing as soon as free resources are available. |
You must resolve the operating system environment issue, and then restart DIVAmigrate. |
|
There are no online instances for an object on the Migration Source. |
DIVAmigrate checks for online instances only during the Initialization phase. If an object does not have any online instances, DIVAmigrate skips it and assign the correct error code to the object in the database. If the object was online, but later became offline during the Initialization phase, then some requests sent to the Manager will fail. The error code is stored in the database, and the request is not retried. If the requests continuously fail up to the maximum number of failures, the job pauses. If the job has multiple sources or destinations, it switches to the next source or destination. If alternative instances migrations fail, the original instances are used instead. |
You can browse the results of migration for each completed migration job. The results contain a list of all objects eligible for migration, and resulting error codes (if any errors occurred). You should make objects accessible online again, and then rerun the migration job. |
|
You perform a migration from a tape group that has offline tapes. |
If the Alternative Sources option is turned on, DIVAmigrate attempts to locate disk instances for all offline instances, and then migrates them. If Recovery Mode is turned on, DIVAmigrate attempts to locate disk or tape instances for offline source instances, and then migrates them. If no online alternative instances are found for some offline instances, they are skipped from migration. An Object Offline error code is assigned to the objects. If the tape transitions to offline during migration, the job pauses after the maximum sequential failure requests. If the job has multiple sources or destinations, it switches to the next one, and then pauses after processing them. |
You can browse the results of migration for each completed migration job. The results contain a list of all objects eligible for migration, and error codes (if any errors occurred). You must make objects accessible online again, and then rerun the migration job. |
|
You submitted the migration job with invalid parameters. |
DIVAmigrate assigns the Aborted status to a job. |
You must confirm the job parameters, and then create a new migration job with correct parameters. |
|
A user deletes unmigrated objects from the source during a migration procedure. |
DIVAmigrate attempts to migrate the objects, and stores the appropriate error codes in the database. |
You should use the DIVArchive Control GUI to Cancel or Delete the migration job. |
|
You realize that you submitted a migration job with incorrect parameters. |
Not applicable |
You should use the DIVArchive Control GUI to Cancel or Delete the migration job. |
|
There is not enough free space on the Destination. |
DIVAmigrate fails the configured maximum number of failed requests sequentially, and then places the job in the Paused state. |
You must resolve the issue on the destination, and then resume the job. |
|
All Migration Destination media goes offline. |
DIVAmigrate fails the configured maximum number of failed requests sequentially, and then places the job in the Paused state. |
You must resolve the issue on the destination, and then resume the job. |
|
The Source Tape List, Instance List, or Exclude List has invalid values, but the syntax is correct. For example, a tape barcode is invalid. |
DIVAmigrate ignores invalid values. If all of source is invalid, the job must terminate. |
Confirm the values entered into these lists, make any necessary corrections, and then rerun the job. |