VeeamON 2024 - Use Code "COMMUNITY10" for 10% Off!
Congrats Geoff, All the best in your new role.
Congrats @Geoff Burke
Is this VM Level backup via VBR or the Agent?
12.1 release notes still only show 15.x as supported https://www.veeam.com/veeam_backup_12_1_release_notes_rn.pdfPostgreSQL 14.x, 15.x (version 15.5 is included in the setup) Note that Veeam Backup & Replication does not support PostgreSQL installations on cloud database services (for example, Amazon Relational Database Service (RDS).
@coolsport00 Thanks for spotting Shane …. I’m blaming old age on that one. Fixed it now :)
The disk space check is a big time saver. We have lots of deployments where the guys always get stung by low disk space when performing upgrades.
Have you edited the job and verified that the backup location path exists?
Does the backup of an individual file work?If you have re-installed the agent it may be worth resetting the DB as well if you haven’t already done so.https://www.veeam.com/kb2335
@Steve Blair easiest way is to open the folder sort on date/time and then run the job. The job logs should be the newest ones.
Thanks for the write up, Geoff. This looks perfect start to expand my knowledge on this subject.
Thanks for this @michaelcade as someone on the wrong side of 50, this shift in computing interests me.I shall try and get my teeth into the #90DaysOfDevOps and expand my knowledge.
If this is SMB it's not an issue with long file names / special characters is it?
I assume you also have AV on these as well. If you have the default rules in place without any exceptions for Veeam this can cause a performance hit as well due to reading/writing of the data.
Great work @keironbell Love seeing the work you’re doing driving the automation of our platform. #proudworkdad
Hi @NemanjaJanicic This blog post may be of assistance.
Its a good point Shane as it seems to have been around for some time (in excess of 10 years) and yet for VMware its still quite a young product and nowhere near as polished as it could / should be.go figure
I’ve seen this issue with things like low space on the server and also issues with the VSS writers.We have also seen it with corrupt blocks on a disk causing the issue.
Brilliant summary @MicoolPaul thanks for collating all the info and sharing Sir :)
We use service accounts to facilitate the majority of this.The Help Center guides provides some great information if you want to go granular with the permissions.Permissions - User Guide for VMware vSphere (veeam.com) Is it just a single domain/environment you’re backing up or multi-tenanted?
Does it work with the VPN disabled? I know you said it worked before the VPN was installed/activated.The log files may also be in %programdata%\Veeam\Endpoint
This may well fix it. Do you have Restrict VPN connections usage checked? https://helpcenter.veeam.com/docs/agentforwindows/userguide/settings_network_vpn.html?ver=60
If it works with the VPN disabled then something within the VPN is blocking it?https://hide.me/en/knowledgebase/how-to-split-a-vpn-tunnel/Looking at their website it is possible to block and whitelist apps.
Thanks @Madi.Cristil
Do you have space to try an active full? I know it will create a new chain but probably the easiest way if there is a chance of a corrupt file.
@Ian Sanderson I’d say probably virtual is the easiest to setup? I think a physical one would be good but we could look to plan that in at some point and have a virtual one first?
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.
