Link to home
Start Free TrialLog in
Avatar of Laszlo Denes
Laszlo DenesFlag for Canada

asked on

Shrinking 2012R2 Server disks using VMware Converter v6.2 will it cause application issues (assuming process completes okay) with e.g. SharePoint 2013?

Firstly thanks to everyone in advance for their time and expert insights. We have several servers (all at least 2012R2) that were overprovisioned due to vendor recommendations and I need to recapture some of the free space on these drives (mostly c: and d: partitions). I worked with VMware using their VMware converter 6.2 (our ESXi is 6.5u2) and we converted a low priority test system and it went okay. I am having some issues with the application on it, but as it is a standby failover server to the main application server I cannot be sure if the issue is VMware related re. conversion or if it existed before and I will talk with the vendor as the server and application seem okay otherwise. However, I wanted to get some insights from others that have done this, since my next candidate is a SharePoint 2013 farm (2012R2 o/s) that consists of a SharePoint 2013 Farm serer and a SharePoint database server running SQL 2012. Assuming there are no issues during the conversion process itself does anyone have any insights into if this is an okay thing to do or are there any issues that VMware is not telling me, because they said it was okay. Appreciate feedback.
Avatar of Alex
Alex
Flag of United Kingdom of Great Britain and Northern Ireland image

So why are you using VMware Converter in order to shrink the disks? Why don't you just shrink it normally within your ESXi homepage/V-Sphere client and then shrink the disks within windows?
Avatar of Laszlo Denes

ASKER

I am following recommendations by VMware and our support contract with them. Do you have an article that explains what you are mentioning? Cheers! Either way my earlier question still stands re. can shrinking disks causes issues, etc.
my earlier question still stands re. can shrinking disks causes issues, etc.

No.... short but accurate.

https://www.vmware.com/support/ws5/doc/ws_disk_shrink.html
Ah and here is the gotcha... --> VMware Workstation 5.0
As noted we are on our ESXi is 6.5u2 which is vSphere not Workstation, but thanks for the article
Crap missed that one...

You're right actually, using the converter is the recommended way so I'll go get back in my box. However, shrinking a disk shouldn't make any difference to the applications that reside on it.

Regards,
Alex
ASKER CERTIFIED SOLUTION
Avatar of Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Appreciate the insights. I had to use the converter (not the other process) because of support requirements by the vendor. Is there any reason why VMware would not have also pointed this out, because they did not. Not sure how I can test this on one off servers e.g. SharePoint? Will see what vendor says re that one application. Cheers again
Hi,

also this question is already answered, my comment :
what last EE says is true, so sometimes it is easier / less risky to create a brand new VM with the appropriate configuration, and migrate datas or applications from source VM to target one.
Is there any reason why VMware would not have also pointed this out, because they did not.

because VMware Support does not care about your virtual machine application or services, and if they are broke after a V2V, it's unlikely VMware Support will have specialized help you with your failed Sharepoint Site or SQL database!

They'll refer you to vendor, or Restore from backup!

(or they'll say, oh it broke it - maybe restore then!)
Turned out to be a process issue on the application in that I did a step in reverse. Everything works perfectly. Thanks again for feedback.