> For the complete documentation index, see [llms.txt](https://central-docs.mymagic.my/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://central-docs.mymagic.my/other-topic/data-handling-management/data-backup.md).

# Data Backup

{% hint style="info" %}
**Policy 1.1.1**

Data backup from the MaGIC central database shall be maintained for two (2) years.
{% endhint %}

* Main Server is backup on daily basis to another cloud server
* All backup performs an auto check when completed to ensure the created backup copy is working as expected

### SOP

1. TI Unit backup data from main server on a daily basis. 
2. TI Unit check that backup performed is kept in another cloud server. 
3. TI Unit checks backup system status in main server. If backup is unsuccessful, proceed to Step 4. If backup is successful, proceed to Step 5. 
4. TI Unit identifies the issue resulting in unsuccessful backups for rectification and prceed to re-perform backup procedures. Return to Step 2.
5. TI Unit maintains backup data within the stipulated duration outlined in Policy 1.1.1.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://central-docs.mymagic.my/other-topic/data-handling-management/data-backup.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.