Important Update: Cohesity Products Knowledge Base Articles
All Cohesity Knowledge Base Articles are now managed via the Cohesity Support Portal: https://support.cohesity.com/s/searchunify. The Knowledge Base articles available here will not reflect the latest information or may no longer be accessible.
Problem
This issue usually appear when some SLP's are able to trigger duplication job but few specific individual SLP's in the environment are not able to trigger duplication job.
Duplication job will not start as duplication operation is showing status "inactive". We can't change the state of duplication operation from inactive to active using GUI or using below command
nbstlutil active -lifecycle <slp_name>
Error Message
At GUI, SLP will keep on showing active status but duplication operation will show inactive state at command line when we run below command in order to check it's state.
Example:- SLP name is Test
nbstl Test -all_versions -L
Name: Test
Data Classification: (none specified)
Duplication Job Priority: 0
State: active
Version: 0
Operation 1 Use for: 0 (backup)
Storage: stu_msdp_nbmaster2
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: false
State: active
Source: 0 (client)
Operation ID: (none specified)
Operation Index: 1
Window Name: --
Window Close Option: --
Deferred Duplication: no
Operation 2 Use for: 1 (duplication)
Storage: stu_adv_nbmaster2
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: false
State: inactive
Source: Operation 1 (backup:stu_msdp_nbmaster2)
Operation ID: (none specified)
Operation Index: 2
Window Name: Default_24x7_Window
Window Close Option: SFN
Deferred Duplication: no
Cause
Solution
Run below command to change the status from inactive to active of duplication operation in SLP:-
nbstlutil active -lifecycle <slp_name> -destination <storage unit of the operation showing inactive status>
Example,
nbstlutil active -lifecycle Test -destination stu_adv_nbmaster2
SLP secondary operation will start showing status active and it will trigger in some time.
nbstl Test -all_versions -L
Name: Test
Data Classification: (none specified)
Duplication Job Priority: 0
State: active
Version: 0
Operation 1 Use for: 0 (backup)
Storage: stu_msdp_nbmaster2
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: false
State: active
Source: 0 (client)
Operation ID: (none specified)
Operation Index: 1
Window Name: --
Window Close Option: --
Deferred Duplication: no
Operation 2 Use for: 1 (duplication)
Storage: stu_adv_nbmaster2
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: false
State: active
Source: Operation 1 (backup:stu_msdp_nbmaster2)
Operation ID: (none specified)
Operation Index: 2
Window Name: Default_24x7_Window
Window Close Option: SFN
Deferred Duplication: no