eviden-logo

Evidian > Products > SafeKit: Simple, Cost-Effective High Availability Software > Milestone Management Migration with SafeKit

Milestone Management Migration with SafeKit

Evidian SafeKit

Warning

Warning, these procedures are simple guidelines. Evidian is not an expert of Milestone migration procedures. They must be validated by Milestone support according your Milestone versions.

3 migration scenarios are considered:

Note: here is described the Milestone Management solution with SafeKit for high availability and redundancy.

1. Scenario with Milestone Management and SQL in the same SafeKit cluster

  1. Decide with the customer a service interruption to make the migration.
  2. Check in the Windows registry of both management nodes that the connection to the SQL databases is really local to each node. According this Milestone KB, the registry key for SQL connection is HKEY_LOCAL_MACHINE\SOFTWARE\VideoOS\Server\ConnectionString.
  3. Make a backup of the SQL databases on MGT+SQL1-PRIM for security. Default databases are according this Milestone KB: Surveillance, Surveillance_IDP, SurveillanceLogServerV2, Surveillance_IM.
  4. Put the cluster in (MGT+SQL1-PRIM, MGT+SQL2-SECOND). Thus, the Milestone SQL databases are the same on both nodes (if they are correctly configured for replication in the SafeKit module).
  5. Protect the nodes from an automatic start of the SafeKit module at boot during the migration (if nodes are rebooted for any reason during the migration).
    Remove the automatic start of the module at boot: in a command prompt under c:\safekit, type "safekit boot -m AM off" where AM is the module name.
    Do it for on both nodes.
  6. Put the cluster in (MGT+SQL1-ALONE, MGT+SQL2-STOP): there is no more replication from SQL1 to SQL2.
  7. Suspend the monitoring of processes during the migration on MGT+SQL1. Use the "Disable/enable" menu in the SafeKit web console to do that. Suspend also checkers with the same menu.
  8. Migrate MGT+SQL1 from Milestone version N to Milestone version N+1 with migration of the databases on node 1.
    Note: the migration requires that the management services are running, that’s why the migration is made in the ALONE state without SafeKit ckeckers.
  9. Register the virtual IP of the SafeKit management cluster with the Server Configurator GUI.
  10. At this step, MGT+SQL1 is migrated to Milestone version N+1 and MGT+SQL2 is in version N.
  11. DO NOT START MGT+SQL2 as SECOND during the previous steps else it will resynchronize the migrated databases from SQL1 (that’s why we remove the automatic start at boot and make a backup for security reasons).
  12. Stop the ALONE SafeKit module: the cluster is in (MGT+SQL1-STOP, MGT+SQL2-STOP).
  13. Force start as prim the SafeKit module on MGT+SQL2 with the version N. Use the "Force start" menu in the SafeKit web console to do that.
  14. The cluster is in (MGT+SQL1-STOP, MGT+SQL2-ALONE).
  15. Suspend the monitoring of processes during the migration on MGT+SQL2. Use the "Disable/enable" menu in the SafeKit web console to do that. Suspend also checkers with the same menu.
  16. Migrate MGT+SQL2 from Milestone version N to Milestone N+1 with migration of the databases on node 2.
  17. Register the virtual IP of the SafeKit management cluster with the Server Configurator GUI.
  18. At this step all nodes are migrated.
  19. Stop the SafeKit module on MGT+SQL2.
  20. The cluster is in (MGT+SQL1-STOP, MGT+SQL2-STOP).
  21. Force start as prim the SafeKit module on MGT+SQL1 (if you want SQL1 to be the reference for the databases).
    The cluster is in (MGT+SQL1-ALONE, MGT+SQL2-STOP).
  22. Force start as second the SafeKit module MGT+SQL2.
    The cluster is in (MGT+SQL1-PRIM, MGT+SQL2-SECOND); the SQL2 databases are resynchronized from SQL1.
  23. Re-enable Automatic start at boot of the SafeKit module and resume the errd and checker monitoring.
  24. The cluster is restarted and migrated.

Use arrows to see main steps

