Does my concept make sense?

[Hunduster]

Hello everyone,
I've recently switched to PVE and PBS and have been thinking about a backup concept that I'm not sure will work the way I think it will

I have a NAS with spinners and SSDs. I have integrated two datastores on the PBS:

• Datastore 1 on SSD
• Datastore 2 on HDD

I have a backup job in PVE that performs a backup to Datastore 1 every hour. The data sets are verified directly after creation on Datastore 1.
Under Datastore 2 there is a sync job that syncs all backups from Datastore 1 to Datastore 2 at 00:00 at night.
At 01:00 the Prune and GC jobs then run on both datastores.

The Prune jobs are set as follows:

Datastore 1



Datastore 2



At 02:00 an offsite PBS then goes and pulls the data from Datastore 2.

My thought or goal behind the concept is that the hourly backups run on the more power-efficient SSDs so that the spinners in the NAS can go into sleep mode.
Once a day, the daily, weekly and monthly backups should then be copied to the spinners for “long-term archiving”.

I am now wondering whether this makes sense and whether PBS understands the connection between the two datastores and whether the backup chains are consistent or whether I am fooling myself here, especially with regard to consistency and deduplication.

I currently had 3 warnings last night under the GC job of Datastore 1: WARN: warning: unable to access non-existent chunk.
This makes me worry that my concept is not as well thought out as I initially thought.

 

[Johannes S]

For me this setup looks ok. But I would expect bad Performance for the remote sync of the offsite pbs, verify and Garbage collection on the hdd datastore. Did you run some benchmarks?
What size do you have on your ssds and hdds? It might be worth to add a mirrored ssd Partition as a special device for Metadata of the hdd data.
I would also setup the remote pbs to sync from the ssds for better performance

 

[Hunduster]

For me this setup looks ok. But I would expect bad Performance for the remote sync of the offsite pbs, verify and Garbage collection on the hdd datastore. Did you run some benchmarks?
What size do you have on your ssds and hdds? It might be worth to add a mirrored ssd Partition as a special device for Metadata of the hdd data.
I would also setup the remote pbs to sync from the ssds for better performance

I only have 50 Mbit/s upload at my home, the remote sync to Offiste is not faster.
The SSDs run in RAID 5 with 1.5 TB. My HDDs in RAID 6 with ~20 TB

 

[Johannes S]

I only have 50 Mbit/s upload at my home, the remote sync to Offiste is not faster.
The SSDs run in RAID 5 with 1.5 TB. My HDDs in RAID 6 with ~20 TB

Ok then you are propably right that there is not much (if at all) to gain from a sync from the HDDs. I'm still curious whether garbage collection and verify jobs on the HDD datastore have sufficient performance.

Concerning the warning about the missing chunks: As far I know missing chunks should be resynced with the next backup or sync job. Did you encounter this warning again?

 

[Hunduster]

Yes, I've been getting the warning for the last few days now too. It really looks to me as if PBS is not aware across the datastores that a part has been moved from one datastore to another

