Forum Discussion

Lylex's avatar
Lylex
Level 3
12 years ago

User Backup & Archive failing with 230 status

This post is a continuation of:  https://www-secure.symantec.com/connect/forums/archiving-client-files-longer-retention-period-backup-policy    My thanks to Martin (mph999) for his help on that one.

I'm having problems getting User Backup and User Archive running.  They always exit with a 230 status in the Activity Monitor, which I believe is "The specified policy name does not exist".  The same entries in the Activity Monitor also show Job Policy as "*NULL*", where I would expect to see the policy name "asb-con-ops-002".

Client is Centos 5.6 running NBU 7.5 client.  I use the BAR gui to select a file (that's under one of the filesystems included in the policy) and just click "Backup".

Server is Solaris 5.10 running NBU 7.5.0.3 server.   An exerpt from the output of "bppllist asb-con-ops-002 -U" below.

Any advice on where to look next is appreciated.  Thanks...Lyle

Policy Name:       asb-con-ops-002
  Policy Type:         Standard
  Active:              yes
  Effective date:      05/07/2008 10:11:35
  Client Compress:     no
  Follow NFS Mounts:   yes
  Cross Mount Points:  yes
  Collect TIR info:    no
  Block Incremental:   no
  Mult. Data Streams:  yes
  Client Encrypt:      no
  Checkpoint:          no
  Policy Priority:     0
  Max Jobs/Policy:     Unlimited
  Disaster Recovery:   0
  Collect BMR info:    no
  Residence:           asb-con-bck-001-hcart2-robot-tld-0
  Volume Pool:         1_year_pool
  Server Group:        *ANY*
  Keyword:             (none specified)
  Data Classification:       -
  Residence is Storage Lifecycle Policy:    no
  Application Discovery:      no
  Discovery Lifetime:      0 seconds
  ASC Application and attributes: (none defined)
  Granular Restore Info:  no
  Ignore Client Direct:  no
  Enable Metadata Indexing:  no
  Index server name:  NULL
  Use Accelerator:  no
  HW/OS/Client:  Linux         RedHat2.6     asb-con-ops-002

  Include:  /opco/srv/nop
            /var
            /etc
            /home/ATSB/sftest/incoming/products
            /opco/srv/ftp/mirrors
            /home/ATSB/sftest
            /opco/shares/public
            /opco/shares/iso

  Schedule:              UserBackup
    Type:                User Backup
    Maximum MPX:         1
    Synthetic:           0
    Checksum Change Detection: 0
    PFI Recovery:        0
    Retention Level:     6 (6 months)
    Number Copies:       1
    Fail on Error:       0
    Residence:           (specific storage unit not required)
    Volume Pool:         6_month_pool
    Server Group:        (same as specified for policy)
    Residence is Storage Lifecycle Policy:         0
    Schedule indexing:     0
    Daily Windows:
          Sunday     00:00:00  -->  Saturday   23:59:59

  • I would firstly double-check that CLIENT_NAME in client's bp.conf corresponds 100% with Client name in policy: asb-con-ops-002 .

    Next, ensure that bprd log exists on the master. If not, create the folder and restart NBU.

    Try the user backup again. 

    Check bprd log on the master for incoming request from client, how client's IP is resolved to a hostname and how master server looks for correct policy for the client.

    Please copy bprd log to bprd.txt and post as File attachment.

2 Replies

  • I would firstly double-check that CLIENT_NAME in client's bp.conf corresponds 100% with Client name in policy: asb-con-ops-002 .

    Next, ensure that bprd log exists on the master. If not, create the folder and restart NBU.

    Try the user backup again. 

    Check bprd log on the master for incoming request from client, how client's IP is resolved to a hostname and how master server looks for correct policy for the client.

    Please copy bprd log to bprd.txt and post as File attachment.

  • Thanks, Marianne.  Once you pointed to name resolution I realized that that lookups on the client weren't working.  The client's domain was wrong.  When I got that straitened out and rebooted, User Backup and User Archive started working.