Conversely, a restore process implies a write operation. Because data is usually being written to a file system during a restore operation, it involves some file system overhead such as creating an entry in a file allocation table or journal, permission setting, ACL and various other file attributes being recorded. This obviously takes more system cycles and ends up being much slower than a simple backup (read) operation.
Some file systems are better than others are at this and a significant restore performance difference can be noted. However, generally speaking, the worst possible restore performance will be observed when restoring a large number (millions) of small files. In comparison, restoring a 500 GB database will be dramatically faster that restoring a 500 GB file server.
Dig Deeper on Data storage strategy
Related Q&A from Pierre Dorion
With some limitations, Federal Continuity Directives 1 and 2 can be used to help conduct a business impact assessment. Continue Reading
Find out what business impact assessment errors you can most easily identify in this Expert Response from Pierre Dorion. Continue Reading
Pierre Dorion highlights some of the business impact analysis tools available to help companies in this Expert Response. Continue Reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.