Backup item not found with Get-VBRBackup but visible in GUI

[stephan.troxler]

I have a Backup item that is visible in the GUI. If I check the properties (via right-click menu), I see some servers that have been backed up and it shows me the restorepoints. The backups seem to be valid and working, I can also find the physical files.

If I however search for the same backup via Get-VBRBackup -name <backup>, it can't be found! I then queried all restorepoints with Get-VBRRestorePoint and searched for a server name that is part of this backup and found the same restorepoints like in the GUI. The lookup with $backup..GetBackup() of one of the restorepoints for the Backup object behind it results in a backupname of "<backupname> - <server>" that is a child backup. A lookup of the ParentBackupId property with "Get-VBRBackup -id <ParentBackupId>" however returns nothing.

Is there a way to fix this broken backup object or is it just somehow hidden?

Bonus question regarding backup objects:
- for how long does a backup object (result of Get-VBRBackup) exist? Is it ever be removed by Veeam? I have some backups with no restorepoints attached it. The backup item can't be found in the GUI and I wonder if they are safe to be removed.

[david.domask]

Hi Stephan,

I think it would be best on this one to open a Support Case and let Support review the issue with you.

Is this an Agent backup by chance or a Backup Copy backup by chance? Get-VBRBackup should handle these just fine, but there are a few possibilities on why you're seeing this behavior and it's best reviewed by Support, but try using a wildcard and removing the last few characters of the job name and see if it returns the backup.

Similarly, try Get-VBRBackup | Where-Object {$_.JobId -eq 'UUID of the job'} and see if that returns it correctly -- if so likely it's about the name as it's stored in the configuration database, but Support can assist with reviewing this.

For your bonus question, such objects should be cleared as part of the backup deletion process. I would point those out to Support and ask them to review the situation before removing via powershell, but if you can catch those "empty" backups with Powershell, it should be fine to just pipe them to Remove-VBRBackup or pass the backup object to Remove-VBRBackup on the -Backup parameter.

[stephan.troxler]

Thanks you. Yes, the backup is an Agent backup. I will open a ticket and also ask for the orphaned backup items.

[david.domask]

Got it, please share the case number once you have it -- since it's Agents, can I ask you to try just passing the first 10 or so characters of the name (or N characters where N == a string that is unique among the job/backup names) and then add a wildcard to it?

e.g., If the job name is "Agent Backups Windows G12543", try passing "Agent Backups Windows G12*" to the -Name paramter, does it show correctly?

[stephan.troxler]

My support case is #07352937.
Filtering with the * did not make any difference. I'm using get-vbrbackup without any filter and looping through all the backups to gather the restorepoints. At least one backup object is missing.