Article ID: 329701
Article Last Modified on 10/25/2007
APPLIES TO
- Microsoft Exchange 2000 Server Standard Edition
- Microsoft Exchange Server 2003 Enterprise Edition
- Microsoft Exchange Server 2003 Standard Edition
This article was previously published under Q329701
SUMMARY
The dynamic disk management functionality in Microsoft Windows 2000 Server and in Microsoft Windows Server 2003 is based on technology licensed to Microsoft by Symantec Corporation. VERITAS Storage Foundation for Windows, formerly named Volume Manager for Windows, provides additional dynamic disk management and replication functionality above that available in the default Windows dynamic disk management services.
If you install VERITAS Storage Foundation or Volume Manager, then Symantec, rather than Microsoft, becomes responsible for support of dynamic disks, and Microsoft will continue to support other aspects of the Exchange system.
MORE INFORMATION
What is VERITAS Storage Foundation?
The dynamic disk management drivers included with Windows are based on technology licensed from Symantec Corporation. VERITAS Storage Foundation provides extended versions of those drivers and provides additional disk management features, including:
- Support for dynamic disks with Windows clustering. (Native Windows drivers support only basic disks in clusters.)
- Snapshot backup of disks.
- Transferring disk ownership between systems.
- Dynamic reconfiguration of online storage.
- Replication of disks between servers.
Does Exchange work with VERITAS Storage Foundation?
Exchange databases can be stored on disks managed by VERITAS Storage Foundation, and Symantec states that Exchange databases will function normally in both clustered and non-clustered environments.
There are many Exchange servers running today on platforms that use VERITAS Storage Foundation. However, Microsoft has not performed in-depth testing of Exchange on disks managed by VERITAS Storage Foundation. Therefore, VERITAS Storage Foundation is not supported by Microsoft, but is supported by Symantec.
If VERITAS Storage Foundation works with Exchange, then why isn’t it supported?
It is supported, but by Symantec, rather than by Microsoft.
VERITAS Storage Foundation replaces core Windows disk management services with a proprietary Symantec solution. The result is a solution that is in part supported by Microsoft and in part supported by Symantec.
To be very clear: Microsoft will provide support for Exchange issues if you run Exchange on a Veritas Storage Foundation platform. However, Microsoft will only troubleshoot and attempt to resolve Exchange-specific issues up to the point that the source of the problem can be reasonably attributed to an issue or incompatibility with Symantec software. This same principle also applies to other third-party products.
Doesn’t the term “unsupported” imply “not recommended”?
Many Exchange customers are made uneasy by the word “unsupported” for a very good reason: they have been refused support by a vendor simply because of the presence of an unsupported component, and this in advance of any determination that the unsupported component has anything to do with the problem.
Microsoft will not require you to remove Symantec software or other third-party products as a precondition of providing support, unless there is a reasonable basis for doing so and less disruptive troubleshooting efforts have not been effective. If neither Microsoft nor Symantec are able to resolve a particular storage-related problem, it may be necessary to remove Symantec components from the system and revert to a fully Microsoft-supported platform. This follows the usual troubleshooting procedures of “last resort.”
What do you mean by a "fully Microsoft-supported platform"?
A fully Microsoft-supported Windows installation is one that uses only Microsoft-provided software drivers and services. In addition, for Exchange, a fully Microsoft-supported platform uses only native Exchange services and components.
When running Exchange in a fully Microsoft-supported configuration, Microsoft has the ability to fully debug and isolate problems. But if third-party components are involved, Microsoft may not be able to fully troubleshoot or resolve an issue.
Microsoft does not typically have access to source code or other proprietary information that may be necessary to resolve some issues with a third-party component. Resolution of some issues may require a change to the design or code of a third-party product, or require that customers reconfigure the product. Customers must rely on the vendor rather than on Microsoft for support and resolution of such issues.
So how do I determine whether a problem is the responsibility of a third-party vendor or of Microsoft?
In some cases, it will be obvious that a problem is the responsibility of one vendor or the other. In other cases, it will not be so clear.
When there is difficulty establishing the root cause of the problem, a very effective strategy is to involve troubleshooting teams from all parties involved.
Can Microsoft Product Support Services (PSS) directly involve Symantec or other third-party vendors in the troubleshooting process?
The customer, not PSS, is primarily responsible for involving a third-party vendor's support organization. PSS is happy to work with other support organizations in resolving customer issues, but should not be considered the primary liaison between customers and third-party vendors.
Every Exchange solution will, necessarily, be a multi-vendor solution. Microsoft strongly recommends that customers develop support relationships with each vendor involved in the end-to-end solution.
Is there a certification program for third-party products with Exchange?
At this time, there is not.
The feasibility of an Exchange certification program similar to the Windows programs has been considered. Microsoft has no current plans for such a program. Microsoft provides extensive guidance and tools for designing Exchange systems and testing their capabilities. For more information, please visit the following Exchange Web site:
Microsoft does recommend that you run Exchange on hardware platforms that have passed Windows Hardware Quality Labs (WHQL) qualification tests and with software that has passed Certified for Windows testing. Passing these tests indicates that the platform meets a baseline definition of features and quality goals for compatibility with Windows.
You can learn more about WHQL testing and the Windows Logo program at the following Web site:
VERITAS Storage Foundation for Windows and Volume Manager have both passed Certified for Windows testing by VeriTest. VeriTest is an independent testing company that tests third-party products for Microsoft’s Certified for Windows program.
The Certified for Windows logo attests that a product meets certain published criteria and has passed rigorous tests for availability, reliability, security and supportability in a Windows server environment. The Certified for Windows program does not certify products for a specific use or application (such as Exchange).
Obtaining Microsoft certification for a hardware or software product does not imply that support of that product thereby becomes the obligation of Microsoft. Certification and support are separate issues that are often confused.
Microsoft publishes detailed certification specifications and requirements. Certification attests that a product has in fact met those specifications and requirements. Support for certified products remains the responsibility of each vendor, regardless of certification status.
The Certified for Windows program also defines a Supported for Windows classification. To be on the Supported for Windows list, a vendor does not have to submit products for testing, but instead promises to provide technical support for the product.
You can learn more about the Certified for Windows program at the following Web site:
Detailed reports on the exact testing done with each Symantec product on each edition of Windows are available at the VeriTest web site:
For information about how to contact Symantec Software, visit the following Symantec Software product support site:
Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.
The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication.
This document is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS DOCUMENT.
Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in, or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.
Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.
2004 Microsoft Corporation. All rights reserved.
Microsoft and Windows are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. The names of actual companies and products mentioned herein may be the trademarks of their respective owners.
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.
Additional query words: XADM veritas cluster
Keywords: kbinfo KB329701
