VeeamON 2024 - Use Code "COMMUNITY10" for 10% Off!
I will start a session on Monday, 11 AM CET, for one hour. This is EMEA focused from a schedule point of view, but anyone can join - just let me know if you haven’t attended one of my classes. Looking at the first session on January 29.Razvan Ionescu
Bandwidth will impact your replication, failover and failback. It depends on the amount of changed data that needs to be sent across. When you will saturate the bandwidth, you have the alternative to put in place WAN accelerators. Then you could go for increasing the bandwidth. Look also at how the VPN terminators are behaving from the point of view of performance.
Do both proxies have the same transport mode configured and the same number of task slots?
Hi,If you failback to the original VM in the original location you can enable Quick Rollback. This will use CBT to query for the changed blocks, instead of reading all the disks. https://helpcenter.veeam.com/docs/backup/vsphere/failback_quick_rollback.html?ver=110
Hi Karun,in VBR it is possible to create a backup copy job with source a VBA external repository and destination a scale out repository with offload to object storage (Microsoft Azure for example). VBA supports AWS KMS encryption of the backup repository (https://helpcenter.veeam.com/docs/vbaws/guide/encryption_repository_level.html?ver=50). You would probably need to encrypt at destination also. Please keep in mind that the backup copy job will be periodic and the scale out repository will also have its offload policy (copy or move). In VBA you could enable EC2 snapshot replication across regions (https://helpcenter.veeam.com/docs/vbaws/guide/add_policy_target_settings_replica.html?ver=50) Hope this helps
Running an immutable repo in a VM brings the risk of having the underlying infrastructure (hypervisor) compromised and that will affect the whole repo. This would not be a scenario for production environments.
You would need to use VBR to restore. https://helpcenter.veeam.com/docs/backup/vsphere/restore_google.html?ver=110
A few tips to make it easier: have the scenario (apps) you want to protect available and their dependencies ready (for example AD/DNS accessible in the recovery site) if using, prepare vCenter tags and categories and assign them to vSphere infra objects before starting Orchestrator config have your users/groups prepared in AD (for assigning them Orchestrator roles later) depending on what you want to showcase - create your Data Lab, custom scripts Orchestrator initial configuration needs the user under which Orchestrator was deployed. During this step you can add other users/groups
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.