getting error while migrating Volumes in Hitachi VSP from Pool 2 to Pool1 .
The problem is with subscription Limit . After changing the subscription limit,able to migrate. Thank you all for your support.
In the HCS User Guide, table 9-1 has a list of volume types & states that determine whether a volume can be migrated. Some common reasons volumes can't be migrated are:
Hi Dang ,
The volume is Migratable.
Hmm, can you provide some screenshots of the volumes involved? Hard to troubleshoot without details .
You also might need to check if they are part of a pair relationship. If they are being replicated, they need to be suspended I believe.
I had the same issue couple of days back. Migration was not able to be started for the volumes, though the target pool has sufficient space available.
Got that resolved by increasing the subscription warning and limit threshold for the target pool (earlier they were around 70%). After increasing the limit to 80% and 100% respectively, the migration completed without issues.
I just guessed it to do the changes. Do we have any document with solution for these specific error codes ?
Usually the error codes can be looked up in the related product documentation manuals.
Dang was asking for the specific error message you were receiving that included the code so we could have looked up the specific error you were getting.
Actually am not the one did the original post, but i had the same error message as like Vijeta had.
He/she have mentioned that in the subject line of this post.
THE MIGRATION PLAN CANNOT BE CREATED. NONE OF THE VOLUMES IN THE MIGRATION PLAN CAN BE MIGRATED. (KAIC17026-E)
So the message is found in the HCS Messages Guide, however it doesn't give you any more information than you already have.. (Generic messages, the migration plan cannot be created, none of the volumes ... etc)
For this particular one, you would have probably had to get into the logs and search for the error reference (KAIC17026-E).
Logs are in <install path>\TieredStorageManager\logs folder
I know not too helpful, but it what I would've done.
The logs didn't show up this error message in any of the traces or messages.
As the changes in the threshold limits helped to remediate this error message, I would assume that is the solution. But will wait for any other right solutions as well.
Anyhow thanks for your help, Nathan.
Can you advise what had been done to fix the error from your side ? So that we can be conclusive on the solution.
Retrieving data ...