Just in case anybody reads this and thinks "I have the same issue and there isn't an answer"....
We resolved the issue, which appears to have been caused by the target pool being too small to receive the file systems on the source VDM - note that all file systems on that VDM will be migrated, not just the one you think you have selected.
The error messages we saw didn't provide any clues as to what the issue was.
Rainer_EMC
4 Operator
•
8.6K Posts
0
August 10th, 2018 02:00
I would suggest to open a service request
paf23
1 Rookie
•
17 Posts
0
August 13th, 2018 05:00
Just in case anybody reads this and thinks "I have the same issue and there isn't an answer"....
We resolved the issue, which appears to have been caused by the target pool being too small to receive the file systems on the source VDM - note that all file systems on that VDM will be migrated, not just the one you think you have selected.
The error messages we saw didn't provide any clues as to what the issue was.
Rainer_EMC
4 Operator
•
8.6K Posts
0
August 13th, 2018 13:00
and yes - all the file systems of a VDM should be migrated
If you not you would end up with "stranded" file systems on the VNX that cant be accessed any longer since its IP has moved to the Unity system
Rainer_EMC
4 Operator
•
8.6K Posts
0
August 13th, 2018 13:00
thanks for the feedback