# Reordering Backups on Web Page?

**URL:** <https://forum.duplicati.com/t/reordering-backups-on-web-page/14774>\
**Category:** Support\
**Created:** [July 29, 2022, 3:50pm UTC](https://forum.duplicati.com/t/reordering-backups-on-web-page/14774 "2022-07-29T15:50:02Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![kmand](https://forum.duplicati.com/letter_avatar_proxy/v4/letter/k/e68b1a/32.png) [@kmand](https://forum.duplicati.com/u/kmand)\
**Post date:** [July 29, 2022, 3:50pm UTC](https://forum.duplicati.com/t/reordering-backups-on-web-page/14774/1 "2022-07-29T15:50:02Z")

</div>

I have quite a few different backups, some daily some less frequent. Their appearance on the web page in the order they were created, while I would like to order them by frequency.

Is there any way to change the web page ordering?

---

<div class="post-metadata">

**Author:** ![JimboJones](https://forum.duplicati.com/letter_avatar_proxy/v4/letter/j/e5b9ba/32.png) [@JimboJones](https://forum.duplicati.com/u/JimboJones)\
**Post date:** [July 29, 2022, 6:52pm UTC](https://forum.duplicati.com/t/reordering-backups-on-web-page/14774/2 "2022-07-29T18:52:38Z")

</div>

There is a feature request sitting on Git Hub to add sort functionality but as it stands there is no way to sort jobs in the list.

---

<div class="post-metadata">

**Author:** ![ts678](https://forum.duplicati.com/letter_avatar_proxy/v4/letter/t/8491ac/32.png) [@ts678](https://forum.duplicati.com/u/ts678)\
**Post date:** [July 30, 2022, 9:04pm UTC](https://forum.duplicati.com/t/reordering-backups-on-web-page/14774/3 "2022-07-30T21:04:57Z")

</div>

Yeah, no easy way. See below for hard way:

The original post leads to the crude solution. Delete them and create them again by frequency.

Make note of the [Database](https://duplicati.readthedocs.io/en/latest/03-using-the-graphical-user-interface/#database-management) for the backup, [Export to file](https://duplicati.readthedocs.io/en/latest/03-using-the-graphical-user-interface/#exporting-a-backup-job-configuration), `Add backup` based on import of that,  
and either copy the old database to the newly assigned database path or move path to old DB.

Either way, be careful of scheduling. You don’t want backups running before things are fully set.  
I suppose you prefer schedule present to export, but maybe unschedule+save old job after that.

To keep new clone from running too soon, the pause control can probably pause until DB is set,  
or move the run schedule forward before job save to have time to get DB set up before run time.
