Adaptec 5325301638 Administration Guide - Page 73

Coordinating Snapshot and Backup Operations, Accessing Snapshots Within the Snapshot Share

Get Adaptec 5325301638 - Snap Server 4500 NAS PDF manuals and user guides
UPC - 753253016389
View all Adaptec 5325301638 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 73 highlights

Coordinating Snapshot and Backup Operations Accessing Snapshots Within the Snapshot Share A snapshot share contains a series of directories. Each directory inside the snapshot share represents a different snapshot. The directory names reflect the date and time the snapshot was created. For example, assume the snapshot share named Sales_SNAP contains the following four directories: latest 2003-12-25.120000 2004-01-01.000100 2004-01-07.020100 The latest directory always points to the most recent snapshot (in this case, 200301-07.020100, or January 7th, 2003, at 2:01 a.m.). A user may view an individual file as it existed at a previous point in time or even roll back to a previous version of the file by creating a file copy to the current live volume. Tip The "latest" subdirectory is very useful for setting up backup jobs as the name of the directory is always the same and always points to the latest available snapshot. Coordinating Snapshot and Backup Operations Like backups, snapshots can be scheduled to recur at a designated time and interval. 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. 1 Create a snapshot for each volume you want to back up. In the Administration Tool, navigate to the Storage > Snapshots screen, and click Create Snapshot. When defining and scheduling the snapshot, consider the following: • In the Create Recovery File pull-down menu, select Yes to ensure that the ACL, extended attributes, and quota information is 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. • Offset the snapshot and backup schedules such that the backup does not occur 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, Chapter 7 Snapshots 59

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
Coordinating Snapshot and Backup Operations
Chapter 7
Snapshots
59
Accessing Snapshots Within the Snapshot Share
A snapshot share contains a series of directories. Each directory inside the snapshot
share represents a different snapshot. The directory names reflect the date and time
the snapshot was created. For example, assume the snapshot share named
Sales_SNAP
contains the following four directories:
latest
2003-12-25.120000
2004-01-01.000100
2004-01-07.020100
The
latest
directory always points to the most recent snapshot (in this case,
2003-
01-07.020100
, or January 7th, 2003, at 2:01 a.m.). A user may view an individual
file as it existed at a previous point in time or even roll back to a previous version of
the file by creating a file copy to the current live volume.
Tip
The “latest” subdirectory is very useful for setting up backup jobs as the name
of the directory is always the same and always points to the latest available
snapshot.
Coordinating Snapshot and Backup Operations
Like backups, snapshots can be scheduled to recur at a designated time and
interval. 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.
1
Create a snapshot for each volume you want to back up.
In the Administration Tool, navigate to the
Storage > Snapshots
screen
,
and click
Create Snapshot
. When defining and scheduling the snapshot, consider the
following:
•
In the Create Recovery File pull-down menu, select
Yes
to ensure that the ACL,
extended attributes, and quota information is 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.
•
Offset the snapshot and backup schedules such that the backup does not occur
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,