I need info on Backup setting

See attached picture.

I need some help understanding the backup settings and what each of these options actually does.

What I’m trying to accomplish is fairly simple:

  • Keep approximately 2 weeks of backups

  • Perform a new full backup once a week

  • Run incremental backups in between the weekly full backups

  • Automatically delete/overwrite the older backups as they fall outside the two-week retention period

Basically, I’d like to have two weeks of restore points available at any given time without unnecessarily filling up the backup storage.

Can you explain which of these settings I should use to accomplish this and how the retention/overwrite process works?

Thank you.

AI asked me to upload that picture and said it would help me figure it out and it did This is what it answered. Does this look right.

Yes. This is HestiaCP’s newer incremental backup system using Restic, and the terminology is a little confusing. Hestia’s documentation confirms that incremental backups use a Restic repository and separate retention values for snapshots/daily/weekly/monthly/yearly backups.

For what you described — backup every day, keep about two weeks, with weekly recovery points — I would configure the section in your screenshot roughly like this:

Setting Recommended Meaning
Enable incremental backup Yes Turns on Restic incremental backups
Repository /backup/restic* Where the Restic repository is stored
Snapshots 14 Keep the most recent 14 snapshots
Keep last daily backups 14 Keep daily restore points for 14 days
Keep last weekly backups 2 Keep 2 weekly restore points
Keep last monthly backups -1 Don’t retain additional monthly points
Keep last yearly backups -1 Don’t retain additional yearly points

*The exact Repository value is the one thing I would verify before entering anything, because Hestia supports local and remote Restic repositories and its configuration depends on where you want these incremental backups stored.

The important part: this isn’t traditional Full → Incremental → Incremental

With Restic, you don’t really need to think of it as:

Sunday: FULL
Monday: Incremental
Tuesday: Incremental
Wednesday: Incremental…

Each Restic run creates a complete restore-point snapshot, but it only stores new/changed data because Restic deduplicates the underlying data. So every day’s snapshot behaves like a full backup when you restore it, without storing another complete copy of everything.

So I would not try to force a weekly full backup inside this Incremental Backups section.

What “Snapshots” means

This is the overall keep-last count.

For example, if the backup runs once every night:

Snapshots = 14

means you’re telling Restic to preserve the most recent 14 snapshots.

The Daily/Weekly/Monthly/Yearly fields are additional retention rules. A snapshot can qualify under one or more of those rules. Hestia’s community explanation specifically notes that these retention categories interact rather than creating completely separate sets of backups.

One correction to your screenshot

You currently have:

Monthly = 0
Yearly = 0

I would not use 0 if your intention is to disable those retention categories. Hestia’s discussion of these settings indicates that a negative value such as -1 disables that retention rule.

So I’d use:

Snapshots: 14
Daily: 14
Weekly: 2
Monthly: -1
Yearly: -1

That gives you a straightforward two-week rolling backup strategy while still identifying weekly recovery points.

One other critical thing: Hestia warns that Restic generates an encryption key/config in /usr/local/hestia/data/users/{user}/restic.conf. Back that file up somewhere other than this server. Without the secret key, Hestia says it cannot restore the Restic backup if the server is lost or the user is deleted.

If you show me the rest of this screen below Yearly and your Panel Cronjobs screen, I can tell you exactly how I’d configure the whole thing, including what runs nightly, what runs weekly, and whether you should keep the old Hestia full backup enabled at all.

I am still having problem configuring backups. need some help.

First off a little confused There’s a backup setting underneath Users I attached a picture not sure exactly how works especially when there’s another backup setting under configuration I need help and clarification.

I have set the backup configuration see picture But I’m still only getting one back each night it’s not passing just the one backup I’m trying to set it for two weeks of backups. With a full image once a week incremental during the then I’m only getting one back each night.

The backups setting user packages are only for the full created via v-backup-user backup

If you enable incremental backups for the user:
14 snapshots / 14 daily backups 2 weekly backups

Still only 1 backup

The user package only allows 1 backup

The incremental back up is a separate feature. also able to enable in the user packages

And like I said yes I would like to do 14 snapshots / 14 daily backups 2 weekly backups, So how do I do What do I enable What do I add What do I do? thank you

As they said your package have 1 of 1 available backup. Go to your packages, edit this package you want and add permission for 16+ backups.

