You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cloudstack.apache.org by "weizhouapache (via GitHub)" <gi...@apache.org> on 2023/02/14 09:33:58 UTC
[GitHub] [cloudstack] weizhouapache commented on issue #6827: Zero size recurring snapshots piling up after server is shutdown
weizhouapache commented on issue #6827:
URL: https://github.com/apache/cloudstack/issues/6827#issuecomment-1429413712
what I understand, if the volume is not changed after last snapshot, then do not create snapshot.
For example, in a period,
- disk is not attached
- disk is attached but vm is stopped
Each volume has the following info in database
```
attached: NULL
updated: 2023-02-13 09:03:59
removed: NULL
state: Ready
```
Each vm instance has the info
```
update_time: 2023-02-08 13:49:22
created: 2023-01-21 15:42:52
removed: NULL
...
power_state: PowerOn
power_state_update_time: 2023-02-13 17:06:59
power_state_update_count: 3
power_host: 1
```
for snapshots
```
uuid: ad841072-70f0-4761-90af-6a718a06872a
snapshot_type: 4
type_description: DAILY
size: 8589934592
created: 2023-01-05 00:13:21
removed: NULL
backup_snap_id: NULL
swift_id: NULL
sechost_id: NULL
prev_snap_id: NULL
```
I think it is feasible based on the information above.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@cloudstack.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org