Server-side Data Migration
Contents
1. Are you sure you want to continue e 6 Click Yes to continue and create the mirror 7 When the mirror is created the resynching process starts This process can take hours to days depending on the total amount of data present on the original disk Disk 7 Dynamic 1 97 GB Online il Disk 8 Dynamic 1 97 GB Online Data1 I 1 97 GB NTFS Resynching 6 Datal I 1 97 GB NTFS Resynching 6 8 When the synchronization process is completed the disks are shown as healthy in the Disk Management console L Disk 7 Dynamic 1 97 GB Online L Disk amp Dynamic 1 97 GB Online To delete the mirror Data I 1 97 GB NTFS Healthy Data l 1 97 GB NTFS Healthy Removing the mirror After the synchronization process is complete the mirror can be removed retaining only one disk of the mirrored set The next section explains the procedure for removing the mirror We recommend that you perform this process during a scheduled maintenance window 1 Inthe Disk Management console right click one of the mirrored disks and select Remove Mirror 25 File Action View Help e m uT AX Efsa Yobe inot ipe feSpiem _ tones___ Copocty_ Fese Son Free __ a AstolfoVMS D Simple Basic Healthy P 1023 87 GB 804 03GB 79 a Data I Mirror Dynamic oe Healthy 1 97 GB 1 01 GB 51 lt a GE Local 1 E Simple Basic NTFS Healthy P 1023 87 GB 958 74GB 94 a GE Local 2 F Simple Ba2. 1023 88 GB Online LaDisk 5 Basic 1023 88 GB Online La Disk 6 Basic 1023 88 GB Online La Disk 7 Basic 1 97 GB Online La Disk 8 Dynamic 1 97 GB Online A StorSimpleVolume G 1023 87 GB NTFS Healthy Primary Partition 1023 88 GB Unallocated 1023 88 GB Unallocated 1 97 GB Unallocated Data1 I 1 97 GB NTFS Healthy W Unallocated If Primary partition I Simple volume Pros and cons of using disk mirroring Disks are online and operational while mirroring process is Mirrors cannot be created with CIFS shares mounted using in progress a drive letter No changes to shares required during or after mirroring Mirrors cannot be created on a NAS device process thus ensuring users are not affected during the The mirroring process mirrors each and every block stored migration process on the existing disk including empty blocks Simple process to implement If the existing disk is a basic disk it will be converted into a dynamic disk Cloud snapshots taken during the sync process are not usable as they will contain incomplete data NTFS AUS will be matched with original disk and may not be optimal for StorSimple ar References Microsoft Azure StorSimple for File Shares PowerShell File Checksum Integrity Verifier PSFCIV DiskBoss documentation Windows Sysinternals 28
3. add the range To add the 15 day to 30 day range select In Range 45 and 30 trom the drop down boxes as shown in the following illustration Click OK 15 Select Advanced File Search Criteria Search Files With the Directory Name Search Files With the File Name Only amp Search Files With the User Name Search Files Last Modified cere LE Advance Syne File Attributes Ma Sync User Group Security Descriptor Syne Discretionary Access Control List DACL wv Sync System Access Control List SACL W Enable Bit Level File Synchronization W Preserve Directories Timestamps W Disable Buffering For Large Files Enable File Write Through 16 5 Add the 0 to 30 days range by repeating steps 1 2 and selecting a range of 30 0 Select Advanced File Search Criteria Search Files Created Search Files With Last Modification Date Search Files With Last Access Date B Search Files With Creation Date E Searc Name Length L 6 Click Ok and save the command Mame t 45 days 30 45 Range jest Hoe Type File Synchronization Command File Synchronization Command File Synchronization Command 7 Execute the tiered command group by right clicking 17 ld Description Status Errors Progress a 3 0 30 Days Range Pending 0 Synchronized 0 Files 0 Bytes me 2 30 45 Day Range Pending 0 Synchronized 0 Files 0 Bytes Scheduled sync job creation This test validates the
4. the StorSimple appliance You should perform this phase during a scheduled downtime to avoid modification to the data during the final copy process During this phase we recommend that you disable user access and close any open handles to the files to ensure that data is copied After the final copy is complete you can give users access to the destination by changing the path to existing shares or by changing the drive letter of the new volume In Robocopy use the following command Robocopy lt source gt lt destination gt COPYALL S MIR ZB R 2 W 5 MT 32 Tools for data verification After you have used Robocopy to perform the file level data migration you must verify your data to ensure its integrity You should compare data from the original share to data on the new share You should perform this activity before you retire the original share You can download and use the PowerShell File Checksum Integrity Verifier PSFCIV for data verification A PsFCIV tracks the integrity status of your files by calculating cryptographic hashes over a file or files and writing them into an FCIV compatible XML database You can determine whether files were changed since the last check ran Important To avoid pulling the data from the cloud you should plan to run the verification tool in batches based on the local capacity of your appliance during the data copy operation Local capacity of the appliance will vary based on the StorSimple appli
5. the type of each file Small files are transferred using a regular buffered file copy mode while large files are transferred using a non buffered file copy mode which when the hardware platform supports it enables the write through I O mode e Regular Buffered File Copy Mode In this file copy mode DiskBoss performs regular buffered file copy operations according to the specified file I O block size and memory alignment e Fault Tolerant File Copy Mode In this file copy mode DiskBoss creates a temporary file for each file that should be copied and only after a successful file copy operation replaces the original file with the new one If a network failure occurs during a file copy operation the original files will remain in place without any changes See the following illustration 12 General Performance Mode File Copy Retries File Copy Block File Copy Mode Verification Mode e Operating System Native File Copy Mode This file copy mode is optimized for modern operating systems such as Windows Server 2012 and later This file copy mode supports SMB direct direct RDMA file transfers multi channel and write through file I O operations To take full advantage of all performance optimizations when synchronizing files via the network Windows Server 2012 or newer should be installed on both sides Performance Mode File Copy Retries File Copy Block File Copy
6. Basic NTFS Healthy B 837 99 GB 628 61GB 75 a StorSimpleVolume Simple Basic NTFS Healthy P 1023 87 GB 1013 69 99 a System Simple Basic NTFS Healthy S 350 MB 49 MB 14 C Disk 4 E Basic StorSimpleVolume G 1023 88 GB 1023 87 GB NTFS Online Healthy Primary Partition C Disk 5 Basic 1023 88 GB 1023 88 GB Online Unallocated iDisk 6 eC Basic 1023 88 GB 1023 88 GB Online Unallocated Basic Data I 1 97 GB 1 97 GB NTFS Open Onli i iti nline Healthy Primary Partition Explore J j Mark Partition as Active m 8 A Change Drive Letter and Paths E sic 1 97 GB 1 97 GB Format Online Unallocated Extend Volume t a Unallocated H Primary partition In the Add Mirror dialog box select the disk that is mounted from the StorSimple appliance Shrink Volume Delete Volume Properties Help Adding a miror to an existing volume provides data redundancy by maintaining multiple copies of a volume s data on different Select a location for a miror of Data f 4 e f i If the original data disk is a basic disk it will be converted to a dynamic disk The following confirmation message will be shown prior to conversion 24 F The operation you selected will convert the selected basic disk s to Jah dynamic disk s If you convert the disk s to dynamic you will not be able to start installed operating systems from any volume on the disk s except the current boot volume
7. EE Microsoft Server side Data Migration Migrating data trom an existing volume to a StorSimple volume September 2 2015 Copyright and Notices This document is provided as is Information and views expressed in this document including URL and other Internet Web site references may change without notice Some examples depicted herein are provided for illustration only and are fictitious No real association or connection is intended or should be interred This document does not provide you with any legal rights to any intellectual property in any Microsoft product You may copy use and modify this document for your internal reference purposes 2015 Microsoft Corporation All rights reserved Microsoft Windows Azure StorSimple Hyper V Internet Explorer Silverlight SQL Server Windows Windows PowerShell and Windows Server are trademarks of the Microsoft group of companies All other trademarks are property of their respective owners The DiskBoss data management product is the property of Flexense Ltd see http www tlexense com and http www diskboss com Contents OI IN NS a eae cena ected nae E dts AE TAE E E E E E Z Erais i getter E NE NE on etn ge ncn eet ntti EE AE TA A AE A conan yeneentyemete 3 EO a E A E E E E E E E E EE EEA E E eabeets z HS a N eaaa a E E E E E E E E E E E E EEE E E EE E E 3 PIT T O E E eee twp Se cn E E E EEE E E E E EEE E a IETS UT a TON IAs E ENEE EETA EE rsdn ke AAEE ET 5 PISO EE
8. Healthy P 1023 87 GB 69 99 a OSDisk C Simple Basic Healthy B 837 99 GB 4 75 a StorSimpleVolume Simple Basic Healthy P 1023 87 GB 69 99 lt a System Simple Basic Healthy S 350 MB 14 CaDisk 4 OOOO Basic StorSimpleVolume G 1023 88 GB 1023 87 GB NTFS Online Healthy Primary Partition C Disk 5 a Basic 1023 88 GB 1023 88 GB Online Unallocated ClDisk 6 Basic 1023 88 GB 1023 88 GB Online Unallocated Data l 1 97 GB NTFS Healthy Primary Partition La Disk 8 Basic 1 97 GB 1 97 GB Online Unallocated BB Unallocated I Primary partition 2 Onthe menu click Action gt Rescan Disks to discover the volume created on the StorSimple appliance Note Please refer to StorSimple documentation for instructions when creating a volume and using iSCSI to connect the Windows server to the StorSimple appliance 3 Right click the new disk and bring the disk online Right click the existing disk which contains data and select Add Mirror 23 s File Action View Help e i Aaxga Volume Layout Type File System Status Capacity Free Spa Free a Astolfo VMS D Simple Basic NTFS Healthy P 1023 87 GB 804 03 GB 79 a Data1 l Simple Basic NTFS Healthy P 1 97 GB 1 01 GB 51 a GE Local 1 E Simple Basic NTFS Healthy P 1023 87 GB 958 74GB 94 a GE Local 2 F Simple Basic NTFS Healthy P 1023 87 GB 1018 69 99 9 OSDisk C Simple
9. ING You should carefully plan a data migration Be sure to consider the cutover dates and the total amount of data being copied Back up the configuration information for accessing existing storage such as share names share permissions and so on Plan a maintenance window for the final cutover phase so that the existing data is not modified during this phase and all file locks are released INITIAL DATA COPY This operation involves copying the bulk of the data from the existing storage location to the new volume mounted on the StorSimple appliance During this operation we recommend copying older data first and then copying the recently created data This ensures that older data tiers to the lower tiers on the StorSimple appliance while retaining the most recently modified data on the SSD tier of the appliance In Robocopy use the following command Robocopy lt source gt lt destination gt COPYALL S MIR ZB MINAGE 30 R 2 W 5 MT 32 e COPYALL copy all the attributes of the files This includes data security NTFS access control lists ACLs attributes timestamps owner information and auditing information e S include subfolders e MIR mirror a directory tree this is equivalent to E plus PURGE e MINAGE 30 exclude files that are newer than 30 days e R 2 retry twice on error default is 1000000 e W 5 wait for 5 seconds before retry default is 30 e MT 32 use 32 threads default is 8 and
10. Mode Verification Mode 5 Click Ok 6 Inthe Advanced Files Search Criteria dialog box select More than 45 and Days from the drop down boxes Click Ok 13 Select Advanced File Search Criteria amp Search Files With the User Name Search Fil ccesse Search Files Created Be Searc 7 On the File Synchronization Options tab select the file sync options Enable the Preserve Directories Timestamps Be sure to enable this option before you run the initial sync operation Click Ok wv Syne File Attributes Sync User Group Security Descriptor Sync Discretionary Access Control List DACL Sync System Access Control List SACL Enable Brt Level File Synchronization Preserve Directories Timestamps Disable Buffering For Large Files Enable File Write Through 8 Save your command and execute it by right clicking in the commands pane Building a complex execution command to enable tiered file sync By right clicking on the Tiered File Sync command group you can edit the simple command that you created and add additional tasks When you right click the Edit Command Group dialog box appears 14 To build the complex command 1 Select the command and click Edit Type File Synchronization Command Tes noe 2 Adda 30 day to 45 day range by repeating the simple file sync steps but now selecting a range 3 The following illustration shows the file synchronization options before you
11. S RAE IY se eect EA N EA EAEN EE 6 FN 0 NT e E E E EE ee E EEE E EE A T A E 6 Daa tagram process W OCOD oee eo ene E ER E EE E ed td E E E E E 6 TO r a V a a E E EA EE EE EE EEEE E E E ER EA E E E E R Best practicas Tor una ROW OC Tal Ori E eaen SE E 8 Prosand cons of using OO CODY sesireisesisrieeriie serren ree ndere EENE EEE AEn PEENES EEO AE Ea ENESE EEEE ENESE Eri 9 Data migration process with DISKBOSS c ccccccccscsssessssesestessstesssessssssssssssssssssssssssssssssssssssnsisassssansssensssessssessssesssenesestsssseessensseeeeees 9 Bie eoa o E E EAE A toting E E E AE 9 Software download and compatibility oo cess esses eessstesestessstessstssesesesessissssssssnssssnssssnsssstesssesssenessstesesesseseesesneseeeeees 10 INStAIING EDILA 1O 10 Simple file SYNC cece cssecessescesesessescsseessseccesecseseessseecesescssesceseesssessesessssessessssssessessasssessesessssesseseesesessessesesesseseateseeteseetsneeteseeteneeteneeenen 11 Building a complex execution command to enable tiered file SYNC woo ccceccscssesesseseesestesestesesteseenesestesesessesteseseeseeeeees 14 Scheduled SYNC JOD creation oeceecececcccccsssesseseeseseesesesessesssssssssesssssssassssessssesssssssssansisinsssessissssssinsssasssssissnsssensssstessetesssesseensseeeeees 18 DiSKBOSS data verification oo eecececcccccsssseesessestesesssssesesssssesscscsussssssssesnssessssussssssusssssssnssessssussnssssussessssussessesisetssesissessesieeessesteeneseesen 22 Data Migration Process with dis
12. ability to run the tiered command Job at set intervals until you are ready for the final sync Depending on your network throughput latency number of files and directories and their size and activity you should carefully estimate the intervals at which you want to run the command group A good reference point would be to set the interval to 1 3 of the initial sync as you do not want to over run your network and affect user experience 18 To complete this task 1 Create a new job ae Periodic Jobs ee ee Periodic Jo Tier File Sync Jab 2 add the trigger Add Periodic Job ele Periodic Job Ti e E Commands el E e Beaute Commands Seauentaly 3 then add the job command 19 4 aa Add Periodic Job Name Type 0 Tiered File Sync Command Group Setup Periodic Job Triggers and Commands to Execute Periodic Job Triggers wf Every 5 Hours bl ES 2 Commands Description C Tiered File Sync Command Group e E amp Save and enable the job 20 a Setup Periodic Job Triggers and Commands to Execute Periodic Job Triggers lw Every 5 Hours Commands C Tiered File Sync Periodic Job Name wv Tier File Sync Job de Save the job and then run it Description Command Group Triggers Commands Last Start 1 1 NA ea E 21 DiskBoss data verification When the option to verify files after copy is selected DiskBoss calculates a hash signatu
13. ance model you have purchased For more information on the local capacity of various models refer to the StorSimple appliance datasheets There are various other third party tools available that you can use for data verification and comparison You may have to purchase or pay the license fee to use a third party tool Best practices for using Robocopy with StorSimple When you use Robocopy pay attention to the following best practices e When running Robocopy with StorSimple use the multi thread feature MT with a maximum of 32 multiple threads Robocopy supports up to 128 MT however the 32 thread recommendation is to ensure that when migrating the data to StorSimple you leave enough CPU cycles on the source appliance server for your primary dataset I Os e Use o MON n Monitor the source run again if there are more than n changes o MOT m Monitor the source run again in m minutes time if changed o Log use the different log options as needed More information on logging switches is available here o J copy using unbuffered I O recommended for large Tiles e Depending on the scenario it is best to have multiple Robocopy jobs running from different hosts and writing on StorSimple For example instead of running one Robocopy job with 32 threads run 4 different Robocopy jobs with 8 threads from separate hosts This helps improve the copy performance because you will use multiple iSCSI sessions for the copy operatio
14. cal Disk E ih Ta oe poi No Media NA w My Documents gt Network Drive Y g Disk C Be See eos SA CA Hard Disk TARGO T ano me EREN NTFS Used 20 7668 A DA CD DVD Drive Total NA Ss NA NA Used NA lakeda Om B EA Hard Disk Total 30 00 TB Astolfo Dep NTFS Used 1 64 TB PRAGAD Sialic E A YA Total 465 39 GB mean res Used 120 55 GB 344 84 GB W 59 72 MB Day ty EY ZN Total 4 00 TB 163 1868 a VSP CSV DI fo Used 3 84 TB Disk Almost Full s EJ Commands StorSimple Sync Total Space 34 65 TB Free Space 29 03 TB No Periodic Jobs No Active Tasks Simple file sync Use the following procedure to create a simple sync command enter the source and destination folders you want to migrate and add a copy of files that have not been accessed for more than 45 days To create the simple sync command 1 Click Add to add a new commana 2 Select the source and destination 11 Edit Command Group x Enter Directories to Synchronize Source Directory Sesion Cancel Click the Advanced Options button On the Advanced tab under file copy mode test both the Fault Tolerant File Copy Mode and the Operating System Native File Copy Mode with the same options DiskBoss has the following copy modes e Active File Copy Mode In this file copy mode DiskBoss automatically switches between different file copy modes depending on the size and
15. e a 4 MB and 32 threads DiskBoss will allocate 128 MB of system memory for O buffers which is acceptable for servers with enough memory However be careful not to use DiskBoss on a production server with all the memory used by other applications e The server hosting DiskBoss should have at least 256 MB of free memory for DiskBoss Ultimate and 512 MB for DiskBoss Server For more on system requirements please refer to DiskBoss help e By default file sync commands are created with the preview mode enabled which may cause some issues for customers trying to synchronize millions of files in the preview mode Consider disabling preview mode for all file sync commands for large directories With scheduled periodic jobs you might accidentally close the desktop application or log out from the server and then the DiskBoss desktop application will be closed by the operating system To use scheduled periodic jobs you need to keep the DiskBoss desktop application running or use the DiskBoss Server version which runs in the background as a service The drawback of running as a service is that many companies do not allow enough permissions for service accounts or for service accounts to have backup operator rights Software download and compatibility As this is a user generated and controlled operation you should use the appropriate version of DiskBoss We used DiskBoss Ultimate x64 in our tests and examples becauseit provides more flexibility than the s
16. ervice version and it does not require a service account with necessary rights Gaining access to such a service account can be difficult because of security and compliance policies DiskBoss Dowload Links DiskBoss Ultimate 32 Bit DiskBoss Ultimate 64 Bit DiskBoss Server 32 Bit DiskBoss Server 64 Bit Installing DiskBoss As most operating systems are 64 bit you will get better performance if you use the 64 bit version of DiskBoss You can verity this by the x64 extension after the DiskBoss version number In this case we selected DiskBoss Ultimate v5 7 14 x64 10 To install DiskBoss 1 Double click the installer The following publisher warning will appear If your organization and or company s policies allow it run the program and install the application Shut down DiskBoss and use the appropriate credentials to mount your network shares Start DiskBoss Ultimate and your shares should be visible In the example Y and Z are properly identified as network drives File View Command Bookmarks History Tools Help Register DiskBoss amp ee2 hea BBSC4 OHSESE A _ a E Smmm Search Sync Analyze Classify Duplicates Attributes Organize Cleanup Network Up Bookmark Refresh Commands SMART Tasks Jobs Database Help Le gt lt 2 Home v Computer Disk Type Space Free Status Tools Bookmarks EJ b amp Local Disk CA F e i Oe w Computer Home b amp Lo
17. k MIPPOLING ceccccccssscssssessesesssstsssstesssssssssssssssssssssssssesssssssssssssisssesssssnsssetesssessssnssssesssensseeeeseees 22 Considerations prior to Creating the disk MIPOM cccecccccsccsessesestesesesssesesessssessssesessesssssssssssssussssussssussesssestessstesssteseateseatenen 22 S NS A GIO CONIA EEEE EAA EAE 22 PIM ZUNE WT NL sett EE E see tens corse assed cet estes cade AAEE E E E ee ed aatesa estos dessa 25 ros a id CO IS of USI le disk Irrorl le Pee m mere e reer reece eereerreereereeererereereeeeeseeee reer eeeeeeeeeeeeeeeeeeeereeEeeeeeeEeeereeEereeeeererererEeeerererererererererererere efere Ices eesesooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo Introduction This document outlines different methods available for copying and synchronizing the data from existing file server volumes to volumes created on the StorSimple appliance You should plan the migration process and identify all cut over times before using any of the outlined methods Your planning process should involve choosing an appropriate data migration method after reviewing the pros and cons of each method A detailed planning guide for using File and Storage Services to migrate data is available from Microsoft TechNet httos technet microsoft com en us library jj863566 aspx Intended audience This document is intended fo
18. n A single iSCSI session has a limit of 32 queue depth e DO NOT USE the MOVE or MOV command to preserve the original copy After you have verified the contents and your users have had the opportunity to verify their data take the original copy offline for a couple of weeks and if there are no complains of missing data then you can delete the original copy Pros and cons of using Robocopy Pros Cons Enables data copy from NAS devices where data mirroring Needs extensive planning for the entire migration process is not possible Allows consolidating of data from multiple locations Data is copied over the network if a different server is used for running the file copy application tiering of old data to the cloud Cloud snapshots taken are usable and will contain all the Shares may need to be re mapped files copied till the cloud snapshot was taken Allows copying of old data first facilitating the prospering Open files cannot be copied using Robocopy Data migration process with DiskBoss Important DiskBoss is a third party utility that we use as an example in this documentation It is optional as you can use any other utility as well As with any third party utility we recommend that you read the latest version of the relevant user manual as its functionality and user interface may have changed since the user manual was initially created Should you decide to use DiskBoss as your utility you can review the DiskBoss u
19. r information technology IT professionals and knowledge workers who are responsible for operating and deploying file servers in a managed environment Migration methods This document considers the following commonly used data migration methods Other data migration methods and tools are outside the scope of this document e Disk mirroring Synchronizing data between two volumes by using RAID on the host server e File copy utilities Copying data by using file copy utilities such as Robocopy or third party applications such as DiskBoss Subsequent sections outline the detailed implementation steps as well as the pros and cons of each method Note When creating volumes on the StorSimple appliance and mounting these volumes follow the best practices defined in the StorSimple documentation Note Use of Robocopy or DiskBoss are optional and not mandatory Migrating data from a NAS A network attached storage NAS device uses a Common Internet File System CIFS or a Network File System NFS share to serve data directly to a user Vendors for NAS devices include NetApp Isilon and EMC Data Movers Migrating data from a NAS device involves copying data from the existing device to the volumes mounted on the Windows server and then routing users to the new data location This process requires extensive planning and the use of a file copy utility to migrate data followed by a cutover from the existing NAS device to the Windows server whe
20. re of the source file while the file is copied to the destination After the file transfer is completed and the destination file is closed DiskBoss reads the destination file again calculates a hash signature of the destination file and then checks if both signatures are identical On the Advanced options tab you can select one of the following hash signatures or CRC checksums e SHA 256 Signature the default the most reliable signature but requires more CPU resources e SHA 1 Signature a good enough signature requires less CPU resources e MD5 Signature a simple hash signature requires less CPU resources e CRC64 Checksum a 64 Bit cyclic redundancy check e CRC32 Checksum a 32 Bit cyclic redundancy check For multi threaded file sync operations verification is performed in parallel using a number of CPUs according to the number of configured file synchronization threads Data migration process with disk mirroring Windows Server provide disk mirroring RAID1 for volumes by using tools built into the operating system The disk mirror feature allows the synchronization of existing data in volumes disks mounted on the Windows server to be mirrored and any subsequent writes to be performed to both disks in the mirror This process allows administrators to synchronize all the data and then break the mirror to use the new volume independently Considerations prior to creating the disk mirror A disk mirror can be crea
21. re the data will be served from StorSimple volumes Migrating data from a SAN Data from a storage area network SAN is served by a host on which the SAN volume is mounted The host server commonly a Windows server uses iSCSI or Fibre Channel protocol to mount a volume from a SAN device You can use the disk mirroring option available on the server that is hosting the SAN volume to mirror the data You can also use file copy utilities to migrate data from the SAN volumes mounted on the Windows server to a different Windows server that is mounting a volume from the StorSimple appliance File copy utilities File copy and data migration utilities can be used to copy data trom existing volumes to the new volumes created on the StorSimple appliance and mounted on a Windows server Windows servers have a built in file copy utility called Robocopy installed on the system The following 2 sections use Robocopy and DiskBoss as examples to outline the steps required for migrating data from existing volumes If you use any other utilities please refer to the documentation for the utilities for best practices Each section of this paper provides Robocopy command recommendations and best practices Data migration process with Robocopy A typical data migration process involves the following steps Planning Initial data copy Incremental sync of data Final data copy and cutover ms wn gt Mapping shares applications to new storage location PLANN
22. ser manual The intent of this section is to show how to go through the process of migrating data with DiskBoss There are a few factors that are key to success when you perform a live file share migration to a share in a StorSimple volume e Minimize the down or offline time and operational burden and provide an estimated cut off window e Ensure data security and structural integrity e Migrate data by different last accessed time stamps to ensure proper tiering e Ensure that you have the ability to audit and do checksums or data verification after a file has been copied e After the migration make sure that you can cleanly uninstall the application DiskBoss facts Diskboss has the following features and limitations e Option to preserve directories timestamps for file synchronization operations e Option to disable I O buffering when transferring large Tiles e Ability to export import commands in command groups e Four different file copy modes for file copy operations e Ability to control the file verification mode for file copy operations e Performance optimization options for file copy operations by fully taking advantage of the SMB3 x capabilities e Fault tolerant file copy mode e Ability to exclude directories for file copy operations e DiskBoss allocates an aligned memory buffer for each file synchronization thread according to the configured number of threads and the buffer size For example when you configur
23. sic NTFS Healthy P 1023 87 GB 1018 69 99 a OSDisk C Simple Basic NTFS Healthy B 837 99 GB 628 61 GB 75 a StorSimpleVolume Simple Basic NTFS Healthy P 1023 87 GB 1013 69 99 Ca System Simple Basic NTFS Healthy S 350 MB 49 MB 14 L Disk 4 Basic StorSimpleVolume G 1023 88 GB 1023 87 GB NTFS Online Healthy Primary Partition Disk 5 Basic 1023 88 GB 1023 88 GB Online Unallocated L Disk 6 Basic 1023 88 GB 1023 88 GB Online Unallocated Disk 7 Dynamic Data1 l 1 97 GB 1 97 GB NTFS Online Open Explore La Disk 8 Remove Mirror Dynamic Data1 I Break Mirrored Volume 1 97 GB 1 97 GB NTFS Online pices Change Drive Letter and Paths Format Repair Volume W Unallocated J Primary partition JJ Mirrored volume EE Delete Volume Properties Help 2 Inthe Remove Mirror dialog box select the disk that you want to remove from the mirror and retain the disk from the StorSimple appliance as the primary disk Removing a miror from this volume removes one copy of the volume s data The volume will no longer contain redundant data Select a disk from which to remove a miror of Data Disks Cones Note Make sure that you select the disk that you want to remove from the mirror 3 A warning message will appear Click Yes to proceed 4 After the disk mirror is removed the new disk will be online and serving data La Disk 4 Basic
24. ted only if the disk volume to be mirrored is present on the Windows server The disk must be converted from a basic disk to a dynamic disk prior to setup of the mirror Mirroring of disks cannot be set up for any share mounted as a drive letter The existing data disk volume should be formatted as an NTFS volume Note You might not be able to use this method if the disk geometries are not the same To find out if your disk geometries align please use diskpart MSINFO32 or NTFSInfo Creating a mirrored volume The procedure in this topic allows you to create a disk mirror for continuous data availability even if one of the disks fails After the mirror is created and the synchronization between the mirrored disks is complete the data will be present on both disks 22 The following illustration shows the existing disk with labeled Data1 as it appears in the Disk Management Microsoft Management Console MMC snap in This disk will be mirrored with a new disk mounted from the StorSimple appliance To create the mirrored volume 1 Open the Disk Management MMC snap in click Start gt Run gt diskmgmt msc File Action View Help Volume Layout Type _ FileSystem Status Capacity Free Spa Free AstolfoVMS D Simple Basic Healthy P 1023 87 GB 804 03GB 79 a Data I Simple Basic Healthy P 1 97 GB g 51 GE Local 1 E Simple Basic Healthy P 1023 87 GB 94 a GE Local 2 F Simple Basic
25. the value can be between 1 and 128 e ZB use restartable mode if access is denied use backup mode We recommend that you include the retry and wait options because the files may be open during the copy operation which will result in an error The copy operation will continue by skipping the open file or the file on which it encounters an error We also recommend that you log the operation for better performance log options are not included in the above example Run Robocopy in administrator mode to ensure it has enough privileges to copy data and all attributes INCREMENTAL SYNC OF DATA This operation copies the changes made to the files after the initial copy operation is performed This will also synchronize any files that were open and not available for copying during the initial copy operation You should run an incremental sync on a regular basis to reduce the amount of data that needs to be copied during the final sync operation During the incremental sync any files that were deleted on the original data volume can be deleted on the destination so that the data remains synchronized In Robocopy use the following command Robocopy lt source gt lt destination gt COPYALL S MIR ZB R 2 W 5 MT 32 Note MINAGE 30 has been removed so that files which were created recently are included in the sync operation FINAL DATA COPY AND CUTOVER This process involves the final sync of data from existing storage to the new volume created on
Download Pdf Manuals
Related Search