Forum Discussion

somesh_p's avatar
somesh_p
Level 4
12 years ago
Solved

Backup partially successful with BMR error

Getting below error

May 2, 2013 12:38:45 PM - Error bpbrm (pid=22878) BMRERR: Received BMR error: Failed to import Config file.

May 2, 2013 12:38:45 PM - Error bpbrm (pid=22878) BMRERR: Received BMR error: Failed sending the discovery.

 May 2, 2013 12:38:45 PM - Error bpbrm (pid=22878) BMRERR: Received BMR error: BMR information discovery failed. (1)

 

I've below system configuration. Can anyone spot what is causing this BMR error

 

we do have:

1.ipmp for link aggregation

2. aside from root disks, all disks are used for ZFS filesystems.

--a ZFS disk

skny911(root) #: prtvtoc /dev/dsk/c1t0d0s0

* /dev/dsk/c1t0d0s0 partition map

*

* Dimensions:

*     512 bytes/sector

* 583838727 sectors

* 583838660 accessible sectors

*

* Flags:

*   1: unmountable

*  10: read-only

*

* Unallocated space:

*       First     Sector    Last

*       Sector     Count    Sector

*          34       222       255

*

*                          First     Sector    Last

* Partition  Tag  Flags    Sector     Count    Sector  Mount Directory

       0      4    00        256 583822054 583822309

       8     11    00  583822310     16384 583838693

 

 

--from format print

 

Part      Tag    Flag     First Sector         Size         Last Sector

  0        usr    wm               256      278.39GB          583822309

  1 unassigned    wm                 0           0               0

  2 unassigned    wm                 0           0               0

  3 unassigned    wm                 0           0               0

  4 unassigned    wm                 0           0               0

  5 unassigned    wm                 0           0               0

 6 unassigned    wm                 0           0               0

  8   reserved    wm         583822310        8.00MB          583838693

 

=============================================================================================================

--root disk

skny911(root) #: prtvtoc /dev/dsk/c3t0d0s0

* /dev/dsk/c3t0d0s0 partition map

*

* Dimensions:

*     512 bytes/sector

*      63 sectors/track

*     255 tracks/cylinder

*   16065 sectors/cylinder

*   17847 cylinders

*   17845 accessible cylinders

*

* Flags:

*   1: unmountable

*  10: read-only

*

*                          First     Sector    Last

* Partition  Tag  Flags    Sector     Count    Sector  Mount Directory

       0      0    00     289170  25045335  25334504

       1      3    01      16065    273105    289169

       2      5    00          0 286679925 286679924

       3      0    00   25334505 232058925 257393429

       5      0    00  257393430     32130 257425559

       6      0    00  257425560   4209030 261634589

       7      2    00  261634590  25045335 286679924

       8      1    01          0     16065     16064

skny911(root) #:

 

--from format print

Part      Tag    Flag     Cylinders         Size            Blocks

  0 unassigned    wm      18 -  1576       11.94GB    (1559/0/0)   25045335

  1       swap    wu       1 -    17      133.35MB    (17/0/0)       273105

  2     backup    wm       0 - 17844      136.70GB    (17845/0/0) 286679925

  3 unassigned    wm    1577 - 16021      110.65GB    (14445/0/0) 232058925

  4 unassigned    wu       0                0         (0/0/0)             0

  5 unassigned    wm   16022 - 16023       15.69MB    (2/0/0)         32130

  6 unassigned    wm   16024 - 16285        2.01GB    (262/0/0)     4209030

  7       root    wm   16286 - 17844       11.94GB    (1559/0/0)   25045335

  8       boot    wu       0 -     0        7.84MB    (1/0/0)         16065

  9 unassigned    wu       0                0         (0/0/0)             0

 

  • The BMR error can be on the client (invalid/unsupported configuration) or on the server (unable to import).

    To verofy:

    1. On the client run "bmrsavecfg -infoonly".  If this completes without error, then check on the Master.

    2. Copy the client configuration file to the Master to some directory location.  For example /tmp.  The client configuration is "/usr/openv/netbackup/baremetal/client/data/bundle.dat".  Then run the command:

    bmrs -o import -res Config -path /tmp/bundle.dat      (sample file location - it can be anywhere)

    If this fails, it points to an import error.

    For the above client, what version of NetBackup is being used?  The use of ZFS was not supported until 7.5.0.4 and later.

     

     

3 Replies

  • The BMR error can be on the client (invalid/unsupported configuration) or on the server (unable to import).

    To verofy:

    1. On the client run "bmrsavecfg -infoonly".  If this completes without error, then check on the Master.

    2. Copy the client configuration file to the Master to some directory location.  For example /tmp.  The client configuration is "/usr/openv/netbackup/baremetal/client/data/bundle.dat".  Then run the command:

    bmrs -o import -res Config -path /tmp/bundle.dat      (sample file location - it can be anywhere)

    If this fails, it points to an import error.

    For the above client, what version of NetBackup is being used?  The use of ZFS was not supported until 7.5.0.4 and later.

     

     

  • Sorry inn_kam. Your post of a zfs file system problem is associated with a restor time issue.  This thread involves a problem registering a client during a normal BMR enabled backup.  If the client was in a restoring phase, it obvioulsy was already properly registered.