|
[x]
Posted via EE Mobile
|
|
| Search, ask, and monitor your questions on the go with EE Mobile. Visit Experts Exchange from your mobile device and never be out of touch again. |
|
|
|
|
|
[x]
The Solution Rating System
|
|
| With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating. - The Grade of the Solution
- The Zone Rank of the Expert Providing the Solution
- The Number of Author and Expert Comments
- The Number of Experts Contributing
- The Feedback of the Community
Your Input Matters Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site. If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support. Thank you! |
|
|
|
|
Asked by unitam in CommVault, Backup & Restore Software
I'm looking to discern exactly what is required to fully recover a server from a hardware failure. The commvault documentation is somewhat ambiguous. I want to better understand the full system backup/recovery process and discover any problems in the configuration of my backup policy.
Background:
Commvault v7.0.0 sp4
Does a System state sub client require a full file system state backup in order to completely recover a server? Is it pointless running a system state without a corresponding full file system with no exceptions?
Example:
Lets say I wanted to recover a Windows Server 2003 R2 machine that is acting as file / print server. Both file system and system state backups are executed as part of the default backup set/default subclient. Only a selective file system copy is executed, namely directories that contain user data. I.e directories like c:\windows and c:\program files are not backed up even though various programs do run out of these directories. Dell management applications, monitoring agents etc
Is the server fully recoverable without the whole file system backed up?
What data does the system state backup collect exactly?
Is there any way of reducing the amount of data that is backed up off my servers without affecting the ability to run a full system state restore?
20091021-EE-VQP-81 - Hierarchy / EE_QW_3_20080625