07-03-2013 08:15 AM
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
Solved! Go to Solution.
08-06-2013 06:09 AM
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
07-03-2013 09:26 AM
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.
07-03-2013 10:22 AM
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
07-03-2013 11:18 AM
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.
07-03-2013 11:21 AM
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 :)
07-03-2013 12:11 PM
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.
07-03-2013 12:21 PM
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
07-03-2013 12:29 PM
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.
07-03-2013 12:49 PM
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
07-03-2013 01:08 PM
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?
07-08-2013 06:09 AM
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
07-08-2013 06:16 AM
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
07-08-2013 11:53 AM
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
07-08-2013 12:07 PM
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
07-08-2013 12:15 PM
I do not see any error to the Policy the storage unit or the SLP.
If possible post the detail status of a job.
07-08-2013 01:07 PM
What happens if you just select KMC_Pool_10 in the backup policy? (Assuming this is your dedupe STU)
07-09-2013 04:26 AM
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>"
07-09-2013 04:48 AM
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
07-09-2013 05:33 AM
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
07-09-2013 06:01 AM
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