Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Errors activating Accelerator on backup policies

Created: 03 Jul 2013 • Updated: 06 Aug 2013 | 34 comments
This issue has been solved. See solution.

Hello,

I am getting error messages when I try to active Accelerator on my backup policies.

We are running NetBackup 7.5.0.4 on Windows Server 2008R2, with NetBackup 5220 Appliances. The backup policies are configured as MS-Windows and use a SLP for the "Policy Storage". We do not have any problems with backups or restores. We are just now trying to implement Accelerator and have run into these issues.

When I check the "Use Accelerator" checkbox and click OK to save the policy, I get the following error message:

Policy Validation Report

- The "Policy Attribute" shows nothing

- The "SLP Attribute" shows the name of my SLP

- The "Conflicts" show "Storage unit in the SLP does not match the accelerator attribute in policy"

I can then click the OK button on the pop-up window, but have to hit Cancel to exit the policy. When I go back into the policy, the "Use Accelerator" box is still checked. If I run a manual backup, there is nothing in the status that states that Accelerator was used, and when I open the policy again, every time I try to click OK to save/exit the policy, I get the same error message above.

I found a TID that showed how to check the attributes of my storage units to see if the "OptimizedImage" flag was enabled, and it is. I then thought it might be a licensing issue, but my licenses show options enabled for "Shared Storage Option", "Open Storage Disk Option", and "PureDisk Option". I found another thread that states that Accelerator requires the "Data Protection Optimization Option".

So, do I not have this option licensed and that is why it is not working? If that's not it, then any ideas on why I'm getting this error and I can't get Accelerator to work?

Thank you!

Larry

Operating Systems:

Comments 34 CommentsJump to latest comment

StefanosM's picture

if you run the command  "bpminlicense -verbose" you must have the following line

 Feature ID      = 88 Accelerator +

If you do not have this line, then the licenses you have are not 7.5 licenses. You must go to my.symantec.com and upgrade your licenses.

If your licenses are for 7.5 then you may have one of the first 7.5 licenses that does not have the accelerator future enables (happen to me two times). In that case you must open a case to licensing (same way as technical support) and ask for new licenses.

Beavisrulz's picture

Hey Stefanos. Well, I ran the command you gave me and the line is definitely there. Looks like we did an upgrade and added new license keys on 8/23/12. I also ran the command bpminlicense -verbose -nb_features, and it showed Accelerator as one of the features with "license type" of permanent.

So, still not fixed. Thanks though!

Larry

D.Flood's picture

Make sure you're only running 7.x keys.  If you have any previous keys still listed, they might be confusing things.  When we did the upgrade from 5.1 to 6.5 to 7.1, we still had the old 5.1 keys as well as the 7.x keys installed and several new features didn't "light up" until I deleted the 5.1 keys.

 

StefanosM's picture

OK, lets start from the beginning.

Change the STU at Attributes from the SLP to the deduplication STU and clear any other STUs from the policy. Run a test backup. This should run fine.

Then create a new SLP that has only one backup definition with the deduplication STU as storage. Run a test backup.

If this backup runs fine, check your SLP for incompatibilities. You can not use storage unit groups as backup definition with accelerated backups. (You can, but with many restrictions).

test all and reply.

EDIT: I presume that you are using deduplication. Accelerator works only with deduplication :)

Beavisrulz's picture

OK, I did all of this (and I'm pretty sure I've done this in the past).

The backups ran fine each time. This time as soon as I tried to activate Accelerator, I received a different error message:

"To use the accelerator, select storage units from a supported storage server: PureDisk Deduplication (PPDO), Media Server Deduplication (MSDP), Symantec clouds, and other qualified storage servers. Currently configured and supported storage servers are: <none>"

I have to cancel out of the backup policy, go back in, and Accelerator is still checked. If I click the OK button to exit/save again, I get the previous message from above.

