# Backup and migration

**URL:** <https://forum.collaboraonline.com/t/backup-and-migration/1510>\
**Category:** Installation & Configuration\
**Tags:** resolved, answered\
**Created:** [December 17, 2022, 10:37am UTC](https://forum.collaboraonline.com/t/backup-and-migration/1510 "2022-12-17T10:37:54Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![garoj](https://avatars.discourse-cdn.com/v4/letter/g/f17d59/32.png) [@garoj](https://forum.collaboraonline.com/u/garoj)\
**Post date:** [December 17, 2022, 10:37am UTC](https://forum.collaboraonline.com/t/backup-and-migration/1510/1 "2022-12-17T10:37:54Z")

</div>

Hello, everyone.

I’ve been testing Collabora online for a few months now.  
(CODE, Debian 10, package from ppa repository [Index of /repos/CollaboraOnline/CODE-debian10](https://www.collaboraoffice.com/repos/CollaboraOnline/CODE-debian10))

It works really well and everyone loves it. Updates where flawlessly, no problems so far. Amazing! MS services are 100% gone as soon as I roll out CODE to productive.

I still have two problems to solve here: Backup and migration.

In the official documentation and also here in the forum there is hardly anything to read about it. We checked at [Search — SDK https://sdk.collaboraonline.com/ documentation](https://sdk.collaboraonline.com/search.html?q=backup) and in the SDK PDF Manual.

Where can I find information about:

1. Backup: directories, files, configuration, dump of database …
2. Migration: how to move to a “bigger” server if scaling becomes a thing.

Many thanks in advance.

---

<div class="post-metadata">

**Author:** ![bearon](https://avatars.discourse-cdn.com/v4/letter/b/9de053/32.png) [@bearon](https://forum.collaboraonline.com/u/bearon)\
**Post date:** [December 19, 2022, 2:57am UTC](https://forum.collaboraonline.com/t/backup-and-migration/1510/2 "2022-12-19T02:57:18Z")

</div>

1. The configuration files are in `/etc/coolwsd`, from the perspective of CODE, those are the only ones you may want to back up.

2. Install the packages on the other server, add the configuration files, and you’re good to go. If you want to scale over multiple servers, you could consider a load balancing setup, but the migration part still only consist of the config files — again, from the perspective of CODE.

---

<div class="post-metadata">

**Author:** ![garoj](https://avatars.discourse-cdn.com/v4/letter/g/f17d59/32.png) [@garoj](https://forum.collaboraonline.com/u/garoj)\
**Post date:** [December 19, 2022, 9:04am UTC](https://forum.collaboraonline.com/t/backup-and-migration/1510/3 "2022-12-19T09:04:10Z")

</div>

Hello and thank you for the answer.

I had the completely wrong assumption that the documents are stored on the coolwsd server.

We use Moodle to communicate with the coolws server (works lik a charm). The data is kept locally on the Moodle server, which completely solves the problem of backup and migration.

---

<div class="post-metadata">

**Author:** ![darshan](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.collaboraonline.com/darshan/32/2230_2.png) [@darshan](https://forum.collaboraonline.com/u/darshan)\
**Post date:** [July 18, 2024, 2:16pm UTC](https://forum.collaboraonline.com/t/backup-and-migration/1510/4 "2024-07-18T14:16:45Z")

</div>

Closed on July 18, 2024, 2:16pm UTC


