Hi Fabian,
What I mean by flexible is that on the command line via Powershell we can specifiy the destination folder in particular where we want the backup files to go. You don't seem to have the same control via "jobs" but it isn't a show stopper. So long as we know where the backup files are written we can move to our NAS and then to offsite backup (removable USB in our case).
The job has a retention of 1 day but doesn't seem to be deleting the previous backup files. We manually delete the VBRZip generated files as part of the PowerShell scripts - we can do the same for the Proxmox backups if we need to.
I think that when we started using Veeam a few years ago the job scheduling might not have been as sophisticated as it is now, so we went down the Powershell script path and we also only have ESXi hosts and VMs.
I guess we were just assuming that our scripts would "just keep working" but perhaps we were a bit too optimistic.
What I mean by flexible is that on the command line via Powershell we can specifiy the destination folder in particular where we want the backup files to go. You don't seem to have the same control via "jobs" but it isn't a show stopper. So long as we know where the backup files are written we can move to our NAS and then to offsite backup (removable USB in our case).
The job has a retention of 1 day but doesn't seem to be deleting the previous backup files. We manually delete the VBRZip generated files as part of the PowerShell scripts - we can do the same for the Proxmox backups if we need to.
I think that when we started using Veeam a few years ago the job scheduling might not have been as sophisticated as it is now, so we went down the Powershell script path and we also only have ESXi hosts and VMs.
I guess we were just assuming that our scripts would "just keep working" but perhaps we were a bit too optimistic.
Statistics: Posted by mhurcombe — Apr 07, 2025 2:03 am
