# Changing \`--prefix\` on existing backup

**URL:** https://forum.duplicati.com/t/changing-prefix-on-existing-backup/485
**Category:** Support
**Created:** [September 7, 2017, 4:47pm UTC](https://forum.duplicati.com/t/changing-prefix-on-existing-backup/485 "2017-09-07T16:47:36Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![kenkendk](https://forum.duplicati.com/user_avatar/forum.duplicati.com/kenkendk/32/5305_2.png) [@kenkendk](https://forum.duplicati.com/u/kenkendk)
#### Post date: [September 11, 2017, 11:07am UTC](https://forum.duplicati.com/t/changing-prefix-on-existing-backup/485/2 "2017-09-11T11:07:49Z")

</div>

The `--prefix` option is meant to support multiple backups in the same directory, but I’ve found that most people have a hard time keeping things separated, so I recommend that you do not use `--prefix` if you can avoid it.

The problem when changing the prefix like you did, is that the database stores each filename in the database to guard against changes on the destination. When you rename the files, you trigger this guarding operation.

You can use the `repair` command to recreate the database, and it will rebuild the local database using the filenames found on the remote destination.

Anything that confuses should be fixed, but I think we should stick to the “do not modify the remote destination” rule.

> [@JonMikelV](#):
>
> Oh - and speaking of the --prefix field, I tried blanking the field and instead of the default duplicati value returning (as I expected) the value true appeared. So I guess that might be a legitimate “bug”.

Yes, that really sounds like a bug, but I think it should not be possible to set an empty prefix as that makes it hard to parse the filenames reliably.

---

_[View the full topic](https://forum.duplicati.com/t/changing-prefix-on-existing-backup/485)._