Video Screencast Help

Moving Enterprise Vault to a SQL instance

Created: 17 Apr 2013 • Updated: 01 May 2013 | 4 comments
This issue has been solved. See solution.

I need to move Enterprise Vault to a new location on a SQL server cluster machine and to a SQL Server instance.  I have read the technical article 35744 which does a great job of listing the steps I need to perform.  One step is updating the Fingerprint database with the new SQL Server instance name.  The current value for the finger print SQL server is a fully qualified domain name (FQDN).  Is a FQDN required for this record field?  Everywhere else in the move process I'm just entering <server\instance>.

Thanks.

Operating Systems:

Comments 4 CommentsJump to latest comment

Marianne's picture

Moved to correct forum...

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

Rob.Wilcox's picture

I don't think it has to be an FQDN, provided all the servers involved can communicate with just the server name.

 

So I'd suggest using servername\instance, but I haven't tried it recently.

SOLUTION
Advisor's picture

Its not always necessary to have FQDN, but sometimes using host name with IP V6 enabled can cause communication issues. Its all about communication between EV and SQL, if using host name everything works fine on EV then there is no need to worry about..