Restart a ShadowProtect chain

Written By Tami Sutcliffe (Super Administrator)

Updated at August 20th, 2021


Restarting a ShadowProtect chain can be part of a normal backup plan or it might be part of a process to address errors in an existing backup chain.


The simple approach is fairly straight-forward:

  1. Pause the ShadowProtect backup job
  2. Archive the existing image chain to another location on the BDR, a NAS device, or delete it.
  3. Optional: Destroy the destination's data via Online Backup Manager's File Manager
  4. Enable the backup job and tell it to create a new base image.
  5. Optional: Preload the new data if necessary

Detailed Description

There are potentially additional considerations, especially if there have been troubleshooting steps which might include reinstalling the agent:

  • ShadowProtect Agent
    • Important: Pausing the job while any additional steps are taken.
  • Existing and New Chain considerations
    • Delete or archive as desired
      • If temporarily archived on the BDR, be sure to do so outside the destination's parent folder
        • Eg: Move contents of X:\VolumeImages\ExchangeServer into X:\VolumeImages-Archive\ExchangeServer
    • Pay attention to the naming of the new chain.  Under most circumstances, where the agent has not been reinstalled, the new base image should increment up from (eg) "b001" to "b002".  With this in mind, the Online Backup Manager steps are optional.  However, if the name is the same as the old, Online Backup Manager steps are important.
  • ImageManager
    • Note: This is only applicable if the new base image name is the same as the old base image name (eg: "b001")
    • Note: This may only be applicable to old versions of ImageManager and not the new v6.x or above.
    • ImageManager has both logs (installdir\Logs) and a tracking database (installdir\ImageManager.mdb) which keeps information about existing chains.
    • Optional Steps:
      1. Open ImageManager
      2. Note the per-folder retention settings: use global or what overrides are configured
      3. Stop managing the destination folder.
      4. Start managing the destination folder.
      5. Reconfigure or confirm retention settings
  • Online Backup Manager (OBM)
    • If a file goes 'missing' from a source directory that had been previously backed up, that file is marked "deleted" and will eventually be destroyed per the Deleted retention and how often the Maintenance is scheduled (Destroy Deleted Files).
      • Settings are found in the Online Backup Manager Options panel > Versioning tab.
    • However, there are two potential considerations that can make waiting less attractive:
      • Waiting for the deleted retention to apply can often take 7+ days (default on an Axcient BDR appliance is 7 days).  This might not be desired if the end of the month is approaching for billing purposes.
      • If other activities with the agent (reinstallation) result in a new chain with the same "b###" name, you can risk "versions" being uploaded rather than fully new files.
    • To avoid confusion or to clear data prior to billing, use the File Manager to destroy the older chain.
    • Exception: Some partners have used the offsite data as a temporary archive.
      • This can only be done if the new chain is a different name than the old.
      • The old chain must stay in the destination folder on the BDR if you don't want the old chain marked deleted in the destination.
      • Be aware of the deleted retention settings in the Online Backup Manager (globally and for the VolumeImages folder-policy)

Copyright © 2017 Axcient Inc. Use of the StorageCraft and ShadowProtect trademarks does not imply official endorsement by StorageCraft Technology Corporation. Axcient and the Axcient logo are trademarks of Axcient Inc. StorageCraft®, ShadowProtect®, ShadowControl®, HeadStart Restore®, ShadowStream®, and intelligentFTP®are registered trademarks of StorageCraft or its licensors in the United States or elsewhere. Axcient AND STORAGECRAFT TECHNOLOGY MAKE NO WARRANTIES, EXPRESSED OR IMPLIED, IN THIS DOCUMENT. All rights reserved.