• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 508
  • Last Modified:

Exchange 2010 Program Files Move

Ok so I installed Exchange 2010 into my new VM (Server 2008 R2), I had the ISCSI initiator pointing to our SAN and put everything on that drive (exchange, databases).  I would like to use Veeam backup software but they do not support the use of ISCSI initiator through windows, I would have to connect the LUN to ESXi and use the drive in that fashion.  

So I am looking for a solution to move everything (exchange install/databases) to the local drive, removed the ISCSI initiator, attach the ISCSI to ESXi, create a new hard drive then move it back.  Or at least move the databases on it.  What would you guys recommend for the move and also, what recommendation would you have for exchange, keep exchange install on the root with database on a seperate drive or all together.
0
uescomp
Asked:
uescomp
  • 9
  • 8
2 Solutions
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Use VMware Converter to perform a V2V, it will convert the iSCSI SAN disk into a VMDK (VMware Virtual Disk)

You can use it, just to select that disk and convert it, not the entire machine, just make sure, you shutdown ALL Exchange Services, when you do the v2v.

Download VMware vCenter Converter here
http://downloads.vmware.com/d/info/infrastructure_operations_management/vmware_vcenter_converter_standalone/5_0

VMware vCenter Converter Standalone 5.x Documentation
http://www.vmware.com/support/pubs/converter_pubs.html
0
 
uescompAuthor Commented:
I guess I am unsure of how that works or I did not explain my problem correctly.  In Server 2008 R2 i have the microsoft ISCSI initiator pointing to our SAN, the ISCSI on the SAN is pointing to the server.  (Again if i am thinking correctly).  I would have to point the Exchange ISCSI on the SAN to the ESX cluster so it is being picked up as a storage, create a 2nd hard drive on the VM, and load point it to the exchange ISCSI on the SAN.

Sorry if its confusing, im not a VMware guru at this point but I plan on getting certified.
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
VMware Coinverter will convert what it currently finds to a new VM, all converted to virtual disks.

When you start up the converted versions, all the drives will be converted with correct drive letters, and data.

You do not have to mess around with anything, other than install VMware Converter on current VM, and Convert it to a new VM!
0
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
A video of the process may give you a better understanding

http://www.experts-exchange.com/Software/VMWare/Q_27232719.html?cid=1572#a36291208

New HD Video - VMware vCenter Converter Standalone 5.0 Convert monolithic sparse to monolithic flat for use with VMware vSphere 4.x 5.0 ESXi 4.x 5.0
http://andysworld.org.uk/2011/10/11/new-hd-video-vmware-vcenter-converter-standalone-50-convert-monolithic-sparse-to-monolithic-flat-for-use-with-vmware-vsphere-4x-50-esxi-4x-50/
0
 
uescompAuthor Commented:
I will be giving it a shot probably next week monday, thank you for your posts, i will let you know how it goes.
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Converter is certainly the easiest, otherwise you are going to have to create a new virtual disk, VMDK, use the Exchange tools to move store to new disk, which would be an iSCSI Copy/Move operation from iSCSI disk to Virtual Disk.

Then disconnect iSCSI LUN from Microsoft Initiator, Restart Server, decommission LUN on SAN, and then you should be ready for Veeam.

Theres also a third option, of adding a RDM virtual LUN to the data alreay present on the LUN, so the data does not move anywhere.
0
 
uescompAuthor Commented:
Ok Ran into a problem. Unless I am missing something.  Let me explain the overall finished product.  I have the root (windows installation files or C:\) stored on the VM storage ISCSI and my Exchange install and datastores stored on another drive connected to the ISCSI Exchange.  I used the converter but it wants to put them on just one vs being able to pick C:\ to VM storage and X:\ to Exchange Storage.  Is that possible?
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
You can specify in the Conversion options, Tick the Advanced Disk Box, to specify individual disks.

you'll then end up with two vritual disks (vmdks), and then start up the VM, and use Disk Manager to Change the assigned drive letter to X:
0
 
uescompAuthor Commented:
But that is to the same ISCSI storage vs 2 seperate ISCSI storage right?
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
I'm not following here?

Converter will convert your disks, to full virtual disks (vmdks), at present, your Exchange Database sits, on a "RAW" iSCSI LUN connected with Microsoft Initiator, and you would like ot to sit inside a VMDK?

VMDKs can sit on any storage, local disk datastore, iSCSI datastore, FC datastore or NFS datastore.
0
 
uescompAuthor Commented:
Ran the Converter with the exchange services stopped, it converted but i can't send any mail, any ideas?
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
We probably need another Question posting, to start "debugging cannot send any email."
0
 
uescompAuthor Commented:
Well your solution did what it was suppose to do but it did not work entirely.  Good thing is I have not deployed exchange just yet so i am going to redo it.  As part of my original question.  I go to install exchange and it shows the path on where its installing (C:\).  I dont see an additional field to save the database on a separate disk or should i manually move the logs and database to the 2nd drive etc.
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Why are we installing Exchange? I thought we were doing a conversion?
0
 
uescompAuthor Commented:
We did and it did not work for my situation, it is a great tool and I highly appreciate you showing/demonstrating the tool.  I just felt that it is a new DC and Exchange server on an isolated switch.  Before i deploy it I don't believe in fixing something broke.  The link with exchange broke with the conversion out of the windows ISCSI initiator, and was not communicating with active directory.  

I am not a firm believer in repairing a fresh installation because there usually are unknown problems down the line.  There was however 2 parts to my question, the conversion part which you answered succesfully and I will be at least giving you 250 points.  I was just wondering about my last statement in the original question.  I have always done exchange installs where i put the install on c:\ and the datastores on another drive.  Exchange 2010 does not allow this option when you go to install it.  It wants just 1 drive all together.  Hence my 2nd part of the question and what put me in this delema in the 1st place.  
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
We just install as normal, and then MOVE the datastore path.

See here

http://technet.microsoft.com/en-us/library/dd351168.aspx
0
 
uescompAuthor Commented:
Thank you very much for your help with this issue.  Very easy to follow and you were spot on even with my confusing statements.  Thanks again.
0

Featured Post

Get quick recovery of individual SharePoint items

Free tool – Veeam Explorer for Microsoft SharePoint, enables fast, easy restores of SharePoint sites, documents, libraries and lists — all with no agents to manage and no additional licenses to buy.

  • 9
  • 8
Tackle projects and never again get stuck behind a technical roadblock.
Join Now