> For the complete documentation index, see [llms.txt](https://docs.vega365.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vega365.com/nidhi/management-client/recording-server-page/outlook.md).

# Outlook

**Will footage stay safe if the cloud goes down? Does the upload schedule leave enough time? What should change?**

Based on what XProtect archived in the last 24 hours, the Outlook tab shows:

* How long this recording server can manage without the cloud.
* What to change so it lasts as long as you plan for.

The tab's name counts the changes, for example **Outlook (3 to change)**. A red or orange dot after it means one of them puts footage at risk.

<figure><img src="https://1044727958-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOkTZH1L3AaRU2hwQk4Ve%2Fuploads%2Fgit-blob-f85d67f5f41f53fb0463b897dcb929bc143b5496%2Fmc-recorder-outlook-rec-04.png?alt=media" alt="The Outlook tab"><figcaption></figcaption></figure>

## The three lines

The top of the tab has three lines. Each has a coloured dot:

* **Green** means all is well.
* **Orange** means it is worth a look.
* **Red** means footage is at risk.

Hover over a line to see the numbers behind it.

| Line                                                                                                             | What it tells you                                                                                                                                                                                                                                                                                                  | Colour                                                                                                                     |
| ---------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------- |
| **If the cloud goes down, nothing is lost for** *time* **— then** *profile* **starts losing its oldest footage** | How long XProtect can keep recording with the cloud down before it must delete footage that never reached the cloud. It also names the storage profile that runs out first, and why (its live storage reaches its **Maximum size**, or its disk is full). The Dashboard shows the same figure as **Outage cover**. | <p>Red under 4 hours.<br>Orange under 24 hours.<br>Green from 24 hours.</p>                                                |
| **Uploads keep up: footage reaches the cloud within** *time*                                                     | Whether the uploads keep up with what XProtect archives, and how long footage waits on the recorder before it reaches the cloud.                                                                                                                                                                                   | <p>Orange when footage waits more than 12 hours, or the headroom is under 1.5×.<br>Red when the uploads can't keep up.</p> |
| **After a** *time* **outage, everything is in the cloud again within** *time*                                    | How long the recorder takes to catch up after the longest outage it can survive. XProtect archives everything it held in one run, and Nidhi uploads it as fast as the upload schedule allows. Until it has caught up, a second outage would have less time.                                                        | <p>Orange over 12 hours.<br>Red over 48 hours.</p>                                                                         |

### When something is wrong

A line can also read one of these:

* **Uploads can't keep up:** *size* **a day more waits to upload — footage is lost in about** *time* **even with the cloud up**
  * The upload schedule lets through less than XProtect archives. What isn't uploaded fills the cloud drive cache until its disk is full.
  * Allow more upload on the [Bandwidth schedule](https://docs.vega365.com/nidhi/management-client/recording-server-page/bandwidth-schedule.md).
* **Footage waits up to** *time* **to upload — longer than** *profile*'s **cloud archive keeps it: some never gets a copy in the cloud**
  * Footage stays in the cache so long that its retention ends before it is uploaded.
  * Allow more upload, or keep footage longer in that cloud archive.
* **... not known yet**
  * There are no archive runs to the cloud to measure yet, or the connection hasn't been measured.
  * Wait for XProtect's first archive run to the cloud, or click **Test upload speed** on the [Traffic](https://docs.vega365.com/nidhi/management-client/recording-server-page/traffic.md) tab.

## Without the cloud, per profile

One bar per storage profile. It shows how long the profile can record without the cloud if the cloud fails at the worst moment (just before an archive run), and what limits it, for example *13 days at worst · then its oldest footage is lost (size limit reached)*.

The shortest bar sets the first of [the three lines](#the-three-lines). To lengthen a bar, raise that profile's live storage **Maximum size** in XProtect (if its disk has room), or give it more disk.

## What to change

This list shows what to change on this recording server, most urgent first. Each suggestion has a coloured dot:

* **Red** means footage is at risk.
* **Orange** means it is worth doing.
* **Blue** is advice only.

Hover over a suggestion to see the numbers behind it.

### How long to plan for

The suggestions are worked out for the time set in **Plan for** *time* **without the cloud**. This is how long the recording server should manage if the cloud is down.

1. Choose a time from the list (1 hour to 30 days), or type one, such as *36 h* or *2 days*.
2. Press Enter.

The time is saved on the recording server. It is the same setting as in the recording server's row under **Suggestions** on the Dashboard.

### Storage

| Suggestion                                                                          | Why                                                                                                             | What to do                                                                                                                                                                                                                                                 |
| ----------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Raise** *profile*'s *storage* **size limit to about** *size*                      | The profile's **Maximum size** is too small for the planned time without the cloud. Its disk has room for more. | Raise the **Maximum size** in XProtect (**Recording Servers >** *recorder* **> Storage**). The hover shows how the size is worked out. It is the planned time at the profile's recording rate, plus what it already holds when the cloud fails, plus 10 %. |
| *Profile* **needs about** *size* **on** *disk* **for** *time* **without the cloud** | The same, but the disk doesn't have the room.                                                                   | Add disk space, record less (lower frame rate or resolution), or keep footage on that disk for less time.                                                                                                                                                  |
| **Free space on** *disk* **lasts only** *time* **without the cloud**                | The profile has no size limit, so its disk fills up first. Other profiles on the same disk count too.           | Add disk space, or move a storage profile to another disk.                                                                                                                                                                                                 |

### Upload

| Suggestion                                                                                                                                                                       | Why                                                                                       | What to do                                                                                                                                                              |
| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| <p><strong>The upload schedule can't keep up with what XProtect archives</strong><br><strong>barely keeps up</strong><br><strong>Little room in the upload schedule</strong></p> | The upload limits you set let through too little.                                         | Allow more upload on the [Bandwidth schedule](https://docs.vega365.com/nidhi/management-client/recording-server-page/bandwidth-schedule.md), especially during the day. |
| **Footage waits up to** *time* **on the recorder before it is in the cloud**                                                                                                     | The upload schedule holds footage back for a long time.                                   | Allow more upload in the busiest hours.                                                                                                                                 |
| <p><strong>The upload is too slow for what XProtect archives to the cloud</strong><br><strong>Little upload headroom</strong></p>                                                | The connection itself is too slow, even with no limits.                                   | Get a faster connection, or have fewer cameras archive to the cloud.                                                                                                    |
| **Archive more often to spread the uploads**                                                                                                                                     | Each archive run is so large that uploading it takes most of the time until the next run. | Archive more often in XProtect (for example every hour instead of every 4 hours). Smaller runs upload sooner and need a smaller cache.                                  |

### Cache

| Suggestion                                                                                     | Why                                                                                     | What to do                                                  |
| ---------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------- | ----------------------------------------------------------- |
| **Raise the cloud drive's cache from** *size* **to about** *size*                              | The cache must hold two archive runs (one uploading while the next arrives), plus 10 %. | See [Changing the cache](#changing-the-cache).              |
| **Cloud drive cache:** *size* **is enough**                                                    | The cache is big enough for the largest run in the last 24 hours.                       | Nothing. This is advice only.                               |
| **The cache's disk** *disk* **has room for only** *size* **of the** *size* **the cache needs** | The disk is too full for the cache.                                                     | Free space on that disk, or move the cache to another disk. |
| **Move the cloud drive's cache off** *disk*                                                    | The cache shares a disk with XProtect's recordings. If one fills up, so does the other. | Move the cache to another disk.                             |

### Footage in the cloud

| Suggestion                                                                    | What to do                                                                                                                 |
| ----------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------- |
| **Check** *size* **of footage XProtect left in the cloud past its retention** | Review it in [Cloud Cleanup](https://docs.vega365.com/nidhi/management-client/recording-server-settings.md#cloud-cleanup). |

### When nothing needs to change

When storage, upload and cache already cover the planned time, the list shows **Nothing to change: storage, upload and cache fit** *time* **without the cloud**.

### Changing the cache

The cache's size and folder are chosen during setup. After that, the only way to change them is:

1. Wait until nothing is waiting to upload.
2. Use [Reset Configuration](https://docs.vega365.com/nidhi/management-client/recording-server-settings.md#reset-configuration).
3. Set the recording server up again on the same bucket and folder.

The footage in the cloud stays where it is, and XProtect finds it again.

## Related

* [When the cloud is down](https://docs.vega365.com/nidhi/how-nidhi-works.md#when-the-cloud-is-down)
* [The local cache](https://docs.vega365.com/nidhi/how-nidhi-works.md#the-local-cache)
* The Dashboard's [Suggestions](https://docs.vega365.com/nidhi/management-client/dashboard.md#suggestions) show the same for every recording server.