If I go into my original SLP, and run the "Validate Across Backup Policies", it comes back with NO errors. I actually have 6 SLPs, and all of them do the same, so no matter which SLP I choose in the backup policy, I get the same errors. I also have 3 storage units, since we have 3 NetBackup 5220s, and it doesn't matter which SLP I pick or which STU they are pointing to. Same errors all around.

Ugh.

StefanosM's picture

Had you clear any storage unit selection you may have a schedule level?

your first test, when you select directly the deduplication  STU, activates and works with accelerator or not?

if yes, did the second test with a new SLP and only one backup definition, activates and works with accelerator or not?

 Try to create a new policy. Some times help

 

Beavisrulz's picture

I actually create a new policy and have been using it all day.

When I choose the STU directly in the backup policy and then check the Accelerator box, I get the 2nd message stating "Currently configured and supported storage servers are: <none>". I can run a test backup successfully, but it does not use Accelerator.

The I switch it back to the new SLP I created (with only 1 backup definition), I then get the initial message when selecting Accelerator. Again, a backup will run, just not using Accelerator.

StefanosM's picture

stay at the first test. If this run, all will run. Do not mess with SLPs.

Please run the bppllist <policy-name> -U command and the bpstulist command and post the output

 

Marianne's picture

NetBackup Appliances do not come with any licenses - you need Data Protection Optimization Option to enable dedupe STU. 

Can you confirm that you are able to perform dedupe backups? Client Side or Media Server Side?

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

Beavisrulz's picture

Stefanos, here is the output you requested:

command: bppllist 00-Larry-Test -U

Policy Name:       00-Larry-Test

  Policy Type:         MS-Windows
  Active:              yes
  Effective date:      07/03/2013 10:04:01
  Backup network drvs: no
  Collect TIR info:    no
  Mult. Data Streams:  no
  Client Encrypt:      no
  Checkpoint:          no
  Policy Priority:     0
  Max Jobs/Policy:     Unlimited
  Disaster Recovery:   0
  Collect BMR info:    no
  Residence:           KMC_to_DR_10
  Volume Pool:         NetBackup
  Server Group:        *ANY*
  Keyword:             (none specified)
  Data Classification:       -
  Residence is Storage Lifecycle Policy:    yes
  Application Discovery:      no
  Discovery Lifetime:      28800 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   khw2k140

  Include:  D:\Service

  Schedule:              Test-Backup
    Type:                Full Backup
    Frequency:           every 7 days
    Maximum MPX:         1
    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:

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

command:  bpstulist

khhpx003-hcart-robot-tld-1 2 khhpx003 8 1 6 8 0 "*NULL*" 0 4 4096 *NULL* 0 1 0 0 0 0 *NULL* khhpx003 0
TLD2-046-DSK-01 0 khw2k046 0 -1 -1 1 0 "D:\TLD2-046-DSK-01" 1 1 524288 khw2k046 0 1 0 98 80 0 TLD2-046-DSK-01 khw2k046 127953
KMC_Pool_12 0 khapbak012 0 -1 -1 40 0 "*NULL*" 1 1 51200 khapbak012 2 6 0 0 0 0 dp_disk_khapbak012 khapbak012 1137911
KMC_Pool_11 0 khapbak011 0 -1 -1 40 0 "*NULL*" 1 1 51200 khapbak011 2 6 0 0 0 0 dp_disk_khapbak011 khapbak011 1137911
KMC_ADV_10 0 khapbak010 0 -1 -1 40 0 "*NULL*" 1 1 524288 khapbak010 0 6 0 0 0 0 dp_adv_khapbak010 khapbak010 1564103
KMC_ADV_11 0 khapbak011 0 -1 -1 40 0 "*NULL*" 1 1 524288 khapbak011 0 6 0 0 0 0 dp_adv_khapbak011 khapbak011 1564103
KMC_ADV_12 0 khapbak012 0 -1 -1 40 0 "*NULL*" 1 1 524288 khapbak012 0 6 0 0 0 0 dp_adv_khapbak012 khapbak012 1564103
CatBack-003-DSK-01 0 khwpbak003 0 -1 -1 3 0 "D:\CatalogBackup" 1 1 524288 khwpbak003 0 1 0 98 80 0 CatBack-003-DSK-01 khwpbak003 127953
KMC_Pool_10 0 khapbak010 0 -1 -1 40 0 "*NULL*" 1 1 51200 khapbak010 2 6 0 0 0 0 dp_disk_khapbak010 khapbak010 1137911
 