2. Scenario with Milestone Management and SQL in two different SafeKit clusters

  1. Decide with the customer a service interruption to make the migration.
  2. Check in the Windows registry of both management nodes that the connection to the SQL databases is really external and connected to the virtual IP of the SafeKit SQL cluster. According this Milestone KB, the registry key for SQL connection is HKEY_LOCAL_MACHINE\SOFTWARE\VideoOS\Server\ConnectionString.
  3. Make a backup of the SQL databases on SQL1-PRIM for security. Default databases are according this Milestone KB: Surveillance, Surveillance_IDP, SurveillanceLogServerV2, Surveillance_IM.
  4. Put the cluster in (MGT1+SQL1-PRIM, MGT2+SQL2-SECOND). Thus, the Milestone SQL databases are the same on both SQL nodes (if they are correctly configured for replication in the SafeKit SQL module).
  5. Protect the nodes from an automatic start of the SafeKit module at boot during the migration (if nodes are rebooted for any reason during the migration).
    Remove the automatic start of the module at boot: in a command prompt under c:\safekit, type "safekit boot -m AM off" where AM is the module name.
    Do it for on both nodes.
  6. Put the cluster in (MGT1+SQL1-ALONE, MGT2+SQL2-STOP): there is no more replication from SQL1 to SQL2.
  7. Suspend the monitoring of processes during the migration on MGT1. Use the "Disable/enable" menu in the SafeKit web console to do that. Suspend also checkers with the same menu.
  8. Migrate MGT1+SQL1 from Milestone version N to Milestone version N+1 with migration of the databases on SQL1.
    Note: the migration requires that the management services are running, that’s why the migration is made in the ALONE state without SafeKit checkers.
  9. Register the virtual IP of the SafeKit management cluster (NOT the SQL virtual IP address) with the Server Configurator GUI.
  10. At this step, MGT1+SQL1 are migrated to Milestone version N+1 and MGT2+SQL2 are in version N.
  11. DO NOT START SQL2 as SECOND during the previous steps else it will resynchronize the migrated databases from SQL1 (that’s why we remove the automatic start at boot and make a backup for security reasons).
  12. Stop SafeKit on ALONE servers: the clusters are in (MGT1+SQL1-STOP, MGT2+SQL2-STOP).
  13. Force start as prim the SafeKit modules on MGT2+SQL2 with the version N. Use the "Force start" menu in the SafeKit web console to do that.
  14. The cluster is in (MGT1+SQL1-STOP, MGT2+SQL2-ALONE).
  15. Suspend the monitoring of processes during the migration on MGT2. Use the "Disable/enable" menu in the SafeKit web console to do that. Suspend also checkers with the same menu.
  16. Migrate MGT2+SQL2 from Milestone version N to Milestone N+1 with migration of the databases on SQL2.
  17. Register the virtual IP of the SafeKit management cluster (NOT the SQL virtual IP address) with the Server Configurator GUI.
  18. At this step all nodes are migrated.
  19. Stop the SafeKit modules on MGT2+SQL2.
  20. The clusters are in (MGT1+SQL1-STOP, MGT2+SQL2-STOP).
  21. Force start as prim the SafeKit modules on MGT1+SQL1 (if you want SQL1 to be the reference for the databases).
    The clusters are in (MGT1+SQL1-ALONE, MGT2+SQL2-STOP).
  22. Force start as second the SafeKit modules on MGT2+SQL2.
    The clusters are in (MGT1+SQL1-PRIM, MGT2+SQL2-SECOND); the SQL2 databases are resynchronized from SQL1.
  23. Re-enable Automatic start at boot of the SafeKit modules and resume the errd and checker monitoring.
  24. The clusters are restarted and migrated.

Use arrows to see main steps

