Changing the name of the SQL server used by Enterprise Vault.

Article:TECH136318  |  Created: 2010-01-11  |  Updated: 2013-04-12  |  Article URL http://www.symantec.com/docs/TECH136318
Article Type
Technical Solution


Issue



Changing the name of the SQL server used by Enterprise Vault.


Solution



Sometimes it is necessary to change the name used by Enterprise Vault to connect to SQL.  Reasons for doing so may be:
 
1) The databases for Enterprise Vault are being moved to another SQL server.
2) The name used by Enterprise Vault to refer to SQL is a short name and it is desired to make this a Fully Qualified Domain Name (FQDN).
3) Backup Exec cannot resolve the DNS alias (DNS CNAME record) that Enterprise Vault uses to connect to the SQL server or SQL cluster.
4) The organization is undergoing a domain name change.

Each of the above examples makes changes in the way DNS is either configured or used.  For each case above, see the following table for a summary of methods that can be used to make changes.

 
Case (see above list) Change What changes What is affected
1 See all steps in TN136318 SQL server hosting the Enterprise Vault databases, new DNS entry/entries, registry key on the Enterprise Vault server Multiple SQL servers, Enterprise Vault, Backup Exec Remote Agent for Windows
2 Perform steps in TN136318 except step 1 (the SQL server isn't changing, so it is unnecessary to migrate data off of it for this process) Registry key on the Enterprise Vault server, database entries in EnterpriseVaultDirectory database referring to the Enterprise Vault Vault Store databases Enterprise Vault, Backup Exec Remote Agent for Windows
3 Perform steps in TN136318 except step 1 (the SQL server isn't changing, so it is unnecessary to migrate data off of it for this process) Registry key on the Enterprise Vault server, database entries in EnterpriseVaultDirectory database referring to the Enterprise Vault Vault Store databases Enterprise Vault, Backup Exec Remote Agent for Windows
4 See below See below See below


The procedures below details the above changes and points to keep in mind during the change.

The databases for Enterprise Vault are being moved to another SQL server

The document How to move an Enterprise Vault (EV) SQL directory and store databases from one SQL server to another. linked in TN136318 in the Related Documents section was written to describe how to perform this migration.  Some additional points to keep in mind while considering this migration:
 
· Components affected:
o Enterprise Vault servers,
o SQL server hosting the EnterpriseVaultDirectory database,
o SQL server(s) hosting the Enterprise Vault Vault store databases,
o Backup Exec Remote Agent for Windows on each Enterprise Vault server,
o Microsoft Cluster services running on any system,
o DNS (whether provided by Active Directory or outside of Active Directory or both).
 
· Restrictions:
o Enterprise Vault servers need to be able to reach the appropriate SQL server that hosts the databases it is seeking.
o Backup Exec Remote Agent for Windows currently does not support backing up SQL servers when they are referred to by a DNS alias (DNS CNAME record).
o Generally, the Microsoft Cluster name for a cluster is different than the names of any given node in that cluster.  A DNS A record or another DNS A record can be assigned in DNS to the Microsoft Cluster name for purposes of Enterprise Vault while retaining failover capability (the DNS A record will resolve to the cluster IP resource, which is used by whichever node is currently active).
o Good DNS configuration allows CNAME records to refer only to A records and not to another CNAME record (CNAME -> A not CNAME -> CNAME -> ... -> A)
o Enterprise Vault services should not be running when changes to its databases are being made.  It is acceptable, while moving a single Enterprise Vault Vault store or updating its SQL references to disable only the associated Enterprise Vault Storage service.

The name used by Enterprise Vault to refer to SQL is a short name and it is desired to make this a Fully Qualified Domain Name (FQDN)

The document How to move an Enterprise Vault (EV) SQL directory and store databases from one SQL server to another. linked in TN136318 in the Related Documents section can be used to perform these steps, but that document assumes a migration from one SQL server to another SQL server.  If this is indeed the case, see the section above for additional guidance on this process.

Step 1 of that document describes the move of the databases from one server to another and Steps 2 through the end of the document describe remaining changes to make Enterprise Vault aware of these changes.  Some additional points to keep in mind while considering this change:
 
· Components affected:
o Enterprise Vault servers,
o Backup Exec Remote Agent for Windows on each Enterprise Vault server,
o Microsoft Cluster services running on any system,
o DNS (whether provided by Active Directory or outside of Active Directory or both).
 
· Restrictions:
o Enterprise Vault servers need to be able to reach the appropriate SQL server that hosts the databases it is seeking.
o Backup Exec Remote Agent for Windows currently does not support backing up SQL servers when they are referred to by a DNS alias (DNS CNAME record).   When changing the name from the short name to the FQDN, use a DNS A record instead of a DNS CNAME record.  For the latest information about capabilities of Backup Exec Remote Agent for Windows and resolution of names in connection with backing up Enterprise Vault resources, see TN317561 in the Related Documents section.
o Generally, the Microsoft Cluster name for a cluster is different than the names of any given node in that cluster.  A DNS A record or another DNS A record can be assigned in DNS to the Microsoft Cluster name for purposes of Enterprise Vault while retaining failover capability (the DNS A record will resolve to the cluster IP resource, which is used by whichever node is currently active).
o Good DNS configuration allows CNAME records to refer only to A records and not to another CNAME record (CNAME -> A not CNAME -> CNAME -> ... -> A)
o Enterprise Vault services should not be running when changes to its databases are being made.  It is acceptable, while moving a single Enterprise Vault Vault store or updating its SQL references to disable only the associated Enterprise Vault Storage service.

Backup Exec cannot resolve the DNS alias (DNS CNAME record) that Enterprise Vault uses to connect to the SQL server or SQL cluster

There are multiple approaches to resolve this issue.  The first, and easiest method is to simply change the CNAME in DNS to be an A record.  Steps for how to do this in Windows DNS are summarized as follows (assumed name for the SQL server is 'sql.domain.local'):
 
1) Stop all Enterprise Vault services on all Enterprise Vault servers.
2) Open DNS management console for the domain 'domain.local',
3) Expand 'Forward Lookup Zones'.
4) Click on 'domain.local'.
5) Verify that the 'sql' record is type 'Alias (CNAME)'.
6) Record the IP address associated with the target record.
7) Delete the 'sql' record.
8) Create a new 'A' record here as follows:
o In the 'Name:' field type 'sql'.
o In the 'IP Address' field type the IP address recorded in step 6.
o Leave 'Create associated pointer (PTR) record' unchecked.

