bprestore difference in GUI and CLI

[Harry_NBAD]

Hello All,

I need to know the difference between the bprestore command when executed using gui and CLI.

If I am using cli we need to mention the -S for master server, -C for client name used for finding backup/archives which will be used to restore files and -D for specifying the destination client upon which the files will be restored.

While using GUI we need to mention the name of the master server as the "server to use for backup and restore", "source client for restores" and "destination client for restores".

Looking at both it is certain that -S and "server to use for backup and restore" is the same as master server, -D and "destination client for restores" is the same as the destination server over which the files will be restored.

I have some ambiguity regarding the -C and "source client for restores" , kindly clarify!

Thanks in advance!!!

[rk1074]

-C client

Specifies a client name to use for finding backups or archives from which to restore files. This name must be as it appears in the NetBackup catalog. The default is the current client name.

so -C specifies the server from which the backup was taken..

[Nicolai]

-C & -D will will be different for redirected restores (e.g. from SRV1 to SRV2).

-C & -D will be the same for restore to the same host. Most likely you will omit -D for same host restore.

[rk1074]

Damn!!!

Missing the thums up button....

[Marianne]

I don't understand where you see ambiguity?

 -C for client name used for finding backup/archives is simply another way to define 'source client'.

[Harry_NBAD]

In our env we are using the STD (standard disks of the ServerB) and BCV (businnes continuity volume alligned at the backup server ServerA), the snapshot of the STD is taken over BCV and then the backup of this data is done by the backup job. This is a raw backup. Master server and the media server is the same machine.

While restoring the from CLI, I am using the following options:

/usr/openv/netbackup/bin/bprestore -r -L bplogs.txt -R rename.txt -C master server -D master-server -S master-server -p policy -s $starttime -e $endtime -f source.txt

But in the GUI, I have to put netbackup server as ServerA, Source machine as ServerB and destination server as per my requirements which could be any machine same as like we can mention any name in the -D option in bprestore command.

Why is this difference between the -C in the bprestore and source server?

[Marianne]

-C in bprestore and Source Client in BAR are EXACTLY the same thing. 

Forget that the data actually belongs to ServerB. In the backup policy you have ServerA as Client name, right?

The Client name in the Policy is the Source Client in the GUI and the same name that must be used with -C in bprestore.

Destination Client in BAR or -D with bprestore can be ServerB or ANY other hostname where NBU is installed.
The fact that the data actually belongs to ServerB means nothing - only the name used in the Policy.

[Harry_NBAD]

