> For the complete documentation index, see [llms.txt](https://help.bioinsight.illumina.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.bioinsight.illumina.com/partek/partek-flow/user-manual/server-management/backing-up-the-database.md).

# Backing Up the Database

![image](https://github.com/illumina-swi/partek-docs/assets/167460925/979641a3-c563-4fbd-a723-e0caea6b2800)

## Linux

### Open a Linux terminal and enter the following commands.

1. Obtain root access:

```
$ sudo su  
```

2. Change to the user account that runs Partek® Flow® . Suppose it is user account *flow*, then\_:\_

```
$ su flow
```

3. Then the default home directory should be/home/flow. Run the following command to make the backup database in home/flow directory, the archived file name is flowdbbackup.tar.gz:

```
$ tar -czvf flowdbbackup.tar.gz .partekflow/
```

4. Log out of the user account that runs Flow:\
   **Ctrl+D**

## MacOS

### Open a Terminal window on the home directory of the user that installed Partek Flow.

1. Run the following command to make the backup database in user's home directory

```
$ tar -czvf flowdbbackup.tar.gz .partekflow/
```

2. The archived file name is flowdbbackup.tar.gz.

## Additional Assistance

If you need additional assistance, please visit [our support page](http://www.partek.com/support) to submit a help ticket or find phone numbers for regional support.


---

# 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://help.bioinsight.illumina.com/partek/partek-flow/user-manual/server-management/backing-up-the-database.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.