Adaptec 5325301638 Administration Guide - Page 70

Scheduling Snapshots, Snapshots and Backup Optimization, NDMP and Snapshots, Snapshots and iSCSI Disks

Page 70 highlights

Snapshot Management and Usage snapshot and clicking the Rollback button. During the rollback operation, data on the volume will be inaccessible to clients. Cautions (1) Rolling back a volume cannot be undone and should only be used as a last resort after attempts to restore selected directories or files have failed; (2) Performing a rollback on a volume may invalidate the NetVault for GuardianOS nvdb directory for the volume, and may also disable the antivirus software. If you are using these features, take the necessary precautions as described in "Volumes" on page 33. Scheduling Snapshots Snapshots should ideally be taken when your system is idle. It is recommended that snapshots be taken before a backup is performed. For example, if your backup is scheduled at 4am, schedule the snapshot to be taken at 2am, thereby avoiding system activity and ensuring the snapshot is backed-up. See "Coordinating Snapshot and Backup Operations" on page 59 for more information. Snapshots and Backup Optimization When you back up a live volume directly, files that reference other files in the system may become "out-of sync" in relation to each other. The more data you have to back up, the more time is required for the backup operation, and the more likely these events are to occur. By backing up the snapshot rather than the volume itself, you greatly reduce the risk of archiving inconsistent data. For instructions, see "Coordinating Snapshot and Backup Operations" on page 59. NDMP and Snapshots A snapshot is automatically initiated by this type of backup operation. Administrators backing up via NDMP should consider the following: • When files and directories on a Windows SnapTree are backed up and restored to a UNIX SnapTree, extended Windows attributes and file ownership are not preserved. • If the snapshot pool does not have sufficient space to fire an additional snapshot, it will remove the oldest snapshots to create the space required. • NDMP backup jobs may not time out for extended periods when interrupted or the NDMP service is stopped. The DMA will continue to attempt to write data to the target device. Snapshots and iSCSI Disks Running a snapshot on a volume containing an iSCSI Disk will abruptly disconnect any clients attempting to write to the iSCSI Disk and the resulting snapshot may contain inconsistent data. Do not use snapshots on a volume containing an iSCSI Disk. 56 Snap Server Administrator Guide

  • 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

Snapshot Management and Usage
56
Snap Server Administrator Guide
snapshot and clicking the
Rollback
button. During the rollback operation, data on
the volume will be inaccessible to clients.
Cautions
(1) Rolling back a volume cannot be undone and should only be used as a last
resort after attempts to restore selected directories or files have failed; (2) Performing a
rollback on a volume may invalidate the NetVault for GuardianOS nvdb directory for
the volume, and may also disable the antivirus software. If you are using these features,
take the necessary precautions as described in “Volumes” on page 33.
Scheduling Snapshots
Snapshots should ideally be taken when your system is idle. It is recommended that
snapshots be taken before a backup is performed. For example, if your backup is
scheduled at 4am, schedule the snapshot to be taken at 2am, thereby avoiding
system activity and ensuring the snapshot is backed-up. See “Coordinating
Snapshot and Backup Operations” on page 59 for more information.
Snapshots and Backup Optimization
When you back up a live volume directly, files that reference other files in the
system may become “out-of sync” in relation to each other. The more data you have
to back up, the more time is required for the backup operation, and the more likely
these events are to occur. By backing up the snapshot rather than the volume itself,
you greatly reduce the risk of archiving inconsistent data. For instructions, see
“Coordinating Snapshot and Backup Operations” on page 59.
NDMP and Snapshots
A snapshot is automatically initiated by this type of backup operation.
Administrators backing up via NDMP should consider the following:
When files and directories on a Windows SnapTree are backed up and restored
to a UNIX SnapTree, extended Windows attributes and file ownership are not
preserved.
If the snapshot pool does not have sufficient space to fire an additional
snapshot, it will remove the oldest snapshots to create the space required.
NDMP backup jobs may not time out for extended periods when interrupted
or the NDMP service is stopped. The DMA will continue to attempt to write
data to the target device.
Snapshots and iSCSI Disks
Running a snapshot on a volume containing an iSCSI Disk will abruptly disconnect any
clients attempting to write to the iSCSI Disk and the resulting snapshot may contain
inconsistent data. Do not use snapshots on a volume containing an iSCSI Disk.