Video Screencast Help

User Backup scripts not working for Windows 2003

Created: 15 Dec 2012 • Updated: 06 Jan 2013 | 15 comments
This issue has been solved. See solution.

Hi All,

I need your help for below issue which we are facing on windows system.

We have created the user backup policies and scripts. After executing the scripts , policy not executed in activity monitor but on the server scripts are in running state without an error.

This server has nated IP and also we have done the necessary changes and communication also done between master and server.

 

Master :- Solaris 10

Client :- windows 2003 X86

NBU Version :- 7.5.0.4

 

Regards,

 

Sagar

 

Comments 15 CommentsJump to latest comment

Nagalla's picture

hi  sagar,

posibally the commands that are running in client side are not reaching to the master server.

1) could you post the commands that you are running on the user side.

2) the bppllist <policyname> -U from mater server

3)bpcltncmd -pn   in client 

4)does the master server listed in first at  servers list in Registory?

 

Sagar_Kolhe's picture

Hi Nagalla,

1) could you post the commands that you are running on the user side.

Commands for what , communication  or policy execution

2) the bppllist <policyname> -U from mater server

Output given below

3)bpcltncmd -pn   in client 

No output , after sometime directly prompt is coming.

4)does the master server listed in first at  servers list in Registory?

Yes

PFA output for the policy.

 

 bppllist BCP_D_W_M_Computer1  -U
------------------------------------------------------------

Policy Name:       BCP_D_W_M_Computer1

  Policy Type:         MS-Windows
  Active:              yes
  Effective date:      03/21/2012 19:28:59
  Backup network drvs: no
  Collect TIR info:    no
  Mult. Data Streams:  no
  Client Encrypt:      no
  Checkpoint:          yes
       Interval:       15
  Policy Priority:     0
  Max Jobs/Policy:     Unlimited
  Disaster Recovery:   0
  Collect BMR info:    no
  Residence:           SF440-hcart3-robot-tld-1
  Volume Pool:         Bang_daily_pool
  Server Group:        Daily
  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:  Windows-x86   Windows2003   computer1

  Include:  d:\cdas
            d:\backupdb

  Schedule:              M_Computer1
    Type:                User Backup
    Maximum MPX:         5
    Synthetic:           0
    Checksum Change Detection: 0
    PFI Recovery:        0
    Retention Level:     10 (12 years)
    Number Copies:       1
    Fail on Error:       0
    Residence:           (specific storage unit not required)
    Volume Pool:         Bang_monthly_pool
    Server Group:        Monthly
    Residence is Storage Lifecycle Policy:         0
    Schedule indexing:     0
    Daily Windows:
          Sunday     00:00:00  -->  Sunday     23:59:59
          Monday     00:00:00  -->  Monday     23:59:59
          Tuesday    00:00:00  -->  Tuesday    23:59:59
          Wednesday  00:00:00  -->  Wednesday  23:59:59
          Thursday   00:00:00  -->  Thursday   23:59:59
          Friday     00:00:00  -->  Friday     23:59:59
          Saturday   00:00:00  -->  Saturday   23:59:59

  Schedule:              W_Computer1
    Type:                User Backup
    Maximum MPX:         5
    Synthetic:           0
    Checksum Change Detection: 0
    PFI Recovery:        0
    Retention Level:     3 (1 month)
    Number Copies:       1
    Fail on Error:       0
    Residence:           (specific storage unit not required)
    Volume Pool:         Bang_weekly_pool
    Server Group:        Weekly
    Residence is Storage Lifecycle Policy:         0
    Schedule indexing:     0
    Daily Windows:
          Sunday     00:00:00  -->  Sunday     23:59:59
          Monday     00:00:00  -->  Monday     23:59:59
          Tuesday    00:00:00  -->  Tuesday    23:59:59
          Wednesday  00:00:00  -->  Wednesday  23:59:59
          Thursday   00:00:00  -->  Thursday   23:59:59
          Friday     00:00:00  -->  Friday     23:59:59
          Saturday   00:00:00  -->  Saturday   23:59:59

  Schedule:              D_Computer1
    Type:                User Backup
    Maximum MPX:         5
    Synthetic:           0
    Checksum Change Detection: 0
    PFI Recovery:        0
    Retention Level:     1 (15 days)
    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
    Schedule indexing:     0
    Daily Windows:
          Sunday     00:00:00  -->  Sunday     23:59:59
          Monday     00:00:00  -->  Monday     23:59:59
          Tuesday    00:00:00  -->  Tuesday    23:59:59
          Wednesday  00:00:00  -->  Wednesday  23:59:59
          Thursday   00:00:00  -->  Thursday   23:59:59
          Friday     00:00:00  -->  Friday     23:59:59
          Saturday   00:00:00  -->  Saturday   23:59:59

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

