Search results

You can do a file-level restore in a bit more manual way by using the proxmox-backup-client map command. This maps the disk to a read-only loopback device. You should then be able to mount refs by hand. This requires a refs driver... There is a company well known for their filesystem ports that...

That is expected. When VMs are shut down the qemu process is closed. The qemu process is the one tracking your changes in the blocks of the disk. It will need to read the entire disk again, but it will only transfer missing chunks (as you already said). The Proxmox Team said they want to think...

thats true :) You don't want to have too much io wait. Just wanted to point that part with network traffic out as a lot of people think that if the dirty bitmap is destroyed it will also upload all the chunks to the PBS server again. That is not what is happening.

Hi, the install from ISO is also a relativly vanilla debian install. Is PBS reachable with its IPv4 adress? You only show the netstat output, read here why netstat doesn't always list services bound to both IPv4 and v6...

This would only stress the disk the VM is on. There is no additional traffic for VMs that don't have dirty bitmaps, it just takes longer and needs to read the entire disk.

This is what a command could look like: proxmox-backup-client map vm/117/2021-01-04T03:00:55Z drive-scsi0.img --repository root@pam@localhost:8007:store02 The <snapshot> is vm/117/2021-01-04T03:00:55Z, the <archive-name> is drive-scsi0.img which is how your disk in the VM is called. You can...

Yes you can do that. The datastore just points to a directory. I don't know how exactly you set up your first datastore. Is it zfs? if yes, you can just create another dataset on that zpool and point a datastore to it. If it is something else, you will have to see if you can create another...

Both PVE Storages are pointed at the same PBS Datastore. When the Backup was first created, it was created with the user root@pam (because you did the backup to the PBS storage). When you want to create another backup to the UserPBS storage, it detects there already is a backup on that datastore...

Well if your Server has no internet connection because the network settings are wrong, you need to find a way to access your Server without Internet. Depending on where that server is set up, there are a couple of different ways to do this. One would be to take a monitor and keyboard and walk...

Can't test it here as I have my datastores on different zpools, but does the webinterface not show the per-datastore disk usage?

You are in the Proxmox Backup Server Forum and are probably talking about Proxmox Virtual Environment, I suggest moving your question to that forum to recieve help

When you have your datastore on a seperate partition you can use the df -h command. Either way you can just take a look in the PBS Webinterface, click on the datastore and see the usage there

As long as the file system supports basic POSIX features every file system should work. BTRFS is POSIX.

another idea that crossed my mind: you can use the proxmox-backup-client map functionality to mount disks from the backup. When you do this, you could dd them to a file. can be automated, but probably not the prettiest option

When backing up the data is split into 4MiB "chunks". These chunks are named after their checksum. It also creates an index file with all the chunks used in that backup. When it calculated the checksum of a chunk it wants to back up, it gets the indexes of backups it should know of (can't get...

Even if the bitmaps are discarded because you stopped the qemu process it will only transfer chunks that changed and won't use your precious bandwith for unnecessary transfers. The process takes longer but does not use more bandwith.

This is the perfect task for cronjobs. Cronjobs are scripts that run in intervals you define yourself. Retention is currently configured on a per-datastore basis. You'd need to create another datastore with different retention times. Then create a backup job that only backs up this directory to...

Hi, to limit the size of a share in Truenas you need to go to your shares and hit the "edit quota" button for your share

It will transfer the delta so you get the same data on both PBS instances with as little network traffic as possible

I have been looking for a similar option as well, but haven't found anything built-in yet. The workaround is writing a script for that, but thats not really the clean way of doing it. So +1 from me for a feature request ;)