cancel
Showing results for 
Search instead for 
Did you mean: 

Storage unit group is not using next storage storage unit media manager

gopi_enovate
Level 4

Hi,
      One Storage unit group is created using three storage units (media manager)
1st media manager storage unit uses shared tape drives from a tape library  (with max concurrent drives set to 2)
2nd media manager storage unit uses 1 SAS Tape library.
3rd media manager storage unit uses 1 SAS Tape library.


Storage unit selection is set to prioritized as the in the order mentioned above.

DSSU job uses only the storage unit from shared tape drives no matter the storage unit selection is round robin or media server load balancing.

 


Label:                eq22-LTO5
Storage Unit Type:    Media Manager
Host Connection:      EN-eq11
Number of Drives:     1
On Demand Only:       no
Max MPX/drive:        12
Density:              hcart2 - 1/2 Inch Cartridge 2
Robot Type/Number:    TLD / 1
Max Fragment Size:    1048576 MB

Label:                EN-eq22-hcart2-robot-tld-2
Storage Unit Type:    Media Manager
Host Connection:      EN-eq22.EN.local
Number of Drives:     1
On Demand Only:       no
Max MPX/drive:        6
Density:              hcart2 - 1/2 Inch Cartridge 2
Robot Type/Number:    TLD / 2
Max Fragment Size:    1048576 MB

Label:                EN-eq11-hcart2-robot-tld-4
Storage Unit Type:    Media Manager
Host Connection:      EN-eq11
Number of Drives:     1
On Demand Only:       no
Max MPX/drive:        12
Density:              hcart2 - 1/2 Inch Cartridge 2
Robot Type/Number:    TLD / 4
Max Fragment Size:    1048576 MB

Label:                EN-bu3-hcart3-robot-tld-0
Storage Unit Type:    Media Manager
Host Connection:      EN-bu3.EN.local
Number of Drives:     3
On Demand Only:       no
Max MPX/drive:        16
Density:              hcart3 - 1/2 Inch Cartridge 3
Robot Type/Number:    TLD / 0
Max Fragment Size:    1048576 MB

Label:                EN-eq22-hcart3-robot-tld-0
Storage Unit Type:    Media Manager
Host Connection:      EN-eq22.EN.local
Number of Drives:     2
On Demand Only:       no
Max MPX/drive:        16
Density:              hcart3 - 1/2 Inch Cartridge 3
Robot Type/Number:    TLD / 0
Max Fragment Size:    1048576 MB

Label:                EN-eq22-hcart2-robot-tld-3
Storage Unit Type:    Media Manager
Host Connection:      EN-eq22.EN.local
Number of Drives:     1
On Demand Only:       no
Max MPX/drive:        6
Density:              hcart2 - 1/2 Inch Cartridge 2
Robot Type/Number:    TLD / 3
Max Fragment Size:    1048576 MB

Label:                Staging1
Storage Unit Type:    Disk
Storage Unit Subtype: Basic (1)
Host Connection:      EN-bu3.EN.local
Concurrent Jobs:      15
On Demand Only:       no
Max MPX:              1
Path:                 "X:\Staging\eq11-1"
Max Fragment Size:    524288 MB
Stage data:           yes
Block Sharing:        no
High Water Mark:      60
Low Water Mark:       30
Ok On Root:           no

Label:                Staging2
Storage Unit Type:    Disk
Storage Unit Subtype: Basic (1)
Host Connection:      EN-bu3.EN.local
Concurrent Jobs:      15
On Demand Only:       yes
Max MPX:              1
Path:                 "X:\Staging\eq11"
Max Fragment Size:    524288 MB
Stage data:           yes
Block Sharing:        no
High Water Mark:      60
Low Water Mark:       30
Ok On Root:           no

Label:                Imaging
Storage Unit Type:    Disk
Storage Unit Subtype: Basic (1)
Host Connection:      EN-bu3.EN.local
Concurrent Jobs:      7
On Demand Only:       yes
Max MPX:              1
Path:                 "R:\Staging/image"
Max Fragment Size:    524288 MB
Stage data:           yes
Block Sharing:        no
High Water Mark:      80
Low Water Mark:       70
Ok On Root:           no

