Bug #54

Cannot create auto-snap service with a 'keep-up-to' greater than 1

Added by Ryan W 5 months ago. Updated 5 months ago.

Status:Closed Start:March 17, 2010
Priority:High Due date:
Assigned to:Anatoly Legkodymov % Done:

0%

Category:-
Target version:-

Description

I'm trying to run an Autosnap service to take a snapshot of a ZVOL I have every minute and keep up to 10 of them. However each time I create the auto-snap service it reverts back to a 'keep-up-to' value of 1. This is with 3.0.0. Beta 1

History

Updated by Ryan W 5 months ago

[WARNINGS]
link-id not found -  mar 17 10:36:02 (zfs-auto-snap, 2547)     pool1/zvol@snap-minute-1-2010-03-17-1035: destroyed as per retention policy 
link-id not found -  mar 17 10:37:02 (zfs-auto-snap, 2601)     pool1/zvol@snap-minute-1-2010-03-17-1036: destroyed as per retention policy 
link-id not found -  mar 17 10:38:02 (zfs-auto-snap, 2656)     pool1/zvol@snap-minute-1-2010-03-17-1037: destroyed as per retention policy 

[ Mar 17 10:35:04 (zfs-auto-snap, 2501) pool1/zvol@snap-minute-1-2010-03-17-1035 OK ] [ Mar 17 10:36:02 (zfs-auto-snap, 2547) pool1/zvol@snap-minute-1-2010-03-17-1035: destroyed as per retention policy ] [ Mar 17 10:36:04 (zfs-auto-snap, 2547) pool1/zvol@snap-minute-1-2010-03-17-1036 OK ] [ Mar 17 10:37:02 (zfs-auto-snap, 2601) pool1/zvol@snap-minute-1-2010-03-17-1036: destroyed as per retention policy ] [ Mar 17 10:37:04 (zfs-auto-snap, 2601) pool1/zvol@snap-minute-1-2010-03-17-1037 OK ] [ Mar 17 10:38:02 (zfs-auto-snap, 2656) pool1/zvol@snap-minute-1-2010-03-17-1037: destroyed as per retention policy ] [ Mar 17 10:38:04 (zfs-auto-snap, 2656) pool1/zvol@snap-minute-1-2010-03-17-1038 OK ]

Updated by Ryan W 5 months ago

Ok, this seems like an NMV bug. If I make the auto-snap in NMC it works (snapshotting every minute). The problem is it's no longer "Keep X snapshots", it's KeepDays (days of snapshots). The NMV seems to still be trying to write keep-up-to into the snapshot service and is not reading the proper variable (keepdays) now.

Updated by Dmitry Yusupov 5 months ago

  • Status changed from New to Assigned
  • Assigned to set to Anatoly Legkodymov

Updated by Anatoly Legkodymov 5 months ago

  • Status changed from Assigned to Closed

Retention policy revised

Auto-snap: keep_days parameter defines number of days to keep snapshots on appliance.

Auto-tier: keep_days parameter defines number of days to keep snapshots on local appliance. Local appliance is the source appliance if service is local-to-remote. If service is remote-to-local, local appliance is destination.

Auto-sync: keep_days parameter defines number of days to keep snapshots on both ZFS systems.

If service is already created by previous versions of appliance, 'keep_days' property will be calculated during first run of upgraded service. New 'keep_days' value is based on old 'keep' value. For second, minute, hourly services new 'keep_days' value will be equal to 1 day. For daily, monthly services new 'keep_days' property will be translated by multiplication of 'keep' and 7 and 30 accordingly. Please check that new 'keep_days' value fits your needs by issuing command: nmc$ setup auto- : property keep_days

Updated by Ryan W 5 months ago

The problem is, if you look at my snap-logs that even with a "keep_days" value of 1, it's deleting my minute snapshots every 1 minute. It should, by all intensive purposes allow me to keep 1440 snapshots if I take 1 per minute for 1 full day.

Also, the GUI verbage needs to change from "keep up to" to "keep for days" as to not confuse the end user.

Updated by Ryan W 5 months ago

[WARNINGS]
link-id not found -  mar 17 10:36:02 (zfs-auto-snap, 2547)     pool1/zvol@snap-minute-1-2010-03-17-1035: destroyed as per retention policy 
link-id not found -  mar 17 10:37:02 (zfs-auto-snap, 2601)     pool1/zvol@snap-minute-1-2010-03-17-1036: destroyed as per retention policy 
link-id not found -  mar 17 10:38:02 (zfs-auto-snap, 2656)     pool1/zvol@snap-minute-1-2010-03-17-1037: destroyed as per retention policy 

Ryan W wrote:

[ Mar 17 10:35:04 (zfs-auto-snap, 2501) pool1/zvol@snap-minute-1-2010-03-17-1035 OK ] [ Mar 17 10:36:02 (zfs-auto-snap, 2547) pool1/zvol@snap-minute-1-2010-03-17-1035: destroyed as per retention policy ] [ Mar 17 10:36:04 (zfs-auto-snap, 2547) pool1/zvol@snap-minute-1-2010-03-17-1036 OK ] [ Mar 17 10:37:02 (zfs-auto-snap, 2601) pool1/zvol@snap-minute-1-2010-03-17-1036: destroyed as per retention policy ] [ Mar 17 10:37:04 (zfs-auto-snap, 2601) pool1/zvol@snap-minute-1-2010-03-17-1037 OK ] [ Mar 17 10:38:02 (zfs-auto-snap, 2656) pool1/zvol@snap-minute-1-2010-03-17-1037: destroyed as per retention policy ] [ Mar 17 10:38:04 (zfs-auto-snap, 2656) pool1/zvol@snap-minute-1-2010-03-17-1038 OK ]

Updated by Anatoly Legkodymov 5 months ago

This ticket was opened on our internal tracker.. so this issue is being tracked.

Also available in: Atom PDF