# הצעות לגיבוי - צור שלט מהבהב גדול כדי לא לשנות את שם הגיבויים שלך

**URL:** <https://meta.discourse.org/t/backup-suggestions-make-a-large-flashing-sign-to-not-rename-your-backups/180282>\
**Category:** Product Support\
**Created:** [19 בפברואר,‏ 2021,‏ 1:09am UTC](https://meta.discourse.org/t/backup-suggestions-make-a-large-flashing-sign-to-not-rename-your-backups/180282 "2021-02-19T01:09:39Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)\
**Post date:** [19 בפברואר,‏ 2021,‏ 1:56pm UTC](https://meta.discourse.org/t/backup-suggestions-make-a-large-flashing-sign-to-not-rename-your-backups/180282/2 "2021-02-19T13:56:26Z")

</div>

It’s fairly rare that someone has this problem. It’s usually pretty easy to resolve. Sending a monthly notice about something that affects virtually no one doesn’t seem very productive.

I think it’s possible to figure out what the name should be by information that’s in the archive. Maybe that’s what you really want.

I think that you might be able to restore the database by hand and then run the migration,for example.

---

_[View the full topic](https://meta.discourse.org/t/backup-suggestions-make-a-large-flashing-sign-to-not-rename-your-backups/180282)._
