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

How can I change the SQL server instance used by ArchiveOne?

  • Type: Knowledgebase
  • Date changed: one year ago
Solution #00007428


ArchiveOne Enterprise, v7 or later



You may wish to change the SQL instance used by Archive One. For instance, you may have reached the maximum database size limit for SQL Express instances and wish to migrate to a full SQL server instance.


Note: This involves editing the Windows machine registry. Using the Registry Editor incorrectly can cause serious, system-wide problems that may require you to re-install Windows to correct them. 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.

To modify ArchiveOne to use a different SQL instance:

1. On the Archive server, open the Microsoft Services console (services.msc).

2. Stop and disable the service 'ArchiveOne Service'.

3. You will need to migrate the ArchiveOne databases to the new SQL instance. These databases can be migrated by a number of methods, see Microsoft's MSDN advice here. ArchiveOne creates the following databases:

4. AOneAudit

5. The AOneAudit database information is not stored elsewhere and is not recoverable if you choose not to migrate this database.C2CAOneConfig

6. The C2CAOneConfig database must be migrated as this contains configuration data for your ArchiveOne installation.AOnePartitionData

7. It is not mandatory to migrate this database as it will be rebuilt automatically from information stored in the ArchiveOne repositories.C2CBrowseArchiveFolders

8. It is not mandatory to migrate this database as it will be rebuilt automatically from information stored in the ArchiveOne repositories. 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.Confirm that the ArchiveOne Service domain account has the correct SQL permissions applied to the new SQL instance as per: FAQ: What SQL database permissions does the ArchiveOne service account require?

If you do not know the name of the ArchiveOne service account, you can check this by following: HOWTO: Determine the current ArchiveOne Enterprise (Policy) configurationOn the Archive server, run 'regedit' to open the Registry Editor.Browse to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\AOnePolService\ParametersChange the value of 'SQLInstance' to the name of the SQL instance in the form 'HOSTNAME\INSTANCE', where HOSTNAME is the SQL server hostname and INSTANCE is the SQL instance name, eg. SQLSRV01\MSSQL.Close the Registry Editor.In the Microsoft Services console (services.msc) and re-enable and start the service 'ArchiveOne Service'.Open the ArchiveOne Admin console.Right-click the 'Status' node and select 'Configure...'.Select the 'Browse Archive' tab and confirm the SQL instance specified has correctly updated. Click 'Verify' to confirm the connection is successful.Click 'Update Now' to start a manual synchronisation of the database.

The new SQL instance name will now be set and the ArchiveOne databases will rebuild automatically in the background if you did not migrate these databases initially. If you did not migrate the databases, you can confirm that the databases have been created successfully on the new SQL instance through SQL Server Management Studio.