The other approach to resolving this issue is to alter the name that is used be Enterprise Vault, ensuring that the new name that is specified is an A record.  These steps are outlined in the previous procedure 'The name used by Enterprise Vault to refer to SQL is a short name and it is desired to make this a Fully Qualified Domain Name (FQDN)'.

The organization is undergoing a domain name change

If the organization is undergoing a domain name change, it is important to know what needs to be updated and where there are possible dependencies on old domain name information.  As the previous several procedures have discussed, all the steps except for step 1 in TN136318 can be used to perform the update of the SQL name that Enterprise Vault uses.  Choosing an A record for the new SQL server provides for maximum benefit.

Outside of changing the DNS name(s) that Enterprise Vault use(s) to contact the SQL server, the Enterprise Vault server(s), storage servers, domain membership, and other resources may also need to be updated.  These changes are outside the scope of this document, but the following documents may provide a starting point for guidance on some of these changes:

How to Update Service Locations (USL) after changing server name or DNS alias for Enterprise Vault (EV).
http://www.symantec.com/docs/TECH52747

Symantec Enterprise Vault Outlook Web Access (OWA) Internal and External WebApp URLs.
http://www.symantec.com/docs/TECH63250

How to change the Enterprise Vault Web Application URL in Enterprise Vault 8.0.
http://www.symantec.com/docs/TECH70238
 
NetBackup Enterprise Vault Agent support using a "SQL alias" or "DNS alias" for the directory database.
 http://www.symantec.com/docs/TECH130581

How to decommission an Exchange Server from Symantec Enterprise Vault (EV).
http://www.symantec.com/docs/TECH50256  

Changing the name of the SQL server used by Enterprise Vault
http://www.symantec.com/docs/TECH136318

 




Legacy ID



355475


Article URL http://www.symantec.com/docs/TECH136318


Terms of use for this information are found in Legal Notices