@DustinB Will give it a try with "1". Thank you!
Posts
-
RE: One pool with more than one job / jobs should not run in parallel
-
RE: One pool with more than one job / jobs should not run in parallel
@DustinB Thank's for your response. But how to set my job-concurrency? Like "just 1 job at the time"?
C
-
One pool with more than one job / jobs should not run in parallel
I have one pool with a bunch ob VMs. I have three backup jobs created (different requirements for different machines). They all are all set to start at 01:00. As far as I read in the docs, etc. all jobs would run in parallel then. Not sure if this is correct?
Is there any option to define that job 2 runs after job 1 finished. Job 3 after job 2, etc.? Cause I do not know for sure how long each job runs. I can estimate of course, but there is still a risk of "conflict".BR
C -
RE: [NOSNAP] [NOBAK] but disk is still backed up
@olivierlambert Sorry. 8.3. Delta Backup.
BR
C -
[NOSNAP] [NOBAK] but disk is still backed up
Hi,
I have a VM with 2 disks. I do not want the second disk to be included in the backup. I have added [NOSNAP] [NOBAK] as prefix to the second disk's name.
Nevertheless, when doing a full backup, the data of this disk is tranfered as well:
I read some posts in this forum about that but it is still not clear to me.
- Is the data of the disk transfered, but then deleted from the backup?
- Did I do anything wrong?
- Shouldn't it be transfered in the first place?
BR
C -
RE: Delta Backup / Snapshot / disk space
@olivierlambert Thank your for poiting this out! Very much apreciated!
-
RE: Delta Backup / Snapshot / disk space
I found some useful information in this thread: https://xcp-ng.org/forum/post/22839
That basically anwers my question: On a LVM storage the amount of disk space doubles when creating the first snapshot. This is due to the fact that a LVM storage uses thick provisioning.Learning: When installing a new server, be carefull if you choose LVM (thick provisioned; seems to be the default) or Local EXT (thin provisioned). According to some other posts, LVM seems to be a little bit more performant.
With VMware this is not the case. Even when using thick provisioning, you do not need double the disk space when creating a snap shot. This is even more critical, when you are running several VMs on a host and there is not a lot of disk space left. You can't make any snapshots then I guess. As you need at least double the amount of disk space than the VM that you want to snaphot already uses.
If anything from above is not correct, maybe someone with more experience can comment on that.
C
-
Delta Backup / Snapshot / disk space
Hi,
I am coming from VMware and I am new to XCP-NG. Regarding Delta backups I have one question:
It seems, that the first Delta Backup is doubling the required space on the LVM storage. Is that correct? Is there any way to avoid that? Any chance to do a differential backup to a NFS without doubling the required disk space? On the NAS (NFS) we have plenty of space, but the high performance (SSD, etc.) disk space is limited.
BR
C