You will need to create 4 snapshots, the first one is reserved for the system the other 3 are used for the scheduled Snapshots located in the Disk Manager. Here is some important information on how to setup the schedule as well as accessing the data from a snapshot.
Accessing the snapshot to restore, is done manually by selecting the files or directories from the Snapshot directory. Recommended reserved space for Snapshot is at least 10% of the total storage capacity of the data in use for current and future. This is then located in each Snapshot filer (snap002, snap003 and so on) where stored. The storage of all changes is independent of the file-system Open-E NAS-XSR uses on block-level.
Only when the snapshot is deleted / removed the changes are permanently transferred to the actual data volume. Through a separate share, which is only available for the administrator (or backup administrator), a complete backup of the dataset can be done. Up to 100 snapshots can be stored for a long history of the dataset.
The Snapshot function is perfectly transparent for the users in the network.
Only the administrator can work with the Snapshots. You can have up to 100 Snapshots with scheduled times.
Snapshots can be activated/deactivated manually or automatically. In the
schedule options "Begin time" and "End time" and day of week are used for
automatic snapshots: this is the time of automatic activation and deactivation
(syntax is “him”). When snapshot start is set, the snapshot will be deactivated
and activated again at the given time. Alternatively, snapshots can be taken manually in the Maintenance �� Snapshot menu even if snapshots are automatically created under “Snapshot Definition”. Button remove all can by useful for removing all snapshot at one time. Snapshots are shared via SMB/CIFS protocol, but for authenticated users only.
Access to snapshots can be granted in Maintenance �� Snapshot. Recommendation: Use only as many active snapshots as really needed – a large count of active snapshots can slow down the system considerably. Please be reasonable, when you are calculating the space reserved for snapshots. Please set as snapshot size as much space as you expect
to change during active snapshot. E.g. when you are doing backup from snapshot which takes one hour please set this snapshot size to as much space that will be changed during one hour. The snapshot will become inactive if the content (data changed on Logical Volume) exceeds the snapshot capacity. You do not lose data in that case, just the dataset, which is virtual for the users at the moment, will be written to the data volume. The old dataset, which has been frozen with the snapshot, is not available any longer.
This example is suitable for companies that start working at 7 am and end
around 3 pm. Every morning - before everybody starts working - snapshot02 will by created (refreshed). This snapshot is designed to hold data from the beginning of
working day untouched to the end of the day. This will enable simple access to
files changed at the same day in order to look at previous file version.
After three hours of work, the second snapshot (03) will by created and will stay
active for 30 minutes. At this time, the backup server (Brightstor, for example) will
connect to clients that are running Open-e NAS and backup all data. This same
situation repeats at 1 pm and 3 pm - but with one difference - at this time, there
is much greater activity (many more files are written), because at 3 pm all
changes are stored in expectance of leaving off work. The last snapshot with only 1% reserved space is forerunning backups on a tape device with a backup server. This backup takes much more time as backing up one single hard drive.
Reply With Quote