Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

FileServerEntry table DNS Name for one target file server

Created: 20 Dec 2012 • Updated: 20 Dec 2012 | 5 comments
This issue has been solved. See solution.

Hi,

We have issues with reporting saying that unable to resolve file server FQDN. Looking at FileServerEntry table looks like all server has FQDN in DnsName aaprt from that one server which has only short name under DnsName column.

Can we edit that manually and change it to FQDN from short name? Or changing it there will have other consequences?

Many Thanks

Comments 5 CommentsJump to latest comment

JesusWept3's picture

I guess the question before editing it is why does the FQDN not work in the first place?

Jeff Shotton's picture

The path in the archivefolder table may also be stored using the short name, but a Sync will take care of that if needed and the paths exist.

Here's the technote for what needs to be done if the fileserver changes to a different domain (and the path/name changes)

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

You *may* have a couple of orphaned paths you need to change.FSAUtility can throw a fit if data is wrong in the archivefolder table.

Regards,

Jeff

Jeff Shotton

Principal Consultant

Adept-tec Ltd

Website: here

SOLUTION
ia01's picture

Hi Jeff,

I have updated FileServerEntry to FQDN but the Folder path in ArchiveFOlder table is still showing ShortName. Do we have to modify that as well? Any easy way to do this using SQL statement as there are thousands of folders.

Many Thanks

Jeff Shotton's picture

as I said...a synch of the filesystem will update the path unless the path is orphaned (i.e folder deleted)

Yes, you can do a replace statement on all the columns at once, but im not going to post that openly on the forums.

Plus you should make sure you have a valid backup before making such a change.

Regards,

Jeff

Jeff Shotton

Principal Consultant

Adept-tec Ltd

Website: here