bppllist BCP_D_W_M_dp12400 -U
------------------------------------------------------------

Policy Name:       BCP_D_W_M_dp12400

  Policy Type:         MS-Windows
  Active:              yes
  Effective date:      03/21/2012 19:28:59
  Backup network drvs: no
  Collect TIR info:    no
  Mult. Data Streams:  no
  Client Encrypt:      no
  Checkpoint:          yes
       Interval:       15
  Policy Priority:     0
  Max Jobs/Policy:     Unlimited
  Disaster Recovery:   0
  Collect BMR info:    no
  Residence:           SF440-hcart3-robot-tld-1
  Volume Pool:         Bang_daily_pool
  Server Group:        Daily
  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:  Windows-x86   Windows2003   dp12400

  Include:  d:\cdas
            d:\backupdb

  Schedule:              M_dp12400
    Type:                User Backup
    Maximum MPX:         5
    Synthetic:           0
    Checksum Change Detection: 0
    PFI Recovery:        0
    Retention Level:     10 (12 years)
    Number Copies:       1
    Fail on Error:       0
    Residence:           (specific storage unit not required)
    Volume Pool:         Bang_monthly_pool
    Server Group:        Monthly
    Residence is Storage Lifecycle Policy:         0
    Schedule indexing:     0
    Daily Windows:
          Sunday     00:00:00  -->  Sunday     23:59:59
          Monday     00:00:00  -->  Monday     23:59:59
          Tuesday    00:00:00  -->  Tuesday    23:59:59
          Wednesday  00:00:00  -->  Wednesday  23:59:59
          Thursday   00:00:00  -->  Thursday   23:59:59
          Friday     00:00:00  -->  Friday     23:59:59
          Saturday   00:00:00  -->  Saturday   23:59:59

  Schedule:              W_dp12400
    Type:                User Backup
    Maximum MPX:         5
    Synthetic:           0
    Checksum Change Detection: 0
    PFI Recovery:        0
    Retention Level:     3 (1 month)
    Number Copies:       1
    Fail on Error:       0
    Residence:           (specific storage unit not required)
    Volume Pool:         Bang_weekly_pool
    Server Group:        Weekly
    Residence is Storage Lifecycle Policy:         0
    Schedule indexing:     0
    Daily Windows:
          Sunday     00:00:00  -->  Sunday     23:59:59
          Monday     00:00:00  -->  Monday     23:59:59
          Tuesday    00:00:00  -->  Tuesday    23:59:59
          Wednesday  00:00:00  -->  Wednesday  23:59:59
          Thursday   00:00:00  -->  Thursday   23:59:59
          Friday     00:00:00  -->  Friday     23:59:59
          Saturday   00:00:00  -->  Saturday   23:59:59

  Schedule:              D_dp12400
    Type:                Full Backup
    Frequency:           every 7 days
    Maximum MPX:         5
    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)
    Residence is Storage Lifecycle Policy:         0
    Schedule indexing:     0
    Daily Windows:
          Sunday     00:00:00  -->  Sunday     23:59:59
          Monday     00:00:00  -->  Monday     23:59:59
          Tuesday    00:00:00  -->  Tuesday    23:59:59
          Wednesday  00:00:00  -->  Wednesday  23:59:59
          Thursday   00:00:00  -->  Thursday   23:59:59
          Friday     00:00:00  -->  Friday     23:59:59
          Saturday   00:00:00  -->  Saturday   23:59:59

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

 

 

Nagalla's picture

hi Sagar,

i was mean the command that you used in the script that you created to run the backup

are you running the script from the Client side?

 

 

3)bpcltncmd -pn   in client 

No output , after sometime directly prompt is coming. ----> this indicating that the client is not getting responce from the master server.

if you are running the script from the client side.. this is the place you need to start working..

you need to check the Server key , client Name key and the name /IP resolutions from Client side.. and need to make sure that you are getting responce from master when you run the command bpcltncmd -pn in client side.

 

 

 

 

