-
- Enthusiast
- Posts: 51
- Liked: 3 times
- Joined: Apr 19, 2013 8:30 pm
- Full Name: Kellen Flood
- Contact:
Exchange 2013 Virtualization
Hey All,
We currently use Veeam and have it deployed in our Netapp FAS infrastructure. We currently run Exchange 2013 in a DAG (3 node) setup and want to use Veeam to backup the passive node, but the Exchange Databases are ISCSI mapped instead of VMDK. This now limits us to the endpoint tool, which hasnt worked the best so far since it isnt "fully" application aware and cant truncate logs.
Does anyone have a good link that would provide steps or best practices on how to convert them to a VMDK?
On another note our Instant VM Recoveries take about 1 minute on the rest of our infrastructure.
Thanks in advance
We currently use Veeam and have it deployed in our Netapp FAS infrastructure. We currently run Exchange 2013 in a DAG (3 node) setup and want to use Veeam to backup the passive node, but the Exchange Databases are ISCSI mapped instead of VMDK. This now limits us to the endpoint tool, which hasnt worked the best so far since it isnt "fully" application aware and cant truncate logs.
Does anyone have a good link that would provide steps or best practices on how to convert them to a VMDK?
On another note our Instant VM Recoveries take about 1 minute on the rest of our infrastructure.
Thanks in advance
-
- Expert
- Posts: 113
- Liked: 16 times
- Joined: Jun 06, 2014 2:45 pm
- Full Name: csinetops
- Contact:
Re: Exchange 2013 Virtualization
I'd say probably the most risk/stress free way I could think of would be to create the vmdk's, create new databases on the vmdk's and migrate your mailboxes to the new DB's. Then disconnect and decommission the old iscsi luns.
You could always use vmware converter or something to convert the iscsi to vmdk but that involves some pretty substantial down time. Same with changing the iscsi to RDM and then storage vmotion to vmdk, down time and risk there too. I am all about mitigating risk and stress
You could always use vmware converter or something to convert the iscsi to vmdk but that involves some pretty substantial down time. Same with changing the iscsi to RDM and then storage vmotion to vmdk, down time and risk there too. I am all about mitigating risk and stress
-
- Product Manager
- Posts: 8191
- Liked: 1322 times
- Joined: Feb 08, 2013 3:08 pm
- Full Name: Mike Resseler
- Location: Belgium
- Contact:
Re: Exchange 2013 Virtualization
I would personally create the VMDK, attach it to the VM and then use PowerShell to do the move of the database (I believe all the information is here: https://technet.microsoft.com/en-us/lib ... .150).aspx) Read very carefully because there is an important note about replicated databases in a DAG.
When the move is done, disconnect the iSCSI drives
When the move is done, disconnect the iSCSI drives
-
- Enthusiast
- Posts: 51
- Liked: 3 times
- Joined: Apr 19, 2013 8:30 pm
- Full Name: Kellen Flood
- Contact:
Exchange 2013 Virtualization
@mike resseler the link looks to be broken or incorrect. I will do some digging. Appreciate the help guys.
-
- Product Manager
- Posts: 8191
- Liked: 1322 times
- Joined: Feb 08, 2013 3:08 pm
- Full Name: Mike Resseler
- Location: Belgium
- Contact:
Re: Exchange 2013 Virtualization
Yes, for some reason it didn't attached the last part of the link... Let me try again: https://technet.microsoft.com/en-us/lib ... .150.aspx)
Who is online
Users browsing this forum: No registered users and 60 guests