VeeamON 2024 - Use Code "COMMUNITY10" for 10% Off!
The steps are good but you should be able to connect to the repository on Azure and restore your VM from there directly without having to use another job in the middle. Adding External Repositories - User Guide for Microsoft Hyper-V (veeam.com) Yes, @Chris.Childerhose is right.After the External Repository is configured you will be able to run the Instant Recovery direct from the backups stored on Azure:
Hello,This will definitely work. I did a few times already.You don’t need to worry about different file extensions, the backups created by Veeam Backup for Azure are different, but it’s all compatible.
C - Use CSV files to create protection groups and create backup jobs for the protection groups https://helpcenter.veeam.com/docs/backup/agents/protection_groups_types.html?ver=120
As everyone told, this is probably happening because the job is not configured to run in the Forever Foward Incremental.Go to Advanced Setting in the Storage section and check how it’s configured. It should be like this: If it’s selected to create synthetic full or active full backup you must deselect those options.
You can create Backup Copy Job to this new repository.
We have already raised a support case with Veeam on this issue. @wesmrt yes, when we deployed this appliance last year, it came with v5. ALmost sure the problem is this that I said.It’s not really a problem, but if you want to protect the VB Azure with Azure Site Recovery, then I believe the only solution is creating a new appliance and perform the configuraiton restore. It’s actually pretty simple and everything will be imported and ready to use.
This happens because your appliance was probably created with the first image of v5. This image is scheduled for deprecation.What you could do is create a new Veeam Backup for Azure appliance and perform a configuration backup and configuration restore in the new appliance. The new appliance is using a new image, so it won’t be a problem anymore. https://helpcenter.veeam.com/docs/vbazure/guide/configuration_backup_and_restore.html?ver=60
A user with administrator access should work.This server has UAC enabled? If so, disabled to have a try.
As support engineer at Veeam I see many, many customers like this.Congrats on make your customer life easier, Nico :)
For me it’s definitely need to suport Hyper-V as a source and AWS as destination in future releases.
Actually, it was updated a few days ago 😁Great reminder about how important is the AV exclusions. You guys have no idea how many problems we have with AV...
I’m so happy that I’m not a sysadmin anymore during this ransomware era.It’s hard to be protected nowadays. :(
Besides all the tips the guys comment, if possible, I would add Field Experience.Of course, you can pass without so much experience, but for me the experience was fundamental. As I work supporting the product I must know each feature and this was great to be able to pass the cert.
I used with a Linux Hardened Repository a few days ago to test a few things, so as Chris said, it`s totally compatible. No problem at all.
To use this option you must have a Storage that supports Snapshots and it’s supported by Veeam.The biggest advatange is the short time the snapshot lives on vSphere side during the backup. We explain better in the User Guide: https://helpcenter.veeam.com/docs/backup/storage/vm_processing.html?ver=120 Also, this KB shows the Storages that supports Snapshot integration with VBR: https://www.veeam.com/kb4206
O Veeam não funciona quando você faz via NAT.A única forma é via VPN ou com o Cloud Connect (que também vai ser via VPN).Explica melhor como é o amibente.
I’m almost sure this changed on v12: https://www.veeam.com/veeam_data_platform_feature_comparison_ds.pdf
The only option you have with Hyper-V is the SureBackup using backups.
To be sure about the reason of this error you need to check the VSS logs in the source machine.Usually they are located on C:\Programdata\Veeam\Backup. You should see files with the names:VeeamGuestHelper VeeamVssSupportThis could help to identify the problem.Also, it’s a good idea to run the command below to see if the Writer are all stable:vssadmin list writers
Congrats everyone!
Hello,The server must be able to communicate with the VBR server.CHeck all the ports requirements here: https://helpcenter.veeam.com/docs/agentforwindows/userguide/ports.html?ver=60
I saw customer using backup copy from StoreOnce to Object Storage, it’s ok, no compatibility issue as far as I know.
Is it not showing anything on inventory → unstructured data, Cary?Like here:
You won’t be able to even install the proxy in the new Backup Server because the original server already has the service.Like Shane said, it’s not possible to do that.
It’s hard to know, but if it’s only 3 clients and this started happening after the update, is it an options remove, reinstall the Agent and start new backup chains?
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.
