Very important questions

[Ultra_Cool]

Hello,
We have unclear questions and hope that we get fast replay. We are making guide and plan for veeam architecture and our customers gave us questions:

1. How often should we replicate data (advantages and disadvantages) and how long it takes to run if it will be disaster?
2. How often should we take backup if we compare it with replication (advantages/disadvantages)?
3. If we run vm on replica server does we have backup on changes?
4. Where should we install Veeam console? Primary , secondary or both servers?
5. Difference beetwen Hyper-V and Veeam replication?

Hope that someone can answer on this questions coz it is very important to know and understand?

[Ultra_Cool]

Is there anyone who can answer on this question, please? It is very important to our business to understand this and answer to our customers.

[Shestakov]

Hello,

1. How often should we replicate data (advantages and disadvantages) and how long it takes to run if it will be disaster?

Replication provides the best recovery time objective, as you actually have a copy of your VM in a ready-to-start state.
It is commonly recommended for the most critical VMs. Frequency of replication runs depends on how critical the loss of data is and system`s capabilities.

2. How often should we take backup if we compare it with replication (advantages/disadvantages)?

Backup jobs run less often in comparison with replication ones. Backup jobs are made primary for archival purposes.

Usually our clients backup daily:
5 incremental backups for weekdays + 1 full backup on the weekend for forward incremental backups.
Daily backups for reversed incremental backup method.

3. If we run vm on replica server does we have backup on changes?

Could you, please, clarify the question?

4. Where should we install Veeam console? Primary , secondary or both servers?

You don`t need to install Veeam on a backup repository.
There are several "best practice" Deployment Scenarios. Please review.

5. Difference beetwen Hyper-V and Veeam replication?

There are a lot of differences. Please review related topic.

Thank you.

[Ultra_Cool]

Hello Nshestakov ,

Thank you for your replay.

3rd Question: I mean with that if we run replica failover shall we have changes saved somewhere while we are in that state and where can we see it?

4th question: If we have promary Veeam can we install console on some other computer to administrate. What will happent if Veeam server crush. We will not be able to start replicas? Is there Veeam console or?

Thank you for your time Nshestakov

[Shestakov]

You are very welcome.

3rd Question: I mean with that if we run replica failover shall we have changes saved somewhere while we are in that state and where can we see it?

Replica Failover is a switching from the original VM on the source host to its VM replica on the target host.
If you perform replication jobs, all changes of the production VMs of the job will be replicated(copied) to VMs on the DR site.
Usually our users also backup those VMs for additional safety, since, say system errors may cause loss of data both on primary and disaster recovery sites.

4th question: If we have promary Veeam can we install console on some other computer to administrate. What will happent if Veeam server crush. We will not be able to start replicas? Is there Veeam console or?

Yes, there is an Enterprise Manager web UI where you can run the server remotely. You can also use RDP for remote administration.
For a case of disaster with Veeam Server, you can backup VBR`s configuration and easily restore the configuration if something unexpected happens.
Here is also an interesting article about Physical vs. Virtual VBR installation practices

Let me know if you have any further questions.

[Gostev]

Normally, you want to have backup server that manages your replication jobs installed in the DR site, so that it is not lost during production site outage, and can still be used to perform failover.