---
title: "Release notes 2.0 and upgrade guide"
canonical: "https://support.appfire.com/space/SCC/84288907/Release%20notes%202.0%20and%20upgrade%20guide"
format: markdown
---
> Macro (aura-html)

# Upgrade guide

> ❌ It is always recommended to backup your Confluence instance when upgrading. Ideally, perform a test run against a Test or Stage environment based upon your production Confluence instance.

Secure Content 2.0 should upgrade without incident from Secure Content 1.x.  However, it is recommended performing a backup of your Confluence instance whenever updating your apps.

## Compatibility

### Confluence Versions

Secure Content 2.0 was tested against Confluence 6.0.1, 6.0.3 and 6.0.5 on Linux 64-bit operating system.  It is not considered compatible with any Confluence release prior to 6.0 and is not supported prior to Confluence 6.0.

### Browsers

Secure Content 2.0 was tested against the latest Google Chrome and Firefox versions as of 6 MAR 2017.

### Database

Secure Content 2.0 was built using ActiveObject Version 1.1.5 (Bundled with Confluence 6.0.x) and tested against these databases and versions.

| **Database** | **Version** |
| --- | --- |
| H2 | 1.3.176 |
| PostgreSQL | 9.2.15 |
| MySQL | 5.6.23 |


Administrator Recommendations

### Pre-Upgrade

In 'Logging and Debugging' add the *com.praecipo.sec* namespace and set the log level to DEBUG.

### Post-Upgrade

In 'Support Tools' generate a Support Zip. Download and review the log for com.praecipio.plugin migration statements to ensure there were no errors.

If errors are identified open a Support Ticket in our [Secure Content Customer Portal](https://praecipio.atlassian.net/servicedesk/customer/portal/3) and attach the log or a snippet containing the migration output.

In 'Logging and Debugging' add the *com.praecipo.sec* namespace and set the log level to WARN or remove it.

# Release Notes

![image](media://b779f6ca-d802-4b1f-958b-abf881fb49f1)