---
title: "Frameworks Licensing Implications"
canonical: "https://kb.myframeworks.com.au/space/FRAM/28378746/Frameworks%20Licensing%20Implications"
format: markdown
---
# What are the licensing Implications for:

# 1. Hot standby

To operate 'hot' standby where the full number of **Progress **and **Frameworks users** are loaded on the remote DR server requires the user to pay a redundancy license fee of 50% of both the Progress and Frameworks licenses. In the case of server failure, communications lines are switched to the DR server, and the system continues with only minimal downtime. AI transfers would be continuous, and data loss in case of failure would be small if at all.

# 2. Warm standby

To operate 'warm' standby would require a **Progress database** **license** (either Workgroup or Enterprise depending on what you are running on your main server) for a minimum of 5 users and at least one **Frameworks license**. The AI file is applied at defined intervals to the remote DR server, and in the case of main server failure, the warm DR server would assume control after the Progress and Frameworks maximum user counts are installed (via the running of scripts).

# 3. Cold Standby

There are no licensing implications with cold standby provided the server is restored from backup AFTER the main server has failed. No Progress or Frameworks users may be loaded on the DR box while the main server is operational.

# <span style="color: #003366">Technical Restrictions for After Imaging</span>

1. The DR server must run exactly the same Network Operating System and Progress database as the main server.
2. The database on the DR server must not be accessed. After imaging requires complete integrity of all indexes as at the last application.
3. After the AI file is applied to the DR server, the database is copied, and this copy may be accessed for interrogation, testing, training, or reporting purposes.

# <span style="color: #003366">The cost includes: </span>

1. A Progress 5-user Enterprise or Workgroup database license.
2. 1 x Frameworks license.
3. Installation and training to the point where the DR server is fully operational and scripts installed and working. This service can be conducted remotely, but clients may prefer an on-site installation to ensure all printers and communication devices are working.


Our recommendation is that this server be utilised as a testing, training, and reporting environment to take pressure off the main server. Additional time may be required if the reporting options are installed. Additional Frameworks users may be required.