VeeamON 2024 - Use Code "COMMUNITY10" for 10% Off!
Congratulations my friend @Iams3le!Well deserved.
Valeu por compartilhar @rfsantos!
Voted!Very nice posts anyway.
I was late with recaps, after a week traveling to my new job.I watched this one right now and was a good one. Thank you @marcofabbri for mention my post on yours.
Amazing recap! Congrats for all post. This mention to Veeam Community on Gartner was insane!!Well done, we are on the right path. No doubt about it!
One thing you need to remember is that you use the same bucket for both layers (Standard S3 and Glacier S3).When I start using the archive option I thought 2 buckets are necessaries.
So, here we are again! Congrats to all of you specially to the new members.Welcome @Andanet, @marco_s, @MarkBoothman, @Moustafa_Hindawi, Tim and @Tyler Jurgens!
Congrats boy!
Como tu fez o deploy do Veeam for AWS? Foi através do marketplace da AWS?Em algum momento a tua job de backup chegou a executar com sucesso ou esse erro já ocorreu logo na primeira execução? Se possível compartilha um print do erro também.
Amazing live!Congrats to all participants and @Scott for the win.
Valeu pelo post @rfsantos!Sempre é bom ficar sabendo desses casos.
Muito legal a iniciativa Ju!A comunidade agradece… 🤙🏻
Thanks for this another recap guys!Nice friday to everyone...
Do not use XFS nowadays is about losing space.I really recommend you to use this kind of filesystem to enable fast cloning on Veeam and enjoy the facility of synthetic fulls to save space on your repository.Is RHEL obligatory on your company?
Welcome here @clownyboots178!One tip I can give you about Veeam Legend program:Think on this about the community and engaging with that, all next improvements on that are going to be a consequence.
Yeah! Try this way to not hit any security problem.Other thing to take care is about VBR version. You will need to have the same version on two sides.
Just take care to not use the same user for multiple connections.Veeam uses a certificate between VBR and repo and you can face problems with that. In the same hand is not a security best practice.
Nice recap as always and have a nice travel Madi!Good Friday to all of you...
This is a case that is not only about technology. 😐
Very nice test man!
First, congrats to all members mentioned.I notice that the quality of all posts is growing up like our community!Good to see this, but only one can get the vote… 🤞
Are talking about a VMware environment, right? During the restore process you can chose what is the datastore that you want to put the VM restored:Step 7. Select Target Datastore and Disk Type - User Guide for VMware vSphere (veeam.com)
Problem solved after adding my user as local admin.I still don’t know if this is the ritgh way.
It seems a Restore operator user privileges with permission only on files. You can check permission on VBR console with administrator rights. No VBR was associate yet. So I believe that is a permission problem only on VEM server.
You do not need the Recovery Media ISO to restore files.You can restore it directly on Agent:Restoring Files and Folders - Veeam Agent for Microsoft Windows Guide
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.