Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.

The document explains data protection mechanism inherit in  Brickstor Brickstor OS. This document provides a high level of the concepts in order to properly configure data protection snapshot and retention policies. For more specific questions or more in-depth knowledge please reach out to our support.


  • It is a good idea for most organizations to have at least a daily snapshot which is retained for some number of days.
  • Of course, if data is considered to be disposable after some amount of time, it does not make sense maintaining snapshots any longer than that period.
  • One may be concerned with too many snapshots, which results in rapid depletion of available capacity. This is a concern when the system is low on disk space. Data protection has intelligence built into it to protect a system from running out of space. This is an area where as administrators we don't need to be concerned very much. 
  • If data is turned over heavily, which could happen in cases where data are files representing VM disks, swaps, temporary holds and the like, one may not be able to maintain the number of snapshots they would like to, due to rapid consumption of storage by the frequent changes. Consider length of time snapshots are stored in this instance. The oldest snapshots will certainly lock in most of the change, therefor resulting in the largest pie consumer of the overall depletion.capacity. The user interface gives a visual display of how much data is being consumed by snapshots.
  • Increasing periods between snapshots taken reduces one'd s change capture granularity, but in the process reduces capacity depletion, which may be desirable in instances where capacity is already low.and may reduce capacity depletion. It will reduce capacity depletion if lots of data was modified, removed or deleted. If the working data set just has additions of data this will have no affect.
  • Use some combination of daily, weekly and monthly snapshots when value of data does not rapidly degrade with time. For example, in the case of Virtual Machines it may not make sense to retain snapshots for long, simply because there is so much context that may be lost of one restores data from weeks ago that the data is made useless in the process.
  • Related data should be on same retention schedule. Make sure that if there is data across datasets data sets that is in some ways related, and restore of some subset from one dataset data set may also require a restore of some subset from another datasetdata set, do not vary schedules between these two datasets data sets as that may make it impossible to recover data from both datasets data sets from exact same time period. Temporal difference differences may make this data useless.