Can`t find any backup on spesific server

[Kristoffer_Lie]

Hi.

I have a BIG problem.  Need to restore a lot of files but when i search for it i can`t find any backups i BAR.

In NAC i can see that i have 2 backups with status 0. Why cant BAR see this? 

The policy is set to backup to tape. 

See picture for details:

System info:

Symantec Netbackup 7.6.0.1 ( server and client )

Backup server 2008 r2

Client server 2012 r2 

[Andy_Welburn]

Use the *exact* same name as in the policy when searching for backups to restore from - I notice a FQDN in the BAR error message & a non-FQDN in the backup status report.

[Kristoffer_Lie]

I know.  i have tryed with both:  
servername.domain  
servername 
SERVERNAME 
SERVERNAME.DOMAIN

Nothing works.... :(
( or did i miss understand you?    FQDM - Fully qualyfied domain name )

Søkeresultater

[Andy_Welburn]

No you didn't mis-understand!

You should use the name per the policy (i.e. at**fs01) which isn't what your attachment is showing (you missed a bit of redaction in that by the way!)

Only other things that immediately spring to mind:

policy type (I presume *is* actually MS_Windows?) ;

permissions (looks like runnning the BAR on the client - have you tried on the master?)

retention (I doubt that they would have already expired, but ....)

[Marianne]

Activity Monitor shows shortname in the Client column.

This name in Source Client of BAR must match EXACTLY.
If client was installed as client.domain, and restore is attempted from Client. this is the name that will be sent to master to request backups.

The next thing to check is the Policy Type in the backup policy.
Is it really MS-Windows?
If policy type was accidently set to Standard, the backup will work, but a search for MS-Windows will fail. 
The policy type in BAR must match the type selected in the Policy.

The last thing to check is the date range (if this was selected in BAR).

Try to open BAR on the master server where you can actually select/type client name in Source Client field.
Ensure Client name an policy type matches what is in the Backup Policy config.

[Kristoffer_Lie · Accepted solution]

Solution found.   The retention was to short...   so noobish of me... thx for the help tho...   :(

[Kristoffer_Lie]

BTW:  If the job was written to a tape....  and the tape is not overwritten... is there any chance for me to stil get it back?

[Marianne]

Yes. You can import the tape. Phase 1 and phase 2 import.

[Kristoffer_Lie]

But how can i find out witch tape the job was written to..  have 2-300 here.....
( i know where to find the Phase 1 and 2 guide )

[Andy_Welburn]

\o/ \o/ \o/

"Yay me!"

[Marianne]

Just had another look at your screenshot. 
So, you are saying that backups made on 31 Jan, 1 Feb, 2 Feb have ALREADY expired??????

Meaning retention is less than a week?
For a fileserver?
This would simply be unforgivable in most organizations as this means that SLAs have been compromised.

[Marianne]

So, how would you know if tapes were overwritten or not? 

NBU keeps log of daily activities for 28 days.

If you run All Log Entries report for this client for backup dates, the media id used for backup will be in the report.

[Kristoffer_Lie]

I dont know if the tapes have been overwritten...  i just have to try.
THANKS SO MUTCH FOR THE HELP!

[Marianne]

LOL! 

Seems you are living up to your Profile Pic - FILE NOT FOUND!

Career limiting statement.....

You need to have a good look at ALL policies and ALL schedules.

[Kristoffer_Lie]

Hehe. The picture is a Joke ;)  
The backup`s you are refering to ( 31,1 and 2 feb ) was failed backup.......    196 and 96.

aka i had to get the 28.01.15 job.  its now retrived and ok.   ( imported from tape. And yes the job had wrong retention. Its fixed and running fina again. And i have checked the reste of my jobs and they are fine.  

;)