FSAUtility returns the error "File Server [ServerName] not found in EV database"
Article ID: 100001611
Updated On:
Description
Error Message
A sample Dtrace of the FSAUtility process shows the following:
(FSAUtility) <11816> EV-H {MOVEPLACEHOLDERNORMAL.EN_US} Exception: File Server \\server02 not found in EV database Info: Diag: Type:KVS.EnterpriseVault.FSARestore.MovePlaceholderException ST: at KVS.EnterpriseVault.FSARestore.MovePlaceHolder.LoadFileServerVolume()| at KVS.EnterpriseVault.FSARestore.MovePlaceHolderNormal.Process()
(FSAUtility) <7528> EV-H {FSARESTORE.EN_US} KVS.EnterpriseVault.FSARestore.MovePlaceholderException: File Server \\server02 not found in EV database| at KVS.EnterpriseVault.FSARestoreCLI.FsaRestore.DisplayStatus(DataMoverBase serverInstance, Boolean resume, Boolean isReportMode)| at KVS.EnterpriseVault.FSARestoreCLI.FsaRestore.Main(String[] args)
Cause
This can be caused by an incorrect value in the FileServerEntry table. FSAUtility assumes that the DnsName values for the source and destination servers have the same format. If one is the Fully Qualified Domain Name (FQDN) and the other is a simple hostname, it cannot resolve the difference and throws this error.
Resolution
To work around the issue, do one of the following:
The entry in the SQL table should be changed to read:
Solution 2: Modify the name in the command to match the name in the database.
Figure 3
Note: It is recommended to follow the instructions in the wizard and enter the FQDN of the target file server. This will minimize the risk of problems related to DnsName mismatch in the future.
1. Modify the name in the database to match the name in the command.
2. Modify the name in the command to match the name in the database.
Solution 1: Modify the name in the database to match the name in the command.
1. Open SQL Server Management Studio and view the FileServerEntry table from the EnterpriseVaultDirectory database.
2. Locate the value in the DnsName field for the server listed in the error.
3. Amend it to contain the FQDN for the server.
2. Locate the value in the DnsName field for the server listed in the error.
3. Amend it to contain the FQDN for the server.
Example of Solution 1
fsautility -m -s \\server01\oldfolder -d \\server02\newfolder gives the error "File Server \\server02 not found in EV database."
The SQL table shows the following:
| DnsName | UncName |
|---|---|
| server01.example.local | \\server01 |
| SERVER02 | \\server02 |
The entry in the SQL table should be changed to read:
| DnsName | UncName |
|---|---|
| server01.example.local | \\server01 |
| server02.example.local | \\server02 |
Solution 2: Modify the name in the command to match the name in the database.
1. Open SQL Server Management Studio and view the FileServerEntry table from the EnterpriseVaultDirectory database.
2. Note the format (FQDN or hostname) of the entries in the DnsName field for the servers in the FSAUtility command.
3. Rewrite the FSAUtility command to use that exact format for both servers.
Example of Solution 2
fsautility -m -s \\server01\oldfolder -d \\server02\newfolder gives the error "File Server \\server02 not found in EV database."
The SQL table shows the following:
Change the FSAUtility command to:
The SQL table shows the following:
| DnsName | UncName |
|---|---|
| server01.example.local | \\server01 |
| SERVER02 | \\server02 |
Change the FSAUtility command to:
fsautility -m -s \\server01.example.local\oldfolder -d \\server02\newfolder
What makes the DnsName column incorrect?
The DnsName column is supposed to contain the file server's FQDN, which was entered when adding the server as a target. If you do not type the FQDN manually in the New File Server wizard (for example, if you use the Browse button or you type only the hostname and click "Yes" to automatically resolve it to the FQDN), then in certain circumstances, the resolution to the FQDN fails, and the DnsName is written as the hostname in SQL.
Browsing the network does not always result in an FQDN in the DnsName column (Figure 1)
Figure 1
Using the hostname does not result in an FQDN in the DnsName column (see Figure 2).
Figure 2
Typing the full FQDN always results in an FQDN in the DnsName column (see Figure 3).
Figure 3
Note: It is recommended to follow the instructions in the wizard and enter the FQDN of the target file server. This will minimize the risk of problems related to DnsName mismatch in the future.
Issue/Introduction
In some circumstances, the following may be returned when using FSAUtility: "File Server [ServerName] not found in EV database."
Was this article helpful?
Yes
No
Powered by
