Restore Point

Scenario

Managing and applying restore points requires a complex combination of PowerShell and the vssadmin tool to manage shadow storage. This process is unified into a single set of instructions.

Product Pack notes:

Scenario

Managing and applying restore points requires a complex combination of PowerShell and the vssadmin tool to manage shadow storage. This process is unified into a single set of instructions.

 

Instructions

Questions

  • Recovery: Show system restore state
  • Recovery: Show status of last restore point action
  • Recovery: Show Shadow Storage
  • Recovery: Show restore points

Actions

 

  • Recovery: Set Shadow Storage to GB on device
  • Recovery: Set Restore Point State Enabled on device
  • Recovery: Set Restore Point Interval to mins on device
  • Recovery: Create Restore Point named on device
  • Recovery: Delete Restore Point With index on device
  • Recovery: Apply Restore Point with index to device

Notes

 

The actions are deliberately constrained to a specified endpoint in order to prevent accidental execution against a large device population, where the results could be undesirable. Note that if the action is not constrained by scope, all endpoints still receive it, but only the target endpoint will actually execute the instruction once it has confirmed that its name matches the parameter.

Restore points each have a unique numeric index. However the description for a restore point is not required to be unique.

Server-class operating systems do not support restore points (they have separate functionality for managing backups which is completely distinct). However they do support volume shadow storage. Consequently you can use the volume shadow storage functionality in this product pack on server devices.

Note however that currently the ‘set shadow storage’ instruction deliberately constrains the parameter to between 1 and 5 GB. An out of range size will be rejected and the instruction will not execute.

The ‘set shadow storage’ instruction only controls shadow storage on the operating system drive (drive C:, typically). It is possible to have shadow storage on other drives, but the instruction does not currently manage this for simplicity.

The instruction to enable/disable restore point state assumes that the backing shadow storage to support restore points will be on the operating system drive. (using the vssadmin utility)

Submitting one of the other actions or questions on a server-class device should not cause any adverse behaviour, but you should exercise caution.

Applying a restore point may take a considerable time on an endpoint. The restore executes asynchronously and the instruction will return success immediately, but the endpoint may reboot during the application of the restore point and be unavailable for a period of time. The Tachyon agent should re-connect after the restore point is applied, providing of course it was installed at the point the restore point was taken.

Exercise caution applying restore points. You may lose installed applications installed subsequent to the restore point, as the registry is completely restored to a consistent state. However endpoint data files should remain intact.

Resizing volume shadow storage to reduce allocated storage may cause some or all existing restore points to be automatically deleted by Windows.

Windows may delete pre-existing restore points at any time when upgrading. It may also automatically create restore points during upgrades or patches.

By default, you cannot create more than one restore point in a 24 hour period. The ‘Set restore point interval’ action allows you to override this behaviour, by setting a registry key which controls the time limit. This will allow you to create restore points more often, if desired.

Reviews

You must log in to submit a review. Click here to login.