Control NDMP Backups

[Patrick_Butler]

Is there a way to define whic server is actually running the backup? Right now my master server is running an NDMP backup and is running really slow. Though the destination server is shown in the topolgy as connected to my Netapp server, It almost looks like the Master is actually running the backup and transferring the data to the destination server?

[Marianne]

Which Storage unit is defined in the policy?

Which STU is listed in the job details?

Have you confirmed that the NDMP STU is configured correctly?

If we know which OS on the master, we can probably help with ways of checking I/O to devices at OS level.

You should be able to also check on the NAS device itself with OS commands (depending on which NAS device).

Monitoring I/O on the SAN switch will also confirm data path.

[Patrick_Butler]

The Storgae for the poilcy is a Windows 2006 R2 stoarge server with Netbackup as a media server with de-dupe.

I am not sure about "STU" or if it is properly configured for NDMP.

The Master is Windows 2003

The NDMP server is a Netapp running the 7.x OS

Id be intrested in these comands as well to monitor

[Marianne]

If you are backing up to disk storage on a Windows media server, the data is for sure transferred via the network.

Please share STU config - run this command on the master server from cmd:

<install-path>\netbackup\bin\admincmd> bpstulist -L

Sorry, I only have commands for Unix to monitor I/O at OS level.

[Patrick_Butler]

Ok here is what I get back.

Label:                usadbk02-hcart2-robot-tld-0
Storage Unit Type:    Media Manager
Host Connection:      usadbk02
Number of Drives:     2
On Demand Only:       no
Density:              hcart2 (14)
Robot Type/Number:    TLD (8) / 0
Max Fragment Size:    1048576
Max MPX/drive:        1

Label:                usadbk01
Storage Unit Type:    Disk
Media Subtype:        Basic (1)
Host Connection:      usadbk02
Concurrent Jobs:      2
On Demand Only:       no
Path:                 "E:\backups"
Robot Type:           (not robotic)
Max Fragment Size:    524288
Max MPX:              1
Stage data:           yes
Block Sharing:        no
File System Export:   no
High Water Mark:      98
Low Water Mark:       80
Ok On Root:           yes

Label:                usadlocal
Storage Unit Type:    Disk
Media Subtype:        Basic (1)
Host Connection:      usadbk02
Concurrent Jobs:      1
On Demand Only:       yes
Path:                 "C:\Backup"
Robot Type:           (not robotic)
Max Fragment Size:    524288
Max MPX:              1
Stage data:           no
Block Sharing:        no
File System Export:   no
High Water Mark:      98
Low Water Mark:       80
Ok On Root:           yes

Label:                dedupe
Storage Unit Type:    Disk
Media Subtype:        DiskPool (6)
Host Connection:      usadbkdd
Concurrent Jobs:      8
On Demand Only:       yes
Robot Type:           (not robotic)
Max Fragment Size:    51200
Max MPX:              1
Block Sharing:        yes
File System Export:   yes
Ok On Root:           no
Disk Pool:            dedupe

Label:                usadbkd2d_d1
Storage Unit Type:    Disk
Media Subtype:        Basic (1)
Host Connection:      usadbkd2d
Concurrent Jobs:      2
On Demand Only:       yes
Path:                 "E:\Backup"
Robot Type:           (not robotic)
Max Fragment Size:    524288
Max MPX:              1
Stage data:           no
Block Sharing:        no
File System Export:   no
High Water Mark:      98
Low Water Mark:       80
Ok On Root:           no

Label:                Usadbkd2d_d2
Storage Unit Type:    Disk
Media Subtype:        Basic (1)
Host Connection:      usadbkd2d
Concurrent Jobs:      2
On Demand Only:       yes
Path:                 "F:\backup"
Robot Type:           (not robotic)
Max Fragment Size:    524288
Max MPX:              1
Stage data:           no
Block Sharing:        no
File System Export:   no
High Water Mark:      98
Low Water Mark:       80
Ok On Root:           no

Label:                Usadbkd2d_d3
Storage Unit Type:    Disk
Media Subtype:        Basic (1)
Host Connection:      usadbkd2d
Concurrent Jobs:      2
On Demand Only:       yes
Path:                 "G:\Backup"
Robot Type:           (not robotic)
Max Fragment Size:    524288
Max MPX:              1
Stage data:           no
Block Sharing:        no
File System Export:   no
High Water Mark:      98
Low Water Mark:       80
Ok On Root:           no

Label:                Usadbkd2d_d4
Storage Unit Type:    Disk
Media Subtype:        Basic (1)
Host Connection:      usadbkd2d
Concurrent Jobs:      2
On Demand Only:       yes
Path:                 "H:\Backup"
Robot Type:           (not robotic)
Max Fragment Size:    524288
Max MPX:              1
Stage data:           no
Block Sharing:        no
File System Export:   no
High Water Mark:      98
Low Water Mark:       80
Ok On Root:           no

[Patrick_Butler]

Bump

[Marianne]

Apologies - I totally missed your last 2 posts...

Any of the storage units in your list will cause backups to be sent across the network to the media server specified in the STU's 'Host Connection:' parameter.

The media server name will also appear in Activity Monitor.

bpbrm and bptm logs on the media server will confirm that the backup is done by this media server and that data is transferred directly from the NAS to the media server.

[Deepak_W]

From this post I understand that you are doing NDMP backup of NetApp storage using Remote NDMP topology and also you have enabled deduplication.

You have dedupe enabled that means that data is travelling over LAN for sure. That means NBU is initiating the backup --> NetApp sending data to NBU server over LAN --> NBU receiving the data and processing single instancing (dedupe) and then saving the data in your dedupe pool MSDP/dedupe alliance.

But in all this excercise note that your data is travelling over LAN and NBU server is engaged doing all above mentioned tasks. If you wanna free your NBU server from these tasks then it is strongly recommended that go for Local NDMP backup topology. This will increase your backup throughput and redice your backup window. Also your major challange will be solved, as NDMP device itself will dump the data to target device over FC instead of it is sending data to NBU server for backup.

Hope this answers your query.