Adaptec 5325301638 Administration Guide - Page 76

Creating the SnapDRImage and Volume Files, SnapDRImage, Volume-specific files

Page 76 highlights

Backing Up Server and Volume Settings • SnapDRImage - The Snap Server disaster recovery image saves server-specific settings such as server name, network, RAID, volume and share configuration, local user and group lists, and snapshot schedules. There is one SnapDRImage file per server, residing on the root directory of the first volume at the following path: \\server_name\volume_name. Tip The SnapDRImage file is in binary form and can be safely used only with the Snap Server Disaster Recovery tool. Other tools will not work and may compromise the integrity of the file. • Volume-specific files - These files, named backup.acl, backup.qta.groups, and backup.qta.users, preserve volume-specific settings such as ACLs, extended attributes, and quota settings. One set of these files exists per volume, residing at the following path: \\server_name\volume_name\.os_private. Caution The Create Recovery Files option in the snapshot feature automatically updates the volume-specific files when the snapshot is taken. If you do not use snapshots to back up a volume to tape, you must manually regenerate these files whenever you change ACL or quota information to ensure that you are backing up the most current volume settings. Creating the SnapDRImage and Volume Files Before you create the disaster recovery files, make sure you have completed the following activities: • You have completely configured the Snap Server. If you subsequently make any major changes to the configuration, you must repeat the procedures described in this section. • You have recorded, in an off-server location, the following information about the configuration: (1) the server name; (2) the number of RAIDs; (3) the number of volumes; and (4) the size of each volume. You may need to enter this information later as part of a disaster recovery operation. • You have devised and implemented a data backup strategy. Use the following procedure to create and secure the disaster recovery files: 1 Create the disaster recovery files. Navigate to the Maintenance > Disaster Recovery screen. Click Create Recovery Images to create the SnapDRImage file and the volume files in a single operation. 2 Copy the files to a safe place off the server. Copy the SnapDRImage file to a safe location on another server or backup medium. (See the previous section for file names and paths.) This strategy ensures that if the file system on the Snap Server is corrupted, the image file will be available to restore server settings. 62 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

Backing Up Server and Volume Settings
62
Snap Server Administrator Guide
SnapDRImage
— The Snap Server disaster recovery image saves server-specific
settings such as server name, network, RAID, volume and share configuration,
local user and group lists, and snapshot schedules. There is one SnapDRImage
file per server, residing on the root directory of the first volume at the following
path:
\\server_name\volume_name.
Tip
The SnapDRImage file is in binary form and can be safely used only with the
Snap Server Disaster Recovery tool. Other tools will not work and may
compromise the integrity of the file.
Volume-specific files —
These files, named
backup.acl
,
backup.qta.groups
, and
backup.qta.users
, preserve volume-specific settings such as ACLs, extended
attributes, and quota settings. One set of these files exists per volume, residing at
the following path:
\\server_name\volume_name\
.os_private.
Caution
The Create Recovery Files option in the snapshot feature automatically
updates the volume-specific files when the snapshot is taken. If you do not use
snapshots to back up a volume to tape, you must manually regenerate these files
whenever you change ACL or quota information to ensure that you are backing
up the most current volume settings.
Creating the SnapDRImage and Volume Files
Before you create the disaster recovery files, make sure you have completed the
following activities:
You have completely configured the Snap Server. If you subsequently make any
major changes to the configuration, you must repeat the procedures described in
this section.
You have recorded, in an off-server location, the following information about the
configuration: (1) the server name; (2) the number of RAIDs; (3) the number of
volumes; and (4) the size of each volume. You may need to enter this information
later as part of a disaster recovery operation.
You have devised and implemented a data backup strategy.
Use the following procedure to create and secure the disaster recovery files:
1
Create the disaster recovery files.
Navigate to the
Maintenance > Disaster Recovery
screen. Click
Create Recovery
Images
to create the SnapDRImage file and the volume files in a single operation.
2
Copy the files
to a safe place off the server.
Copy the SnapDRImage file to a safe location on another server or backup
medium. (See the previous section for file names and paths.) This strategy
ensures that if the file system on the Snap Server is corrupted, the image file will
be available to restore server settings.