- Community Home
- >
- Storage
- >
- HPE Nimble Storage
- >
- Application Integration
- >
- Exchange 2010 SnapShots
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-07-2013 02:47 PM
10-07-2013 02:47 PM
Per Nimble's Exchange 2010 best practice I am presenting database and log storage to my exchange server via the guest iSCSI software initiator. I will put the database and log volumes in a collection and snapshot using Microsoft VSS synchronization. The Windows operating system disk will be presented through vmware on a vmfs5 volume.
My question is should I snapshot the db, logs and os disks at the same time? If I need to recover to a point in time shouldn't the os disks be from the same time the db and logs were snapshot or does it not matter? I can't put these in the same collection because of the synchronization conflict (Microsoft VSS vs. Vmware vCenter). I was thinking of lagging the OS snapshot 5 minutes behind the db/logs snapshot.
Also - do I need to use any synchronization when snap shotting a Windows OS vmdk that has Exchange installed bearing in mind that the logs and databases are in a different collections and use synchronization.
Thanks.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-07-2013 08:30 PM
10-07-2013 08:30 PM
SolutionBryan,
I don't see any issues with this approach particularly if you are doing a snapshot just 5 minutes prior to the VSS sync'd snapshot of the Exchange volumes.
As a best practice, I typically configure any VMFS datastore volume with vCenter synchronized snapshots. You can probably get away with no-synchronization for a VMFS datastore volume with OS drives but I like knowing that with vCenter sync'd snapshots that I'm getting a mountable RPO that is VMware consistent.
Hope this helps.
Eddie
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-10-2013 09:13 AM
10-10-2013 09:13 AM
Re: Exchange 2010 SnapShots
Bryan,
You're question:
Bryan Rogers wrote:
My question is should I snapshot the db, logs and os disks at the same time?
Also - do I need to use any synchronization when snap shotting a Windows OS vmdk that has Exchange installed bearing in mind that the logs and databases are in a different collections and use synchronization.
The answer to both is no. You do not need or want the os in the same collection as the db and logs.