Beavisrulz's picture

Marianne, we've been doing client-side dedupe and direct to storage backups for over a year now. We originally had 5020 appliances and recently replaced them with 5220's thru the Symantec Outreach program. I had this same issue when we had the 5020's and I believe we were on NetBackup 7.1 at the time.

Thanks for your assistance!

Larry

StefanosM's picture

this KMC_to_DR_10 is an SLP or storage unit group?

If it is SLP post the output of nbstl KMC_to_DR_10 -L
The storage unit you are using is KMC_Pool_10?

Please post the activity monitor detailed status of the job

Beavisrulz's picture

Yes, the "KMC_to_DR_10" is our SLP and the "KMC_Pool_10" is the storage unit. The storage unit is specified inside the SLP for my backup operation.

If I select the SLP for the "Policy Storage" in the backup policy, I get the initial error message I reported. If I select the storage unit for the "Policy Storage" in the policy, I get the 2nd error.

Here is the ouput for the command nbstl KMC_to_DR_10 -L:

                                Name: KMC_to_DR_10
                 Data Classification: (none specified)
            Duplication job priority: 0
                               State: active
                             Version: 0
 Operation  1              Use for: 0 (backup)
                             Storage: KMC_Pool_10
                         Volume Pool: (none specified)
                        Server Group: (none specified)
                      Retention Type: 0 (Fixed)
                     Retention Level: 1 (2 weeks)
               Alternate Read Server: (none specified)
               Preserve Multiplexing: false
      Enable Automatic Remote Import: true
                               State: active
                              Source: 0 (client)
                        Operation ID: (none specified)
                     Operation Index: 1
 Operation  2              Use for: 3 (replication to remote master)
                             Storage: Remote Master
                         Volume Pool: (none specified)
                        Server Group: (none specified)
                      Retention Type: 0 (Fixed)
                     Retention Level: 0 (1 week)
               Alternate Read Server: (none specified)
               Preserve Multiplexing: false
      Enable Automatic Remote Import: false
                               State: active
                              Source: Target 1 (backup:KMC_Pool_10)
                        Operation ID: (none specified)
                     Operation Index: 2
 

StefanosM's picture

I do not see any error to the Policy the storage unit or the SLP.

If possible post the detail status of a job.

Marianne's picture

What happens if you just select KMC_Pool_10 in the backup policy? (Assuming this is your dedupe STU)

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

Beavisrulz's picture

Marianne,

If I select the STU "KMC_Pool_10", I get the 2nd message:

"To use the accelerator, select storage units from a supported storage server: PureDisk Deduplication (PPDO), Media Server Deduplication (MSDP), Symantec clouds, and other qualified storage servers. Currently configured and supported storage servers are: <none>"

 

Marianne's picture

So, what kind of STU is KMC_Pool_10?

Do you have any dedupe STU's?

Please provide output of:

nbdevquery -liststs -U

bpstulist -L 

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

Beavisrulz's picture

All of our storage units are dedupes. Here is the output you requested:

nbdevquery -liststs -U

Storage Server      : khw2k046
Storage Server Type : BasicDisk
Storage Type        : Formatted Disk, Direct Attached
State               : UP
Flag                : AdminUp
Flag                : InternalUp
Flag                : SpanImages
Flag                : BasicStaging
Flag                : FragmentImages
Flag                : CatalogBackup
Flag                : Cpr
Flag                : RandomWrites
Flag                : FT-Transfer