Label:                App1
Storage Unit Type:    Disk
Storage Unit Subtype: Basic (1)
Host Connection:      EN-bu3.EN.local
Concurrent Jobs:      8
On Demand Only:       yes
Max MPX:              1
Path:                 "X:\Staging\App1"
Max Fragment Size:    524288 MB
Stage data:           yes
Block Sharing:        no
High Water Mark:      55
Low Water Mark:       30
Ok On Root:           no

Label:                App01_Users
Storage Unit Type:    Disk
Storage Unit Subtype: Basic (1)
Host Connection:      EN-eq11
Concurrent Jobs:      10
On Demand Only:       yes
Max MPX:              1
Path:                 "K:\App01_users"
Max Fragment Size:    524288 MB
Stage data:           yes
Block Sharing:        no
High Water Mark:      60
Low Water Mark:       30
Ok On Root:           yes

Label:                App01_Companies
Storage Unit Type:    Disk
Storage Unit Subtype: Basic (1)
Host Connection:      EN-eq11
Concurrent Jobs:      10
On Demand Only:       yes
Max MPX:              1
Path:                 "K:\App01_companies"
Max Fragment Size:    524288 MB
Stage data:           yes
Block Sharing:        no
High Water Mark:      60
Low Water Mark:       30
Ok On Root:           no

Label:                SQL_DB
Storage Unit Type:    Disk
Storage Unit Subtype: Basic (1)
Host Connection:      EN-bu3.EN.local
Concurrent Jobs:      21
On Demand Only:       no
Max MPX:              1
Path:                 "R:\SQL_DB_Tmp"
Max Fragment Size:    524288 MB
Stage data:           yes
Block Sharing:        no
High Water Mark:      60
Low Water Mark:       30
Ok On Root:           yes

Label:                Image
Storage Unit Type:    Disk
Storage Unit Subtype: Basic (1)
Host Connection:      EN-bu3.EN.local
Concurrent Jobs:      7
On Demand Only:       no
Max MPX:              1
Path:                 "R:\Staging\system2"
Max Fragment Size:    524288 MB
Stage data:           yes
Block Sharing:        no
High Water Mark:      80
Low Water Mark:       70
Ok On Root:           no

Label:                eq22_System_Image_Staging
Storage Unit Type:    Disk
Storage Unit Subtype: Basic (1)
Host Connection:      EN-bu3.EN.local
Concurrent Jobs:      12
On Demand Only:       yes
Max MPX:              1
Path:                 "R:\Staging"
Max Fragment Size:    524288 MB
Stage data:           yes
Block Sharing:        no
High Water Mark:      60
Low Water Mark:       30
Ok On Root:           yes

Label:                Catalog
Storage Unit Type:    Disk
Storage Unit Subtype: Basic (1)
Host Connection:      EN-eq11
Concurrent Jobs:      2
On Demand Only:       no
Max MPX:              1
Path:                 "F:\Catalog_Backup"
Max Fragment Size:    524288 MB
Stage data:           no
Block Sharing:        no
High Water Mark:      80
Low Water Mark:       70
Ok On Root:           yes

Label:                ENCR_eq22_1_SU
Storage Unit Type:    Disk
Storage Unit Subtype: Basic (1)
Host Connection:      EN-eq22.EN.local
Concurrent Jobs:      42
On Demand Only:       yes
Max MPX:              1
Path:                 "M:\ENCR_eq22_MX6"
Max Fragment Size:    524288 MB
Stage data:           yes
Block Sharing:        no
High Water Mark:      60
Low Water Mark:       30
Ok On Root:           yes

Label:                DBImage
Storage Unit Type:    Disk
Storage Unit Subtype: Basic (1)
Host Connection:      EN-bu3.EN.local
Concurrent Jobs:      14
On Demand Only:       yes
Max MPX:              1
Path:                 "R:\DBImage_tmp"
Max Fragment Size:    524288 MB
Stage data:           yes
Block Sharing:        no
High Water Mark:      60
Low Water Mark:       30
Ok On Root:           yes

