Unable to move VM drive from one store to another.
I am having problems moving a virtual drive from one storage location to another on one of my VM Machines but can't understand why. The VM I am trying to move the drive on is our Production SQL server that serves up data for our ERP system. The data and all drives currently sits on a SAN we purchased but the 10K drives cannot handle the requests so I thought I could move that drive that contains the SQL database to a HOST that has a bank of SSD drives. That datastore is 735GB and the drive I want to move is 400GB so it should fit however when I go to Migrate the drive it says that there is not enough room. What am I doing wrong? Can I move a drive off a SAN to a local Datastore on a host? Do I need to move the whole VM drive structure to a new datastore? I was under the impression I could move just one drive which it looks like can be done but I don't completely understand the process.
When I am in the advanced settings of the migration process do I need to tell the application where all the drives need to stay and where to move? I mean In the Advanced window do I need to tell the system to keep all the drives on the current datastore (SAN) and change the one drive to the new location? I was just telling it to move just the drive but each time I would click next it would tell me that there isn't enough space.
When I am in the advanced settings of the migration process do I need to tell the application where all the drives need to stay and where to move? I mean In the Advanced window do I need to tell the system to keep all the drives on the current datastore (SAN) and change the one drive to the new location? I was just telling it to move just the drive but each time I would click next it would tell me that there isn't enough space.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Sorry I haven't responded to this question in a long time but was pulled off this project to work on another project.
Right now there are no thin-provisioned VM's on that drive. The drive was specifically created to hold the SQL database drive on it and I thought that since the maximum size of the current drive is 400GB that 746GB would be more than enough room to hold that database. Could it be that the server wants that logs to reside on that drive too and that is why it won't allow it? Could I have provisioned that drive incorrectly?
Right now there are no thin-provisioned VM's on that drive. The drive was specifically created to hold the SQL database drive on it and I thought that since the maximum size of the current drive is 400GB that 746GB would be more than enough room to hold that database. Could it be that the server wants that logs to reside on that drive too and that is why it won't allow it? Could I have provisioned that drive incorrectly?
ASKER
I have given up on trying to make this work. Thank you for all your suggestions.
ASKER
I am trying to move this drive when the SQL server is shutdown so there is no activity on the drive when I am trying to move it.