3. Scenario with Milestone Management in a SafeKit cluster and an external SQL not in a SafeKit cluster

  1. Decide with the customer a service interruption to make the migration.
  2. Check in the Windows registry of both management nodes that the connection to the SQL databases is really external and the same for each node. According this Milestone KB, the registry key for SQL connection is HKEY_LOCAL_MACHINE\SOFTWARE\VideoOS\Server\ConnectionString.
  3. Make a backup of databases on the external SQL for security and also for step 11. Default databases are according this Milestone KB: Surveillance, Surveillance_IDP, SurveillanceLogServerV2, Surveillance_IM.
    This step is mandatory for step 12.
  4. Put the cluster in (MGT1-PRIM, MGT2-SECOND).
  5. Protect the SafeKit nodes from an automatic start of the SafeKit module at boot during the migration (if nodes are rebooted for any reason during the migration).
    Remove the automatic start of the module at boot: in a command prompt under c:\safekit, type "safekit boot -m AM off" where AM is the module name.
    Do it for on both nodes.
  6. Put the cluster in (MGT1-ALONE, MGT2-STOP).
  7. Suspend the monitoring of processes during the migration on MGT1. Use the "Disable/enable" menu in the SafeKit web console to do that. Suspend also checkers with the same menu.
  8. Migrate MGT1 from Milestone version N to Milestone version N+1 with migration of the databases on the external SQL.
    Note: the migration requires that the management services are running, that’s why the migration is made in the ALONE state without SafeKit checkers.
  9. Register the virtual IP of the SafeKit management cluster (NOT the SQL IP address) with the Server Configurator GUI.
  10. At this step, MGT1+SQL are migrated to Milestone version N+1 and MGT2 is in version N.
  11. Stop the ALONE SafeKit module: the cluster is in (MGT1-STOP, MGT2-STOP) with the external database migrated to version N+1.
  12. To succeed the MGT2 migration, restore the backup of the database taken at step 3 (as a precaution before restoring, you can take a backup of the newly migrated SQL to version N+1). The cluster is in (MGT1-STOP, MGT2-STOP) with the external database restore to version N.
  13. Force start as prim the MGT2 SafeKit module with the version N. Use the "Force start" menu in the SafeKit web console to do that.
  14. On MGT2, if the management services do not restart after the databases restore, you may have to reset the Milestone IDP on MGT2 (reset it with the cmd iisreset /restart and register the virtual IP of the SafeKit management cluster (NOT the SQL IP address) with the Server Configurator GUI). Check with Milestone support.
  15. The cluster is in (MGT1-STOP, MGT2-ALONE).
  16. Suspend the monitoring of processes during the migration on MGT2. Use the "Disable/enable" menu in the SafeKit web console to do that. Suspend also checkers with the same menu.
  17. Migrate MGT2 from Milestone version N to Milestone N+1 with migration of the databases on the external SQL.
  18. Register the virtual IP of the SafeKit management cluster (NOT the SQL IP address) with the Server Configurator GUI.
  19. At this step all nodes are migrated.
  20. Stop the SafeKit module on MGT2.
  21. The cluster is in (MGT1-STOP, MGT2-STOP).
  22. Force start as prim the SafeKit module on MGT1.
    The cluster is in (MGT1-ALONE, MGT2-STOP).
  23. Force start as second the SafeKit module on MGT2.
    The cluster is in (MGT1-PRIM, MGT2-SECOND).
  24. Re-enable Automatic start at boot of the SafeKit module and resume the errd and checker monitoring.
  25. The cluster is restarted and migrated.

Use arrows to see main steps

SafeKit: The Benchmark in High Availability for Partners

How does SafeKit contribute to our partners' customer success?

This platform-independent software is ideal for partners reselling critical applications who need to offer customers a simple, cost-effective high availability (HA) and system redundancy option, without the complexity and expense of SANs (Storage Area Networks). SafeKit’s core features — load balancing, real-time data replication, and automatic failover — significantly simplify the integration of HA into any service or product offering.

Why is SafeKit the simplest high availability solution on the market?

With a proven track record and numerous deployments in over 30 countries through our extensive partner network, SafeKit is recognized as the easiest and fastest HA solution to implement for critical systems. This includes sectors like video management systems (VMS), access control, building management (BMS), SCADA software, automated logistics, and critical air/rail traffic control, ensuring maximum uptime across the board.

How does SafeKit accelerate partner mastery of HA deployment and support?

SafeKit offers a complete, free, and open-access resource kit to support its partners, including free trials, comprehensive online training modules, and the opportunity to obtain official SafeKit certification at no cost. These tools enable partners to rapidly acquire the necessary technical skills to effectively deploy and provide world-class support for the solution, minimizing deployment time and reducing the learning curve.

How the SafeKit mirror cluster works with Windows or Linux?

Step 1. Real-time replication

Server 1 (PRIM) runs the Windows or Linux application. Clients are connected to a virtual IP address. SafeKit replicates in real time modifications made inside files through the network.

File replication at byte level in a mirror Windows or Linux cluster

The replication is synchronous with no data loss on failure contrary to asynchronous replication.
You just have to configure the names of directories to replicate in SafeKit. There are no pre-requisites on disk organization. Directories may be located in the system disk.

