Exchange 2010 and moving database in hyper v

Hi there

In the process of running up a new Exchange 2010 with Service pack 2 ,  issues we are facing is moving the database file to the drive partition ,

Any comments or fixes for this

The database file path "d:\Program Files\Microsoft\Exchange Server\V14\Mailbox\Mailbox Database 0611388559\Mailbox Database 0611388559.edb" is not valid because it is not on a fixed drive.
Parameter name: EdbFilePath

Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Kamalasekar ParthasarathyMessaging SupportCommented:
planetiwareAuthor Commented:
does not answer my question

Madan SharmaConsultantCommented:
This seems some HDD issue.  first of all you must have a fix drive for to have hyper V  VHD file on that for exchange. Second the HDD for hyper V machine which is running exchange should have fixed size HDD not a dynamically HDD.
Determine the Perfect Price for Your IT Services

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden with our free interactive tool and use it to determine the right price for your IT services. Download your free eBook now!

planetiwareAuthor Commented:
Hi aki

i understand thsi however it seems that its only since Exchaneg SP2 has been installed that the move feature is not allowed

I have moved data files before using dynamic disks
Madan SharmaConsultantCommented:
I am completely agree with you and I am also running my exchange 2010 SP2 on HyPerv with dynamically expanded HDD. But I didn't tried to move database yet on that.

did you add new HDD in hyperV exchange machine and then trying to move. if yes then what the location of that VHD is that on physical server HDD or any NAS drive or any removable drive ?
Svet PaperovIT ManagerCommented:
Moving Exchange 2010 SP2 database on a dynamically expanded VHD is possible. I've just tested it in my lab environment.

However, according to this document about the Exchange 2010 System Requirements, virtual disks that dynamically expand aren't supported by Exchange. Virtual disks, created on NAS storage are also not supported, even if it is presented as block-level storage via the hypervisor. The only option for NAS is to configure it as iSCSI disk and attach it via iSCSI initiator on the host or on the guest machine.
planetiwareAuthor Commented:

i understand that its not supported but i want to do it anyway ,  how did you get it move database ?


Svet PaperovIT ManagerCommented:
What type is the host volume where the VHD file is created: local, iSCSI, USB, etc? Did you try with fixed VHD?
planetiwareAuthor Commented:

Server is running raid 5 , i just created a virtual machine and assigned 500 GB of this for exchange as VHD , c: dribe has 100 and D drive has 400

can i convert it to fixed disk ? can i convert it back after that ?

Svet PaperovIT ManagerCommented:
Yes, you can convert a dynamic to fixed VHD and back.

However, having two or more volumes on one VHD is not a good practice: for example, a dynamic VHD cannot be compressed effectively. Much better solution is to have a separated VHD per volume in the virtual machine. The advantages: only the bootable partition needs to be on a virtual IDE disk, all other volumes could be on virtual SCSI disks; fixed and dynamic disks can be combined as needed (in your case you can have the boot volume C: on dynamic and the exchange mailbox databases on a fixed VHD); the dynamic disk can be compressed as needed.

If recreating a new virtual machine is not an option, you could still create a new fixed VHD for drive D: and keep the first VHD dynamic (even if it’s 500GB) with only 100GB partition for drive C. If you like to go further and reduce the size of the existing VHD to 100GB, there are some unofficial, Linux-based tools that can do that.

The reason for using fixed VHD vs. dynamic for the mailbox databases could be, because of the transaction logs the size of the dynamic VHD will go fast up to the maximum and the VHD file could become fragmented. Otherwise, the performance of either dynamic or fixed VHD is similar in Hyper-V R2.

I hope this could solve the problem with the database move.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.