Adaptec 5325301507 Administration Guide - Page 77

Data Migration, Preserving Permissions

Page 77 highlights

Data Migration Data Migration Use the Data Migration feature to migrate data from a legacy SnapServer or other computer that supports CIFS or NFS (v2 or v3) to a new SnapServer. The Data Migration (DM) feature can be used to copy or move files and folders from a server on the network (source) to a SnapServer (target). To access the Data Migration utility, navigate to Maintenance > Data Migration. If an error is encountered during migration (e.g., a file or folder is locked and cannot be migrated), the DM utility records the error in a log, and continues the operation. When the migration is completed, the administrator can view the log of migration errors. Once the errors have been corrected, the user returns to the DM main screen, and recreates the migration. With the exception of the password, all fields will still be populated with the specifications of the last job. The following migration options can be specified: • Copy or move data • Include subfolders • Overwrite existing files • Preserve the original permissions settings Note If you elect to preserve original permissions settings, be sure to review Preserving Permissions. • Verify migrated data Note If you elect to verify migrated data, all data will be read twice, once for migration and once for comparison to the copied data. This could be a lengthy process. For details about setting up a migration job, see the online help. Note If a migration failed, it is strongly recommended that you enable the Verify migrated data option for the re-migration. Preserving Permissions The types of permissions retained will differ, depending on which of the following migration scenarios is applied: Migrating from a Windows Security Model to a Windows SnapTree If you are migrating from a Windows server (or other type of server that follows the Windows security model) to a Windows SnapTree on a SnapServer, permissions will be retained exactly as they exist on the source. However, as is the case when moving files with permissions between Windows servers, permissions for users Chapter 4 Storage Configuration and Expansion 61

  • 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
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250

Data Migration
Chapter 4
Storage Configuration and Expansion
61
Data Migration
Use the Data Migration feature to migrate data from a legacy SnapServer or other
computer that supports CIFS or NFS (v2 or v3) to a new SnapServer. The Data
Migration (DM) feature can be used to copy or move files and folders from a server
on the network (source) to a SnapServer (target).
To access the Data Migration utility, navigate to
Maintenance > Data Migration
.
If an error is encountered during migration (e.g., a file or folder is locked and cannot
be migrated), the DM utility records the error in a log, and continues the operation.
When the migration is completed, the administrator can view the log of migration
errors. Once the errors have been corrected, the user
returns to the DM main
screen, and recreates the migration. With the exception of the password, all fields
will still be populated with the specifications of the last job.
The following migration options can be specified:
Copy or move data
Include subfolders
Overwrite existing files
Preserve the original permissions settings
Note
If you elect to preserve original permissions settings, be sure to review
Preserving Permissions.
Verify migrated data
Note
If you elect to verify migrated data, all data will be read twice, once for
migration and once for comparison to the copied data. This could be a lengthy
process.
For details about setting up a migration job, see the online help.
Note
If a migration failed, it is strongly recommended that you enable the
Verify
migrated data
option for the re-migration.
Preserving Permissions
The types of permissions retained will differ, depending on which of the following
migration scenarios is applied:
Migrating from a Windows Security Model to a Windows SnapTree
If you are migrating from a Windows server (or other type of server that follows the
Windows security model) to a Windows SnapTree on a SnapServer, permissions
will be retained exactly as they exist on the source. However, as is the case when
moving files with permissions between Windows servers, permissions for users