Storage Server      : khwpbak003
Storage Server Type : BasicDisk
Storage Type        : Formatted Disk, Direct Attached
State               : UP
Flag                : AdminUp
Flag                : InternalUp
Flag                : SpanImages
Flag                : BasicStaging
Flag                : FragmentImages
Flag                : CatalogBackup
Flag                : Cpr
Flag                : RandomWrites
Flag                : FT-Transfer

Storage Server      : khapbak012
Storage Server Type : AdvancedDisk
Storage Type        : Formatted Disk, Direct Attached
State               : UP
Flag                : OpenStorage
Flag                : AdminUp
Flag                : InternalUp
Flag                : SpanImages
Flag                : LifeCycle
Flag                : CapacityMgmt
Flag                : FragmentImages
Flag                : Cpr
Flag                : RandomWrites
Flag                : FT-Transfer
Flag                : CapacityManagedRetention
Flag                : CapacityManagedJobQueuing
Flag                : OptimizedImage

Storage Server      : khapbak012
Storage Server Type : PureDisk
Storage Type        : Formatted Disk, Network Attached
State               : UP
Flag                : OpenStorage
Flag                : CopyExtents
Flag                : AdminUp
Flag                : InternalUp
Flag                : LifeCycle
Flag                : CapacityMgmt
Flag                : FragmentImages
Flag                : Cpr
Flag                : FT-Transfer
Flag                : OptimizedImage

Storage Server      : khapbak011
Storage Server Type : AdvancedDisk
Storage Type        : Formatted Disk, Direct Attached
State               : UP
Flag                : OpenStorage
Flag                : AdminUp
Flag                : InternalUp
Flag                : SpanImages
Flag                : LifeCycle
Flag                : CapacityMgmt
Flag                : FragmentImages
Flag                : Cpr
Flag                : RandomWrites
Flag                : FT-Transfer
Flag                : CapacityManagedRetention
Flag                : CapacityManagedJobQueuing
Flag                : OptimizedImage

Storage Server      : khapbak011
Storage Server Type : PureDisk
Storage Type        : Formatted Disk, Network Attached
State               : UP
Flag                : OpenStorage
Flag                : CopyExtents
Flag                : AdminUp
Flag                : InternalUp
Flag                : LifeCycle
Flag                : CapacityMgmt
Flag                : FragmentImages
Flag                : Cpr
Flag                : FT-Transfer
Flag                : OptimizedImage

Storage Server      : khapbak010
Storage Server Type : AdvancedDisk
Storage Type        : Formatted Disk, Direct Attached
State               : UP
Flag                : OpenStorage
Flag                : AdminUp
Flag                : InternalUp
Flag                : SpanImages
Flag                : LifeCycle
Flag                : CapacityMgmt
Flag                : FragmentImages
Flag                : Cpr
Flag                : RandomWrites
Flag                : FT-Transfer
Flag                : CapacityManagedRetention
Flag                : CapacityManagedJobQueuing
Flag                : OptimizedImage

Storage Server      : khapbak010
Storage Server Type : PureDisk
Storage Type        : Formatted Disk, Network Attached
State               : UP
Flag                : OpenStorage
Flag                : CopyExtents
Flag                : AdminUp
Flag                : InternalUp
Flag                : LifeCycle
Flag                : CapacityMgmt
Flag                : FragmentImages
Flag                : Cpr
Flag                : FT-Transfer
Flag                : OptimizedImage

bpstulist - L

Label:                KMC_Pool_12
Storage Unit Type:    Disk
Media Subtype:        DiskPool (6)
Host Connection:      khapbak012
Concurrent Jobs:      40
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:            dp_disk_khapbak012
Snapshots:            no
Replication Primary:  no
Replication Source:   no
Replication Target:   no
Mirror            :   no
Independent       :   no