Label:                ENCR_Mail
Storage Unit Type:    Disk
Storage Unit Subtype: Basic (1)
Host Connection:      EN-bu3.EN.local
Concurrent Jobs:      99
On Demand Only:       no
Max MPX:              1
Path:                 "R:\eq11-5_tmp"
Max Fragment Size:    524288 MB
Stage data:           yes
Block Sharing:        no
High Water Mark:      60
Low Water Mark:       30
Ok On Root:           no

Label:                Imaging2
Storage Unit Type:    Disk
Storage Unit Subtype: Basic (1)
Host Connection:      EN-bu3.EN.local
Concurrent Jobs:      9
On Demand Only:       no
Max MPX:              1
Path:                 "R:\eq11-2_tmp"
Max Fragment Size:    524288 MB
Stage data:           yes
Block Sharing:        no
High Water Mark:      60
Low Water Mark:       30
Ok On Root:           no

Label:                ENCR_eq11_MX
Storage Unit Type:    Disk
Storage Unit Subtype: Basic (1)
Host Connection:      EN-eq11
Concurrent Jobs:      28
On Demand Only:       no
Max MPX:              1
Path:                 "K:\ENCR_eq11__MX"
Max Fragment Size:    524288 MB
Stage data:           yes
Block Sharing:        no
High Water Mark:      60
Low Water Mark:       30
Ok On Root:           yes

Label:                ENCR_eq22_SU
Storage Unit Type:    Disk
Storage Unit Subtype: Basic (1)
Host Connection:      EN-eq22.EN.local
Concurrent Jobs:      26
On Demand Only:       yes
Max MPX:              1
Path:                 "M:\ENCR_eq22"
Max Fragment Size:    524288 MB
Stage data:           yes
Block Sharing:        no
High Water Mark:      60
Low Water Mark:       30
Ok On Root:           yes

Label:                EnterpriseVault
Storage Unit Type:    Disk
Storage Unit Subtype: Basic (1)
Host Connection:      EN-bu3.EN.local
Concurrent Jobs:      5
On Demand Only:       no
Max MPX:              1
Path:                 "R:\eq11-4_tmp"
Max Fragment Size:    524288 MB
Stage data:           yes
Block Sharing:        no
High Water Mark:      60
Low Water Mark:       30
Ok On Root:           no

Label:                eq22_AD_Staging
Storage Unit Type:    Disk
Storage Unit Subtype: Basic (1)
Host Connection:      EN-eq22.EN.local
Concurrent Jobs:      12
On Demand Only:       yes
Max MPX:              1
Path:                 "M:\Staging\AD_Backup"
Max Fragment Size:    524288 MB
Stage data:           yes
Block Sharing:        no
High Water Mark:      80
Low Water Mark:       70
Ok On Root:           no

Label:                eq22_Enterprise_Vault
Storage Unit Type:    Disk
Storage Unit Subtype: Basic (1)
Host Connection:      EN-eq11
Concurrent Jobs:      10
On Demand Only:       no
Max MPX:              1
Path:                 "K:\evault"
Max Fragment Size:    524288 MB
Stage data:           yes
Block Sharing:        no
High Water Mark:      60
Low Water Mark:       30
Ok On Root:           no

Label:                eq22_APP09
Storage Unit Type:    Disk
Storage Unit Subtype: Basic (1)
Host Connection:      EN-bu3.EN.local
Concurrent Jobs:      9
On Demand Only:       yes
Max MPX:              1
Path:                 "X:\Staging\app09"
Max Fragment Size:    524288 MB
Stage data:           yes
Block Sharing:        no
High Water Mark:      60
Low Water Mark:       30
Ok On Root:           no

Label:                eq22_App01
Storage Unit Type:    Disk
Storage Unit Subtype: Basic (1)
Host Connection:      EN-bu3.EN.local
Concurrent Jobs:      8
On Demand Only:       yes
Max MPX:              1
Path:                 "R:\fp3_tmp"
Max Fragment Size:    524288 MB
Stage data:           yes
Block Sharing:        no
High Water Mark:      60
Low Water Mark:       30
Ok On Root:           no

Label:                SQL2008R2DB_SU
Storage Unit Type:    Disk
Storage Unit Subtype: Basic (1)
Host Connection:      EN-eq22.EN.local
Concurrent Jobs:      4
On Demand Only:       yes
Max MPX:              1
Path:                 "M:\SQL2008R2DB_Disk"
Max Fragment Size:    524288 MB
Stage data:           yes
Block Sharing:        no
High Water Mark:      60
Low Water Mark:       30
Ok On Root:           no

