- VOX
- Data Protection
- NetBackup
- SLP won't start duplications
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-20-2013 02:01 PM
I have *one* SLP that doesn't seem to want to start duplications... and I can't for the life of me figure out why it won't. Other SLPs in my environment are starting just fine.
Backlog of incomplete SLP Copies
In Process (Storage Lifecycle State: 2):
Number of copies: 682
Total expected size 22834039 MB
SLP Name: (state) Number of copies: Size:
DEN-DENSYM_ADV_DEV01-stu_disk_densy... (active) 682 22834039 MB
Total: 682 22834039 MB
Solved! Go to Solution.
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-21-2013 09:28 AM
Not great news to have images half way through their SLP life when the SLP gets modified.
This can leave them half orphaned!
You cannot change the SLP version for an image so you need to do the following:
1. Only edited SLPs when everything has completed its lifecycle within them so that the next batch start afresh.
2. It doesn't look like any are set to expire immediately after the SLP completes so you should be safe to cancel the ones that are left orphaned so that at least youy can manually duplicate them
3. You will need to pipe out a list of all incomplete SLPs (looks like you are familiar enough with nstluitl to do that OK) and then run nbstlutil cancel -backupid **** -version 1 (or 2 or 3 etc,)
4. Manually duplicate the them as required
You can then start afresh
Hoipe this helps
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-20-2013 02:11 PM
Details on the SLP itself. NOTE: This SLP has been modified since the images in the backlog went "active"... not sure if that has any bearing on anything, but thought I'd mention it.
# sudo nbstl DEN-DENSYM_ADV_DEV01-stu_disk_densyma01p -L
Name: DEN-DENSYM_ADV_DEV01-stu_disk_densyma01p
Data Classification: (none specified)
Duplication job priority: 0
State: active
Version: 3
Operation 1 Use for: 0 (backup)
Storage: DENSYM_ADV_DEV01
Volume Pool: NetBackup
Server Group: Any
Retention Type: 1 (Capacity Managed)
Retention Level: 0 (1 week)
Alternate Read Server: (none specified)
Preserve Multiplexing: false
Enable Automatic Remote Import: false
State: active
Source: 0 (client)
Operation ID: 0
Operation Index: 1
Operation 2 Use for: 1 (duplication)
Storage: stu_disk_densyma01p
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: Operation 1 (backup:DENSYM_ADV_DEV01)
Operation ID: 0
Operation Index: 2
Operation 3 Use for: 1 (duplication)
Storage: densyma01p_I6K-LTO5
Volume Pool: NetBackup
Server Group: Any
Retention Type: 0 (Fixed)
Retention Level: 8 (1 year)
Alternate Read Server: (none specified)
Preserve Multiplexing: false
Enable Automatic Remote Import: false
State: active
Source: Operation 1 (backup:DENSYM_ADV_DEV01)
Operation ID: 0
Operation Index: 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-20-2013 02:31 PM
Here is a representative image that is in the backlog for that SLP:
# sudo nbstlutil stlilist -U -image_incomplete -backupid DENWEBPRCH01p_1359559324 Image DENWEBPRCH01p_1359559324 for Lifecycle DEN-DENSYM_ADV_DEV01-stu_disk_densyma01p is IN_PROCESS Copy to densyma01p_I6K-LTO5 of type DUPLICATE is NOT_STARTED Copy to stu_disk_densyma01p of type DUPLICATE is NOT_STARTED
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-20-2013 02:32 PM
-L image info:
# sudo nbstlutil stlilist -L -image_incomplete -backupid DENWEBPRCH01p_1359559324 V7.5.0 I DENWEBPRCH01p_1359559324 DEN-DENSYM_ADV_DEV01-stu_disk_densyma01p 2 V7.5.0 C densyma01p_I6K-LTO5 1 1 V7.5.0 C stu_disk_densyma01p 1 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-20-2013 05:23 PM
Well - it appears other SLPs are also having an issue. I activated an SLP today and it ran through about half of the backlog and now I have incomplete images that will not run... I'm currently collecting the incomplete image lists to see if I can find something that would account for them not running their duplications...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-21-2013 09:08 AM
A bit more information on the image referenced above:
Storage Lifecycle Policy: DEN-DENSYM_ADV_DEV01-stu_disk_densyma01p Storage Lifecycle Policy Version: 1 STL_Completed: 2
So it looks like it is SLP v1... while the current version for that SLP is v4. Although it looks like all the older versions are still "Active":
# sudo nbstl DEN-DENSYM_ADV_DEV01-stu_disk_densyma01p -L -all_versions | less
Name: DEN-DENSYM_ADV_DEV01-stu_disk_densyma01p
Data Classification: (none specified)
Duplication job priority: 0
State: active
Version: 4
Operation 1 Use for: 0 (backup)
Storage: DENSYM_ADV_DEV01
Volume Pool: NetBackup
Server Group: Any
Retention Type: 1 (Capacity Managed)
Retention Level: 0 (1 week)
Alternate Read Server: (none specified)
Preserve Multiplexing: false
Enable Automatic Remote Import: false
State: active
Source: 0 (client)
Operation ID: 0
Operation Index: 1
Operation 2 Use for: 1 (duplication)
Storage: stu_disk_densyma01p
Volume Pool: (none specified)
Server Group: (none specified)
Retention Type: 0 (Fixed)
Retention Level: 3 (1 month)
Alternate Read Server: (none specified)
Preserve Multiplexing: false
Enable Automatic Remote Import: false
State: active
Source: Operation 1 (backup:DENSYM_ADV_DEV01)
Operation ID: 0
Operation Index: 2
Operation 3 Use for: 1 (duplication)
Storage: densyma01p_I6K-LTO5
Volume Pool: NetBackup
Server Group: Any
Retention Type: 0 (Fixed)
Retention Level: 8 (1 year)
Alternate Read Server: (none specified)
Preserve Multiplexing: false
Enable Automatic Remote Import: false
State: active
Source: Operation 1 (backup:DENSYM_ADV_DEV01)
Operation ID: 0
Operation Index: 3
------------------------------------------------------------------------
Name: DEN-DENSYM_ADV_DEV01-stu_disk_densyma01p
Data Classification: (none specified)
Duplication job priority: 0
State: active
Version: 3
Operation 1 Use for: 0 (backup)
Storage: DENSYM_ADV_DEV01
Volume Pool: NetBackup
Server Group: Any
Retention Type: 1 (Capacity Managed)
Retention Level: 0 (1 week)
Alternate Read Server: (none specified)
Preserve Multiplexing: false
Enable Automatic Remote Import: false
State: active
Source: 0 (client)
Operation ID: 0
Operation Index: 1
Operation 2 Use for: 1 (duplication)
Storage: stu_disk_densyma01p
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: Operation 1 (backup:DENSYM_ADV_DEV01)
Operation ID: 0
Operation Index: 2
Operation 3 Use for: 1 (duplication)
Storage: densyma01p_I6K-LTO5
Volume Pool: NetBackup
Server Group: Any
Retention Type: 0 (Fixed)
Retention Level: 8 (1 year)
Alternate Read Server: (none specified)
Preserve Multiplexing: false
Enable Automatic Remote Import: false
State: active
Source: Operation 1 (backup:DENSYM_ADV_DEV01)
Operation ID: 0
Operation Index: 3
------------------------------------------------------------------------
Name: DEN-DENSYM_ADV_DEV01-stu_disk_densyma01p
Data Classification: (none specified)
Duplication job priority: 0
State: active
Version: 2
Operation 1 Use for: 0 (backup)
Storage: DENSYM_ADV_DEV01
Volume Pool: NetBackup
Server Group: Any
Retention Type: 1 (Capacity Managed)
Retention Level: 0 (1 week)
Alternate Read Server: (none specified)
Preserve Multiplexing: false
Enable Automatic Remote Import: false
State: active
Source: 0 (client)
Operation ID: 0
Operation Index: 1
Operation 2 Use for: 1 (duplication)
Storage: stu_disk_densyma01p
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: Operation 1 (backup:DENSYM_ADV_DEV01)
Operation ID: 0
Operation Index: 2
Operation 3 Use for: 1 (duplication)
Storage: densyma01p_I6K-LTO5
Volume Pool: NetBackup
Server Group: Any
Retention Type: 0 (Fixed)
Retention Level: 3 (1 month)
Alternate Read Server: (none specified)
Preserve Multiplexing: false
Enable Automatic Remote Import: false
State: active
Source: Operation 1 (backup:DENSYM_ADV_DEV01)
Operation ID: 0
Operation Index: 3
------------------------------------------------------------------------
Name: DEN-DENSYM_ADV_DEV01-stu_disk_densyma01p
Data Classification: (none specified)
Duplication job priority: 0
State: inactive
Version: 1
Operation 1 Use for: 0 (backup)
Storage: DENSYM_ADV_DEV01
Volume Pool: NetBackup
Server Group: Any
Retention Type: 1 (Capacity Managed)
Retention Level: 0 (1 week)
Alternate Read Server: (none specified)
Preserve Multiplexing: false
Enable Automatic Remote Import: false
State: active
Source: 0 (client)
Operation ID: 0
Operation Index: 1
Operation 2 Use for: 1 (duplication)
Storage: densyma01p_I6K-LTO5
Volume Pool: NetBackup
Server Group: Any
Retention Type: 0 (Fixed)
Retention Level: 3 (1 month)
Alternate Read Server: (none specified)
Preserve Multiplexing: false
Enable Automatic Remote Import: false
State: active
Source: Operation 1 (backup:DENSYM_ADV_DEV01)
Operation ID: 0
Operation Index: 2
Operation 3 Use for: 1 (duplication)
Storage: stu_disk_densyma01p
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: Operation 1 (backup:DENSYM_ADV_DEV01)
Operation ID: 0
Operation Index: 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-21-2013 09:28 AM
Not great news to have images half way through their SLP life when the SLP gets modified.
This can leave them half orphaned!
You cannot change the SLP version for an image so you need to do the following:
1. Only edited SLPs when everything has completed its lifecycle within them so that the next batch start afresh.
2. It doesn't look like any are set to expire immediately after the SLP completes so you should be safe to cancel the ones that are left orphaned so that at least youy can manually duplicate them
3. You will need to pipe out a list of all incomplete SLPs (looks like you are familiar enough with nstluitl to do that OK) and then run nbstlutil cancel -backupid **** -version 1 (or 2 or 3 etc,)
4. Manually duplicate the them as required
You can then start afresh
Hoipe this helps
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-21-2013 10:42 AM
Well - it's good to know, I suppose. :) I'll just manually dupe things and get back to square one. Thanks for the help!
