How to Take backup of Exchange 2013 IP less DAG

[Priteshp]

Hi,

Please let me know how to configure the backup for exchange 2013 DAG where there is no virtual interface face or the ip address for the DAG name. in this senario what will be my client selection and backup selacti in policy?

Netbackup version 7.6.0.3

OS RHEL 6.5

Exchange 2013

OS Windows 2012 R2

Netbackup 7.6.0.3 clients are installed on all exchange mailbox server

if we configure the individual mailbox server as a client and respective DBs in backup selection which that client holds, it works fine.

how do I protect Exchange 2013 where the DAG has no virtual IP?  

[RiaanBadenhorst]

Please explain the reason for this, is this new in 2013?

[Priteshp]

Yes IP less DAG is new feature in Exchange 2013.

[V4]

http://www.symantec.com/docs/TECH223843

Check this

[V4]

IP less DAG was introduced in Exchange 2013 SP1

http://msexchangeguru.com/2014/08/25/impossible-to-convert-dag/

Also check this

http://www.symantec.com/docs/TECH218366

[Priteshp]

Hi Captain Jack Sparrow,

We have gone through the following technote

http://www.symantec.com/docs/TECH223843

but in this case how my reverse lookup will work?.

we tried that way but backup snapshot fails with error status 2

[RiaanBadenhorst]

Why don't you just make a CNAME alias for the DAG? Then reverse lookup will work.

[RiaanBadenhorst · Accepted solution]

http://technet.microsoft.com/en-us/library/dd979799%28v=exchg.150%29.aspx

So you should really be using a administrative access point.

For DAGs with cluster administrative access points, Windows failover clustering registers the IP addresses for the cluster in the Domain Name System (DNS) when the Network Name resource is brought online. In addition, when EX1 is added to the cluster, a cluster name object (CNO) is created in Active Directory. The network name, IP address(es), and CNO for the cluster are not used for DAG functions. Administrators and end users don't need to interface with or connect to the cluster/DAG name or IP address for any reason. Some third party applications connect to the cluster administrative access point to perform management tasks, such as backup or monitoring. If you do not use any third party applications that require a cluster administrative access point, and your DAG is running Exchange 2013 SP1 or later on Windows Server 2012 R2, then we recommend creating a DAG without an administrative access point. This simplifies DAG configuration, eliminates the need for one or more IP addresses, and reduces the attack surface of a DAG.