Label:                SQL2008R2DB_Diff_SU
Storage Unit Type:    Disk
Storage Unit Subtype: Basic (1)
Host Connection:      EN-eq22.EN.local
Concurrent Jobs:      10
On Demand Only:       yes
Max MPX:              1
Path:                 "M:\SQL2008R2DB_Diff_Disk"
Max Fragment Size:    524288 MB
Stage data:           yes
Block Sharing:        no
High Water Mark:      61
Low Water Mark:       30
Ok On Root:           no

Label:                SP2010All_Full_SU
Storage Unit Type:    Disk
Storage Unit Subtype: Basic (1)
Host Connection:      EN-eq11
Concurrent Jobs:      13
On Demand Only:       yes
Max MPX:              1
Path:                 "K:\Sharepoint"
Max Fragment Size:    524288 MB
Stage data:           yes
Block Sharing:        no
High Water Mark:      60
Low Water Mark:       30
Ok On Root:           yes

Label:                eq22_EN-TFS01
Storage Unit Type:    Disk
Storage Unit Subtype: Basic (1)
Host Connection:      EN-eq11
Concurrent Jobs:      8
On Demand Only:       yes
Max MPX:              1
Path:                 "K:\TFS"
Max Fragment Size:    524288 MB
Stage data:           yes
Block Sharing:        no
High Water Mark:      80
Low Water Mark:       70
Ok On Root:           no

Label:                SP2010All
Storage Unit Type:    Disk
Storage Unit Subtype: Basic (1)
Host Connection:      EN-eq11
Concurrent Jobs:      6
On Demand Only:       yes
Max MPX:              1
Path:                 "K:\SharepointDiff"
Max Fragment Size:    524288 MB
Stage data:           yes
Block Sharing:        no
High Water Mark:      60
Low Water Mark:       30
Ok On Root:           no

Label:                EVOpen
Storage Unit Type:    Disk
Storage Unit Subtype: Basic (1)
Host Connection:      EN-eq11
Concurrent Jobs:      10
On Demand Only:       yes
Max MPX:              1
Path:                 "K:\EVOPEN"
Max Fragment Size:    524288 MB
Stage data:           yes
Block Sharing:        no
High Water Mark:      60
Low Water Mark:       30
Ok On Root:           yes

Label:                EVClosed
Storage Unit Type:    Disk
Storage Unit Subtype: Basic (1)
Host Connection:      EN-eq11
Concurrent Jobs:      18
On Demand Only:       yes
Max MPX:              1
Path:                 "f:\EVClosed_Disk"
Max Fragment Size:    524288 MB
Stage data:           yes
Block Sharing:        no
High Water Mark:      60
Low Water Mark:       30
Ok On Root:           yes

Label:                EVDir
Storage Unit Type:    Disk
Storage Unit Subtype: Basic (1)
Host Connection:      EN-eq11
Concurrent Jobs:      10
On Demand Only:       yes
Max MPX:              1
Path:                 "k:\EVDir_Disk"
Max Fragment Size:    524288 MB
Stage data:           yes
Block Sharing:        no
High Water Mark:      60
Low Water Mark:       30
Ok On Root:           no

Label:                Files
Storage Unit Type:    Disk
Storage Unit Subtype: Basic (1)
Host Connection:      EN-bu3.EN.local
Concurrent Jobs:      6
On Demand Only:       no
Max MPX:              1
Path:                 "R:\eq11-3_tmp"
Max Fragment Size:    524288 MB
Stage data:           yes
Block Sharing:        no
High Water Mark:      60
Low Water Mark:       30
Ok On Root:           yes

 

Label:                App02
Storage Unit Type:    Disk
Storage Unit Subtype: Basic (1)
Host Connection:      EN-bu3.EN.local
Concurrent Jobs:      7
On Demand Only:       yes
Max MPX:              1
Path:                 "R:\secure_Bu3_tmp"
Max Fragment Size:    524288 MB
Stage data:           yes
Block Sharing:        no
High Water Mark:      60
Low Water Mark:       30
Ok On Root:           yes


