| title | summary | isUpgradeGuide | reviewed | component | redirects | |
|---|---|---|---|---|---|---|
New persistence format |
How to migrate ServiceControl Audit instances to the new persistence format introduced in version 4.26 |
true |
2022-10-21 |
ServiceControl |
|
Version 4.26 of ServiceControl introduced a new persistence format for audit instances. The new persistence format is faster and more efficient, using less space on disk.
New audit instances created with ServiceControl version 4.26 and above will use the new persistence format. Existing audit instances created with ServiceControl version 4.25 and below will continue to use the old persistence format, even if it is upgraded.
Warning
Updating an existing audit instance to version 4.26 and above will not automatically change the persistence format.
It is recommended to update to the new persistence format. The old persistence format will remain supported for a limited time to enable this transition.
Changing the persistence format of an existing audit instance is not supported.
To switch to the new persistence format, follow the steps for zero downtime upgrades, ensuring that the new audit instance is created with ServiceControl 4.26 or above.
Audit instances created using ServiceControl version 4.25 and below use the old instance format. Even if this instance is upgraded to a newer version, it will continue to use the old format.
The persistence format of an instance can be verified using ServiceControl Management or the Get-ServiceControlAuditInstances powershell cmdlet after installing ServiceControl 4.26 or above.
If the value is RavenDB 5 (ServiceControl 4.x) or RavenDB (ServiceControl 5.x or later) then the instance is using the new persistence format and does not require upgrading.
If the value is RavenDB 3.5 then the instance is using the old persistence format and should follow the instructions above to migrate to the new persistence format.