Hi.
We want to give a customer a new server. hyper-v with 1 virtualized server. We want to leverage the older hardware to use for replicaation in case of emergeny.
The new server is a HP DL-360 Gen9 with 32gb ram and Raid10 4 disk 15K SAS and the old server is the same but an G7 server and 10k drives.
How often can i replicate without the system suffocating with performance issues.
I want to achive this if possible:
1 nightly backup
replication between 7 A.M - 3 P.M. every 15 min. so if the server crashes they can become avaiable with a maximum of 15 min. data loss. 15 min. lost is not critical for this customer.
Can i leverage the 4 NIC in the server somehow to reduce load f.ekx.?
Or is the backup io controller a good thing to use here? Eventually what settings you suggest?
-
- Service Provider
- Posts: 1092
- Liked: 134 times
- Joined: May 14, 2013 8:35 pm
- Full Name: Frank Iversen
- Location: Norway
- Contact:
-
- Veteran
- Posts: 7328
- Liked: 781 times
- Joined: May 21, 2014 11:03 am
- Full Name: Nikita Shestakov
- Location: Prague
- Contact:
Re: replication tips
Hi Frank,
You can enable I/O storage control to throttle tasks if latency goes to high.
Thanks!
Depends on the infrastructure. Give it a try to see how it works.frankive wrote:How often can i replicate without the system suffocating with performance issues.
You can enable I/O storage control to throttle tasks if latency goes to high.
NIC teaming sounds good. I would also review the full job statistic first to find out bottleneck.frankive wrote:Can i leverage the 4 NIC in the server somehow to reduce load f.ekx.?
Thanks!
Who is online
Users browsing this forum: Bing [Bot], Semrush [Bot] and 127 guests