I have checked that the client name specified in the policy is the SERVERA(backup server), but when I need to restore the file using the GUI I need to mention the source client as SERVERB(to which the STD's belong).

Instead if I use cli, I mention the name of ServerA in the -C option.

[Marianne · Accepted solution]

Sorry, this is not how NetBackup works.

If ServerB's bcv is mapped to ServerA and you have a policy with ServerA in the Clients tab of the policy, there is no way that NBU knows that the data actually belongs to ServerB. Unless you are using Snapshot Client to automate this process, but then the Client name in the policy would be ServerB, with the 'offhost-client' in Attributes configured as ServerA.

If you can type/select ServerB in the Source Client tab of the GUI and find backed up data, it means that there is a policy with ServerB in Clients tab.

Please show us the backup policy that is backing up ServerB's data on ServerA:

bppllist <policy-name> -L

[Harry_NBAD]

eux290{root}# bppllist bck_raw_vg730d_gdc -L

Policy Name:       bck_raw_vg730d_gdc
Options:           0x0
template:          FALSE
audit_reason:         ?
Names:             (none)
Policy Type:       Standard (0)
Active:            yes
Effective date:    11/03/2004 15:54:12
Client Compress:   no
Follow NFS Mnts:   no
Cross Mnt Points:  no
Collect TIR info:      no
Block Incremental: no
Mult. Data Stream: yes
Perform Snapshot Backup:   no
Snapshot Method:           (none)
Snapshot Method Arguments: (none)
Perform Offhost Backup:    no
Backup Copy:               0
Use Data Mover:            no
Data Mover Type:           -1
Use Alternate Client:      no
Alternate Client Name:     (none)
Use Virtual Machine:      0
Hyper-V Server Name:     (none)
Enable Instant Recovery:   no
Policy Priority:   10
Max Jobs/Policy:   Unlimited
Disaster Recovery: 0
Collect BMR Info:  no
Keyword:           vg730d
Data Classification:       -
Residence is Storage Lifecycle Policy:    no
Client Encrypt:    no
Checkpoint:        no
Residence:         eux290-hcart-robot-tld-0
Volume Pool:       HPUX_Retention_1W
Server Group:      *ANY*
Granular Restore Info:  no
Exchange Source attributes:              no
Exchange 2010 Preferred Server: (none defined)
Application Discovery:      no
Discovery Lifetime:      0 seconds
ASC Application and attributes: (none defined)
Generation:      40
Ignore Client Direct:  no
Enable Metadata Indexing:  no
Index server name:  NULL
Use Accelerator:  no
Client/HW/OS/Pri/DMI:  eux290 HP9000-800 HP-UX11.11 0 0 0 0 ?
Include:           NEW_STREAM
Include:           /dev/rdisk/disk13861
Include:           /dev/rdisk/disk2273
Include:           /dev/rdisk/disk2274
Include:           /dev/rdisk/disk2275
Include:           /dev/rdisk/disk2268
Schedule:              monthly
  Type:                FULL (0)
  Frequency:           28 day(s) (2419200 seconds)
  Maximum MPX:         2
  Synthetic:           0
  Checksum Change Detection: 0
  PFI Recovery:        0
  Retention Level:     5 (3 months)
  u-wind/o/d:          0 0
  Incr Type:           DELTA (0)
  Alt Read Host:       (none defined)
  Max Frag Size:       0 MB
  Number Copies:       1
  Fail on Error:       0
  Residence:           (specific storage unit not required)
  Volume Pool:         HPUX_Retention_3M
  Server Group:        (same as specified for policy)
  Residence is Storage Lifecycle Policy:         0
  Schedule indexing:     0
  Daily Windows:
   Day         Open       Close       W-Open     W-Close
   Sunday      000:00:00  000:00:00
   Monday      000:00:00  000:00:00
   Tuesday     000:00:00  000:00:00
   Wednesday   000:00:00  000:00:00
   Thursday    000:00:00  000:00:00
   Friday      000:00:00  000:00:00
   Saturday    000:00:00  000:00:00
Schedule:              weekly
  Type:                FULL (0)
  Frequency:           7 day(s) (604800 seconds)
  Maximum MPX:         2
  Synthetic:           0
  Checksum Change Detection: 0
  PFI Recovery:        0
  Retention Level:     3 (1 month)
  u-wind/o/d:          0 0
  Incr Type:           DELTA (0)
  Alt Read Host:       (none defined)
  Max Frag Size:       0 MB
  Number Copies:       1
  Fail on Error:       0
  Residence:           (specific storage unit not required)
  Volume Pool:         HPUX_Retention_1M
  Server Group:        (same as specified for policy)
  Residence is Storage Lifecycle Policy:         0
  Schedule indexing:     0
  Daily Windows:
   Day         Open       Close       W-Open     W-Close
   Sunday      000:00:00  000:00:00
   Monday      000:00:00  000:00:00
   Tuesday     000:00:00  000:00:00
   Wednesday   000:00:00  000:00:00
   Thursday    000:00:00  000:00:00
   Friday      000:00:00  000:00:00
   Saturday    000:00:00  000:00:00
Schedule:              daily
  Type:                FULL (0)
  Frequency:           1 day(s) (86400 seconds)
  Maximum MPX:         2
  Synthetic:           0
  Checksum Change Detection: 0
  PFI Recovery:        0
  Retention Level:     0 (1 week)
  u-wind/o/d:          0 0
  Incr Type:           DELTA (0)
  Alt Read Host:       (none defined)
  Max Frag Size:       0 MB
  Number Copies:       1
  Fail on Error:       0
  Residence:           (specific storage unit not required)
  Volume Pool:         HPUX_Retention_1W
  Server Group:        (same as specified for policy)
  Residence is Storage Lifecycle Policy:         0
  Schedule indexing:     0
  Daily Windows:
   Day         Open       Close       W-Open     W-Close
   Sunday      000:00:00  000:00:00
   Monday      000:00:00  000:00:00
   Tuesday     000:00:00  000:00:00
   Wednesday   000:00:00  000:00:00
   Thursday    000:00:00  000:00:00
   Friday      000:00:00  000:00:00
   Saturday    000:00:00  000:00:00
eux290{root}#
eux290{root}#
eux290{root}#

[Marianne]

Client/HW/OS/Pri/DMI:  eux290 HP9000-800 HP-UX11.11 0 0 0 0 ?

To restore data backed up by this policy, the source client in BAR will be eux290.

The same name will be used with -C option in bprestore.

[Harry_NBAD]

I enquired it further in the policy details and found that the there are 2 different policies one is for raw backup in which the client name is used same as backup server and in the other source server is listed as the client. Hence it clarifies the usage of serverB in the source client for that particular policy using gui.

[Marianne]

I thought as much...

As per my post 2 days ago:

If you can type/select ServerB in the Source Client tab of the GUI and find backed up data, it means that there is a policy with ServerB in Clients tab.