Restore strange behaviour after using SLP duplication rule

[MiloHaze]

Hello All,

Recently the backup environment that I'm responsible for, got two 5220 Symantec appliances.

Each is located in different data center (primary - APPL1 and disaster - APPL2 DC).

I've confugred SLP rule that each backup on APPL1 is duplicated to APPL2.

Everything looks fine up to the point when I want to restore something in the priamry DC from APPL1.

The catalog shows that the needed image is primary copy @ APPL1 and copy 2 @ APPL2.

However, when the restore starts, all the data is pulled from APPL2 over the network. Restore completes succesfully.

Anyone seen this before and any ideas how to fix it?

Thank you forward.

[RamNagalla]

by any chance below file is presented on your master server 

/usr/openv/netbackup/ALT_RESTORE_COPY_NUMBER with number 2 in it

if yes.. that explines the reason.. and you need to remove that inorder to take the restore from Primanry copy.

[Nicolai]

http://www.symantec.com/docs/TECH5584

You can use bpimagelist to check which copy is the primary copy by looking at field 28 "Primary Copy"

e.g: bpimagelist -hoursago 24 | grep -i image | awk '{ print $28 }

If copy 2 is always the primary copy it explain the behavior.

[Kiril_V_Dimitro]

Hello,

Regarding /usr/openv/netbackup/ALT_RESTORE_COPY_NUMBER, there's no such file on my master server.

Regarding bpimagelist -hoursago 24 | grep -i image | awk '{ print $28 }', it returns only 1 and 0.

Forgot to mention NBU versions that I'm using:

Master - 7.5.0.6

APPL1 and APPL2 - 7.5.0.5

Clients - 7.5.0.6

Any other ideas what to check?

Thank you forward.