Step 2. Automatic failover

When Server 1 fails, Server 2 takes over. SafeKit switches the virtual IP address and restarts the Windows or Linux application automatically on Server 2.
The application finds the files replicated by SafeKit uptodate on Server 2. The application continues to run on Server 2 by locally modifying its files that are no longer replicated to Server 1.

Failover of Windows or Linux in a mirror cluster

The failover time is equal to the fault-detection time (30 seconds by default) plus the application start-up time.

Step 3. Automatic failback

Failback involves restarting Server 1 after fixing the problem that caused it to fail.
SafeKit automatically resynchronizes the files, updating only the files modified on Server 2 while Server 1 was halted.

Failback in a mirror Windows or Linux cluster

Failback takes place without disturbing the Windows or Linux application, which can continue running on Server 2.

Step 4. Back to normal

After reintegration, the files are once again in mirror mode, as in step 1. The system is back in high-availability mode, with the Windows or Linux application running on Server 2 and SafeKit replicating file updates to Server 1.

Return to normal operation in a mirror Windows or Linux cluster

If the administrator wishes the application to run on Server 1, he/she can execute a "swap" command either manually at an appropriate time, or automatically through configuration.

SafeKit: High Availability (HA) and Redundancy Choices

What are the two primary choices for ensuring high availability and redundancy?

You can choose between setting up redundancy:

  • At the application level
  • At the virtual machine (VM) level

What is "Redundancy at the application level"?

In this solution, only the application data are replicated. In the event of a failure, only the application is restarted, not the entire operating system or VM.

SafeKit diagram for Application Level High Availability (HA): Illustrates synchronous replication of critical application data between active and passive servers, enabling fast application failover without needing a full VM restart.

Technical Requirements:

  • It requires a technical understanding of the application itself.
  • You must manually define:
    • Which services need to be restarted.
    • The specific application folders that need real-time replication.
    • The configuration of a virtual IP address for failover.

Platform Compatibility:

  • This solution is platform-agnostic.
  • It works inside physical machines, virtual machines, or in the Cloud.
  • Any hypervisor is supported (e.g., VMware, Hyper-V, etc.).
  • More information: Windows, Linux

What is "Redundancy at the virtual machine (VM) level"?

In this solution, the full Virtual Machine (VM) is replicated, including both the Application and the Operating System (OS). In the event of a failure, the full VM is restarted.

SafeKit diagram for Virtual Machine (VM) Level High Availability (HA): Illustrates the full replication of the VM, including the OS and application, between two physical servers to ensure service continuity upon hardware failure.

Key Advantages:

  • It does not require a technical understanding of the application installed within the VM.
  • It is the best solution if you do not know how the application works.
  • You only need to define the location of the VM files.

Platform Compatibility:

  • This solution works with Windows/Hyper-V and Linux/KVM.
  • It does not support VMware for this type of redundancy.
  • This is typically an active/active solution where several virtual machines can be replicated and restarted between two nodes.
  • More information: Windows/Hyper-V, Linux/KVM

Typical usage with SafeKit

Why a replication of a few Tera-bytes?

Resynchronization time after a failure (step 3)

  • 1 Gb/s network ≈ 3 Hours for 1 Tera-bytes.
  • 10 Gb/s network ≈ 1 Hour for 1 Tera-bytes or less depending on disk write performances.

Alternative

Why a replication < 1,000,000 files?

  • Resynchronization time performance after a failure (step 3).
  • Time to check each file between both nodes.

Alternative

  • Put the many files to replicate in a virtual hard disk / virtual machine.
  • Only the files representing the virtual hard disk / virtual machine will be replicated and resynchronized in this case.

Why a failover ≤ 32 replicated VMs?

  • Each VM runs in an independent mirror module.
  • Maximum of 32 mirror modules running on the same cluster.

Alternative

  • Use an external shared storage and another VM clustering solution.
  • More expensive, more complex.

Why a LAN/VLAN network between remote sites?

Alternative

  • Use a load balancer for the virtual IP address if the 2 nodes are in 2 subnets (supported by SafeKit, especially in the cloud).
  • Use backup solutions with asynchronous replication for high latency network.

SafeKit High Availability (HA) Solutions: Quick Installation Guides for Windows and Linux Clusters

