UPDATE! The community will be go into read-only on April 19, 8am Pacific in preparation for migration on April 21. Read more.
UPDATE! The community will be go into read-only on April 19, 8am Pacific in preparation for migration on April 21.Read more.

Support for more than one Exchange 2016 database on a single native MS drive or NTFS mount

Idea ID 2859535

Support for more than one Exchange 2016 database on a single native MS drive or NTFS mount

0 Votes

For what reason ever for our new Exchange environment our Exchange Admin team had reduced the number of volumes, increased their size, and had instead configured two databases  and their log files per NTFS mount. (16 databases in 8 NTFS mounts on each DAG node of a total of 48 databases in the DAG).

But Data Protoector doesn't support this. Only one VSS Agents starts per volume.  So it is being accessed twice with the same Volume GUID on VSS. VSS returns with  error VSS_E_OBJECT_ALREADY_EXISTS. So only one of the two database ist backed up.

A change of the running Exchange environment is not a solution for our Exchange Admin team!

My workaround are two specifications for each DAG node: one for all first databases of all volumes, and a second for all second databases of all volumes.

My idea is, that Micro Focus investigates with Microsoft  if such configuration is common for Exchange installations (that not backed up with Data Protoector).
In this case should Data Protector support  such configuration.

Maybe with one VSS Agent per database instead per Volume ...?

 

2 Comments
Micro Focus Expert
Micro Focus Expert
Status changed to: Needs Clarification

@paulsupport 

Are you using the Exchange Integration Agent or VSS File System Integration? 

Please also provide more info about the DP Version, platforms etc ...

Lieutenant
Lieutenant

DP MS Exchange 2010+ Integration Agent, which includes MS Volume Shadow Copy Integration.

Exchange 2016 @ Windows Server 2016 physical Nodes with external Volumes on HPE 3PAR 

DP 10.50 aka 2019.08 @ RHEL 7.9  on a VM

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.