I confirmed my 'volume snapshot policy' for 'none' was -enable=false.
... and yes, these snapshots do seem to line up with the confuration backups that are occuring. Hadn't thought of that.
However, while not a big deal, I've got a pair of clusters (both installed as 8.3.2) and I'm watching and comparing vol0 snapshots and sys-conf-backup settings. I'm seeing one system tending to retain just one of these named (.tmp.bk*) snapshots while the other one retains up to 6 I think (2 of each kind: 8hour,daily,weekly). However, I'm gonna keep watching it as I played around with vol0 size yesterday after getting some aggr0 space-util alerts that look like they cooresponded in time to when these backups run. Could be the backups where aborting and not cleaning up snapshots.
I'd like to move the focus of this topic from 'mystery snapshots' to the 'configuration backup process' running in cDOT. As a result of researching the above issue I've come upon another fact: I want to tune down the system configuration process and don't see a way to do it.
Important note: this question is somewhat specific to ONTAP Simulators because I don't think a normal system running on FAS hardware would have this same issue. But I'm running qty=2 1-node-cluster VMs (cdot 8.3.2 & 9.0) on the same ESXi hypervisor (quad-core Xeon, 3.3Ghz, on a single-drive SATA datastore). Sometimess I run qty=3 cDOT VMs. So when the sys-config-backup kicks off, I have 2 or 3 ONTAPs backup up (hammering) their configurations on vol0's on that single ESX with a single disk.
FWIW: The .tmp.bk snapshots (orig topic of this discussion) have disappeared after I resolved the aggr0 space issue I previously had. But now I've been watching the 'system configuration backup' settings and files more closely. Everything appears to be running fine with the sys-conf-backup process, HOWEVER, I'm now more aware of sys-conf-backup and think it is hosing me every morning at 10:15am. It probably hoses me at midnight, 2am and 6pm too but I'm not around then :-). Below are some harvest/grapha graphs over 24-hours showing sys-conf-backup process hammering both vol0s and it seems to take (when they compete) 1.5-hours to complete.
I'm not complaining ... just looking for a way to control better. I've played with the 'system config backup' commands but all I see is a way to control the how many of the backup files are retained of each type ... and I can't say 0 (zero) to turn it off complelety for type (-numbackups1|2|3). What I thought I would do is either chnage the Schedule-1 from '8hour' to 'none' or create a new schedule completely for Schedule-1 that didn't fire off during the day.
The only thing I can think of now is to change the system-wide schedule called '8hour' to not include the 10am setting ... but I don't think it's wise to change a system-wide schedule just for this one thing as I don't know what else might be using it.
Am I missing anything? other suggestions? (Note: I even explored advanced and diag mode but still do not see a way)
PS: Harvest/Graphana graphs showing both my aggr0s getting hammerer for 1.5 hours. (the 00:10 is the daily, the 2:15am, 10:15am and 18:15pm are the 8hour 'ly ... I'd like to eliminate the 8hour 'ly ones. Any suggestions?
Thanks Justin, so I just went ahead and decided to chnage my 8hour 'ly schedule and it nicely warned me exactly what else was using that schedule. In my case, nothing. So I went ahead and set 8hour down to just a 6:15pm backup. I think tha should temper the situation for my environment.