4430 Storage partition migration for DR linked partition is paused. User action is required.
Explanation
This error is raised if explicit user action is required for storage partition migration of a partition in DR replication.- For Event ID 054001
-
This event is raised on source system after initializing the migration, if partition contains one or more recovery volume groups.
- For Event ID 054002
-
This event is raised on source system post rollback, if partition contains one or more independent volume groups that were previously recovery volume groups locally.
- For Event ID 054003
-
This event is raised on source system if abort is triggered and partition contains one or more independent volume groups that were previously recovery volume groups locally.
- For Event ID 054004
-
This event is raised on target system if partition contains one or more independent volume groups that were previously recovery volume groups locally.
- For Event ID 054005
-
This event is raised on target system, if rollback is triggered and partition contains one or more recovery volume groups.
- For Event ID 054006
-
This event is raised on source or target system, if DR link status (dr_link_status) of partition is in problem state at certain stages of storage partition migration.
- For Event ID 054007
-
This event gets raised at the source system or target system that is involved in partition migration. It is raised on the system that is active management system but not the preferred management system. Partition migration can only continue from system that is active management system as well as preferred management system.
- For Event ID 054008
-
This event is raised on source system if partition contains one or more independent volume groups.
User response
- For Event ID 054001
-
- Fix the event by marking each recovery volume group in partition to be independent with the
following
command:
chvolumegroupreplication -mode independent <volumegroup_id> - You can abort the migration by using the following
command:
chpartition -override -location <source_system> <partition_id>
- Fix the event by marking each recovery volume group in partition to be independent with the
following
command:
- For Event ID 054002
-
- Fix the event by marking each independent volume group (which was recovery volume group locally)
in partition to production on remote DR system, and to make it recovery volume group again on source
system. This ensures that the previous DR replication mode is maintained for specific volume group.
You can also decide to mark this independent volume group as production on source system but
previous DR replication mode is not maintained for the specific volume group. Following is the
command to mark volume group as production on the
system:
chvolumegroupreplication -mode production <volumegroup_id> - Fix the event reported without resuming DR replication by using the following command:
chpartition -migrationaction fixeventskipchecks <partition_id> - You can abort the migration using the following
command:
chpartition -override -location <source_system> <partition_id>
- Fix the event by marking each independent volume group (which was recovery volume group locally)
in partition to production on remote DR system, and to make it recovery volume group again on source
system. This ensures that the previous DR replication mode is maintained for specific volume group.
You can also decide to mark this independent volume group as production on source system but
previous DR replication mode is not maintained for the specific volume group. Following is the
command to mark volume group as production on the
system:
- For Event ID 054003
-
- Fix the event by marking each independent volume group (which was recovery volume group locally)
in partition to production on remote DR system, to make it recovery volume group again on source
system. This ensures that the previous DR replication mode is maintained for specific volume group.
User can also decide to mark this independent volume group as production on source system, but
previous DR replication mode is not maintained for specific volume group. Following is the command
to mark volume group as production on the system.
chvolumegroupreplication -mode production <volumegroup_id> - Fix the event reported without resuming DR replication by using the following command:
chpartition -migrationaction fixeventskipchecks <partition_id>
- Fix the event by marking each independent volume group (which was recovery volume group locally)
in partition to production on remote DR system, to make it recovery volume group again on source
system. This ensures that the previous DR replication mode is maintained for specific volume group.
User can also decide to mark this independent volume group as production on source system, but
previous DR replication mode is not maintained for specific volume group. Following is the command
to mark volume group as production on the system.
- For Event ID 054004
-
- Fix the event by marking each independent volume group (which was recovery volume group locally)
in partition to production on remote DR system, to make it recovery volume group again on target
system. This ensures that the previous DR replication mode is maintained for specific volume group.
User can also decide to mark independent volume group as production on target system, but previous
DR replication mode is not maintained for specific volume group.
Following is the command to mark volume group as production on the system.
chvolumegroupreplication -mode production <volumegroup_id> - Fix the event reported without resuming DR replication by using the following command:
chpartition -migrationaction fixeventskipchecks <partition_id> - You can rollback the migration to the source system by using the following
command.
chpartition -override -location <source_system> <partition_id>
- Fix the event by marking each independent volume group (which was recovery volume group locally)
in partition to production on remote DR system, to make it recovery volume group again on target
system. This ensures that the previous DR replication mode is maintained for specific volume group.
User can also decide to mark independent volume group as production on target system, but previous
DR replication mode is not maintained for specific volume group.
- For Event ID 054005
-
- Fix the event by marking each recovery volume group in partition to be independent with the
following command
chvolumegroupreplication -mode independent <volumegroup_id> - You can cancel the rollback operation using the following
command:
chpartition -migrationaction cancelrollback <partition_id>
- Fix the event by marking each recovery volume group in partition to be independent with the
following command
- For Event ID 054006
-
- Check DR link status (dr_link_status) field of partition with following
command:
If it is in problem state. Try to resolve this DR link specific error.lspartition <partition_id> - If this event is raised on source system, you can abort the migration by using the following
command:
chpartition -override -location <source_system> <partition_id> - If this event is raised on target system, you can cancel the rollback operation by using the
following
command.
chpartition -migrationaction cancelrollback <partition_id>
- Check DR link status (dr_link_status) field of partition with following
command:
- For Event ID 054007
-
- Check DR link status (dr_link_status) field of partition with following
command:
If it is in problem state. Try to resolve this DR link specific error. Check system event log and if there is any unfixed error event logged against any volume group in partition, try to resolve that error.lspartition <partition_id> - You can set the preferred management system of partition to a local system by using the
following command:
chpartition -preferredmanagementsystem <local_system> <partition_id>
- Check DR link status (dr_link_status) field of partition with following
command:
- For Event ID 054008
-
- Fix the event by marking each independent volume group in partition to production on source
system or on DR linked system (after checking whether it was production or recovery on respective
system before it became independent). This ensures previous DR replication mode is maintained for
specific volume group. Following is the command to mark volume group as production on the system.
chvolumegroupreplication -mode production <volumegroup_id> - You can abort the migration using the following command.
chpartition -override -location <source_system> <partition_id>
- Fix the event by marking each independent volume group in partition to production on source
system or on DR linked system (after checking whether it was production or recovery on respective
system before it became independent). This ensures previous DR replication mode is maintained for
specific volume group. Following is the command to mark volume group as production on the system.