Label:                KMC_Pool_11
Storage Unit Type:    Disk
Media Subtype:        DiskPool (6)
Host Connection:      khapbak011
Concurrent Jobs:      40
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:            dp_disk_khapbak011
Snapshots:            no
Replication Primary:  no
Replication Source:   no
Replication Target:   no
Mirror            :   no
Independent       :   no

Label:                KMC_ADV_10
Storage Unit Type:    Disk
Media Subtype:        DiskPool (6)
Host Connection:      khapbak010
Concurrent Jobs:      40
On Demand Only:       yes
Robot Type:           (not robotic)
Max Fragment Size:    524288
Max MPX:              1
Block Sharing:        no
File System Export:   no
Ok On Root:           no
Disk Pool:            dp_adv_khapbak010
Snapshots:            no
Replication Primary:  no
Replication Source:   no
Replication Target:   no
Mirror            :   no
Independent       :   no

Label:                KMC_ADV_11
Storage Unit Type:    Disk
Media Subtype:        DiskPool (6)
Host Connection:      khapbak011
Concurrent Jobs:      40
On Demand Only:       yes
Robot Type:           (not robotic)
Max Fragment Size:    524288
Max MPX:              1
Block Sharing:        no
File System Export:   no
Ok On Root:           no
Disk Pool:            dp_adv_khapbak011
Snapshots:            no
Replication Primary:  no
Replication Source:   no
Replication Target:   no
Mirror            :   no
Independent       :   no

Label:                KMC_ADV_12
Storage Unit Type:    Disk
Media Subtype:        DiskPool (6)
Host Connection:      khapbak012
Concurrent Jobs:      40
On Demand Only:       yes
Robot Type:           (not robotic)
Max Fragment Size:    524288
Max MPX:              1
Block Sharing:        no
File System Export:   no
Ok On Root:           no
Disk Pool:            dp_adv_khapbak012
Snapshots:            no
Replication Primary:  no
Replication Source:   no
Replication Target:   no
Mirror            :   no
Independent       :   no

Label:                CatBack-003-DSK-01
Storage Unit Type:    Disk
Media Subtype:        Basic (1)
Host Connection:      khwpbak003
Concurrent Jobs:      3
On Demand Only:       yes
Path:                 "D:\CatalogBackup"
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:                KMC_Pool_10
Storage Unit Type:    Disk
Media Subtype:        DiskPool (6)
Host Connection:      khapbak010
Concurrent Jobs:      40
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:            dp_disk_khapbak010
Snapshots:            no
Replication Primary:  no
Replication Source:   no
Replication Target:   no
Mirror            :   no
Independent       :   no

 

Marianne's picture

We can see that KMC_Pool_10 uses disk pool named dp_disk_khapbak010.

Please list all dedupe disk pools:

nbdevquery -liststs -stype PureDisk -U 

To list all disk pools:

nbdevquery -listdp -U

 

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

Beavisrulz's picture

Here is the output you requested:

nbdevquery -liststs -stype PureDisk -U

Storage Server      : khapbak012
Storage Server Type : PureDisk
Storage Type        : Formatted Disk, Network Attached
State               : UP
Flag                : OpenStorage
Flag                : CopyExtents
Flag                : AdminUp
Flag                : InternalUp
Flag                : LifeCycle
Flag                : CapacityMgmt
Flag                : FragmentImages
Flag                : Cpr
Flag                : FT-Transfer
Flag                : OptimizedImage

Storage Server      : khapbak011
Storage Server Type : PureDisk
Storage Type        : Formatted Disk, Network Attached
State               : UP
Flag                : OpenStorage
Flag                : CopyExtents
Flag                : AdminUp
Flag                : InternalUp
Flag                : LifeCycle
Flag                : CapacityMgmt
Flag                : FragmentImages
Flag                : Cpr
Flag                : FT-Transfer
Flag                : OptimizedImage

