VeeamON 2024 - Use Code "COMMUNITY10" for 10% Off!
Thanks! ..and same. Was never a Norton fan. Never heard of, thus never used. ‘Commander’ myself. And, I am (almost) old
Thanks @Inder !! :)
Well said Craig!
If you are not installing the Mgmt Pack on a server running SC Ops Mgr (i.e. you have SC Config Mgmr), or, as @MicoolPaul and @Chris.Childerhose stated, not running the SC Ops Mgr minimum version as shown in your error, then you will have this install problem. For Mgmt Pack installation System Requirements, see here.
Hi @dmarkham ...need more info here. How is the test backup job for the VM configured? Do you have AAIP and/or guest processing settings configured? Error looks possibly like could be credentials issue with ap-aware integration processing maybe? What are other settings? (i.e. encryption, etc) Thanks.
Wonder also what the job properties looks like. Is Direct SAN used? Hot add? NBD? Did the job try SAN or Hot Add & couldn't so failed over to NBD? If so, is there a NFS permission issue somewhere?
You bet @dips ..thank you. Stay tuned as I hope to clear up some misconceptions about restore point behavior in subsequent posts.Cheers!
Nice! Glad you got it sorted.
Thank you @AndyPilk ...totally agree!
Thanks Chris!
Hi @BirdMan ...sorry for the vague answer, but “it depends”. My recommendation, and what I would do, is leave the max concurrent for each repo. You could then stagger your jobs such that they would not use the same Host the Repos are on at the same time and your jobs would “rock out” on the Host resources. I actually do that myself. And, Veeam would automatically ‘hold back’ on tasks anyway if they are “in use” by other tasks/jobs.Hope that helps.Cheers!
What I also recommend is viewing Tim Smith’s “Architect Sizing” Session from VeeamON. It’s pretty amazing and would no doubt help you in moving forward. Go to veeam.com/veeamon and ‘log in’, then view Sessions from the Americas. Video is here.Cheers!
Appreciate the kind words @Nico Losschaert . Agree on the wording. I’ll mark that down and maybe make mention of that in the Forums, along with a question or 2 I still need answered before I finish my Part III post :) Cheers!
Did @vmiss33 just say "snazzy"?? bwahahaha LOVE IT! 😂😂
Something to be aware of the rare time I need to do recovery processes. Eek! VMware strikes again 🙄Thanks for sharing @regnor !
Hi @Pegasus - that is actually how Veeam Replication works. Veeam doesn’t create vbk/vib files, but rather snaps. This is the same behavior for Veeam Repl for vSphere.
It’s explained pretty well in the ‘About Rep’ section of the Hyper-V Guide here and here.
Yes sir...when you need to recover, use the Veeam Console and use the Failover Wizard. Choose the specified VM you need, then click the ‘Point’ button to choose the restore point (snapshot) you want to recover to. Follow through the rest of the Wizard, as shown here.
You bet...glad to help!Cheers!
Thanks Chris….I’m not looking forwad to writing Part III. hahaha
Not too bad anymore, now that I have it (mostly) figured out. But, putting it into comprehensible, easy-to-understand words?...that’s another thing. ;)
For sure!..thanks Chris!
Appreciate it Rick!
Hi @Vinicius Silva ..as Chris mentioned, we need a bit more clearer info to assist you better. If you’re just wanting to know about a VM Disk in Hyper-V (I assume, based on .vhd you stated), then yes..you can. Just follow the VM Disk Restore wizard, as shown in the Hyper-V Guide here. If this is for the Veeam Server...then we need to know that. Again...just needing a bit more clearer and detailed info.Cheers!
@Vinicius Silva ...then yes, you can do this. Just select the Incremental restore point in the VM Files Restore wizard, then the location you want it to go. I believe the link I provided should give you all the details you need. Let us know if not.Cheers!
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.
