The Quick Service Protection ARK creates a new resource type – “qsp”, in the LifeKeeper application type “gen”. Each QSP resource protects a single Windows service.

During create, the startup type of the protected service is set to “Manual”.

In order to create a QSP resource, the service to be protected must be in the Running state.

The kit provides the following LifeKeeper actions:

  • restore: the protected service is started
  • remove: the protected service is stopped
  • quickchk: the state of the protected service is queried and verified to be “running”
  • recover: the protected service is cleanly stopped and then started

If multiple services need to be protected simultaneously, each of the services should have a corresponding QSP instance. If there are service dependencies (i.e. Svc2 depends on Svc1), then the LifeKeeper hierarchy should reflect those dependencies. If no dependencies exist between services, the hierarchy can be created without dependencies between the QSP resources – they can be removed and restored in parallel.

After a QSP resource has been created on the Primary node, the protected service must exist on any Secondary node In order to be extend that node. Extend will set the startup type of that service to “Manual” on the Secondary node.

The QSP ARK implements a custom Properties page that can be used to change resource parameters on a given node. In the LifeKeeper GUI, right-click the resource and choose “Properties” – the GUI will allow you to modify the settings here.

When a QSP resource is deleted, the service startup type is left as Manual.


Was this helpful?

Yes No
You indicated this topic was not helpful to you ...
Could you please leave a comment telling us why? Thank you!
Thanks for your feedback.

Post your comment on this topic.

Post Comment