-
- Novice
- Posts: 5
- Liked: never
- Joined: Jul 29, 2015 3:53 pm
- Full Name: Aaron Hamlen
- Contact:
ESX4 To ESX5 Cluster
We need to move two servers one file and the other sql to our Vcenter 5 cluster. I've used quick migration for a couple vm's without any errors the quick migration failed last night on our sql server. Should we use replication for the
two servers? File server has over 2.4 TB of data sql is approx 400 GB. Veeam is new to us trying to figure out best practices. Thanks to all
two servers? File server has over 2.4 TB of data sql is approx 400 GB. Veeam is new to us trying to figure out best practices. Thanks to all
-
- Product Manager
- Posts: 20406
- Liked: 2298 times
- Joined: Oct 26, 2012 3:28 pm
- Full Name: Vladimir Eremin
- Contact:
Re: ESX4 To ESX5 Cluster
What particular error you got? Both quick migration and replication jobs are applicable migration means. Thanks.
-
- Novice
- Posts: 5
- Liked: never
- Joined: Jul 29, 2015 3:53 pm
- Full Name: Aaron Hamlen
- Contact:
Re: ESX4 To ESX5 Cluster
It's case # 00980263. I'm looking at the server.
-
- Novice
- Posts: 5
- Liked: never
- Joined: Jul 29, 2015 3:53 pm
- Full Name: Aaron Hamlen
- Contact:
Re: ESX4 To ESX5 Cluster
What log are you looking for on the server? Our requirement is to keep the servers up with minimal downtime. What type of job would work best replication?
-
- Product Manager
- Posts: 20406
- Liked: 2298 times
- Joined: Oct 26, 2012 3:28 pm
- Full Name: Vladimir Eremin
- Contact:
Re: ESX4 To ESX5 Cluster
I was not looking for a log, but more for an error you got inside backup console during migration.
As I've said, both quick migration and replication should work fine for the described scenario. Replication will allow to preserve original copy for some time, though.
Thanks.
As I've said, both quick migration and replication should work fine for the described scenario. Replication will allow to preserve original copy for some time, though.
Thanks.
-
- Veteran
- Posts: 385
- Liked: 39 times
- Joined: Oct 17, 2013 10:02 am
- Full Name: Mark
- Location: UK
- Contact:
Re: ESX4 To ESX5 Cluster
Hi I've been doing a similar exercise over the last few months.
If possible we always do cold quick migrations, its longer downtime but we can tell people the exact maintenance outage rather than letting the VM's change automatically.
For larger VM's over about 200GB, we use replication to seed the copy first, shut down the source VM and then do a final rep once its turned off before turning on the new copy. This method has worked well with many VMs, from big SQL to Large Exchange DB servers.
If possible we always do cold quick migrations, its longer downtime but we can tell people the exact maintenance outage rather than letting the VM's change automatically.
For larger VM's over about 200GB, we use replication to seed the copy first, shut down the source VM and then do a final rep once its turned off before turning on the new copy. This method has worked well with many VMs, from big SQL to Large Exchange DB servers.
Who is online
Users browsing this forum: apolloxm, Bing [Bot] and 280 guests