sharepoint and winodws backup failing with error code 58

[KS2]

We sharepoint, SQl and local drives backup configured for one of the client. We are facing strange issue with the client now.

1. D: drive full backup started failing for one of the drive with error code 58 and sometimes 42. Incremental backup worked for 2 days

2. sharepoint backup was also working fine.

3. SQl backup started failing with error code 25.

4. Full backup of D: ran and got successful last night but when checked on BAR it has backed up D: of master server.

5. we ran the incremental backup and it backed up master server's drives not the client. Drives which are not there on master server but present on client failed with error code 71.

6. sharepoint backup has started failing with error code 2.

7. OS backup not getting initiated now. Parent job is running from past half an hour and seems to be hung.

I have checked all the communication with bpclntcmd and bptestbpcs on master, media and client and all working fine.

Any assistance on this highly appreciated.

[Marianne]

Something VERY wrong with hostname lookup...  Using DNS or hosts files?

Have you tried all the 'normal' hostname lookup utilities?

bpclntcmd -hn <hostname>
bpclntcmd ip <ip-address-returned-above>

nslookup <hostname>
nslookup <ip-address-returned-above>

Do this in all directions - master to client and client to master.

[V4]

For sharepoint backup check on front end server if BEDS exist under logs if it's not create is manually and try to execute job again....

[KS2]

Hi Marianne,

Its using DNS. though i have added the client on master server host file also. We have issue with hostname resolution which we have fixed now and reverse lookup is resolving the correct host name of the client.

Now backup is not getting initiated and if i start particular drive backup it is taking backup of master server drive.

I have noticed one more thing while runnning bptestbpcd it is communicating on pbx port instead of vnetd

C:\Documents and Settings\abc>bptestbpcd -client ukss01
1 1 1
10.165.102.224:4994 -> 10.168.118.56:1556
10.165.102.224:4999 -> 10.168.118.56:1556
10.165.102.224:1119 -> 10.168.118.56:1556

PS: beds folder already present on log driectory.

[Marianne]

The network lookup seems fine.

We can see the source IP address on the master and client are different and that connection is fine.

PBX port connection is the default since 7.0.1. See http://www.symantec.com/docs/TECH136090

Do you have bpcd log on the client? Did bptestbpcd write to client's bpcd log?

Seems there might be some mis-configuration within NBU........

Please share output of config for master and client:

bpgetconfig -M <master>

bpgetconfig -M <client>

[KS2]

yes bptestbpcd is writing to client's bpcd logs. Please find the output of bpget config attached.

[KS2]

Please refer this output for master server.

[KS2]

Any further suggestions on this?

[MKT]

Try running this on the master/media/client and post the results

Windows: C:\Program files\veritas\netbackup\bin
UNIX: /usr/openv/netbackup/bin

bptestnetconn -as

bptestnetconn -sc -t 60 -o 30
 

[Marianne]

I don't see the client name (ukss01) in the Clients list on the master server?

Which Client name is specified in the problematic policy?

Please post output of 
bppllist <policy-name> -U

[KS2]

Hi Marriane please refer the second master file i attached later.

Please find the output of policy.

------------------------------------------------------------

Policy Name:       UK-WIN

  Policy Type:         MS-Windows
  Active:              yes
  Effective date:      02/08/2010 11:26:03
  Backup network drvs: no
  Collect TIR info:    yes, with move detection
  Mult. Data Streams:  yes
  Client Encrypt:      no
  Checkpoint:          no
  Policy Priority:     0
  Max Jobs/Policy:     6
  Disaster Recovery:   0
  Collect BMR info:    yes
  Residence:           PD-STU-UK
  Volume Pool:         NetBackup
  Server Group:        *ANY*
  Keyword:             (none specified)
  Data Classification:       -
  Residence is Storage Lifecycle Policy:    no

Granular Restore Info:  no
Ignore Client Direct:  no
  HW/OS/Client:  Windows-x86   Windows2003   UKdc01
                 Windows-x86   Windows2003   ukdc02
                 Windows-x86   Windows2003   ukma01
                 Windows-x86   Windows2003   ukss04
                 Windows-x86   Windows2003   ukms04
                 Windows-x86   Windows2003   ukss05
                 Windows-x86   Windows2003   ukms08
                 Windows-x86   Windows2003   ukms12
                 Windows-x86   Windows2003   ukms0b
                 Windows-x86   Windows2003   ukms3a
                 Windows-x86   Windows2003   ukms3e
                 Windows-x86   Windows2003   ukms18
                 Windows-x86   Windows2003   ukmsa2
                 Windows-x86   Windows2003   ukmsa3
                 Windows-x86   Windows2003   ukmsa6
                 Windows-x86   Windows2003   ukms23
                 Windows-x86   Windows2003   ukms27
                 Windows-x86   Windows2003   ukmsab
                 Windows-x86   Windows2003   ukmsaa
                 Windows-x86   Windows2003   ukmsac
                 Windows-x86   Windows2003   ukmsad
                 Windows-x86   Windows2003   ukms20
                 Windows-x86   Windows2003   ukms15
                 Windows-x86   WindowsXP     ukms06
                 Windows-x86   Windows2003   ukmsa5
                 Windows-x86   Windows2003   ukMS09
                 Windows-x86   Windows2003   ukss01

  Include:  ALL_LOCAL_DRIVES

  Schedule:          Weekly
    Type:            Full Backup
    Frequency:       every 3 days
    Maximum MPX:     1
    Synthetic:       0
    PFI Recovery:    0
    Retention Level: 3 (5 weeks)
    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)
    Residence is Storage Lifecycle Policy:     0
    Daily Windows:
          Tuesday    21:00:00  -->  Thursday   16:00:00

  Schedule:          Daily
    Type:            Differential Incremental Backup
    Frequency:       every 14 hours
    Maximum MPX:     1
    Synthetic:       0
    PFI Recovery:    0
    Retention Level: 1 (2 weeks)
    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)
    Residence is Storage Lifecycle Policy:     0
    Daily Windows:
          Monday     21:00:00  -->  Tuesday    08:00:00
          Wednesday  21:00:00  -->  Thursday   08:00:00
          Thursday   21:00:00  -->  Friday     08:00:00
          Friday     21:00:00  -->  Saturday   08:00:00

Also please find the attached putput of bptestcon

[Marianne]

I still don't quite understand your config... All other clients are backing up fine, just this one backs up the master server when the client name is specified?

Why whould the 1st bpgetconfig NOT have any reference to ukss01, the second one has UKss01 as Client but your policy contains  ukss01 (different case) ?

Maybe best to log a Support call with Symantec  - they have the time to analyze high level logs and config output (e.g. nbsu).

[Marianne]

One more thing:

The actual backup of the data is done by a media server.

Is PD-STU-UK assigned to one media server or a number of media servers?

See in Activity monitor which media server was used for the last backup and perform all the connection/lookup tests between the media server and the client.
(bptestbpcd, bpclntcmd, etc.)