Difference between revisions of "Copying Large Files"
Jump to navigation
Jump to search
(New page: == Overview == You need to copy a very large file - at least in the gigabyte, often hundreds of gigabytes range. You are finding that it is slow (mb/sec) or fails. == Option 1 == Use Es...) |
|||
| Line 1: | Line 1: | ||
== Overview == | == Overview == | ||
You need to copy a very large file - at least in the gigabyte, often hundreds of gigabytes range. You are finding that it is slow (mb/sec) or fails. | You need to copy a very large file - at least in the gigabyte, often hundreds of gigabytes range. You are finding that it is slow (mb/sec) or fails. | ||
| + | |||
| + | This is often encountered when copying the EHR database (e.g. the Works DB for Allscripts) file, especially over a network. | ||
Revision as of 06:56, 14 March 2009
Overview
You need to copy a very large file - at least in the gigabyte, often hundreds of gigabytes range. You are finding that it is slow (mb/sec) or fails.
This is often encountered when copying the EHR database (e.g. the Works DB for Allscripts) file, especially over a network.
Option 1
Use Eseutil. This is the solution recommended by Microsoft - technically, the Enterprise Platforms Support Windows Server Performance team. You can check out the article here.
It is a command-line program. The usage for file copies is: eseutil /y <srcfile> /d <destfile>
Option 2
A client of Galen's has used CLF with success.