Shadow Copy Exchange?

I am running Exch2010 Ent on a 2008 R2 Ent Server.

Does it make sense to have shadow copies of the hard drive that is dedicated to Exchange databases?  I doubt that you would ever restore exchange from a shadow copy, but I am interested in recommended best practice.

Would you ever use the Shadow copy for anything?

Do you recommend disabling shadow copy on that drive?

Any other recommednations??

Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

AkhaterConnect With a Mentor Commented:
again you don't need it you can disactivate it it will not affect the backup of exchange, I have never enabled it on any exchange server
AmitIT ArchitectCommented:
Exchange 2010 support VSS only. What Backup tool are you using currently?
ArchitectChuckAuthor Commented:
I am using both Wbadmin and Backup Exec 2010 R2 to backup Exchange
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

AmitIT ArchitectCommented:
I recommend you to give a check with vendor once. If I understand your issue correctly, you want to disable the shadow copy from Disk property, in order to save disk space. I don't see in disabling it. This saves the disk space.
disk shadows copies are not required for exchange 2010, disable them
ArchitectChuckAuthor Commented:
I should have been more clear.  I have plenty of disk space.  

My question is, if shadow copy is never used, why leave it activated?  It seems to be a waste of resources.  My thought is, keep it simple.

If I dectivate shadow copies, does it have any impact on VSS or the time required to backup Exchange?
Adam RayCommented:
for future readers... I remember a reading (I *think* it was in the MS SBS 2011 docs) that Shadow Copies [for shared folders] should NOT be enabled on an volume with the exchange databases for reasons other than just the performance hit. -- But take that with a grain of salt, I'm having trouble finding it again

I infered from this that it would be perferrable not to have Shadow Copies enable on any volume with a database. E.G. MSSQL. That files with constant access are best not snapped during high load times due to the quiet time needed may lead to I/O errors/timeouts. But maybe that is reading too much into it.

Note: Diabling Shadow Copies [for shared folders] via the vssuirun utility should not affect VSS from creating snapshots for regular backups using Windows Server Backup or some third party backup.
All Courses

From novice to tech pro — start learning today.