This table presents the SafeKit High Availability (HA) solutions, categorized by application and operating environment (Databases, Web Servers, VMs, Cloud). Identify the specific pre‑configured .safe module (e.g., mirror.safe, farm.safe, and others) required for real‑time replication, load balancing, and automatic failover of critical business applications on Windows or Linux. Simplify your HA cluster setup with direct links to quick installation guides, each including a download link for the corresponding .safe module.

A SafeKit .safe module is essentially a pre‑configured High Availability (HA) template that defines how a specific application will be clustered and protected by the SafeKit software. In practice, it contains a configuration file (userconfig.xml) and restart scripts.

SafeKit High Availability (HA) Solutions: Quick Installation Guides (with downloadable .safe modules)
Application Category HA Scenario (High Availability) Technology / Product .safe Module Installation Guide
New Applications Real-Time Replication and Failover Windows mirror.safe View Guide: Windows Replication
New Applications Real-Time Replication and Failover Linux mirror.safe View Guide: Linux Replication
New Applications Network Load Balancing and Failover Windows farm.safe View Guide: Windows Load Balancing
New Applications Network Load Balancing and Failover Linux farm.safe View Guide: Linux Load Balancing
Databases Replication and Failover Microsoft SQL Server sqlserver.safe View Guide: SQL Server Cluster
Databases Replication and Failover PostgreSQL postgresql.safe View Guide: PostgreSQL Replication
Databases Replication and Failover MySQL mysql.safe View Guide: MySQL Cluster
Databases Replication and Failover Oracle oracle.safe View Guide: Oracle Failover Cluster
Databases Replication and Failover Firebird firebird.safe View Guide: Firebird HA
Web Servers Load Balancing and Failover Apache apache_farm.safe View Guide: Apache Load Balancing
Web Servers Load Balancing and Failover IIS iis_farm.safe View Guide: IIS Load Balancing
Web Servers Load Balancing and Failover NGINX farm.safe View Guide: NGINX Load Balancing
VMs and Containers Replication and Failover Hyper-V hyperv.safe View Guide: Hyper-V VM Replication
VMs and Containers Replication and Failover KVM kvm.safe View Guide: KVM VM Replication
VMs and Containers Replication and Failover Docker mirror.safe View Guide: Docker Container Failover
VMs and Containers Replication and Failover Podman mirror.safe View Guide: Podman Container Failover
VMs and Containers Replication and Failover Kubernetes K3S k3s.safe View Guide: Kubernetes K3S Replication
AWS Cloud Real-Time Replication and Failover AWS mirror.safe View Guide: AWS Replication Cluster
AWS Cloud Network Load Balancing and Failover AWS farm.safe View Guide: AWS Load Balancing Cluster
GCP Cloud Real-Time Replication and Failover GCP mirror.safe View Guide: GCP Replication Cluster
GCP Cloud Network Load Balancing and Failover GCP farm.safe View Guide: GCP Load Balancing Cluster
Azure Cloud Real-Time Replication and Failover Azure mirror.safe View Guide: Azure Replication Cluster
Azure Cloud Network Load Balancing and Failover Azure farm.safe View Guide: Azure Load Balancing Cluster
Physical Security / VMS Real-Time Replication and Failover Milestone XProtect milestone.safe View Guide: Milestone XProtect Failover
Physical Security / VMS Real-Time Replication and Failover Nedap AEOS nedap.safe View Guide: Nedap AEOS Failover
Physical Security / VMS Real-Time Replication and Failover Genetec (SQL Server) sqlserver.safe View Guide: Genetec SQL Failover
Physical Security / VMS Real-Time Replication and Failover Bosch AMS (Hyper-V) hyperv.safe View Guide: Bosch AMS Hyper-V Failover
Physical Security / VMS Real-Time Replication and Failover Bosch BIS (Hyper-V) hyperv.safe View Guide: Bosch BIS Hyper-V Failover
Physical Security / VMS Real-Time Replication and Failover Bosch BVMS (Hyper-V) hyperv.safe View Guide: Bosch BVMS Hyper-V Failover
Physical Security / VMS Real-Time Replication and Failover Hanwha Vision (Hyper-V) hyperv.safe View Guide: Hanwha Vision Hyper-V Failover
Physical Security / VMS Real-Time Replication and Failover Hanwha Wisenet (Hyper-V) hyperv.safe View Guide: Hanwha Wisenet Hyper-V Failover
Siemens Products Real-Time Replication and Failover Siemens Siveillance suite (Hyper-V) hyperv.safe View Guide: Siemens Siveillance HA
Siemens Products Real-Time Replication and Failover Siemens Desigo CC (Hyper-V) hyperv.safe View Guide: Siemens Desigo CC HA
Siemens Products Real-Time Replication and Failover Siemens Siveillance VMS SiveillanceVMS.safe View Guide: Siemens Siveillance VMS HA
Siemens Products Real-Time Replication and Failover Siemens SiPass (Hyper-V) hyperv.safe View Guide: Siemens SiPass HA
Siemens Products Real-Time Replication and Failover Siemens SIPORT (Hyper-V) hyperv.safe View Guide: Siemens SIPORT HA
Siemens Products Real-Time Replication and Failover Siemens SIMATIC PCS 7 (Hyper-V) hyperv.safe View Guide: SIMATIC PCS 7 HA
Siemens Products Real-Time Replication and Failover Siemens SIMATIC WinCC (Hyper-V) hyperv.safe View Guide: SIMATIC WinCC HA

