Showing results for 
Search instead for 
Did you mean: 

Cannot restore: Verify Failed with "Found no files in the database for backup id...."

Level 2

Dear Experts,

We have a Solaris Master Server, Windows 2008 Media Server and we are trying to restore some files form a Linux client.

When attempting to view files for restore, a message stating "There are no files matching the specified criteria" occurs, even though selections are correct.

If we clic on  the "use Backup History to set date range" we can see the image backed-up with the correct size.

Aldo, we can find the image with


bpimagelist -U -client xxxxxxxxx -d 01/01/2016
Backed Up Expires Files KB C Sched Type On Hold Index Status Policy
---------------- ---------- -------- -------- - ------------ ------- ------------ ------------
10/04/2016 15:36 10/18/2016 20 58070944 N Full Backup 0 0 F11241



but bplist give us an empty list


bplist -C xxxxxxxxx -s 01/01/2016 /
EXIT STATUS 227: no entity was found


If we verify the image the result is:

10:09:27 INF - Verifying policy <Policy>, schedule Full (<ClientName>_1475588169), path "@aaaiF", created 04.10.2016 15:36:09.
10:09:28 INF - Found no files in the database for backup id <ClientName>_1475588169
10:09:43 INF - Beginning verify on server <MediaServer> of client <ClientName>, reading file @aaaiF.
10:09:44 /var/opt/six/exports/dati/
10:09:44 INF - Expected filename /var/opt/six/exports/dati/ in database, found no more files.
10:09:44 /var/opt/<SomePath>
10:09:45 INF - Expected filename /var/opt/<SomePath> in database, found no more files.
10:11:37 /var/opt/<SomePath>/


Can you help us??

Thank you in advance




Level 6

Where are you trying the restore/verify from ?

Have seen some issues with unix files, when done from a windows server as the default policy then is Windows (13) rather than standard which should be used for Unix.

Also pretty sure I have seen a tech note about unix files backed up with a Windows type policy, just can't remember what the solution was.

The standard questions: Have you checked: 1) What has changed. 2) The manual 3) If there are any tech notes or VOX posts regarding the issue

Partner    VIP    Accredited Certified

Try to run


#bplist -t 0 -C xxxxxxxxx -s 01/01/2016 00:00:00 -R -l / | grep filename 

Does it show file you'd like to restore? You can get policy_type_number from the man bplist but I think you're trying to restore file that was backed up via "Standard" policy. -C <clientname> should be exactly like it's in the policy.  



Hello Michael thank you for your reply.

We are trying to restore and verify from the Java console.

We correctly backup hundreds of Linux clients with the same policy, master and media server.

So I think it's not a policy related issue...




Partner    VIP    Accredited Certified

It might be f-file corruption. Try to find that  <ClientName>_1475588169_FULL.f:

#find /usr/openv/netbackup/db/images -name <ClientName>_1475588169*

after that:

#strings <ClientName>_1475588169_FULL.f | grep <filename you tried to retore>


No, I got:

EXIT STATUS 227: no entity was found

Partner    VIP    Accredited Certified

Have you tried to locate the .f file as per the recommendation above? 

You maybe want to run bpdbm -consistency 2 to check image consistency.

Any chance that anyone have done some 'manual cleanups' in images folder? 


As stated above we located the .f file and all seems ok.

We also run the bpdbm -consistency 2 but still no luck.

All backups on this client end successfully but we cannot restore files (we don't need a specific file to restore at this time but we cannot restore any files).

We can also exclude absolutely that no one have done some 'manual cleanups'.

We an eventually destroy the client registration, all backups, any restore of this client provìding that we could start to restore file from now on.

any idea??

Partner    VIP    Accredited Certified
So, when you located the .f files, did you run 'strings' command against the file?
What kind of output was produced?

And bpdbm -consistency command results? It does not fix anything - you need to look for errors in the output...

The only other thing to do is log a Support call.
It does not seem as if we are going to be able to pinpoint the issue in this forum as information coming from your side is 'few and far between'....