Hello my friends, here I am again, the problem is this, I have a requisition for restoring a folder, so I've gone in restore, gone where the folder I need to restore is and BAM, it gives me the error message "No Entity Was Found". Tried to increase the backup window and the error continues. Looking in the problem, most of folders in the same directory don't gives error, but, as murphy's law, only the critical folders in this parent folder do this error. Oh, and looking the reports of this policy, all jobs exited with status 0. Anyone knows this message, and how can I workaround and restore the files? NetBackup 7.5.0.4 Master Server: HP-UX IA64 Client where the folder is: SuSe 2.6 with NetBackup 7.5.0.4

Have you tried using a Windows Admin Console - probably give the same result but may be worth a try?

No Entity was found restoring some folders

22 Replies

revarooo
Level 6
13 years ago
It's simply not finding the files in the catalog. Have you selected the correct type of backup?
Andre_Torres
Level 5
13 years ago
Sure. It is in a Linux, and type is standard, so, yeah, I'm selecting the correct type.
Marianne
Level 6
13 years ago
'No entity found' means that 'for the parameters that you have specified, no entity was found'.

So, you need to carefully check ALL of the parameters.

Please post output of the policy completing with status 0:

bppllist <policy-name> -U

as well as what you need to restore.

Unless policy is backing up ALL_LOCAL_DRIVES, how sure are you that all required contents is getting backed up?

Let us start by having a look at policy config. Based on that, we will let you know what else we need...
Mark_Solutions
Level 6
13 years ago
Also check the exclusions on that client This normally happens during an incremental backup when nothing has changed so the job ends with 0 but nothing has been backed up Likewise with exclusions where the folder is backed up but not the files which gives the same.error
Andre_Torres
Level 5
13 years ago

Policy Name: <policy name>

Policy Type: Standard

Active: yes

Effective date: 06/17/2002 12:00:00

Client Compress: no

Follow NFS Mounts: no

Cross Mount Points: yes

Collect TIR info: no

Block Incremental: no

Mult. Data Streams: yes

Client Encrypt: no

Checkpoint: no

Policy Priority: 0

Max Jobs/Policy: Unlimited

Disaster Recovery: 0

Collect BMR info: no

Residence: <Storage Unit>

Volume Pool: Netware

Server Group: *ANY*

Keyword: (none specified)

Data Classification: -

Residence is Storage Lifecycle Policy: no

Application Discovery: no

Discovery Lifetime: 0 seconds

ASC Application and attributes: (none defined)

Granular Restore Info: no

Ignore Client Direct: no

Enable Metadata Indexing: no

Index server name: NULL

Use Accelerator: no

HW/OS/Client: Linux SuSE2.6 <Server Name>

Include: NEW_STREAM

/media/nss/SYS_K1/

/media/nss/VOL1/

/media/nss/VOL2/

/media/nss/IPRINT/

/backup/

NEW_STREAM

/media/nss/VOL3/

/media/nss/SYS_K/

Schedule: <schedule name>

Type: Differential Incremental Backup

Frequency: every 1 day

Maximum MPX: 1

Synthetic: 0

Checksum Change Detection: 0

PFI Recovery: 0

Retention Level: 8 (1 year)

Number Copies: 1

Fail on Error: 0

Residence: (specific storage unit not required)

Volume Pool: (same as policy volume pool)

Server Group: (same as specified for policy)

EXCLUDE DATE 0 - 08/15/2004

EXCLUDE DATE 1 - 10/30/2004

EXCLUDE DATE 2 - 10/31/2004

EXCLUDE DATE 3 - 07/02/2005

EXCLUDE DATE 4 - 03/24/2006

EXCLUDE DATE 5 - 09/25/2007

EXCLUDE DATE 6 - 10/15/2007

EXCLUDE DATE 7 - 11/01/2007

EXCLUDE DATE 8 - 11/15/2007

EXCLUDE DATE 9 - 12/01/2007

EXCLUDE DATE 10 - 12/15/2007

EXCLUDE DATE 11 - 01/01/2008

EXCLUDE DATE 12 - 01/15/2008

EXCLUDE DATE 13 - 02/01/2008

EXCLUDE DATE 14 - 02/15/2008

EXCLUDE DATE 15 - 03/01/2008

EXCLUDE DATE 16 - 03/15/2008

EXCLUDE DATE 17 - 04/01/2008

EXCLUDE DATE 18 - 04/15/2008

EXCLUDE DATE 19 - 05/01/2008

EXCLUDE DATE 20 - 05/15/2008

EXCLUDE DATE 21 - 06/01/2008

EXCLUDE DATE 22 - 06/15/2008

EXCLUDE DATE 23 - 07/01/2008

EXCLUDE DATE 24 - 07/15/2008

EXCLUDE DATE 25 - 08/01/2008

EXCLUDE DATE 26 - 08/15/2008

EXCLUDE DATE 27 - 09/01/2008

EXCLUDE DATE 28 - 09/15/2008

EXCLUDE DATE 29 - 10/01/2008

EXCLUDE DATE 30 - 10/15/2008

EXCLUDE DATE 31 - 10/30/2008

EXCLUDE DATE 32 - 11/13/2008

EXCLUDE DATE 33 - 11/29/2008

EXCLUDE DATE 34 - 12/13/2008

EXCLUDE DATE 35 - 06/26/2009

EXCLUDE DATE 36 - 06/15/2010

EXCLUDE DATE 37 - 09/18/2010

Residence is Storage Lifecycle Policy: 0

Schedule indexing: 0

Daily Windows:

####################################################################

I need to restore a file in a subdirectory under /media/nss/VOL1/
Mark_Solutions
Level 6
13 years ago
Does the nss have a relevance to what it is? The policy says not to follow network systems - how is that location mounted? Again - check for excludes Also look in the catalog for that image or the client backup report to see how many kb were actually backed up
Marianne
Level 6
13 years ago
"Cross mount points' should cover everything under /media/nss/VOL1/ , even if folder is another mount point and not just a folder....

Question now is - when was folder created? Did it contain anything when backup ran?
Without verbose bpbkar log it is difficult to say...

Please check output of bplist on the master server:

bplist -t 0 -C <client-name> -s <mm/dd/yyyy> -e <mm/dd/yyyy> -R 4 /media/nss/VOL1/
(-s = start date, -e = end date)
Jim_Horalek
Level 4
13 years ago
Most of the time I have seen "No Enty Found" it was a DNS issue. Short name vs Long names(FQDN).

Try looking for the client with the other name.
thesanman
Level 6
13 years ago
I note your exclude dates go way to 2004 yet your policy output only lists a single schedule, a differential incremental with a 1 year retention. Is this the only schedule you have for this policy and are the files that you are trying to restore older than 1 year? If so it would seem to me that with no full backup any unmodified files older than one year are not being retained.
Andre_Torres
Level 5
13 years ago
Well we've managed to identify the problem. Some folders have special characters, such as 'Ç', '~', '^'. As the words are written in portuguese.

Restoring the above directory, it returns everything, including the folders with this characters, but this workaround can't be done everytime, as we have very huge folders, and renaming the folders is not an option, because it will lose a lot of network mappings, and we can't afford remapping hundreds of computers.

So, knowing now, what is the cause of the problem, I want a tip to what can we done to solve once and for all this problem.