VeeamON 2024 - Use Code "COMMUNITY10" for 10% Off!
As far as the purpose of VRO, it simply orchestrates actions you would normally perform manually as well as execute scripts that you have created to perform specific tasks.If you are tasked with manually testing your DR plan on a regular basis and maintaining the documentation then you should consider VRO. Not only can you execute your DR plan in a sandbox environment to comply with testing requirements, your DR documentation and testing results can be saved to a pdf or printed off to hand to anyone needing proof of compliance. By utilizing tags in vmware, your DR plans automatically update to include new workloads and your documentation is updated as well.
Ed, the first place you should visit is the Hands-on Labs for VRO. https://go.veeam.com/hands-on-lab-experience The guide will walk you through connecting to VCenter and VBR in that sandbox environment. There are a lot of steps, agreed, but once it is connected you are able to orchestrate any actions you would normally do through VBR and Vcenter to facilitate a recovery.Reach out to me directly if you would like to discuss.
Great article, complementing the one I had written. I arrive at the same conclusions as many of you: the Inline Entropy module remains quite vague in terms of information and requires thorough investigation. I have a question about malware detection using the File System Analysis module,do you have a warning in the job session in case of detection? However, for those interested, here are some screenshots of the detection results🕵️♂️🔍: What VBR build # are you on?
Grand slam!
Already have an account? Login
Enter your 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.