Hi Dmitry Grinev
thank you both for answering.
That said, is there a reason why you aren't running a DAG between these Hyper-V hosts? You would not have any issues of data loss whereas both Veeam and Hyper-V replication would lose anything after the last time the replication ran.
I had a discussion with some customers. To be clear: I don't know the excact configuration, this is only what they told me:
They are all currently using VMWare Hosts with one Exchange Server, no DAG, on a Fibre Channel SAN with two Disksystems which are replicating to each other.
So if a VMWare host brake, they restarted the Exchange Server and everything worked fine again.
In a situation, where one of those Disksystems failed, they could work with Exchange after a restart of the machine.
Specialy one customer was pretty direct in his question:
Because of a new admin, they want to switch over to hyper-v because in his opinion the current setup is oversized for this company.
He is thinking, that two Hyper-V Servers with direct installed storage in the box should be enough. He doesn't want a DAG. (He think it is simpler to have only one Exchange)
All incoming and outgoing mails are saved in an external mailarchiv. So there should be no "real" dataloss because this is an external box.
So where is the difference between Hyper-V Replica and a Veeam Replication with a snapshot?
In the discussion he started with what could happen if:
- Hyper-V Replication is activated and replication is done every 15 min. (NO VSS active)
In his opinion, the host with the replica should start the guest. hyper-V will integrate the last known changes in his vhdx file.
This vhdx will be used to start Windows and Exchange. Worst case is that in the last 15 min a huge amount of mails where send. Those mails are now not available. Exchange "should" be running.
When "enabling "Configuring additional Recovery points" and "Volume Shadow copy Service (VSS) frequency" the Exchange logfiles should be truncated, so the database should have at least the last hour of mails.
If not, he has to bring the database up againt
And as "foggy" said: "Microsoft does not support non-application aware backups of Exchange:"
but it does work differently from Hyper-V replica in that respect.
Where can I find information what the differences are?
So I told him about Replication with Veeam.
In this thread: https://forums.veeam.com/microsoft-hyper-v-f25/hyper-v-2012-r2-replica-vs-veeam-off-host-replication-t16374.html
the main reason to use Veeam is reduced disk I/O. (In his configuration, he has a lot of SSDs, so he thinks that this wouldn't be a problem.)
The other points are not interesting for him.
I would like to convince my customer to do it the "right" way.
But I need more arguments, the best would be a "killer" argument.