Schedule Snapshots - Overland Storage SnapServer Administrator's Manual

SnapServer GuardianOS 7.2 Administrator's Guide
share's path into snapshots mimics the original share's path into the live volume. The
snapshot share is created in the Shares section under the Security tab. See
page 7-6

Schedule Snapshots

Like backups, snapshots can be scheduled to recur at a designated time and interval. Part of
the initial creation process is to set the time and date when the snapshot will occur or recur.
In addition to synchronizing the backup and snapshot schedules, you must create a share
(and snapshot share) to the appropriate directory so that the backup software can access the
snapshot. For most backup purposes, the directory specified should be one that points to the
root of the volume so that all of the volume's data is backed up and available from the
snapshot share.
Step 1: Create a snapshot for each Traditional RAID volume or DynamicRAID
storage pool you want to back up.
In the Web Management Interface, navigate to Storage > Snapshots, and click Create
Snapshot. When defining and scheduling the snapshot, consider the following:
• Check the Create Recovery File checkbox to ensure that the ACL, extended
• Offset the snapshot and backup schedules such that the backup does not occur
Step 2: If you have not already done so, create a share for each volume with
snapshot share enabled.
In the Web Management Interface, navigate to the Security > Shares page, and click
Create Share. Select the volume you want the share to point to (if you want to create a
share to the root of the volume, simply accept the default path). Click Advanced Share
Properties, then select Create Snapshot Share.
Step 3: Set the backup software to archive the latest version of the snapshot.
The SnapServer makes it easy to configure your backup software to automatically archive
the most recent snapshot. Simply configure your backup software to copy the contents of
the
latest
For example, assume the snapshot share named SHARE1_SNAP contains the following
four directories:
latest
2011-09-25.120000
2011-10-01.000100
2011-10-07.020200
10400317-003 05/2012
and "Snapshot Access" on page C-4
attributes, and quota information are captured and appended to the snapshot. This
step is needed because many backup packages do not back up native ACLs and
quotas. Placing this information in a recovery file allows all backup packages to
include this information. If the volume needs to be restored from tape, or the entire
system needs to be recreated from scratch on a different server, this information
may be required to restore all rights and quota information.
until you are sure the snapshot has been created. The snapshot itself does not
require much time, but creating the recovery file may take up to 30 minutes,
depending on the number of files in the volume.
For example, assuming you schedule nightly backups for a heavily used volume at
3:00 a.m., you might schedule the snapshot of the volume to run every day at 2:30
a.m., allowing half an hour for the snapshot to run to completion.
directory within the snapshot share you created.
©2010-12 Overland Storage, Inc.
for details.
Snapshots
"Shares" on
 6-5