solaris bmr errors

[manatee]

NBU 7.5.0.5, solaris 10/8 64bit

i copied an existing bmr backup policy i made for a Windows server and just edited the clients list. everything else is the same.

ran the test bmr backup policy and it finished with an exit status of 1. below are the errors:

2/08/2014 14:10:13 - collecting BMR information
12/08/2014 14:10:13 - connecting
12/08/2014 14:10:13 - connected; connect time: 0:00:00
12/08/2014 14:10:13 - transfering BMR information to the master server
12/08/2014 14:10:13 - connecting
12/08/2014 14:10:13 - connected; connect time: 0:00:00
12/08/2014 14:10:19 - Error bpbrm (pid=22282) BMRERR: Received BMR error: Failed to import Config file. (1)
12/08/2014 14:10:19 - Error bpbrm (pid=22282) BMRERR: Received BMR error: Failed sending the discovery. (1)
12/08/2014 14:10:19 - Error bpbrm (pid=22282) BMRERR: Received BMR error: BMR information discovery failed. (1)
12/08/2014 14:10:19 - Info bmrsavecfg (pid=0) done. status: 1: the requested operation was partially successful
12/08/2014 14:10:19 - end writing
Operation Status: 1

i've also attached the "Attributes" screenshot. i compared with the Windows version that is working perfectly and everything checks out. could i be missing something else?

[Marianne]

The screenshot is too small to make out anything. Try to add it as attachment or else post the text output of policy config:
bppllist <policy-name> -U

Please also run this command on the client and post the output:

bmrsavecfg -infoonly

[manatee]

this is the policy:

[root@ovmmanager ~]# bppllist ruh1siebdbt1_bmr -U
------------------------------------------------------------

Policy Name:       ruh1siebdbt1_bmr

  Policy Type:         Standard
  Active:              no
  Effective date:      12/12/2012 12:31:10
  Client Compress:     no
  Follow NFS Mounts:   no
  Cross Mount Points:  no
  Collect TIR info:    yes, with move detection
  Block Incremental:   no
  Mult. Data Streams:  no
  Client Encrypt:      no
  Checkpoint:          no
  Policy Priority:     0
  Max Jobs/Policy:     Unlimited
  Disaster Recovery:   0
  Collect BMR info:    yes
  Residence:           SLP-PureDisk-to-Tape
  Volume Pool:         Daily
  Server Group:        *ANY*
  Keyword:             (none specified)
  Data Classification:       Gold
  Residence is Storage Lifecycle Policy:    yes
  Application Discovery:      no
  Discovery Lifetime:      0 seconds
ASC Application and attributes: (none defined)

  Granular Restore Info:  no
  Ignore Client Direct:  yes
Enable Metadata Indexing:  no
Index server name:  NULL
  Use Accelerator:  no
  HW/OS/Client:  Solaris       Solaris10     ruh1siebdbt1

  Include:  ALL_LOCAL_DRIVES

  Schedule:              Monthly
    Type:                Full Backup
    Maximum MPX:         1
    Synthetic:           0
    Checksum Change Detection: 0
    PFI Recovery:        0
    Retention Level:     0 (1 week)
    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)
    Calendar sched: Enabled
      SPECIFIC DATE 0 - 12/08/2014
    Residence is Storage Lifecycle Policy:         0
    Schedule indexing:     0
    Daily Windows:
          Monday     12:00:00  -->  Monday     15:00:00

from the client, i get an error:

root@ruh1siebdbt1 # ./bmrsavecfg -infoonly
cat: cannot open /etc/path_to_inst

[Marianne]

/etc/path_to_inst is an important OS file that contains device-related info. Most definitely needed by BMR. Show this error to the Solaris sysadmin to investigate and fix.

[manatee]

that file (if it's the exact name) doesn't exist.

should it have been created by some NBU install process?

[Marianne]

/etc/path_to_inst is not a NBU file.

It is an OS file that is created during OS installation and updated each time a reconfiguration boot is done.
It maps physical device names to instance numbers.
Seems that someone working on this system may have manually deleted the file.

If you search Oracle web site for /etc/path_to_install you will find links on how to recreate this file.

This is however a task for a Solaris System Administrator, not a backup admin.

See this link for a sample file: https://docs.oracle.com/cd/E23823_01/html/816-5174/path-to-inst-4.html

[manatee · Accepted solution]

tried to recreate "/etc/path_to_install" using

• cfgadm –al
• devfsadm –Cv

without rebooting. nothing. ran into more problems.

i guess that particular server was not correctly created. will look into reinstalling the OS.