How Draw Animals
How Draw Animals
Author
Suresh Elumalai
In computing, a file server is a computer attached to a network that has the primary purpose
of providing a location for shared disk access. This is a shared storage of computer files (such
as documents, sound files, photographs, movies, images, databases, etc.) that can be
accessed by the workstations that are attached to the same computer network.
Included Topics
The File Services Migration documents provide instructions on how to migrate the File
Services role, including data, shared folders, and NTFS permission from the source server to
the destination server. It includes information about the following:
Excluded Topics
Clustering migration for clustered server configurations
Migrating file allocation tables (FAT) and FAT32 file systems
Migrating encrypted files from Encrypting File System (EFS)
Migrating different platform file server (other than windows)
Audience
The intended audience for this document is:
FS File Server
GPO Group Policy Object
RDC Remote Differential Compression
SPOC Single Point of Contact
Overview:
Link Fixer Advanced, links (such as hyperlinks, Word, Excel, PDF, OLE object links, Paste-
Special links, VBA macro links, mail merge links and image links) can be automatically
repaired when files are moved or renamed.
Identify linked files on the files server (links created inside an excel file which points to
another excel file/s). The link fixer third party tool will fix this issue.
Working Procedures:
A link fixer is third party license software; it scans the folders or volumes and identifies the
list of linked files on the file server.
Once the scanning process is completed, we have to inoculate the files that have been
scanned by the link fixer using the inoculation process, mark those links and save them.
After this is process, if you move the folders to the destination server or rename the files, it
will fix the links automatically.
Note: The link fixer is required only if the server name is changed or the folders are renamed
on the new file server. The link fixer is not required if the same file server name and volumes
are retained on the new file server.
There are many file server migration approaches, but here we will discuss only about two
effective approaches
Overview
Robocopy is a utility to copy the files and folders from the source file server to the
destination file server with the same timestamp and security permissions. It is a built-in
utility of the Windows operating system. It is also simple, efficient and easy to use.
When executing robocopy for the first time, data copied for the first time is called as full
robocopy. If you execute the same script for the second time, it will copy only the changes
that have happened after the full robocopy, and are called the increment robocopy.
Incremental robocopy needs to execute every day until the cutover time.
Prerequisites:
Get appropriate access to the file server,
Confirm that you have the backup in place to save data from accidental deletion.
Identify that the file server has linked files.
The robocopy script can be executed from either the source file server or the destination file
server. Because of this, you can save 20 to 50 % of the total running time. It is also executed
from the client machines (Windows XP or Windows 7) if the bandwidth is very good.
ROBOCOPY Command:
Sample Syntax:
Where:
Swith Description
source driver path (should be mapped in
G:\
Destination)
H:\ destination drive path (local drive)
/E copy subdirectories, including empty ones
/COPYALL Copy all file info (equivalent to /COPY:DATSOU).
MIRROR a directory tree (equivalent to /E plus
/MIR
/PURGE).
Number of retries on failed copies: default 1
/R:n
million (we set here as 2)
Wait time between retries: default is 30
/W:n
seconds(we set here as 2)
/Z Copy files in restartable mode.
/DCOPY:T COPY directory timestamps.
/log+:G:\vol2\TMF_FS_log_10April2013 Log file folder path
.txt
/TEE Output to console window, as well as the log file.
/NP No Progress - don't display percentage copied.
Similarly, create a script for all the volumes or folders as per the requirement, save the file as
a .bat extension and execute it when needed.
1. Click Start, point to Administrative Tools, and then click Server Manager.
2. In Roles Summary, click Add Roles.
3. In the Add Roles Wizard, on the Before You Begin page, click Next.
4. On the Select Server Roles page, select File Services, and then click Next.
5. On the File Services page, click Next.
6. On the Select Role Services page, in Role Services, ensure that File Server is selected,
then click Next.
7. On the Confirm Installation Selections page, confirm your selections, and then
click Install.
8. On the Installation Results page, confirm that your installation of the File Services role
and the required role services are completed successfully, and then click Close.
Copy date from source File Server to the Destination File Server:
Pre-check List:
Cross verify the script before you start the robocopy
Make sure that the source and destination paths are mentioned correctly in the
script.
Make sure that all the source folders are accessible
Make sure that the drives are mapped correctly as mentioned in the script.
Make sure that the log file location is accessible
Double click the written script .bat file to start the robocopy. The data copy progress shows
as follows:
Copy only 500 MB of data from source to destination (pilot test). After the completion of
robocopy, you can see the report as follows. Using this, we can calculate the speed and
approximate completion time.
10
Length files and folder path (Folder paths must be less than 248 characters and fully
qualified file names must be less than 260 characters)
Special characters which are not identified by the robocopy
Files which were open during the robocopy
Digital signature PDF files
Incremental Robocopy:
Run the same robocopy script for every day and verify the logs. The incremental robocopy
script can be automated using schedule task, but it is risky. For example, while running this
script, if the drive is mapped incorrectly with a different path, then the data will be copied
incorrectly to the other location, and there will be data loss.
It is recommended to run the incremental robocopy manually, change the log file name with
respect to date (e.g. volume1_01_july_2013.txt).
11
12
The performance of your source server can be affected during the data migration. This can
result in slower access to files that are stored on the server.
The robocopy script should be written with extra caution. Interchanging the source and
destination paths will lead to data loss.
Permission Requirement
For Robocopy, users who start the migration must be a member of the local administrator of the
source and destination servers.
Make sure you have appropriate access to do the file server migration.
Estimated Duration:
The time required to complete the migration depends upon the total size of the data to be migrated
and the network speed.
Monitor that the file server daily backup is running successfully. The backup will protect against any
accidental deletion of data.
Identify linked files on the files server (like links created inside an excel file that is pointing to another
excel file).
In Robocopy, make sure that the source and destination paths are mentioned correctly.
13
Team work, pre planning, proactive thinking, excellent understanding of technologies, and enormous
confidence bring us successful file server migration with zero escalations.
14