Label:                Pier01
Storage Unit Type:    Disk
Storage Unit Subtype: Basic (1)
Host Connection:      EN-eq11
Concurrent Jobs:      6
On Demand Only:       no
Max MPX:              1
Path:                 "F:\Peach"
Max Fragment Size:    524288 MB
Stage data:           yes
Block Sharing:        no
High Water Mark:      60
Low Water Mark:       30
Ok On Root:           yes

Label:                SU_TEST
Storage Unit Type:    Disk
Storage Unit Subtype: Basic (1)
Host Connection:      EN-bu4.EN.local
Concurrent Jobs:      1
On Demand Only:       yes
Max MPX:              1
Path:                 "I:\SU_TEST"
Max Fragment Size:    524288 MB
Stage data:           no
Block Sharing:        no
High Water Mark:      81
Low Water Mark:       65
Ok On Root:           no

Label:                SLP_TEST
Storage Unit Type:    Disk
Storage Unit Subtype: DiskPool (6)
Host Connection:      EN-eq11
Concurrent Jobs:      10
On Demand Only:       yes
Max MPX:              1
Max Fragment Size:    51200 MB
Block Sharing:        yes
Ok On Root:           no
Disk Pool:            Dedup_1
Snapshots:            no
Replication Primary:  no
Replication Source:   no
Replication Target:   no
Mirror            :   no
Independent       :   no

Label:                App1_Tmp
Storage Unit Type:    Disk
Storage Unit Subtype: Basic (1)
Host Connection:      EN-bu3.EN.local
Concurrent Jobs:      9
On Demand Only:       yes
Max MPX:              1
Path:                 "R:\App1Tempbkp"
Max Fragment Size:    524288 MB
Stage data:           yes
Block Sharing:        no
High Water Mark:      60
Low Water Mark:       30
Ok On Root:           no

Label:                eq11_Files
Storage Unit Type:    Disk
Storage Unit Subtype: Basic (1)
Host Connection:      EN-eq11
Concurrent Jobs:      15
On Demand Only:       yes
Max MPX:              1
Path:                 "K:\files"
Max Fragment Size:    524288 MB
Stage data:           yes
Block Sharing:        no
High Water Mark:      80
Low Water Mark:       70
Ok On Root:           no


 

18 REPLIES 18

sdo
Moderator
Moderator
Partner    VIP    Certified

As a test... If you DOWN all of the tape drives within the first STU - does the DSSU job then use the second STU in the STG?  Or does the DSSU duplication job fail?  This will tell us whether the configuration is supposed to work.

Or... temporarily remove the first STU from the STG, and see if it works?

And/or... re-order the STU's so that the first STU is now the last... does it still pick the same (was first, now third) STU?

gopi_enovate
Level 4

I tried to remove the storage unit from the group, it didnt kick the second one in line.

Re ordering the storage units worked for a two days and the issue started again.

 

 

RamNagalla
Moderator
Moderator
Partner    VIP    Certified

Label:                EN-eq22-hcart3-robot-tld-0
Storage Unit Type:    Media Manager
Host Connection:      EN-eq22.EN.local
Number of Drives:     2
On Demand Only:       no
Max MPX/drive:        16
Density:              hcart3 - 1/2 Inch Cartridge 3
Robot Type/Number:    TLD / 0
Max Fragment Size:    1048576 MB

 

is this one of the shared tape Drives storage unit?

if yes, the desnity for this is selected as Hcart3, and rest are selected as Hcart2

Do you have Hcart2 tapes avaliable?

sdo
Moderator
Moderator
Partner    VIP    Certified

It's beyond my skill level to debug what's going on with this.  My guess is that it will down to something deep in the RB (Resource Broker) probably.

Out of curiousity - what OS and NetBackup version is the Master Server?

And I can't help but ask, how many tape drives are there in each storage unit?  The fact that re-ordering the storage-unit 'works' for a day or two, makes me think that RB is establishing some kind of affinity, until it can no longer use whichever drive it used before, and then moves on, and then sticks with the next selected drive until that is no longer available - and so if you have lots of drives in the first storage unit - then maybe it will just take a very long time before the condition arises whereby it can no longer use what it previously used.  All of this is nothing more that musing/conjecture, and very probably hog-wash.  I think you may need a support case if you want a true root cause analysis.

