It seems like your browser didn't download the required fonts. Please revise your security settings and try again.


Starting May 1st, 2018, we will no longer offer the ArchiveOne family of products. This includes all editions of ArchiveOne, ArchiveOne for Files, Max Compression, and Access Security Manager. If you currently hold a maintenance and support contract, you will continue to receive our award-winning support until your contract expires, or until May 1st, 2019, whichever occurs first. The license for ArchiveOne is perpetual; therefore the software may continue to be used independently without any updates or support indefinitely.

How to Change the SQL Server Instance

  • Last updated on

This article refers to Barracuda ArchiveOne version 7.0 and higher.

You can change the SQL Server instance used by Barracuda ArchiveOne Enterprise for example, if you have reached the maximum database size limit for SQL Express instances and want to migrate to a full SQL server instance.

The steps in this article involve editing the Windows machine registry. Using the Registry Editor incorrectly can cause serious, system-wide problems that may require re-installation of Windows. Barracuda cannot guarantee that any problems resulting from the use of Registry Editor can be solved. Use this tool at your own risk; it is highly recommended that you create a backup of the registry before making any changes.

ArchiveOne utilizes a number of SQL databases which should be migrated to the new SQL instance:

  • AOneAudit
  • AOnePartitionData
  • C2CAOneConfig
  • C2CBrowseArchiveFolders

    These databases can be migrated by a number of methods; for more information, see the Microsoft Developer article Move a database from one server to another server in SQL Server 2008.

    The C2CAOneConfig database must be migrated to the new SQL instance to avoid data loss and maintain the current configuration. The AOneAudit database must be migrated to conserve audit data. However, if you do not require historical audit data it is not mandatory to migrate this database. The AOnePartitionData and C2CBrowseArchiveFolders can be repopulated from information stored in the Barracuda ArchiveOne repositories, so it is not a mandatory requirement to migrate these SQL databases. Bear in mind that the C2CBrowseArchiveFolders database may be of considerable size if you have a large amount of data in the archive, and may take significant time to rebuild if it is not migrated manually. While the databases are repopulating, you may observe an impact on the search performance (which utilizes the AOnePartitionData database) and not all folders are visible in the Archive Search website folder hierarchy (which utilizes the C2CBrowseArchiveFolders database).

To change the SQL Server instance,

  1. Confirm that the ArchiveOne Service domain account has the correct SQL permissions applied to the new SQL instance.
  2. Ensure that the ArchiveOne databases are mounted in the new SQL instance.
  3. On the Archive server, open the Microsoft Services console (services.msc), right-click each ArchiveOne Service, and click Stop. Ensure all ArchiveOne Services are stopped before proceeding.
  4. Browse to the Local Configuration Store in C:\ProgramData\Barracuda\ArchiveOne\LocalConfigurationStore
  5. Open the file System_Service.ini in a text editor such as Notepad.
  6. Edit the line SQLInstance= to the new SQL instance name in the form SERVERNAME\INSTANCE, or if using the default instance, just SERVERNAME.
  7. Save and close the file.
  8. Open the Microsoft Services console (services.msc), right-click each ArchiveOne Service, and click Start.
  9. Open the ArchiveOne Admin console.
  10. Right-click Status, and click Configure.
  11. Click the Browse Archive tab, and confirm the SQL instance is updated with your changes. Click Verify to confirm the connection is successful.
  12. Click Update Now to start a manual database synchronization.
  13. The new SQL instance name is now set and the AOnePartitionData and C2CBrowseArchiveFolders databases automatically rebuild in the background if you did not migrate these databases initially. If you did not migrate these databases, confirm that the AOnePartitionData and C2CBrowseArchiveFolders databases are created successfully on the new SQL instance through SQL Server Management Studio.