Effective data management is critical for any system that relies on spatial data, and backing up spatial data is essential for both platform support and disaster recovery. While Konect instances are backed up daily by the platform to ensure that environments can be restored in the event of a system-wide failure, it is important to note that individual client instances are not archived by Konect. This means that customers are responsible for backing up all projects, lists, queries and basemap data.
Regular backups provide peace of mind and ensure that critical spatial datasets can be restored efficiently if needed, while also allowing for reuse in other applications or future projects.
By implementing manual or automated backup processes, customers can leverage the Konect platform to archive their project and data at a chosen interval within their environment.
Choosing a backup strategy
Ultimately, the responsibility for defining backup procedures lies with the client. Organisations should determine whether a manual or automated backup approach best suits their operational needs.
Using batch scripting as a starting point allows administrators to establish a repeatable process and define appropriate backup timeframes. From there, the process can be expanded into more advanced automation if required.
Separating spatial data from the KPK project file
Within a Konect environment, it is recommended that the spatial data is backed up separately from the main Konect project file. This approach improves reliability, flexibility and recoverability in the event of system issues or data loss.
A Konect environment typically uses a KPK project file to store the configuration and operational structure of the system. This file acts as a data transfer package that contains elements such as maps, lists, queries, forms and associated data tied to the environment.
While the KPK file is essential for recreating the application structure, it is not always the best place to rely solely on for spatial data backup. Instead, spatial datasets should be exported individually and archived as standalone files. This allows the data to be restored independently and makes it easier to reuse the datasets in other applications or systems.
Exporting individual datasets provides greater control over data management. If a single dataset becomes corrupted or needs to be restored, administrators can recover that dataset without needing to restore the entire Konect environment.
Manual backup options in Konect Manager
For basic implementations of Konect, the Import/Export tab within Konect Manager provides a straightforward way to manually back up spatial data. Administrators of a standalone Konect instance can use this feature to export datasets and save them to a secure location.
This process allows teams to create backups on demand, which can be useful before major changes, system upgrades or data updates. Manual exports are a practical starting point for organisations that do not yet have automated backup processes in place.
Using batch scripts for structured backups
As environments grow, manual backups can become difficult to manage. Writing batch scripts is a useful way to catalogue and back up Konect data to a nominated location on the client side.
Batch scripting allows administrators to define a consistent backup process. For example, scripts can export datasets and store them in organised folders with timestamps. This approach helps maintain a clear archive of historical backups and simplifies the process of locating a specific dataset when needed.
Batch scripts can also form the foundation for automated backup schedules. Administrators can configure these scripts to run daily, weekly or monthly, depending on organisational requirements.
Considerations for restoring data
When restoring a Konect environment, it is important to proceed carefully. Restoring an entire KPK project file into an existing environment can sometimes lead to conflicts or unexpected behaviour.
For this reason, it is recommended to restore the KPK file into a new environment or into an environment that does not yet contain spatial data. Once the project structure has been restored successfully, the spatial datasets can then be imported separately.
Spatial data can be re-imported using the Import tab in Konect Manager, or through command-line interface (CLI) or API tools, depending on the workflow being used.
A more reliable recovery process
By separating spatial data backups from the KPK project file and maintaining structured dataset exports, organisations gain greater control over their data recovery process. This approach reduces risk, simplifies restoration and ensures that critical spatial datasets remain accessible when they are needed most.
Get started backing up your critical data
Backing up spatial data separately from your KPK project file ensures greater flexibility, reliability and control over your Konect environment. By combining manual exports, batch scripting and structured restore processes, administrators can safeguard critical datasets and simplify recovery when needed.
A thoughtful backup strategy not only protects your data but also empowers your team to manage and reuse it efficiently.
For more help, please visit https://www.gbmkonect.com/support/ to log a support request.