File_System_Migration

Recommendations

Info

Preface Related documentation Conventions used in this guide ! Related documents include: ◆ VNX Glossary ◆ Problem Resolution Roadmap for VNX ◆ EMC VNX Command Line Interface Reference for File ◆ VNX 1.0 Release Notes ◆ Configuring Events and Notifications on VNX for File ◆ Configuring NDMP Backups on VNX ◆ Configuring NDMP Backups to Disk on VNX ◆ Configuring and Managing CIFS on VNX ◆ Configuring VNX User Mapping ◆ Configuring and Managing Networking on VNX ◆ Managing a Multiprotocol Environment on VNX ◆ Managing Volumes and File Systems for VNX Manually ◆ Managing Volumes and File Systems with VNX Automatic Volume Management ◆ Using VNX Event Enabler ◆ Using EMC Utilities for the CIFS Environment ◆ Using FTP and TFTP on VNX ◆ Using International Character Sets on VNX for File ◆ Using Windows Administrative Tools on VNX EMC uses the following conventions for special notices. Note: A note presents information that is important, but not hazard-related. CAUTION A caution contains information essential to avoid data loss or damage to the system or equipment. WARNING A warning contains information essential to avoid a hazard that can cause severe personal injury, death, or substantial property damage if you ignore the warning. 12 VNX File System Migration Version 2.0 for NFS and CIFS User Guide 7.1
Typographical conventions EMC uses the following type style conventions in this document: Normal Used in running (nonprocedural) text for: • Names of interface elements (such as names of windows, dialog boxes, buttons, fields, and menus) Names of resources, attributes, pools, Boolean expressions, buttons, DQL statements, keywords, clauses, environment variables, functions, utilities URLs, pathnames, filenames, directory names, computer names, filenames, links, groups, service keys, file systems, notifications Bold Used in running (nonprocedural) text for: Names of commands, daemons, options, programs, processes, services, applications, utilities, kernels, notifications, system calls, man pages Used in procedures for: Names of interface elements (such as names of windows, dialog boxes, buttons, fields, and menus) What user specifically selects, clicks, presses, or types Italic Used in all text (including procedures) for: Full titles of publications referenced in text Emphasis (for example a new term) Variables Courier Used for: System output, such as an error message or script URLs, complete paths, filenames, prompts, and syntax when shown outside of running text Courier bold Used for: Specific user input (such as commands) Courier italic Used in procedures for: Variables on command line User input variables < > Angle brackets enclose parameter or variable values supplied by the user [ ] Square brackets enclose optional values | Vertical bar indicates alternate selections - the bar means “or” { } Braces indicate content that you must specify (that is, x or y or z) ... Ellipses indicate nonessential information omitted from the example Preface VNX File System Migration Version 2.0 for NFS and CIFS User Guide 7.1 13
Page 1 and 2: EMC ® VNX Series VNX File System
Page 3 and 4: Preface Contents Chapter 1 CDMS Ove
Page 5 and 6: Administrative share methodology...
Page 7 and 8: Figures Title Page 1 NFS configurat
Page 9 and 10: Tables Title Page 1 CIFS migration
Page 11: Preface As part of an effort to imp
Page 15 and 16: Invisible Body Tag 1 CDMS Overview
Page 17 and 18: Supported capabilities CDMS Overvie
Page 19 and 20: CIFS specific The following support
Page 21 and 22: Scope CDMS Overview This section co
Page 23 and 24: Assumptions CDMS Overview This sect
Page 25 and 26: Configuring VNX User Mapping provid
Page 27 and 28: CDMS Overview ◆ The user account
Page 29 and 30: System requirements CDMS Overview T
Page 31 and 32: Restrictions and limitations CDMS O
Page 33 and 34: CDMS Overview ◆ Microsoft guarant
Page 35 and 36: NFS specific The following tools ar
Page 37 and 38: CDMS Overview Figure 2 on page 37 s
Page 39 and 40: Mail Options Users Alex Ted Joe mai
Page 41 and 42: CDMS Overview 4. The mail.txt file
Page 43 and 44: Issue tracker CDMS Overview The iss
Page 45 and 46: Invisible Body Tag 2 Site Preparati
Page 47 and 48: Checklist This section contains a c
Page 49 and 50: Site Preparation ❑ Configure the
Page 51 and 52: Using the server_cdms command Table
Page 53 and 54: User interfaces choices GUI support
Page 55 and 56: Determining file system size Runnin
Page 57 and 58: Site Preparation ◆ If the source
Page 59 and 60: Site Preparation ◆ Creating print
Page 61 and 62: Usermapper methods Site Preparation
Page 63 and 64:
Adding Win32 API to Perl script (CI
Page 65 and 66:
Step Action Table 5 Adding Win32 AP
Page 67 and 68:
Invisible Body Tag 3 Migration Proc
Page 69 and 70:
Personnel qualifications Migration
Page 71 and 72:
Invisible Body Tag 4 Planning and D
Page 73 and 74:
Planning and Design migrations, a c
Page 75 and 76:
Planning and Design Do files get co
Page 77 and 78:
Planning and design Planning and De
Page 79 and 80:
Step Action Planning and Design 4 (
Page 81 and 82:
Data Migration Analysis and detaile
Page 83 and 84:
Step Action To complete the file sy
Page 85 and 86:
Planning and Design File format The
Page 87 and 88:
Invisible Body Tag 5 NFS The follow
Page 89 and 90:
Summary Table 6 on page 89 summariz
Page 91 and 92:
2. If the Data Mover assumes the IP
Page 93 and 94:
Step 2: Preparing file systems for
Page 95 and 96:
Action To create an MGFS, use this
Page 97 and 98:
6. Check that the file system is mo
Page 99 and 100:
Step 4: Starting the CDMS migration
Page 101 and 102:
Action localPort= = port number use
Page 103 and 104:
3. Check the server log to ensure t
Page 105 and 106:
The fstab must be modified as follo
Page 107 and 108:
Step 6: Ensuring that all data is m
Page 109 and 110:
Output $ server_2 : pmacF30: path =
Page 111 and 112:
Extending disk space If you run out
Page 113 and 114:
Step 8: Verifying migration complet
Page 115 and 116:
Action To verify the status of a mi
Page 117 and 118:
Step 9: Converting the migration fi
Page 119 and 120:
Many-to-one migration Step 5: Conne
Page 121 and 122:
-type {nfsv2|nfsv3} = NFS version 3
Page 123 and 124:
Parallelization or serialization Si
Page 125 and 126:
Ensure that you monitor the progres
Page 127 and 128:
Postmigration testing Assuming the
Page 129 and 130:
Invisible Body Tag 6 CIFS The follo
Page 131 and 132:
Administrative share methodology Us
Page 133 and 134:
One-to-one migration Source file se
Page 135 and 136:
Summary Table 8 on page 135 summari
Page 137 and 138:
Step 1: Creating an account Create
Page 139 and 140:
For a Windows NT 4.0 environment If
Page 141 and 142:
Output SHAREDUP 01.06 Copyright (c)
Page 143 and 144:
where: exclude = default prefix =
Page 145 and 146:
Step 4: Identifying high-priority f
Page 147 and 148:
Note: Kerberos is a security system
Page 149 and 150:
3. Enable Unicode for the Data Move
Page 151 and 152:
Action To configure interfaces betw
Page 153 and 154:
Perform the following: 1. Create st
Page 155 and 156:
Output Note id = 18 name = mgfs1 ac
Page 157 and 158:
Step 8: Preparing for migration Per
Page 159 and 160:
a. If migrating from a Windows 2000
Page 161 and 162:
Step 9: Setting up the CIFS environ
Page 163 and 164:
3. For Windows environments, ensure
Page 165 and 166:
Two rights are required for the lgd
Page 167 and 168:
Step 11: Creating CDMS connections
Page 169 and 170:
For a Windows NT 4.0 environment Ac
Page 171 and 172:
Configure the Data Mover by using a
Page 173 and 174:
Step 14: Ensuring that all data is
Page 175 and 176:
If the error log is not empty, foll
Page 177 and 178:
Monitoring progress Action To monit
Page 179 and 180:
Action To verify the status of a mi
Page 181 and 182:
Step 17: Converting the MGFS to a U
Page 183 and 184:
! CAUTION Step 18: The next step If
Page 185 and 186:
Summary The steps to implement many
Page 187 and 188:
Retained server name merge New serv
Page 189 and 190:
Step 4: Evaluating the source file
Page 191 and 192:
Output Note id = 246 name = stv1 ac
Page 193 and 194:
Output id = 33 name = mgfs2 acl = 0
Page 195 and 196:
Two rights are required for the lgd
Page 197 and 198:
Step 10: Setting up the CIFS enviro
Page 199 and 200:
For a Windows NT 4.0 environment Ac
Page 201 and 202:
Step 11: Migrating local group info
Page 203 and 204:
Action To migrate the local group i
Page 205 and 206:
Create connections for each CIFS so
Page 207 and 208:
To perform this task, use a command
Page 209 and 210:
= mount point name of the MGFS (wit
Page 211 and 212:
The sharedup.exe utility output fil
Page 213 and 214:
Step 14: Ensuring all data is migra
Page 215 and 216:
Step 6: Backing up the source file
Page 217 and 218:
Step 10: Setting up the CIFS enviro
Page 219 and 220:
Step 16: The next step If all CIFS
Page 221 and 222:
Invisible Body Tag 7 Troubleshootin
Page 223 and 224:
Problems and solutions Troubleshoot
Page 225 and 226:
CDMS connect fails on session setup
Page 227 and 228:
Migration suspension (hang) conditi
Page 229 and 230:
For example, if the system server_3
Page 231 and 232:
Connection command failures (CIFS)
Page 233 and 234:
Time skews too much in a Windows 20
Page 235 and 236:
Example SMB: 3: CIFSCallBackForMGFS
Page 237 and 238:
Managing a failed verification or c
Page 239 and 240:
Step Action Troubleshooting CDMS 5
Page 241 and 242:
Using the server_cdms command Troub
Page 243 and 244:
Table 14 Migration error codes (pag
Page 245 and 246:
CDMS server log error messages Trou
Page 247 and 248:
Invisible Body Tag A Using CDMS Mig
Page 249 and 250:
Tool description summary Using CDMS
Page 251 and 252:
ackupWrapper.exe utility Using CDMS
Page 253 and 254:
# #SHAREDUP FILE @Revision:1 @Sourc
Page 255 and 256:
Using CDMS Migration Tools to migra
Page 257 and 258:
ch_group.pl script Tool location UN
Page 259 and 260:
Using CDMS Migration Tools “Migra
Page 261 and 262:
Using CDMS Migration Tools ◆ If t
Page 263 and 264:
Running the script Run the scripts
Page 265 and 266:
Displaying directory structure (Win
Page 267 and 268:
Using CDMS Migration Tools Using a
Page 269 and 270:
Using CDMS Migration Tools If the a
Page 271 and 272:
Using CDMS Migration Tools Function
Page 273 and 274:
Step Action Using CDMS Migration To
Page 275 and 276:
Using CDMS Migration Tools xxxxxxxx
Page 277 and 278:
International multibyte character s
Page 279 and 280:
Subdirectory open successfully Clie
Page 281 and 282:
Known issues There are known issues
Page 283 and 284:
diskUsage.pl script Using CDMS Migr
Page 285 and 286:
Entering the pathname for the log f
Page 287 and 288:
Using CDMS Migration Tools ========
Page 289 and 290:
Using CDMS Migration Tools As shown
Page 291 and 292:
lgdup.exe utility Using CDMS Migrat
Page 293 and 294:
Table 19 The shareup.exe utility op
Page 295 and 296:
Invisible Body Tag B Estimating NFS
Page 297 and 298:
Assumptions Estimating NFS Data Mig
Page 299 and 300:
Initial time estimate Example Estim
Page 301 and 302:
Small file data migration rates Est
Page 303 and 304:
Estimating NFS Data Migration Times
Page 305 and 306:
Parallel migration Estimating NFS D
Page 307 and 308:
Invisible Body Tag C NFS Mount and
Page 309 and 310:
Constructing read requests NFS Moun
Page 311 and 312:
NFS Mount and Export Options File i
Page 313 and 314:
NFS Mount and Export Options The an
Page 315 and 316:
Migrating files with the SetGroupID
Page 317 and 318:
Invisible Body Tag D Logging The fo
Page 319 and 320:
Sample session The following is an
Page 321 and 322:
. Using a text editor, open the par
Page 323 and 324:
Invisible Body Tag E Network Applia
Page 325 and 326:
Procedure Step Action Network Appli
Page 327 and 328:
! Output Network Appliance Consider
Page 329 and 330:
Network Appliance Considerations 7.
Page 331 and 332:
Symbols .ckpt file, disposition 269
Page 333 and 334:
connection command spaces in share
Page 335 and 336:
converting 51 exporting for NetApp
Page 337 and 338:
duration variables 110, 174 example
Page 339 and 340:
Windows systems 33 sequential migra
Page 341 and 342:
X xlt.cfg file, editing for interna
show all

File_System_Migration

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?