Can I ask why it's important to you?  To me, a storage unit group really implies that any storage unit can be used, so why is it important which storage unit does actually get used?

sdo
Moderator
Moderator
Partner    VIP    Certified
Label:                eq22-LTO5
Storage Unit Type:    Media Manager
Host Connection:      EN-eq11
Number of Drives:     1
On Demand Only:       no
Max MPX/drive:        12
Density:              hcart2 - 1/2 Inch Cartridge 2
Robot Type/Number:    TLD / 1
Max Fragment Size:    1048576 MB

Label:                EN-eq22-hcart2-robot-tld-2
Storage Unit Type:    Media Manager
Host Connection:      EN-eq22.EN.local
Number of Drives:     1
On Demand Only:       no
Max MPX/drive:        6
Density:              hcart2 - 1/2 Inch Cartridge 2
Robot Type/Number:    TLD / 2
Max Fragment Size:    1048576 MB

Label:                EN-eq11-hcart2-robot-tld-4
Storage Unit Type:    Media Manager
Host Connection:      EN-eq11
Number of Drives:     1
On Demand Only:       no
Max MPX/drive:        12
Density:              hcart2 - 1/2 Inch Cartridge 2
Robot Type/Number:    TLD / 4
Max Fragment Size:    1048576 MB

Label:                EN-bu3-hcart3-robot-tld-0
Storage Unit Type:    Media Manager
Host Connection:      EN-bu3.EN.local
Number of Drives:     3
On Demand Only:       no
Max MPX/drive:        16
Density:              hcart3 - 1/2 Inch Cartridge 3
Robot Type/Number:    TLD / 0
Max Fragment Size:    1048576 MB

Label:                EN-eq22-hcart3-robot-tld-0
Storage Unit Type:    Media Manager
Host Connection:      EN-eq22.EN.local
Number of Drives:     2
On Demand Only:       no
Max MPX/drive:        16
Density:              hcart3 - 1/2 Inch Cartridge 3
Robot Type/Number:    TLD / 0
Max Fragment Size:    1048576 MB

Label:                EN-eq22-hcart2-robot-tld-3
Storage Unit Type:    Media Manager
Host Connection:      EN-eq22.EN.local
Number of Drives:     1
On Demand Only:       no
Max MPX/drive:        6
Density:              hcart2 - 1/2 Inch Cartridge 2
Robot Type/Number:    TLD / 3
Max Fragment Size:    1048576 MB

.

Server    TLD     Drives     Type      MPX    Max Jobs

en-eq11   1        1              hcart2    12        12

en-eq22   2        1             hcart2     6          6

en-eq11   4         1            hcart2     12        12

en-bu3     0         3            hcart3     16        48

en-eq22   0         2            hcart3     16        32

en-eq22   3        1             hcart2     6          6

.

Server       Max Jobs    Type

en-eq11     24               hcart2

en-eq22     44              hcart2 (12) / hcart3 (32)

en-bu3       48              hcart3

.

Do you definitely get more than 48 jobs attempting to use the STU on en-bu3?

.

FYI - once NetBackup starts an MPX "job set" then as jobs in the set finish, then NetBackup will continue to try to re-add "new jobs" to any "MPX job set" rather than allocate the job to a new storage unit drive.  So, if you never have more than 48 jobs run, and they all use the same pool and retention, and the first job gets a drive on en-bu3 then I would think that NetBackup will stick with that storage unit, and not move on to another storage unit until no resource slots (i.e. "mpx job set entry opportunites") are available.

sdo
Moderator
Moderator
Partner    VIP    Certified

And, if you have any max partially full media settings on your pools, then NetBackup is going to attempt to use  those non-full media first - and so it will stick with the used, but not yet full media in whichever library has those media - and not select scratch (from another library/storage-unit) until it has to.

And can anyone confirm... whether once a media does get full, whether NetBackup will stick with selecting scratch media from the same storage unit (in a group), or is it free (and able/featured/supported) to select scratch from another storage unit (in the group)?

gopi_enovate
Level 4

