> For the complete documentation index, see [llms.txt](https://kb.hostednetwork.com.au/support/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.hostednetwork.com.au/support/services/cloud/backup-as-a-service.md).

# Backup as a Service

This article contains general information and notes about the BaaS solution

## Veeam Documentation

For complete Veeam Cloud Connect documentation please see the [Veeam Cloud Connect Tenant Guide](https://helpcenter.veeam.com/docs/backup/cloud/cloud_connect_user_guide.html?ver=120)

{% hint style="warning" %}
Backup as a Service requires Veeam Backup and Replication version 12 or higher
{% endhint %}

## Requirements

To successfully complete configuration of the BaaS solution you will need the following:

* A completed Backup as a Service order with Hosted Network
* Access to the Veeam Backup & Replication server for your customer (if using BaaS as a cloud repository for an existing Veeam deployment)
* Administrative access to any servers or workstations you need to install a Veeam Agent on (if backing up directly to cloud rather than using VBR server)
* Access to any advanced firewalls or UTM in use at the customer site in case opening of ports or adjustment of security policies is required for backups to succeed


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://kb.hostednetwork.com.au/support/services/cloud/backup-as-a-service.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.