Storage Server      : khapbak010
Storage Server Type : PureDisk
Storage Type        : Formatted Disk, Network Attached
State               : UP
Flag                : OpenStorage
Flag                : CopyExtents
Flag                : AdminUp
Flag                : InternalUp
Flag                : LifeCycle
Flag                : CapacityMgmt
Flag                : FragmentImages
Flag                : Cpr
Flag                : FT-Transfer
Flag                : OptimizedImage

nbdevquery -listdp -U

Disk Pool Name   : dp_disk_khapbak012
Disk Pool Id     : dp_disk_khapbak012
Disk Type        : PureDisk
Status           : UP
Flag             : Patchwork
Flag             : Visible
Flag             : OpenStorage
Flag             : SingleStorageServer
Flag             : CopyExtents
Flag             : AdminUp
Flag             : InternalUp
Flag             : LifeCycle
Flag             : CapacityMgmt
Flag             : FragmentImages
Flag             : Cpr
Flag             : FT-Transfer
Flag             : OptimizedImage
Raw Size (GB)    : 62881.17
Usable Size (GB) : 62881.17
Num Volumes      : 1
High Watermark   : 98
Low Watermark    : 80
Max IO Streams   : -1
Comment          :
Storage Server   : khapbak012 (UP)

Disk Pool Name   : dp_disk_khapbak011
Disk Pool Id     : dp_disk_khapbak011
Disk Type        : PureDisk
Status           : UP
Flag             : Patchwork
Flag             : Visible
Flag             : OpenStorage
Flag             : SingleStorageServer
Flag             : CopyExtents
Flag             : AdminUp
Flag             : InternalUp
Flag             : LifeCycle
Flag             : CapacityMgmt
Flag             : FragmentImages
Flag             : Cpr
Flag             : FT-Transfer
Flag             : OptimizedImage
Raw Size (GB)    : 62864.08
Usable Size (GB) : 62864.08
Num Volumes      : 1
High Watermark   : 98
Low Watermark    : 80
Max IO Streams   : -1
Comment          :
Storage Server   : khapbak011 (UP)

Disk Pool Name   : dp_disk_khapbak010
Disk Pool Id     : dp_disk_khapbak010
Disk Type        : PureDisk
Status           : UP
Flag             : Patchwork
Flag             : Visible
Flag             : OpenStorage
Flag             : SingleStorageServer
Flag             : CopyExtents
Flag             : AdminUp
Flag             : InternalUp
Flag             : LifeCycle
Flag             : CapacityMgmt
Flag             : FragmentImages
Flag             : Cpr
Flag             : FT-Transfer
Flag             : OptimizedImage
Raw Size (GB)    : 62828.95
Usable Size (GB) : 62828.95
Num Volumes      : 1
High Watermark   : 98
Low Watermark    : 80
Max IO Streams   : -1
Comment          :
Storage Server   : khapbak010 (UP)

Disk Pool Name   : dp_adv_khapbak010
Disk Pool Id     : dp_adv_khapbak010
Disk Type        : AdvancedDisk
Status           : UP
Flag             : Patchwork
Flag             : Visible
Flag             : OpenStorage
Flag             : AdminUp
Flag             : InternalUp
Flag             : SpanImages
Flag             : LifeCycle
Flag             : CapacityMgmt
Flag             : FragmentImages
Flag             : Cpr
Flag             : RandomWrites
Flag             : FT-Transfer
Flag             : CapacityManagedRetention
Flag             : CapacityManagedJobQueuing
Flag             : OptimizedImage
Raw Size (GB)    : 11264.00
Usable Size (GB) : 11264.00
Num Volumes      : 1
High Watermark   : 98
Low Watermark    : 80
Max IO Streams   : -1
Comment          :
Storage Server   : khapbak010 (UP)