2024-11-06T14:04:23+01:00: starting garbage collection on store SSD
2024-11-06T14:04:23+01:00: Start GC phase1 (mark used chunks)
2024-11-06T14:04:24+01:00: WARN: warning: unable to access non-existent chunk 0579485bda57e8ee1ba5a087ff7e948627c82a40a88a406e26408718f836349b, required by "/mnt/nas01/ssd/vm/103/2024-11-05T16:00:13Z/drive-scsi0.img.fidx"
2024-11-06T14:04:30+01:00: WARN: warning: unable to access non-existent chunk 82bdc5e0d93f252d53a7cb07f37cccaee369084946426a6d9e0af1edc1796ae0, required by "/mnt/nas01/ssd/vm/103/2024-11-05T16:00:13Z/drive-scsi0.img.fidx"
2024-11-06T14:04:30+01:00: WARN: warning: unable to access non-existent chunk a584eac99211673d2081c1b5bc85e724e27ff0ce615fb7b51074ff30263e1a35, required by "/mnt/nas01/ssd/vm/103/2024-11-05T16:00:13Z/drive-scsi0.img.fidx"
2024-11-06T14:04:32+01:00: WARN: warning: unable to access non-existent chunk abfc89d1bd6fde06a77201601b701ec46f2d4b972886493262e422aeb1fee0c5, required by "/mnt/nas01/ssd/vm/103/2024-11-05T16:00:13Z/drive-scsi0.img.fidx"
2024-11-06T14:04:41+01:00: WARN: warning: unable to access non-existent chunk e5805ff1b6e45f0cd73793e710946d41a56af85a7c59f2b3b66928610786cd38, required by "/mnt/nas01/ssd/vm/103/2024-11-05T17:00:12Z/drive-scsi0.img.fidx"
2024-11-06T14:04:48+01:00: WARN: warning: unable to access non-existent chunk afce64eb31dad3fcbdf9abcf2ba31bd0c6489a3a7999dcc9822ec94bdd7638a8, required by "/mnt/nas01/ssd/vm/103/2024-11-05T17:00:12Z/drive-scsi0.img.fidx"
2024-11-06T14:04:48+01:00: WARN: warning: unable to access non-existent chunk a3f0eb9a94782ea80cd0b161c145cd6bc76299de9edc58ddae42cb6f6882e298, required by "/mnt/nas01/ssd/vm/103/2024-11-05T17:00:12Z/drive-scsi0.img.fidx"
2024-11-06T14:04:49+01:00: WARN: warning: unable to access non-existent chunk e8977cebbb1944d2cbc7413f792db04649829f8631b10b7d9b35ddc8f107b5f7, required by "/mnt/nas01/ssd/vm/103/2024-11-05T17:00:12Z/drive-scsi0.img.fidx"
2024-11-06T14:04:50+01:00: WARN: warning: unable to access non-existent chunk 7f5bad7f821c54d8bc29c3082330d6c6d5dbfc3b7e7d0546f0f5e048e46300e3, required by "/mnt/nas01/ssd/vm/103/2024-11-05T17:00:12Z/drive-scsi0.img.fidx"
2024-11-06T14:04:56+01:00: marked 1% (2 of 169 index files)
2024-11-06T14:04:58+01:00: WARN: warning: unable to access non-existent chunk 1fd3c45a635e635ceb38095c2c8456df22bc9cfe8217e7706540e58335609207, required by "/mnt/nas01/ssd/vm/103/2024-11-05T18:00:13Z/drive-scsi0.img.fidx"
2024-11-06T14:05:05+01:00: WARN: warning: unable to access non-existent chunk dc2f75c9eb9a190b1ca694567e2207ed794cbceed2d50b2a131364a82f912afe, required by "/mnt/nas01/ssd/vm/103/2024-11-05T18:00:13Z/drive-scsi0.img.fidx"
2024-11-06T14:05:05+01:00: WARN: warning: unable to access non-existent chunk d6dd0dcc0f28deac0c8830e638108f3ede5d3b741aacbe018eccde9f55bdf1c2, required by "/mnt/nas01/ssd/vm/103/2024-11-05T18:00:13Z/drive-scsi0.img.fidx"
2024-11-06T14:05:07+01:00: WARN: warning: unable to access non-existent chunk 049ac6670a3da2e8267eae17bdc019fde1383052182ea3cbdfebb65bb6798333, required by "/mnt/nas01/ssd/vm/103/2024-11-05T18:00:13Z/drive-scsi0.img.fidx"
2024-11-06T14:05:07+01:00: WARN: warning: unable to access non-existent chunk 7f5bad7f821c54d8bc29c3082330d6c6d5dbfc3b7e7d0546f0f5e048e46300e3, required by "/mnt/nas01/ssd/vm/103/2024-11-05T18:00:13Z/drive-scsi0.img.fidx"
2024-11-06T14:05:15+01:00: WARN: warning: unable to access non-existent chunk 5860f5185e847b87bbd7e8a33cac21bb846ae608bd5691000dcd99ade02ba29f, required by "/mnt/nas01/ssd/vm/103/2024-11-05T19:00:13Z/drive-scsi0.img.fidx"
2024-11-06T14:05:21+01:00: WARN: warning: unable to access non-existent chunk e577c87882638e5bfa4524dac7ea69e2e628fedee24f3366e2f91f914c5d6107, required by "/mnt/nas01/ssd/vm/103/2024-11-05T19:00:13Z/drive-scsi0.img.fidx"
2024-11-06T14:05:21+01:00: WARN: warning: unable to access non-existent chunk 866c87a7d87538944fd3956005a826d7c0925af3fca041e2975f13425cf8cceb, required by "/mnt/nas01/ssd/vm/103/2024-11-05T19:00:13Z/drive-scsi0.img.fidx"
2024-11-06T14:05:23+01:00: WARN: warning: unable to access non-existent chunk 317199864ceb8660184f61743b661596aaea2b9f780d5a839c10c8ce9ac35746, required by "/mnt/nas01/ssd/vm/103/2024-11-05T19:00:13Z/drive-scsi0.img.fidx"
2024-11-06T14:05:23+01:00: WARN: warning: unable to access non-existent chunk 566e7eac3eb2b714818d0193d501b1552636359140790694764b700e18fadedd, required by "/mnt/nas01/ssd/vm/103/2024-11-05T19:00:13Z/drive-scsi0.img.fidx"
2024-11-06T14:05:23+01:00: WARN: warning: unable to access non-existent chunk 3cb7be04d30905d33fe87b431c57477f9887a9a51efbbacffb0c10d485508101, required by "/mnt/nas01/ssd/vm/103/2024-11-05T19:00:13Z/drive-scsi0.img.fidx"
2024-11-06T14:05:30+01:00: marked 2% (4 of 169 index files)

 

[Zappy]

did you test the restore frp, each and every datastore ?