You will need to update in your user package:

Backups is for the old “Backup”

Incremental Backups for the Restic backup settings

Thank you

ok, Now getting 7 full back which I have it set to only do two full backup one weekly and the rest incremental a total of 14. I’m getting 7 full back and no incremental Can you look at the pictures and see if figure out what’s going on? I set backup solutions for entire businesses I don’t know why this is so confusing. I can tell you having to look in three different places to set the backup is not the best. But anyways it’s not doing what I’m trying to do.

Show the output of these commands:

ls -la /backup
v-backup-user-restic admin
root@webserver:~# ls -la /backuptotal 36527056drwxr-xr-x  2 root      root        4096 Sep  6 22:01 .drwxr-xr-x 21 root      root        4096 Aug  7 20:41 ..-rw-r-----  1 hestiaweb admin 4959621120 Sep  1 22:01 admin.2026-09-01_22-00-57.tar-rw-r-----  1 hestiaweb admin 4980398080 Sep  2 22:01 admin.2026-09-02_22-01-02.tar-rw-r-----  1 hestiaweb admin 4978708480 Sep  3 22:01 admin.2026-09-03_22-01-01.tar-rw-r-----  1 hestiaweb admin 4987258880 Sep  4 22:01 admin.2026-09-04_22-00-57.tar-rw-r-----  1 hestiaweb admin 4952135680 Sep  5 06:56 admin.2026-09-05_06-56-18.tar-rw-r-----  1 hestiaweb admin 6278840320 Sep  5 22:01 admin.2026-09-05_22-01-14.tar-rw-r-----  1 hestiaweb admin 6266695680 Sep  6 22:01 admin.2026-09-06_22-01-12.tar-rw-rw----  1 root      root        1922 Sep  6 22:01 admin.log----
root@webserver:~# v-backup-user-restic admin
created restic repository 32789335df at /backup/admin

Please note that knowledge of your password is required to access
the repository. Losing your password means that your data is
irrecoverably lost.
-- SYSTEM --
2026-09-07 07:34:43 admin.conf
2026-09-07 07:34:43 stats.log
2026-09-07 07:34:43 history.log
2026-09-07 07:34:43 pam


-- WEB --
2026-09-07 07:34:44 webserver.pacificdatacom.net
2026-09-07 07:34:44 rocketfuelpump.com
2026-09-07 07:34:44 flometrics.com
2026-09-07 07:34:44 pacificdatacom.net
2026-09-07 07:34:44 artisticimages.com
2026-09-07 07:34:44 whelanlake.org
2026-09-07 07:34:44 alyssasnaturesanctuary.org
2026-09-07 07:34:44 alyssasnaturesanctuary.com
2026-09-07 07:34:44 chilldyne.com
2026-09-07 07:34:44 whelanlake.com
2026-09-07 07:34:44 *** 10 domains ***

-- MAIL --
2026-09-07 07:34:44 johnzapf.com
2026-09-07 07:34:44 *** 1 domain ***

