- Community Home
- >
- Storage
- >
- HPE Nimble Storage
- >
- Array Performance and Data Protection
- >
- Re: Exchange 2010
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
Discussions
Discussions
Forums
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
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
тАО08-18-2017 03:40 PM
тАО08-18-2017 03:40 PM
Hello,
We currently have an Exchange 2010 on-premises on a physical server. I recently created 2 volumes (data/logs) on out nimble and connected over iSCSI to our Exchange box. The drives are working great. What I need help with is getting the logs on the new drive truncated when we take a snapshot of the database drive.
I've tried this:
Nimble OS Part 11: Exchange Snapshot Log Truncation / Verification , but no go. When I try to force a snapshot i get the following error:
Message: Failed to snapshot volumes associated with volume collection MY-VOLUME schedule SCHEDULE-Daily, Invalid response status: 4. VSS snapshot creation failed. Error: Protection set does not contain all the volumes required to take application consistent snapshot. Check the protection set configuration.
Help!
Thanks,
Kevin
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-18-2017 04:12 PM
тАО08-18-2017 04:12 PM
Re: Exchange 2010
Hello Kevin,
Have you followed the steps required to set up application consistent (VSS) snapshots? You will need to have the Nimble Windows toolkit installed on the Exchange Server, and both volumes must be in a volume collection, with the Exchange server information populated in the Application Server setting. As you are not running a DAG, you would select Exchange Server as your application, and you must make sure that verification is selected for the Exchange database. Truncation will occur after verification.
Dianne
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-18-2017 04:26 PM
тАО08-18-2017 04:26 PM
Re: Exchange 2010
Hey Dianne,
Are there more steps to setting up VSS other than whats in the guide I posted above?
Kevin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-18-2017 04:39 PM
тАО08-18-2017 04:39 PM
SolutionHello Kevin,
The Nimble Connect blog post covers how to set up a volume collection for a DAG environment, but for a complete guide to our Exchange setup, refer to the Deployment Considerations Guide for Exchange, available on Infosight.
A summary of the steps you will need to follow (I am skipping steps for LUN connectivity, focusing on the application integration):
1- Install NWT on the Exchange host.
2- Configure the Volume Collection on the array. All volumes must be part of the protection set.
3- Verify the volume collection.
4- If verification is successful, create a Snapshot collection (execute a snapshot of the volume collection), or wait until the volume collection schedule executes.
The error you are receiving is indicative of either a problem with your volume collection setup, or Exchange database and log files are not on the volumes specified in the volume collection, causing VSS to error out.
Dianne
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-21-2017 08:08 AM
тАО08-21-2017 08:08 AM
Re: Exchange 2010
Yay! It works!
Thank you!