One PBS with raid1 or two with single discs?

bomart

Active Member
Feb 21, 2020
9
0
41
54
Which solution is better:
1. One PBS host with two disks raid1
2. Two PBSs with single disc and sync from one to two?
Hardware costs doesn't matter.
 
Between this 2 options I would go with Raid1.
If more disks possible then maybe Raid 6.
 
Hardware costs doesn't matter.
Two independent PBS' with two disks each ;-)

1. One PBS host with two disks raid1
2. Two PBSs with single disc and sync from one to two?
In this specific case, without any other option: there are multiple elements in a system that may die - starting from the power supply over the CPU and chipset to RAM. The disk is just one element.

With this in my mind: I would expect option 2) to be more reliable on the long run...
 
Last edited:
I also like the idea of two servers versus one if forced to pick, but also with the added arrangement that the servers are geographically separated.
 
  • Like
Reactions: UdoB and bomart
What are you protecting against? Do you back up or replicate the data from PBS already? My instance of PBS does run on RAID 1, but I also backup my PBS datastore to my Synology, a NUC, and to the cloud. I would have no problem having PBS on a single disk on a single server if there are a sufficient number of copies of the data.
 
  • Like
Reactions: Johannes S
To be clear, this is more of a thought experiment so in the real world you do really want disk redundancy as well even in this two-server scenario. Sure, the odds are low that both will fail during the same time frame causing data loss, but there are situations that happen in the real world. For example, read errors on the hard drive of the second server during a restore, or just an outright disk failure due to the continuous restore load.

Ultimately, all the other server components could be eventually replaced, but the one thing that has your data can't.
 
I think the answer really depends on the risk being mitigated. I would go two servers if PBS needs to be nearly highly available. Neither solution is the answer for data durability. As has often been mentioned, RAID is not a backup. Neither is two servers in my opinion. You need a proper 3/2/1 back up if data durability is the concern.
 
Maybe it was missed, but the OP's original query was about two PBS servers, not two servers in general. Having one PBS server with a single disk onsite and a second PBS server with a single disk, but offsite as my addition, would meet the 3-2-1 rule.

However, 3-2-1 was just an archaic minimum guideline so only the incompetent ever accepted that for production! But for home use, many people were happy to have just one backup via an external drive after hearing horror stories from friends/family about lost family photos or whatever. Ultimately, deciding how many copies of your data to make will depend on specifics, such as budget and value of the data.

I think it's also important to note that backups alone are not really adequate for many production environments. You need a place to restore the backups to, and really even that is not adequate because restoring takes time. So now you add continuous replication to the mix, DR sites, etc. The conversation can go on for a while...
 
One angle nobody's mentioned: if ransomware or a stolen admin login is on your list of risks, option 2 gives you something RAID1 can't. Set it up so the second PBS pulls from the first with a sync job, using a user or API token on the first box that only has read access to the datastore (DatastoreReader), and leave remove vanished off. Then someone who gets into the first PBS, or into PVE with the PBS credentials, can't delete what's already on the second box, and deletes on the first don't carry over. Keep the second box's root password and web UI separate from everything else.

I'd still add a second disk to each when you can, for the reasons J-Rod gave.

(I'm the founder of CyberSnap, which looks at existing snapshots for signs of encryption and file tampering.)
 
  • Like
Reactions: Johannes S and UdoB
For the second PBS server, you could also leave it powered off all the time except to run the daily sync pull and this could enhance your ransomware protection.
 
  • Like
Reactions: Johannes S
J-Rod's power-off habit for the second PBS is a solid extra layer on top of the pull-sync + DatastoreReader token setup. The second box only comes online for the sync window, so there is almost no always-on management surface for a compromised production side to reach.

When you do power it on, I would treat that short window as the moment to confirm the newest generation actually landed, and to open a couple of real files from an older generation too. Encryption that runs for days can sit quietly in several recent generations. Knowing what normal looks like across the ladder makes the later choice of which generation to bring operations back from much less guessy.

Keep root and the web UI on that second box off any shared password store that production admins use.

Disclosure: I'm founder and CEO of CyberSnap, which looks at existing snapshots for signs of encryption and file tampering. Not a PBS vendor pitch.
 
  • Like
Reactions: Johannes S