Disk Pool Name   : dp_adv_khapbak011
Disk Pool Id     : dp_adv_khapbak011
Disk Type        : AdvancedDisk
Status           : UP
Flag             : Patchwork
Flag             : Visible
Flag             : OpenStorage
Flag             : AdminUp
Flag             : InternalUp
Flag             : SpanImages
Flag             : LifeCycle
Flag             : CapacityMgmt
Flag             : FragmentImages
Flag             : Cpr
Flag             : RandomWrites
Flag             : FT-Transfer
Flag             : CapacityManagedRetention
Flag             : CapacityManagedJobQueuing
Flag             : OptimizedImage
Raw Size (GB)    : 11264.00
Usable Size (GB) : 11264.00
Num Volumes      : 1
High Watermark   : 98
Low Watermark    : 80
Max IO Streams   : -1
Comment          :
Storage Server   : khapbak011 (UP)

Disk Pool Name   : dp_adv_khapbak012
Disk Pool Id     : dp_adv_khapbak012
Disk Type        : AdvancedDisk
Status           : UP
Flag             : Patchwork
Flag             : Visible
Flag             : OpenStorage
Flag             : AdminUp
Flag             : InternalUp
Flag             : SpanImages
Flag             : LifeCycle
Flag             : CapacityMgmt
Flag             : FragmentImages
Flag             : Cpr
Flag             : RandomWrites
Flag             : FT-Transfer
Flag             : CapacityManagedRetention
Flag             : CapacityManagedJobQueuing
Flag             : OptimizedImage
Raw Size (GB)    : 11264.00
Usable Size (GB) : 11264.00
Num Volumes      : 1
High Watermark   : 98
Low Watermark    : 80
Max IO Streams   : -1
Comment          :
Storage Server   : khapbak012 (UP)

 

Marianne's picture

Okay, so we can see that dedupe STU/disk pool is indeed selected:

Disk Pool Name   : dp_disk_khapbak010
Disk Pool Id     : dp_disk_khapbak010
Disk Type        : PureDisk

Lets get back to licensing:

As per Stefanos'  post, bpminlicense -verbose  -nb_features needs to list 

Feature ID      = 88 Accelerator

on the master as well as on the Appliance (assuming khapbak010 is the name of your appliance?)

Can you confirm that?

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

Mark_Solutions's picture

I know this thread has run for a while but just picked it up and I have seen this error before.

If it was not licensed correctly you would not even get the accelerator option in the policy, it would be greyed out so I am not looking that way ...

But in the case where i saw it happen it was just down to user rights... in my case we were using the Windows Remote Admin Console and a PC or Server that had UAC enabled

The user needed to get his local admin rights on that PC specified specifically and open the console using "Run As Administrator" before the policy would save correctly (cannot remember now if the firewall was also an issue for this error or not - but it was turned off anyway)

Hope this may help

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.

Beavisrulz's picture

OK, I already checked the master server and it shows Accelerator as one of the features, but I just found the command to get the license info on the appliances and that line does not appear in the list. I think what happened was Symantec has to release new license codes because the first ones we received did not have Accelerator activated. We updated the master server at that time. When the 5220's were built, they must have used the initial license code and not the updated one that included Accelerator.

I will add the new license to the appliances later today and see if that fixes the issue. There are some backup & restore jobs running right now, and adding a license to the appliances will stop the NBU services and abort those jobs.

I'll let you know how it goes when I'm done. Thanks a lot!

 

Marianne's picture

Just wondering - what is the software version on the 5220?

Have you been able to add updated license key on the appliance yet?

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

Beavisrulz's picture

Appliance Version: 2.5.1

NetBackup Version: 7.5.0.4

Build Date: 20121114

 

I tried the adding the updated license key late yesterday afternoon and it wouldn't take. I got some error message about invalid string, can't remember exactly what it said. A backup is running right now so I can't try to add it again. My NetBackup master server (Windows-based) accepted the key when we added it in August of last year and it shows Accelerator as a feature in the list, but the appliance did not like the key. I haven't called Support yet, and thought about creating a separate post in the NetBackup Appliances forum to see if anyone had any clues on the license key issue.

 

Beavisrulz's picture

OK, sorry, I was on vacation and have been swamped at work. Go figure.

