Requesting a Backup of Invenias

Overview

Invenias Customers are entitled to one full backup without charge. If this backup request is part of a decision to leave Invenias, please ensure that you communicate this at the start of the process. Our "Final" backup process will include us disabling the database so that that database can not be edited or accessed once the backup is triggered. Each additional backup you request will incur a charge of £500 per backup.

Whilst your database is "Live" your data is automatically backed every 5 minutes for the last 7 days. After that, we keep a weekly backup for 4 weeks. On completion of a Final Backup, we will "Disabled" your database and your data will only be retained for 25 days form that date before it is deleted from our Platform.

Backup requests can only be made by Users who have the Systems Administrator Role for your company. Invenias will only provide backups in an MS Azure SQL BACPAC format. A BACPAC is a Windows file with a .bacpac extension that encapsulates a database's schema and data. This is the raw data format of the Invenias Azure database and you can import a SQL Server database into Azure SQL Database or SQL Managed Instance using a BACPAC file. Here is an article on the Microsoft website that explains how. Invenias will only provide backups in that format, we will not support requests to provide backups in CSV or other formats.

Standard Backup

The platform will automate the production of a backup at the time of any request. With a Standard Backup, you will be able to continue to access the database, although anything entered after the backup is triggered will not be included in the backup.

Like a snapshot in time, the backup will contain the entire database at that moment.

Backup Contents

  • All of the relations, records, and documents are compiled within a db.bacpac image.

  • There will be two or three supporting folders.

    • These contain the binaries (Documents linked to Records), images (all photos from People and Companies), and any settings/customization.

The customisation is not always available or required, but the enumerations for settings are held within the db.bacpac file.

Database Only Backup

We offer the option of a Database-Only Backup for clients with specific use cases.

This Database-Only Backup option ensures that you have the flexibility to tailor your backup strategy to your specific needs. The benefit is really highlighted when working with third-party companies that require a more streamlined backup solution for documentation and mapping of relational tables held within the backup.

Backup Contents

  • All of the relations, records, and documents are compiled within a db.bacpac image.

A Database Only Backup excludes binaries (EX: Document and Images), providing a leaner backup option.

Final Backup

This will be the same as a Standard Backup. However, the entire database will first be set offline for ALL users. This is to ensure that after the request no additional data can be added which would not be included in the backup. This is usually the last backup that is issued, should a customer leave Invenias by Bullhorn.

The Backup Process

This has 3 steps, which our Support team will walk you through.

  • Initiate the request for a Backup
  • Approval for that request
  • Downloading the backup

Initiate the Request for a Backup

  1. Contact your Account Manager. Kindly, specify whether you require a Standard Backup (i.e. the entire database and files) or a Database Only Backup (i.e. excluding binaries).
    • Your Account Manager needs to raise the request in our system. They will ensure that Finance is notified that a backup process has been initiated.
      • This needs to happen for every backup request.
  2. Once the request has been approved by Finance, that team will raise a Support request.
    • Our Support Team will contact your specified and designated Invenias Systems Administrator.
  3. Our Support Agent will connect remotely to the designated Systems Administrator's computer using GoToAssist by Citrix.
    • This is the same remote connection method we use for all remote support sessions.
  4. They will navigate to the Invenias web application (yourcompany.invenias.com).
  5. When appropriate, the Systems Administrator will log in.
  6. Our Support Agent will remotely direct you to the Invenias API and assist in sending the request to the server to start the process.

The login you use will be the only recipient of communications for the backup. This User will be required to initiate the request and manage the whole process, as communications cannot be sent to any other user account.

You will need access to the login email address for communications during the Backup Process.

The Approval Process

  1. Once initiated, the Bullhorn Accounts Team will be notified that the request has been triggered
  2. An email confirming that the process was authorised by the Accounts Team will then be sent to the email address of the User that initiated the request
  3. This in-turn starts the data compilation process
  4. Once the backup compilation has completed you will receive an automated completion email
  5. The same Systems Administrator User must then contact inveniassupport@bullhorn.com who will reconnect and assist with the backup data download.

The backup can only be approved, once the monthly subscriptions for your company have been paid for up front. If this is not your first backup, we will also need to have received payment for the backup before our Accounts team will approve.

The Download Process

  1. The backup download will only be available to you for 14 days after it's been compiled. After this time the data will be purged and further backup requests will need to be requested via inveniassupport@bullhorn.com.
  2. During this 14-day window our Support Team will reconnect with the User who made the request and install the software required to download the data
  3. The Microsoft Azure Storage Browser software (MS ASE) can be downloaded here and is the only method available for downloading the backup as this process is automated on the Azure platform
  4. We will only connect with the requester to initiate the download on that User's PC
  5. We will confirm the storage space requirements for the download and where you want the data saved.
  6. The download process will then start.

We can only check the data download size, once the compilation process has completed.