Documentation
    {{docApp.userSession.userId}}
    {{docApp.userSession.userName}}
    {{docApp.userSession.email}}
    Issuer : {{docApp.userSession.issuerInstance}}
    Expires : {{new Date(docApp.userSession.validUntil).toLocaleDateString()}}

{{docApp.title}}

{{docApp.description}}

INDEX

Documentation Library

Search for information on Hornbill Documentation.

{{docApp.searchError}}

{{docApp.searchResultFilteredItems.length}} results for "{{docApp.currentResultsSearchText}}" in {{docApp.searchFilterBySpecificBookTitle}}

Have questions about this site?

What is this site?

  • This website is Hornbill's new product documentation website and is currently under development.
  • It is intended that all existing and future public-facing documentation we produce will be available to search, browse and share.
  • Hornbill's current documentation is available at Hornbill Wiki but over time this content will be migrated to this documentation site.
  • Please feel free to have a look around at any time.

Why has Hornbill created this site?

  • Hornbill's products have moved on considerably since we introduced it almost 10 years ago. At the time, the MediaWiki tool was sufficient, but we have outgrown it.
  • Our customers are more enterprise focused and more self-sufficient than ever before, so for 2023 and beyond we have established a new documentation platform and team to drive our documentation initiative forwards.
  • We are aiming to deprecate the use of Hornbill Wiki for most Hornbill related documentation.
  • We want to enable our growing partner network with product resources and information, documentation beyond our Wiki approach is required.
  • We could definitely do with some help, and may even pay for some! If you have domain knowledge and would like to help, please check out our Hornbill Docs Contributor Guide and contact the Hornbill docs team at docs@hornbill.com.

What will this site be good for?

  • Community contribution will be facilitated, encouraged, and most welcome.
  • High quality documentation, will be kept up to date as rapidly as our products evolve.
  • Real-time content search and discovery.
  • Articles organized into books, books into libraries, creating a more natural and logical structure to our documentation.
  • Legacy API documentation and various other documentation sources will all be consolidated into a single unified documentation system.
  • Documentation available in browser as well as printable/viewable as PDF on demand.
  • Personalized documentation experience, allowing dark/light mode, article subscriptions, social media sharing and other useful features.
  • Almost all publicly available documentation on docs.hornbill.com will be open-source and available to fork on GitHub, allowing customers to derive their own custom documentation around Hornbill products should they wish to.

What is the timeline for this site?

  • We have taken the decision to publish and make available early, there is very little content at this time.
  • As and when we have completed/usable documentation, it will be published here.
  • We have a host of additional features we wish to add over time, so please watch this space.
  • We expect most of our existing documentation should be reviewed/migrated to docs.hornbill.com over the coming months.
  • The documentation project will be ongoing, will continue to expand, evolve and improve day-by-day.

{{docApp.libraryHomeViewProduct.title || docApp.libraryHomeViewProduct.id}}

{{docApp.libraryHomeViewProduct.description}}

  1. {{book.title}}

{{group.title || group.id}}

{{group.description}}

  1. {{book.title}}

{{group.title}}

{{book.title}}
More...

Business Continuity

Hornbills configuration of servers\services has been planned to ensure that their is no single point of failure, all services have fail over servers or spare capacity.

Business Continuity and Disaster Recovery plan

Hornbill are committed to providing customers with access to their subscribed services and data even in the event of a emergency or disaster. Our plan is designed so that in the worst possible case customers will be without access to instances for the minimum time possible whilst a full restore is carried out to a secondary data center.

In the event of a disaster or high impact issue the Cloud team have the option to invoke the Emergency plan. Once started this ensures additional resources are provided to the cloud team and non-critical work is suspended.

The plan is tested against 2 main scenarios at least once every year to ensure that in the case of Loss of Hornbill offices or Loss of Data Center we are able to continue to provide all services as expected.

Testing is performed remotely and its objectives are to show that we can continue to provide all services to existing customer, recreate the contents of 1 or more data centers in time specified in our SLAs and begin to provide all back end services used by Hornbill offices by the end of 1 working day.

Our ‘Maximum Data Loss Time Period’ or RPO is a maximum of 24 hours (or the time back to the last 23:00 backup). However, we aim for 15 minutes, as we replicate customer data at this frequency. Hornbill’s RTO ‘Recovery Time Objective’ in the event Hornbill has to invoke its DR (Disaster Recovery) plan is defined as

Emergency response to assess the level of damage, decide whether to invoke the plan and at what level, notify staff, etc. (to be completed within 1 – 2 business hours of the disaster)

  • Provision of an emergency level of service (within 4 business hours of the disaster)
  • Restoration of key services (within 8 business hrs of the disaster)
  • Recovery to business as normal. (within one week of the disaster)

The emergency level of service is to ensure our customers and their customers can use the Hornbill Services and applications with minimal disruption. To this end all Applications and databases will be restored however file attachments (Associated with emails, workspaces, Document Manager, or requests) might not be available, and search functionality will be limited.

Restoration of Key services will be to provide the customer with a fully working system and no difference from what they had before the DR plan was activated. All Applications, Databases, File Attachments, and functionality restored.

Recovery to business as Normal would only ever be needed should a true Disaster occur. This would include the total loss of 1 or more data centers AND Hornbill offices at the same time. The Recovery to business as Normal would ensure that all Hornbill services (both customer facing and internal) were fully restored).

Any outcomes\failings in the tests are noted and addressed within 1 month of the exercise and if necessary a new test scheduled.

A redacted version of the DR Plan is available on request.

Backups

All instances are replicated real time to a central server located within the same geographical location as the live instance and then nightly backups of these are taken and stored within S3 (again within same geographical location) every evening. The backup process is monitored\tested to ensure successful upload automatically and a manual restore of a random instance performed every month to ensure data integrity. In the event of the emergency plan being activated and needing to restore, we will first attempt to use the live replication and should that be unavailable (Unlikely) we would revert to the last nightly backup.

See also FAQ:Availability & Scheduled Maintenance

  • Version {{docApp.book.version}}
  • Node {{docApp.node}} / {{docApp.build}}
In This Document