VeeamON 2024 - Use Code "COMMUNITY10" for 10% Off!
Sorry Jorge can I ask you which version of veeam backup would I need to buy to have the API ready? For the Restful API you need the Veeam Universal License Foundation at least or Veeam Backup & Replication Enterprise Plus
@JMeixner Thanks for sharing! I will try the exam this year 🙂
After change to per-VM Chain, an Active-Full backup is automatically created on the next job run.
What a speed 😎We have normally also around 1-2 GB/sec in our environments and some faster/slower.
Sounds very interesting!
Maybe there’s a VSS writer in failed state?
@vNote42 Thanks for sharing. This can be very helpful..
Well, I tried all of your advices and it worked 🙂 I cleaned up Exchange Server and won 10 GB extra space on disk and I started VSS Service (which was stopped); now backup is free from warnings. Thankes a lot again guys :) Perfect. 👍
Are you doing daily Backups as well or only weekly?
The job runs once a week on Sunday. The small setup: Server with connected Tandberg RDX External Drive published over a Network-Share to the Veeam-VM - VM1 on Server which is backuped - VM2 on Server with Veeam to backup VM1 The External Drive should exchanged weekly (maybe sometimes they forget it) If the job runs every week, the oldest vbk will removed after the 11 full-backup is completed.
To save space, you can make full backups on a monthly basis. The weekly backups are then incremental and smaller.
Thank you @JMeixner
@marco_s Thank’s for sharing 😎
@wolff.mateus Seems to be a very interesting software that I have to test in my lab 😎
You have to upgrade your Backup Chain befor it works
@marcofabbri Yes, after installing V12 you can switch your per-VM Backup Chain to True per-Machine Backup Chain see here:https://helpcenter.veeam.com/docs/backup/vsphere/per_vm_backup_files.html?ver=120
Thank you @jorge.delacruz !
Another great recap! Congrats to all 🤝
Thank you @Martin Weber!
Congratulations @Shaokat! Well done 🎉
After having our network team investigate we have learned that our inspection policy on our Palo firewall permits traffic to our cloud connect environment that matches the signature for Veeam cloud connect traffic using port 6180. The traffic is now presenting as unknown to the Palo and there for dropped. The work around was to disable the inspection. After that change was pushed our v12 Tenants were able to access their cloud resources as expected. I have the same Problem with one Tenant and a Fortigate Firewall on customers site. After deactivating the security profiles on the outgoing Firewall Rule the tenant connected to the VCSP successfully.
If you want to realize with Veeam, may an initial Seed can help. https://helpcenter.veeam.com/docs/backup/vsphere/backup_copy_mapping_auxiliary.html?ver=120
Great recap as always!
If you enable encryption for an existing job, except the backup copy job, during the next job session Veeam Backup & Replication will automatically create a full backup file. https://helpcenter.veeam.com/docs/backup/vsphere/encryption_best_practices.html?ver=120
@IT.support 🙈Sorry, overlooked Microsoft Azure in title...
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.