VeeamON 2024 - Use Code "COMMUNITY10" for 10% Off!
Hi @M.Mamdouh -Yep, that is expected behavior for encryption. If you restore using the SAME VBR server you used to create the encrypted jobs, you will not be prompted for a pwd. You are only prompted if a backup file is attempting to be restored from a different VBR server than where the job was encrypted at. You can read more about that behavior in the User Guide.Encryption No Pwd for Encryption
Hi @M.Mamdouh . Yeah, we’ve had a couple posts by others on here with the same issue which shared all they needed to do was reboot, thus why I shared to try that first. Glad to hear it resolved your issue. And thanks for sharing what worked with the Community. Don’t forget to mark if one of the provided comments helped you resolve this, so others who may come across your post with a similar issue may benefit.Best!
Hi @Noushad -The Community isn’t actually support. We do try to assist members with questions, but your best resolution is to wait and see what Support suggests to do.Best.
Ok, keep us posted.
Well done @jcolonfzenpr !! We don't use VB365 or I'd give it a try. Thanks for sharing.
Okay Thanks will do that. Keep us posted what they find out.
At this point @juggu , I think it best you get ahold of Veeam Support.
From the Home node > Backups section, click Disks, expand the Job then select VM to restore. There is no Entire VM option in the ribbon or by rt-clicking?
Nice post Michael. For sure things to consider when devising a recovery strategy and a DR Plan.
Is AAIP enabled in the backup job, as was asked earlier?
Can you restore it successfully on the same HV host? Are you able to try that?
@Chris.Childerhose thank you, I tried reboot and that did not help. Which specific log should I check? @coolsport00 thank you I will check Ok.. Keep us posted.
Hi @Keren -I found a Forums post which states it could be something with a user.config file in your AppData folder. See this post what Egor (PM) suggests to do. Obviously, in the path he references, yours would be 12.1###. Basically, you’ll just need to change the name of the user.config file. Try that and see if it works. Just to be safe, make sure to take a snapshot of the VM before attempting the change.
Great adds there @Andanet ! Thank you for sharing.
Thanks @leduardoserrano . Looking forward to helping the Community here!
What about using “per-vm” repo vs normal repo? Are synthetic operations faster than traditional operations since Veeam uses existing restore points to create the synthetic full? Sorry @jaceg23 ...didn’t see the 2nd part of your question re: Synth vs Active Fulls - well, mostly I would say definitely yes, especially if you’re using a Block Clone filesystem like ReFS (Windows) or XFS (Linux). Creating a Synth Full is almost negligible/instantaneous because of how this storage filesystem architecture works. 1. all data is currently on the Repo storage so Veeam just uses all data “local” to the Repo, as such 2. Veeam doesn’t have to traverse the network as is needed to create the Active Full; and 3. Veeam doesn’t have to create snaps on the source VM lessening the load on the prod storage and thus doesn’t hinder production VM performance.
I'd configure per-vm for 2 reasons...1. To get the most stream usage out of your SAN, 2. because new (starting with v12) copy jobs by default use per-vm.
I used to use the latter @jaceg23 (FFwd and periodic compact, etc), but since I now use Immutable storage, the only option there is Fwd. And, I configure synthetic fulls. I actually recommend that route, if you can.
Another thing to keep in mind @jaceg23 ...if you use ReFS on Windows or XFS in Linux for your Repo, it is recommended to do Synthetic vs Active fulls as the time it takes to perform is negligible. Just FYI.
Only when you reach your configured retention settings...yes. You have to retain a full chain, due example.. 7, or you wouldn't be able to perform a restore. So, for the Fwd method, you need more Repo storage because you can have up to 2 full chains before the previous one is deleted.
Basically speaking, yes, Veeam has to keep all previous restore points in a chain to adhere to your configured retention settings.
Hi @jaceg23 -Imo the best way to see how it all works, is to watch the retention animations Veeam has in a KB. See below, and click the link there for each backup method (Fwd, FFwd, Rev). For your specific question, you would focus on the Fwd method. https://www.veeam.com/kb1799
Great list @Chris.Childerhose !!Great point about the hands-on. Probably the best learning method.
@loughraj - another way to possibly narrow down where the ‘access’ issue is, is to look at the other Win11 machines which are fine and look at the log process for those to see where Veeam is accessing at each step. Maybe something stands out that’s different between the success and failure computers?
As Chris shared, yep..you can. You can read more about Surebackup creation, etc in the Guide for assistance:https://helpcenter.veeam.com/docs/backup/vsphere/vlab_datastore_vm.html?ver=120https://helpcenter.veeam.com/docs/backup/vsphere/surebackup_hiw.html?ver=120
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.