I created a separate thread and was able to get the license key adding to my appliances and the Accelerator option is now listed. Here is that thread if anyone wants to see the solution:

https://www-secure.symantec.com/connect/forums/accelerator-not-activated-5220-appliances

I created a new backup policy and new SLP, but I'm still getting the same error messages when I try and select the "Use Accelerator" checkbox and clicking OK.

So, I'm still stuck. Any more ideas, or should I go ahead and call Support?

Thanks.

Mark_Solutions's picture

Just re-read the entire thread .. and have spotted something (I hope!!)

The SLP is used for AIR replication

The backup target is a disk pool group if i have read everything correctly.

And that is your issue ... you cannot use a Storage Unit Group for AIR replication

This means that you need to backup to a SLP that has a storage unit specified and not a group - it also means you will need to split your policies per media server to balance the load as you cannot use groups

Hope this helps

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.

SYMAJ's picture

Are you doing this work from a Remote Admin Console or from the Master Server ?  I have had exactly this problem from an RAC, but all worked fine from the master.

If you are using an RAC then do the following:

Copy <install-path>\VERITAS\NetBackup\var\global\device_mappings.txt from Master/Media server to <install-path>\VERITAS\NetBackup\var\global\device_mappings.txt your PC.

Restart RAC and try again.

If you are doing this from the Master then ignore this comment.

AJ

Beavisrulz's picture

Sorry, but we are definitely NOT using storage groups. I triple checked and we are only using storage units. We haven't used groups since we were backing up to tape drives and libraries over a year and a half ago.

You are correct in everything else though...we are using SLPs for AIR replication, but the backup operation in the SLP points to a storage unit, not a storage group. See my posts from July 8th and 9th.

Beavisrulz's picture

I have been using the admin console on the master server. Just tried the Java version Remote Admin and I get the same results. Guess I'll be calling Support!  ;-)

Thanks everyone for all your help. I will let you know the outcome.

Marianne's picture

You're right - time to log a support call.

Please keep us updated!

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

Mark_Solutions's picture

OK - sorry about the groups part, obviously mis-read that!

So could you try one more thing (as I have seen policies cache things that will just not go away)

Make sure you open the Admin Console on the Master using "Run as Administrator" whilst being logged onto the server as a user with full local admin rights - Accelerator will not get added if you do not do it this way

Create a new SLP from scratch with a name you have never used before - backup destination being your pure disk storage unit, replication to remote master (I assume you have added the remote master details to the Storage Servers credentials already?)

Next create a new policy, again one with a new name, select the SLP as the policy storage unit but do not tick the accelerator button yet.

Add your schedules (If you need to override for Weekly / Monthly schedules then make sure you are also using new Weekly / Monthly SLPs)

Save the policy

Re-open it and see if you can now tick the use Accelerator check box

Screen shot any errors so that we can see exactly what you get

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.

Beavisrulz's picture

I've done all of that before, and still receive the same errors. Here are screen shots of what I'm seeing. Pic labeled Error1.jpg is the error I receive if I have it set to use a SLP. Pic labeled Error2.jpg is the error I receive if it is set directly for a storage unit.

I have opened a call with Support this morning. Ticket #04841806.

Thanks,

Larry

Error1.jpg Error2.jpg
Beavisrulz's picture

RESOLVED!   WOOHOO!

Working with tech support, the issue revolved around an outdated device mappings file. So basically, each time Accelerator tried to validate my storage unit, it didn't recognize it as a support device since it didn't exist in the device mappings file.

According to this document, it will be fixed in 7.6:

http://www.symantec.com/business/support/index?page=content&id=TECH189730

But you can update the file yourself by following this document:

http://www.symantec.com/business/support/index?page=content&id=TECH72544

All is well! I have been able to activate Accelerator on all policies with no issues. Now I'm just waiting to see what performance benefits I should see during the next full backup.

Thanks everyone for helping me. I really appreciate it!

Larry

SOLUTION