Nagalla's picture

one more thing.. just an idea...

I am seeing you have specified the backup selection for both the policies... 

if that is correct... and if you does not need to chage that ..

you can make the  Schedule type as Automatic and have the script run in the master server at your desired time.. 

/usr/openv/netbackup/bin/bpbackup -i -p <policyname> -s <schedulename>

Sagar_Kolhe's picture

Hi Nagalla,

We are using below command

<install path> netbackup/bin/

bpbackup -p <policy name > -s schedule name -S master name -w path

We are getting connctivity to the srvers as  backup coming in wiritng mode , when we fired manually...

Yes we are running the script form client side.

Kindly help to resolve the bplcntmcd issue , as this servers has nated i/ps.

Sagar_Kolhe's picture

Nagalla,

Here we are using AUTOSYS to execute the user backups , so all this integrated according to the applications.

Nagalla's picture

hi Sagar,

bplcntmcd is the verification that to make sure that client is communicating with master properly..

please provide me the below outputs.

from client:-

bpclntcmd -self

bpclntcmd -hn  <mastername>

bpclntcmd -ip <masterip>

route print

ifconfig -a

nslookup <masterservername>

nslookup <masterserver IP>

entires of client registory keys... 

1)servers key

2) client name key

from master server:-

bpclntcmd -self

bpclntcmd -pn

 

bpclntcmd -hn  <mastername>

bpclntcmd -ip <masterip>

bpclntcmd -hn  <Client name>

bpclntcmd -ip <Client IP>

you can just attache a notepad with all this outputs.. 

 

 

Sagar_Kolhe's picture

Hi Nagalla,

Sorry for wrong update,

We are getting the response from master and client both.PFA output.

 

From client to master.

D:\Veritas\NetBackup\bin>bpclntcmd -pn

expecting response from server SF440

computer1 computer1 10.159.37.85 1849

Sagar_Kolhe's picture

And from Master Server to Client,

 

bpclntcmd -hn computer1
host computer1: computer1 at 10.159.37.85
aliases:     computer1     10.159.37.85

 

Nagalla's picture

hi Sagar,

that is a good sign,

try this command from client , i have added -i switch...and removed  -w , it says about the window time.. not path.. 

bpbackup -i -p <policy name > -s schedule name -S master name d:\backupdb

 

if you want to use more then one file or directy.. then keep all those in a file and provide those to the command with -f switch

bpbackup -i -p <policy name > -s schedule name -S master name -f <filelistfile>

if those commands work, you can keep the same in the script and make sure of those..

check this below tech note for more help about bpbackup

http://www.symantec.com/business/support/index?pag...

 

PS:-to run the above commands your schedule type does not needs to be User backup, it can be automatic backup also..

hope this helps.. 

 

 

SOLUTION
Sagar_Kolhe's picture

Hi Nagalla,

PFA output for client and master.

AttachmentSize
output.txt 5.12 KB
output.txt 913 bytes
Sagar_Kolhe's picture

Hi Nagalla,

Issue is resolve for one server, But the ohter server issue is same,

Kindly check above output and confirm.

 

Nagalla's picture

hi Sagar,

see the below output, you master server IP is 10.225.4. 44 but when you check that with bpclntcmd -hn SF440 its showing 10.159.37.70.

something wrong with Name resolutions.

 

---------------------
C:\Veritas\NetBackup\bin>bpclntcmd -hn SF440
host SF440: SF440 at 10.159.37.70
aliases:     SF440     10.159.37.70

-------------------------
C:\Veritas\NetBackup\bin>bpclntcmd -ip 10.225.4.44
host 10.225.4.44: SF440 at 10.159.37.70
host 10.225.4.44: SF440 at 10.225.4.44
aliases:     SF440     10.225.4.44     10.159.37.70

Make sure your server dp12400 etc/hosts file does not have the multiple entries.. of Master server.

and also if you have DNS, make sure that is resolvig the correct IP.

hope this helps..

Sagar_Kolhe's picture

Hi ,

This servers are having nated IP so that any backup traffic is going throgh 10.159.37.70

Nagalla's picture

if that is the case...

remove the entires of 10.225.4.44 in the hosts file of client server.. just make sure that its resolving only 10.159.37.70.

as you need only communication with 10.159.37.70, ... you can remove anoter IP, OneName having 2 IP address in hosts file is not a good sing.. 

and then check..