> 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/moving-data.md). # Moving Data If you wish to move a Partek Flow project data from one disk to another and continue using the project, please follow the steps below: 1. Use rsync to copy the project data from the old disk to the new disk. For example, if you wish to move Project A from an internal disk to an external drive mounted as hdd: ``` $ rsync -avr /home/user/FlowData/Project_A /mnt/HDD/FlowData2/Project_A ``` Using rsync -avr guarantees that the time stamps would not change.\\ 2. In Partek Flow, logon as a user with Admin privileges. Go to **Settings**>**Directory permissions** page 3. In the **Directory Reassignment** section, type the Former directory and select the Current directory (Figure 1) For example: * Former directory: /home/user/FlowData/Project\_A * Current directory: /mnt/HDD/FlowData2/Project\_A

Figure 1: Directory Reassignment

4. Select **Reassign** button 5. Open the project. * In the Analyses tab, check if the Project disk space on the lower right has been updated * In the Data tab, check the project output directory has changed to the new directory\\ 6. You can now remove the former directory ## 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/moving-data.md?ask=&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.