Questions: Delta backup initial seed
Hi, I have a simple question about Delta backup initial seed.
in the documentation it says:
"3. edit the job to target the other remote
4. copy files from the first remote to the other one"
I created a differential backup, I set the concurrency to 3 and full backup interval to 20.
I ran a full backup as per
"1. create a delta backup job to the first remote
2. run the backup (full)"
My questions are,
where can I find the full backup of each of the VMs it created since these VMs aren't listed at each of the VMs "Snapshot" tabs and what does "target the other remote" mean? Does it mean my TrueNAS server or does it mean XCP-NG server that's the host of XO? It is a bit confusing.
I thought that concurrency means the number of previous backups XO keeps around and that full backup intervals are the number of differential backs it would have done before doing a full backup again.
Thanks for your clarification in advance.
- Backups aren't snapshot. The first time we do a backup, XO will make a snapshot, then export the whole snapshot content (that's what we call the full). Next backup run: we'll do another snapshot, and only export the diff between old and new snapshot (the delta). When it's done, we remove the oldest snapshot on the VM. A remote is where XO will store that content, so even if you lose your host, you'll be able to restore the backup from your remote.
- Retention is how many backups you'll keep, concurrency is how many jobs in parallel.
@olivierlambert I think I'm getting it. So, if I have setup NFS as my storage repository, how will I be able to find the first snapshot over there? and how do I use that first snapshot in order to do a restore? Currently, I can only see the nightly differential backups from the UI in XO
Thanks for clarifying the meaning of retention.
In regards to concurrency, by jobs do you mean the number of VM backups running when the backup is running night/daily/weekly if I have several VMs set in the backup job?
Sorry I'm not sure to understand what you meant. Snapshots aren't backup. Snapshots can be used to go back in time or be exported via XO to make a backup. But we do not "store" snapshots (or we don't call them that way when it's exported: it's just a backup).
Concurrency: it means inside the same job, how many VMs will be exported at once.
@olivierlambert I'm sorry for generating a confusion. Per your reply, if these are snapshots, then, why not just use snapshots instead of differential backups? Confused.
At least in snapshots, I can have and keep as many snapshots as I want. In differential backups, it only keeps one and deletes the old one -- even though, per my settings, it seems and it is supposed to keep at least 3 differential backups.
I don't understand what you meant. Snapshots are not backups. Snapshots are stored on the same SR where your live data is. Backups are outside.