ONTAP Discussions
ONTAP Discussions
I migrated a vfiler and re-established the snapmirror on the command line (outside PM)
Now I want to clear the status in PM back to "not started"
I tried
dfm vfiler delete <ObjectID>
dfm vfiler add <ObjectID>
but it remember the "Migrated, cleanup required" status
Is there way to clear/reset this without destroying my existing snapmirror ?
thanks
Solved! See The Solution
Hello fletch2007,
1. Is cutover done? If done did you use provisioning Mgr to do it? At this point can you try using provisioning mgr itself to cleanup using the command "dfpm migrate cleanup <Dataset_name> | <vfilername_or_id>"
2. If 1. doesn't work or alternately you can try to set the status manually using the command "dfpm migrate status -c 'not_started' " i.e. -c option changes the migration status.
the help for the following command.
[root@lnx186-239 ~]# dfpm migrate status help
NAME
status -- list the migrating datasets or vFiler units.
SYNOPSIS
dfpm migrate status [ -d | -v | -m | -c <new-status> ][ <dataset-name-or-id | vfiler-name-or-id> ]
DESCRIPTION
List the migrating datasets and vFiler units.
-d option lists all migrating datasets.
-v option lists all migrating vFiler units.
-c option changes the migration status. Valid migration status values are:
'not_started', 'migrated_cleanup_required', 'rolledback'.
-m option lists the migrating members of the dataset/vFiler units.
[root@lnx186-239 ~]#
I hope this helps.
warm regards,
Abhishek
I am not clear on your question.
Is this offline migration or online migration in the first place?
“Migrated, cleanup required” is a state where the vFiler is migrated with cutover done, but the source vFiler is not cleaned up.
But you mention,
“I migrated a vFiler and re-established the snapmirror on the command line (outside PM)
Now I want to clear the status in PM back to "not started"
Give up or relinquish the migration? is that what you are looking for?
Regards
adai
Hello fletch2007,
1. Is cutover done? If done did you use provisioning Mgr to do it? At this point can you try using provisioning mgr itself to cleanup using the command "dfpm migrate cleanup <Dataset_name> | <vfilername_or_id>"
2. If 1. doesn't work or alternately you can try to set the status manually using the command "dfpm migrate status -c 'not_started' " i.e. -c option changes the migration status.
the help for the following command.
[root@lnx186-239 ~]# dfpm migrate status help
NAME
status -- list the migrating datasets or vFiler units.
SYNOPSIS
dfpm migrate status [ -d | -v | -m | -c <new-status> ][ <dataset-name-or-id | vfiler-name-or-id> ]
DESCRIPTION
List the migrating datasets and vFiler units.
-d option lists all migrating datasets.
-v option lists all migrating vFiler units.
-c option changes the migration status. Valid migration status values are:
'not_started', 'migrated_cleanup_required', 'rolledback'.
-m option lists the migrating members of the dataset/vFiler units.
[root@lnx186-239 ~]#
I hope this helps.
warm regards,
Abhishek
dfpm migrate status -c not_started <vfiler ID from dfm vfiler list>
worked
thanks!
Can explain how you ended up in this state ?
Regards
adai