>>Yes, that is how the current variable sized chunking algorithm works.
...
"zfs diff" does not provide the information needed for our deduplication
algorithm, so we cannot use that.
<<
1) Can you please outline the algorithm?
2) Why you think, it is not possible to use the changed information
> Container backup is very slow compared to VM backup. I have a 500 GB
> container (sftp server) with minimal changing files, but even the incremental
> bakcups take 2 hours with heavy disk activity. Almost nothing is transfered
> to the backup server. It seems that it it reads the whole conta
Container backup is very slow compared to VM backup. I have a 500 GB container
(sftp server) with minimal changing files, but even the incremental bakcups
take 2 hours with heavy disk activity. Almost nothing is transfered to the
backup server. It seems that it it reads the whole container every
applied both patches, thanks :)
___
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
idea sounds good, patch looks sane (compiled it, but did not test it
though, since i have no iscsi around atm)
the only thing that 'could' go wrong afaics, is that we maybe
have some codepaths were we only use the default initiatorname
and some setups could not do that anymore
but this would me
Gave it a quick test: Moving some disks from one VM to another on a CIFS
storage worked for me. Had to do some conflict resolution upon application
though.
=> If (there is more feedback and) you rebase it, then I can test it (+ GUI)
more thoroughly :)
I would probably rename the parameter name d
When using the path to request properties, and no ZFS file system is mounted
at that path, ZFS will fall back to the parent filesystem:
> # zfs unmount myzpool/subvol-172-disk-0
> # zfs get mounted /myzpool/subvol-172-disk-0
> NAME PROPERTY VALUESOURCE
> myzpool mounted yes -
> #
Signed-off-by: Dominic Jäger
---
Somehow selecting storages is not possible anymore. It was at some point.
You can add disks that are not in the OVF in the importwizard at the moment.
PVE/API2/Nodes.pm | 48 +++
www/manager6/Makefile | 2 +
www/manager6
Make importing single disks easier.
Required to import a whole VM via GUI.
Signed-off-by: Dominic Jäger
---
www/manager6/qemu/HDEdit.js | 134 ++
www/manager6/qemu/HardwareView.js | 24 ++
2 files changed, 141 insertions(+), 17 deletions(-)
diff --git a/ww
Required to create a GUI for importdisk.
Add parameters that enable directly attaching the disk to a bus/device with all
known disk options. This avoids intermediate steps as unused disk.
We allow different places as source
* Regular VM images on PVE storages (Normal users + root)
* Other disk im
As I've talked with Thomas & Dominik about the current state.
I cleaned up the worst chaos, but it's still very much work in progress.
Nonetheless, if
- you have an .ovf
- and its disks somewhere on your server
- and are root
then you can click through the wizard and will have a VM
- that actu
---
www/manager6/Workspace.js| 15 +++
www/manager6/node/CmdMenu.js | 12
2 files changed, 27 insertions(+)
diff --git a/www/manager6/Workspace.js b/www/manager6/Workspace.js
index 3d0f3fec..6ee7c957 100644
--- a/www/manager6/Workspace.js
+++ b/www/manager6/Workspace.
12 matches
Mail list logo
