Reconfiguring AVFS Server for a New Connection - Is Reinstallation Necessary?

[shubham.raturi2308]

Hi Everyone,

I currently have an Autodesk AVFS server set up and successfully connected to Server X. It's functioning as expected. Now, I’m looking to connect this same AVFS server instance to a different machine—Server Y.

I’d like to know:
Can I simply go to Tools → Administration → Basic (Server Configuration Settings) and update the server connection details (Server name, username, password, etc.) to connect to Server Y?

Or

Do I need to uninstall the existing AVFS setup and reinstall it entirely to establish the connection with the new server?

I'd appreciate any insights or experiences anyone has had while switching server connections within the existing AVFS environment.

Thanks in advance!

@ihayesjr,  @CGBenner , @johannes.bauer 

[steveh3]

In Professional you can point to a different ADMS as show in screenshot below that you had mentioned.

Assuming you can do the same with Vault Basic...

[shubham.raturi2308]

@steveh3 ,

I’m working with Vault Professional - sorry for not specifying that in the post.

You only need to change the settings in Basic (or in Advanced as well, if required).

Regarding the folder structure, it will either ask for a new location when entered new login information (which will be contained in the Y server) or use the same location as the file store selected for X.

Thanks

[ihayesjr]

Is Server Y a restore from Server X?

If not, you cannot use the same file store location on AVFS, unless it is empty, as the one you used for Server X.

If so, you can use the same file store location on AVFS as you used for Server X.

FYI Vault Basic doesn't have a separate AVFS.

[shubham.raturi2308]

@ihayesjr 

The servers X and Y are completely independent, each with different Vault names.

If I understand you correctly, I would first need to clear the location where the filestore files are kept and then update the login information. Is that correct?

[ihayesjr · Accepted solution]

Here are the steps you need to take.

1. Backup the AFVS file store.
2. On the ADMS Server, run a file store validation. Verify the ADMS Server is not missing any files. If so, resolve this issue.
3. Disconnect the AFVS from Server X. This should start a file replication process to move any missing files to the ADMS server.
4. On the ADMS Server, rerun a file store validation. 
5. If you are going to use the same AVFS file store location, you will need to delete the file store folder so it is empty.
6. Connect the AFVS to Server Y.

Keep the backup of the AFVS Server X file store, in case you need files from it.

[shubham.raturi2308]

Thanks for the detailed steps.

I have a question - if I use this article to disconnect the AVFS server, will it delete the AVFS filestore automatically, or do I need to remove it manually?

Also, after disconnecting, I plan to move the filestore files to another location as a backup, as suggested. Once the AVFS site is deleted or disconnected, when I reopen the AVFS application on the server, will it prompt me to enter credentials for the new server? Or will I need to go into the settings to update them manually?

Knowledge Article link: How to remove Autodesk Vault File Server (AVFS) site in Vault?

[ihayesjr · Accepted solution]

"I have a question - if I use this article to disconnect the AVFS server, will it delete the AVFS filestore automatically, or do I need to remove it manually?"

No, this will only disconnect the AVFS from the ADMS. See the Note at the bottom of that page. 

Also, if there are any unreplicated files, you will need to wait for replication to take place.

See: Vault Help | Delete a Site | Autodesk

It should prompt you to connect to another server.

[gohiseb324]

Reinstallation usually isn’t necessary when reconfiguring an AVFS server for a new connection. In most cases, you just need to update the configuration files with the new connection details (IP, port, or authentication credentials) and then restart the service to apply the changes. However, if you’re switching to a completely different environment or version, a clean install might be more efficient to avoid compatibility issues.

For a smoother experience, always back up your existing configuration and data before making any changes. That way, if anything goes wrong, you can easily roll back.

If you’re looking for a break after tackling tech setups, check out this Dune Buggy Dubai adventure — sometimes the best reset is hitting the desert trails instead of the command line!