@olivierlambert whoops! Well spotted Will post in the real one
Best posts made by mauzilla
-
RE: Best way to determine whether files in the backups are still relevant
-
RE: Best way to determine whether files in the backups are still relevant
@florent you guys are absolute geniuses, there isn't a company in the world that matches your quality support.
I have a question though, say I have my backup set with 2 retentions on delta, and we do a full backup say each 20 backups. Am I right to assume that when the full backup occurs (so after 20 backups), in theory, there will be 2 full sets on the backup storage?
Example
Day 19: Full.vhd delta.vhd On day 20: oldfull.vhd (which is a merge of the day 19 full + delta) newfull.vhd (which is the new VM) Day 21: full.vhd (which is now the old newfull.vhd) delta.vhd (delta for day 21)
If so, that means that if we have large VM's (some are 2.5TB in size), there will come a time that that VM will use up double it's size on the backup storage.
Lastly, as we will be moving to XCP Pro + support in January, we want to move our backups from the now historical / community edition to the new one. I know at some point I saw you had moved to NBD backups and there is also an option to "test" the backups. Would this then make periodical full backups irrelevant as there would be no need to worry about backup corruption over time?
-
RE: Best way to determine whether files in the backups are still relevant
@florent Good morning @florent
I once again have to thank you guys for your amazing support (even in a case like this). I have added the 2 remotes to our paid enterprise version (it's added verbatim as per our community version).
Other info:
- Backups are setup as incremental
- Backups run either daily or weekly (2 backup jobs) but both configured the same
- 1 concurrent backup
- 2 Backup retention
I will open a ticket now, thank you!
-
RE: increase 24 hour timeout-limit on backup/copy
You guys are absolute rockstarts! Yannick connected and was able to resolve the issue, thank you again for all of your hard work!
-
RE: increase 24 hour timeout-limit on backup/copy
@olivierlambert strange one, thank you Olivier, I created a ticket 7714072
-
RE: XCP / XO and Truenas Scale or Core
Thank you all seems I've got my answer, will go core
-
RE: Backups not starting after failed NFS mount
@olivierlambert you're a grandmaster, never even considered that It seems to be stuck but likely firewall will have a look thank you
-
log4j vulnerability impact
Just checking if there is any impact in XCP-NG and / or XO that may be impacted by the log4j vulerability? Not sure if some of the API's uses java?
-
RE: LICENSE_RESTRICTION (PCI_device_for_auto_update)
@olivierlambert Perfect, setting the parameter on both the VM and the snapshot resolves the issue. I am able to continue backups Thank you both for helping!
Latest posts made by mauzilla
-
RE: Incremental replication testing
@Danp sorry I more meant Cr testing. Backup testing involves restoring the VM, is there an option to test the Delta replication? I imagine an automation of cloning the VM, boot without network, check for existance of the management agent and if it does not boot it can mark the backup as failed and trigger a full backup?
-
Incremental replication testing
Backups have the full backup retention, is there a similar process for Delta replication?
-
Restarting network when swopping SFP modules
We have an Intel card and have been running unsupported SFP's for a while (we did not know it as we were still getting network 1GB) but only noted that it wasnt running ton 10GB a couple of months into production.
We have a number of VM's running on the host using local SR, so we're trying to avoid having to restart the server. My understanding is that we cannot use modprobe to reload the driver (when we replace the SFP's with Intel SFP's). Is there any other way to restart only the network if we swop out the SFP's instead of a full system reboot?
-
RE: Best way to determine whether files in the backups are still relevant
@olivierlambert whoops! Well spotted Will post in the real one
-
RE: Best way to determine whether files in the backups are still relevant
I'm back on this one, we've setup a test bench with a similar card, and can confirm we dont even see the interface anymore upon booting, and during boot we get the following:
As there is a flag we can set, I am following this guide but not sure if this is applicable to the filesystem of XCP (for one there is no /etc/default/grub file)
https://www.serveradminz.com/blog/unsupported-sfp-linux/
Anyone able to assist in which file I would need to set the "Fix the issue permanently" part?
-
Accessing XCP host outside of private network
We're running a test XCP-NG host at our office and want to add it to our XOA appliance which is at our DC. I assume that we would need to do port forwarding from our local network.
Which ports are needed to be open and can we elect a custom port? I see when we add servers we can select the port, is just not sure if there are other ports that also need to be opened / forwarded?
-
RE: Best way to determine whether files in the backups are still relevant
@florent you guys are absolute geniuses, there isn't a company in the world that matches your quality support.
I have a question though, say I have my backup set with 2 retentions on delta, and we do a full backup say each 20 backups. Am I right to assume that when the full backup occurs (so after 20 backups), in theory, there will be 2 full sets on the backup storage?
Example
Day 19: Full.vhd delta.vhd On day 20: oldfull.vhd (which is a merge of the day 19 full + delta) newfull.vhd (which is the new VM) Day 21: full.vhd (which is now the old newfull.vhd) delta.vhd (delta for day 21)
If so, that means that if we have large VM's (some are 2.5TB in size), there will come a time that that VM will use up double it's size on the backup storage.
Lastly, as we will be moving to XCP Pro + support in January, we want to move our backups from the now historical / community edition to the new one. I know at some point I saw you had moved to NBD backups and there is also an option to "test" the backups. Would this then make periodical full backups irrelevant as there would be no need to worry about backup corruption over time?
-
RE: Best way to determine whether files in the backups are still relevant
@florent Good morning @florent
I once again have to thank you guys for your amazing support (even in a case like this). I have added the 2 remotes to our paid enterprise version (it's added verbatim as per our community version).
Other info:
- Backups are setup as incremental
- Backups run either daily or weekly (2 backup jobs) but both configured the same
- 1 concurrent backup
- 2 Backup retention
I will open a ticket now, thank you!
-
Best way to determine whether files in the backups are still relevant
We're running out of free space on our of our remotes. The remote itself has 30TB of storage, and our collective pool for VM's doesn't reach 15-16TB's
Looking at the files, we can see some of the files on the remote has very old timestamps and seems like they were duplicated at some point (some of the files was last touched in July and we have weekly backups)
How can I determine whether some of these files are possibly orphaned files we can delete? Worth noting the backup "health" does not show these backups as orphaned.
Note that although we have a paid for version of XO, our backups are still running on a legacy / community version until Feb when we will be moving onto a combined XCP / XO bundle, hence why I am asking the question on the forum and not opening a ticket.
-
RE: Changing the backup name
Okay let me rephrase, is there then an option to "move" a VM's backup from 1 backup to another. This is simply to avoid having to restart the backup process on some of them?
VM is backup on with delta backups on hypervisor 1 with a backup called "Backup Weekly" - I now want to move that backup to a new Backup called "Host 1 Backup Weekly" - Everything stays the same, destinations etc, it's only that a CR process will also be added now to the new backup.