Comments (14)
Hi,
I was thinking of adding in the vmid parameter the ability to specify the pool name using the 'pool-' prefix.
What do you think?
Best regards
from cv4pve-autosnap.
Well, actually it is possible to have a VM named "pool-1". So such prefix seems not to be a good idea.
"@" as prefix looks much nicer and is not ambiguous. :-)
from cv4pve-autosnap.
Hi,
actually, if you read the documentation, prefixes are already used.
--vmid The id or name VM/CT comma separated (eg. 100,101,102,TestDebian)
-vmid or -name exclude (e.g. -200,-TestUbuntu)
'all-???' for all VM/CT in specific host (e.g. all-pve1, all-\$(hostname)),
'all' for all VM/CT in cluster
from cv4pve-autosnap.
For compatibility maintaining old format and introduce new format:
'@pool-???' for all VM/CT in specific pool (e.g. @pool-customer1),
'@all-???' for all VM/CT in specific host (e.g. @all-pve1, @all-\$(hostname)),
'@all' for all VM/CT in cluster
from cv4pve-autosnap.
Look nice. :-)
...and what about "all vm's in a given pool on a specific node"? :-) :-) :-)
from cv4pve-autosnap.
The pool is unique in the cluster. Is not necessary to specify host
from cv4pve-autosnap.
...but node is not unique to the pool. You might want to do backup on one node only. (All vm's on that node in a particular pool.)
Actually this is reasonable. If you run cv4pve-autosnap in a cron on one node - everything goes fine until that node fails. Then your snapshots are not being created anymore, even through another nodes are still up. It is better idea to run cv4pve-autosnap separately on every node - so that every node takes care of its own VMs only. So you need to "snapshot all vm's in a given pool, on a specific node only".
from cv4pve-autosnap.
It is not necessary to install cv4pve-autosnap internally of node but externally this use API.
The VMs in a cluster are as unique as the pools, even if the node dies everything works. You must specify in the --host parameter to use all the nodes of the cluster in the form "host[: port],host1[:port],host2[:port]"
Installation outside the cluster is preferred.
from cv4pve-autosnap.
Good point. :-)
But... anyway it's still possible to install and use cv4pve-autosnap directly on a node. And I sure people do it. And when they do... they might want to separate processing "by node".
from cv4pve-autosnap.
when you execute cv4pve-autosnap it is not important which node you run it on because it will snap the vms that are specified in the -vmid parameter, as the vms are in the custer (even if only one node). What you want is perhaps something different. Give me some examples.
Best regards
from cv4pve-autosnap.
Execution is successful as long as it is executed at all.
Imagine: there are 2 nodes (node1, node2). cv4pve-autosnap is installed on node1 and automatically creates snapshots of all vms in a pool. The snapshots are created on all nodes. Everything works.
Now: Node1 goes down. Node2 still work, but snapshots are not created anymore.
Solution: Install cv4pve-autosnap on all nodes, each of them to create snapshots on its own node only. This way snapshots on node2 are not affected by failure of node1.
from cv4pve-autosnap.
installing cv4pve-autosnap outside the cluster the problem does not exist. However, if in HA the vm are moved from one node to another what happens? That you would no longer snap.
from cv4pve-autosnap.
installing cv4pve-autosnap outside the cluster the problem does not exist.
Yes, but that requires "the outside" not to fail. So we come back to the initial problem: one failure stops snapshots in whole cluster.
However, if in HA the vm are moved from one node to another what happens? That you would no longer snap.
Why? After migration the vm will stay in the same pool, so no problem. Snapshots will be automatically made on the new node. (If the node make snapshots of "all my own vm's in the pool", then the newly migrated vm will be also snapshotted. And this is clou of the idea.)
from cv4pve-autosnap.
In the latest version you can specify the pool using:
'@pool-???' for all VM/CT in specific pool (e.g. @pool-customer1),
Best regards
from cv4pve-autosnap.
Related Issues (20)
- Save snap to another storage HOT 2
- Same error trying to snap on proxmox 6.2 HOT 9
- Proxmox 7.2-11 issues HOT 3
- [FEATURE] Add an option to snapshot only running VMs/CTs HOT 4
- Can this be made possible to run locally on the proxmox server shell? HOT 3
- Feature: Snap from tags HOT 7
- Is it safety to use cv4pve-autosnap in conjunction with Storage Replication (pvecm)? HOT 7
- Obsolete defaults-extra-file HOT 1
- Object reference not set to an instance of an object. HOT 2
- Cannot exclude vm disks HOT 3
- Include an example of how to use a snapshot to restore a VM/CT ? HOT 1
- Can't snapshot a VM without disk HOT 4
- No usable version of libssl was found HOT 6
- API tokens syntax is an unlucky choice HOT 13
- Documentation unclear about exclusions in vmid parameter and missing other parameters HOT 15
- Feature: Option to disable Memory on snapshot HOT 1
- Incomplete error handling (or lack of filtering) for "non-snapshottable" machines HOT 1
- Destination storage HOT 2
- is promox 8 supported? HOT 1
- Capture snapshot with RAM HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from cv4pve-autosnap.