Yes, it is the shared tape drive.
There are hcart2 devices as well.

Hcart2 devices storage unit are the ones which are not being picked up from the storage unit group.

 

Can hcart2 and hcart3 storage units not be in the same storage unit group?

gopi_enovate
Level 4

OS- Windows 2008 R2
Netbackup Version - 7.5.0.7
 

 

Shared tape drive unit has 5 tape drives with maximum concurrent set to 2.
 

Our staging is very slow due to read performance from our SAN.
If individual storage units are used for staging from storage units, there are duplications jobs which are queued and tape drives from other storage units are not being used.

 

If all tape drives are used in tandem, duplication are happening on time.

 

sdo
Moderator
Moderator
Partner    VIP    Certified

Do you have media ownership set as an "any" type configuration?

gopi_enovate
Level 4

Yes, it is.
Moreover, storage unit group is created for storage units from same media server.

sdo
Moderator
Moderator
Partner    VIP    Certified

Why is it important to you that another storage unit is used?

sdo
Moderator
Moderator
Partner    VIP    Certified

I can't find (quickly via google) any notes on how to restart just EMM.  My understanding is that the EMM is a critical core component of the NetBackup suite, in that most features/functionality use the EMM which functionally sits just in front of the Sybase database - so I think you may have to restart NetBackup on the master and all media servers.

RonCaplinger
Level 6

Correct me if I am wrong, but disk staging storage units don't make use of multiplexing to tape, all data is pulled off disk and sent to tape single-threaded.  So that really shouldn't matter here, right? 
 

RonCaplinger
Level 6

Gopi,

You have both HCART2 & HCART3 tape devices and storage units in the same group, correct? So are you *sure* you have both HCART2 & HCART3 *media* available in the robots mentioned?  Since it seemed to work for a couple of days when you removed one of the libraries, could the library simply have run out of available media to continue writing to that library and it stopped trying to use it?

sdo
Moderator
Moderator
Partner    VIP    Certified

Good point Ron, thanks for reminding us.

Gopi, only backups to tape (or VTL) can be multiplexed - and the only duplications that can be multi-plexed are duplications of already multi-plexed backups currently residing on tape/VTL being duplicated to another tape/VTL.

Thus, the duplications from DSSU are not, and will not be, multi-plexed.

gopi_enovate
Level 4

Yes, both hcart2 and hcart2 tape drives are available within same storage unit group.
No, all libraries have enough media to start the next duplication.

gopi_enovate
Level 4

Hi Sdo,
        Thanks! We have one 5 tape drive library and 2 SAS quantum robots.
When the storage unit is ready for duplication, we would like all the drives be used in tandem so that no drive is free when there is more data to be to staged to tape.

Hence, we created a storage unit group for duplication.

 

mph999
Level 6
Employee Accredited

I would have to test this myself to be honest, if I get time over the weekend I will have a play.

So if I understand:

The dup starts, and uses two drives from your 1st media manager STU as mentioned above.

You would like other images not yet duplicated to make use of the other two STUs.

 

I tried to remove the storage unit from the group, it didnt kick the second one in line.

I presume by this you mean it failed totally ?

Re ordering the storage units worked for a two days and the issue started again.

OK, so here it made use of all the STUs, though only for a couple of days.

TBH, I am thinking the best way to look at this will be via the logs - your test shows some unpredictable behaviour and I'm not that sure it is going to reproduce (I'll still try if I get time, but I'm not hopeful).

I would suggest geting nbemm and mds /da (111 and 143 /144 ) at Debug 6

vxlogview -a -p 51216 -o 111 -s DebugLevel=6 -s DiagnosticLevel=6

vxlogview -a -p 51216 -o 143 -s DebugLevel=6 -s DiagnosticLevel=6

vxlogview -a -p 51216 -o 144 -s DebugLevel=6 -s DiagnosticLevel=6

Start a manual relocation, then after you can see it is not using the other STUs turn the logs back down (same commands just use DebugLevel = 1 (or 0)

Then copy the raw log from /usr/openv/logs/nbemm

(143 and 144 go into 111 (emm) so only one log to get)

You only need the emm log that covers the time period of the test, you should be able to spot this via the timestamps.