Q: How the product is licensed?
A: Per physical CPU socket of "source" hypervisor host where processed virtual machines reside. Destination hosts (for replication, and migration jobs) do not need to be licensed.
The backup repository is deployed closer to the source host – so the source-side agent can easily communicate with the agent hosted on the repository to obtain metadata required for incremental job runs
admcomputing wrote:Vitaliy S. wrote:
Here is the procedure you should follow:
1. Configure a backup job for the VM you want to perform initial seeding for.
2. Create and choose any local repository for the backup files.
3. Once you have backup files created, move them to a DR site and place them on the DR site repository (you should create it beforehand).
4. Scan DR site repository to populate backup files in the backup console.
5. After that just create a replication job with "Low connection bandwidth" checkbox enabled.
6. On the "Seeding" step of the replication job wizard specify DR site repository where you've placed VM backup files.
7. Finish configuration of replication job wizard and start replication job.
Hope this helps!
joemagjr wrote:So my question is can this repository that sits at the DR site be a VM? I have not been able to locate that information in the documentaion.
Users browsing this forum: Bing [Bot], Google Feedfetcher and 8 guests