-- DB --
2026-09-07 07:34:44 admin_27558 (mysql)
/home/admin/backup//db/admin_27558/admin_27558.mysql.sql :  3.40%   (14346034 => 487979 bytes, /home/admin/backup//db/admin_27558/admin_27558.mysql.sql.zst)
2026-09-07 07:34:45 admin_rocketfuelpump_wp (mysql)
/home/admin/backup//db/admin_rocketfuelpump_wp/admin_rocketfuelpump_wp.mysql.sql : 21.04%   (11004371 => 2314915 bytes, /home/admin/backup//db/admin_rocketfuelpump_wp/admin_rocketfuelpump_wp.mysql.sql.zst)
2026-09-07 07:34:45 admin_chilldyne_wp (mysql)
/home/admin/backup//db/admin_chilldyne_wp/admin_chilldyne_wp.mysql.sql :  9.21%   (46781346 => 4307061 bytes, /home/admin/backup//db/admin_chilldyne_wp/admin_chilldyne_wp.mysql.sql.zst)
2026-09-07 07:34:46 admin_flometrics_wp (mysql)
/home/admin/backup//db/admin_flometrics_wp/admin_flometrics_wp.mysql.sql : 18.82%   (18220819 => 3429462 bytes, /home/admin/backup//db/admin_flometrics_wp/admin_flometrics_wp.mysql.sql.zst)
2026-09-07 07:34:47 admin_pacificdatacom_wp (mysql)
/home/admin/backup//db/admin_pacificdatacom_wp/admin_pacificdatacom_wp.mysql.sql : 18.06%   (13179859 => 2380324 bytes, /home/admin/backup//db/admin_pacificdatacom_wp/admin_pacificdatacom_wp.mysql.sql.zst)
2026-09-07 07:34:47 admin_artisticimages_wp (mysql)
/home/admin/backup//db/admin_artisticimages_wp/admin_artisticimages_wp.mysql.sql : 13.84%   (35589853 => 4927378 bytes, /home/admin/backup//db/admin_artisticimages_wp/admin_artisticimages_wp.mysql.sql.zst)
2026-09-07 07:34:48 admin_78076 (mysql)
/home/admin/backup//db/admin_78076/admin_78076.mysql.sql : 25.51%   (387224 =>  98778 bytes, /home/admin/backup//db/admin_78076/admin_78076.mysql.sql.zst)
2026-09-07 07:34:49 admin_WLDB (mysql)
/home/admin/backup//db/admin_WLDB/admin_WLDB.mysql.sql : 18.28%   (34590721 => 6323187 bytes, /home/admin/backup//db/admin_WLDB/admin_WLDB.mysql.sql.zst)
2026-09-07 07:34:49 admin_36799 (mysql)
/home/admin/backup//db/admin_36799/admin_36799.mysql.sql : 22.92%   (923853 => 211762 bytes, /home/admin/backup//db/admin_36799/admin_36799.mysql.sql.zst)
2026-09-07 07:34:50 admin_db_sanctuary (mysql)
/home/admin/backup//db/admin_db_sanctuary/admin_db_sanctuary.mysql.sql : 10.79%   (58094486 => 6265541 bytes, /home/admin/backup//db/admin_db_sanctuary/admin_db_sanctuary.mysql.sql.zst)
2026-09-07 07:34:51 admin_db_chilldyne (mysql)
/home/admin/backup//db/admin_db_chilldyne/admin_db_chilldyne.mysql.sql :  2.54%   (236883646 => 6013736 bytes, /home/admin/backup//db/admin_db_chilldyne/admin_db_chilldyne.mysql.sql.zst)
2026-09-07 07:34:53 *** 11 databases ***

-- CRON --
2026-09-07 07:34:54 *** 1 job ***
2026-09-07 07:34:54 Runtime: 1 minute
repository 32789335 opened (version 2, compression level auto)
created new cache in /root/.cache/restic
no parent snapshot found, will read all files
[0:00]          0 index files loaded

Files:       190572 new,     0 changed,     0 unmodified
Dirs:        32356 new,     0 changed,     0 unmodified
Added to the repository: 6.763 GiB (5.428 GiB stored)

processed 190572 files, 8.418 GiB in 9:16
snapshot 0f42cb58 saved
repository 32789335 opened (version 2, compression level auto)
Applying Policy: keep 14 latest, 14 daily, 2 weekly snapshots
keep 1 snapshots:
ID        Time                 Host                          Tags        Reasons          Paths        Size
----------------------------------------------------------------------------------------------------------------
0f42cb58  2026-09-07 07:34:54  webserver.pacificdatacom.net              last snapshot    /home/admin  8.418 GiB
                                                                         daily snapshot
                                                                         weekly snapshot
----------------------------------------------------------------------------------------------------------------
Timestamps shown in local time
1 snapshots

The restic repository was not created, it has been created now. From now on you should see the snapshots for the admin user.

Make sure to create an cronjob in /edit/server/hestiaweb/

Yes there’s one job showing up in incremental, so I assume it’s working. So now this seems to be doing incremental should I change backup number two 14?

So in addition to this I have to make a Cronjob also?

And where is the backup location(s) I want to keep track of that.

No, that number is only for normal backups.

Yes, you need to add a cronjob: Server settings → Configure → Panel Cronjobs and add something like this:

10 04 * * * sudo /usr/local/hestia/bin/v-backup-users-restic

As you added /backup/ as the dir for the incremental backups, the backups are there… /backup/YourUser/

Thank you for all you help