SafeKit: Technical Demonstrations and Tutorials

SafeKit Customers in all Business Activities

  • Best high availability use cases with SafeKit

    Best use cases [+]

  • High availability of video management, access control, building management with SafeKit

    Video management, access control, building management [+]

  • Harmonic has deployed more than 80 SafeKit clusters for TV broadcasting

    TV broadcasting [+]

  • Natixis uses SafeKit as a high availability solution for banking applications

    Finance [+]

  • Fives Syleps implements high availability with SafeKit for automated logistics

    Industry [+]

  • Air traffic control systems supplier, Copperchase, deploys SafeKit high availability in airports.

    Air traffic control [+]

  • Software vendor Wellington IT deploys SafeKit in banks

    Bank [+]

  • Paris transport company (RATP) chose the SafeKit high availability for metro lines

    Transport [+]

  • Systel deploys SafeKit in emergency call centers

    Healthcare [+]

  • ERP high availability and load balancing of the French army (DGA) are made with SafeKit.

    Government [+]

Comparison of SafeKit with Traditional High Availability (HA) Clusters

How does SafeKit compare to traditional High Availability (HA) cluster solutions?

This comparison highlights the fundamental differences between SafeKit and traditional High Availability (HA) cluster solutions like Failover Clusters, Virtualization HA, and SQL Always-On. SafeKit is designed as a low-complexity, software-only solution for generic application redundancy, contrasting with the high complexity and specific storage requirements (shared storage, SAN) typical of traditional HA mechanisms.
Comparison of SafeKit with traditional High Availability (HA) clusters
Solutions Complexity Comments
Failover Cluster (Microsoft) High Specific Storage (shared storage, SAN)
Virtualization (VMware HA) High Specific Storage (shared storage, SAN, vSAN)
SQL Always-On (Microsoft) High Only SQL is redundant, requires SQL Enterprise Edition
Evidian SafeKit Low Simplest, generic and software-only. Unsuitable for large data replication.

SafeKit's Advantage in Application Redundancy

SafeKit achieves its low-complexity High Availability through a simple, software-based mirroring mechanism that eliminates the need for expensive, dedicated hardware like a SAN (Storage Area Network). This makes it a highly accessible solution for quickly implementing application redundancy without complex infrastructure changes.

SafeKit High Availability Resources, Downloads, and Documentation

💡 To kickstart your high availability journey with SafeKit, begin with the Quick Installation Guides.

📦 SafeKit's HA Software Packages - Version 8.2

This table provides the SafeKit installation files for the current version, organized by operating system and installer type.

OS / Platform Installer Type Key Benefit Download Link
Windows (64-bit) .exe Installer Includes Microsoft VC++ Redistributable ⬇️ Download SafeKit 8.2 Windows EXE
Windows (64-bit) .msi Installer Does not include Microsoft VC++ Redistributable ⬇️ Download SafeKit 8.2 Windows MSI
Linux (64-bit) Auto-extractable .BIN Includes Linux package and installation script ⬇️ Download SafeKit 8.2 Linux BIN File

➡️ Go to v7.5 Archives