One benefit of duplication is that, in the event of a failure, the system still operates in a suitable mode. This can help avoid losing data, although it cannot ensure that the data has not been corrupted. However, parity duplication is a good starting point, and it is important that the backup process produces an exact copy of what you want to protect. This means the data, including its sequence.
A backup can be performed using a patch-based approach. This involves using a temporary backup to continue the system’s normal work, and then using the duplicate to restore the original. In addition, you can use “pending” backups in parallel to provide ongoing support. This means you can also make copies of the copy.
Sometimes you need more flexibility, and it is worth considering having two servers running similar roles but with slightly different data. This helps ensure that, if one server fails, the system is in a state that allows it to continue working effectively. This flexible redundancy strategy is sometimes called “active-active” rather than “active-standby” as it involves two servers running similar roles or architectures but with slightly different data. This approach helps ensure that the system is more reliable.
This flexibility can help provide a more robust SCCM infrastructure, which is why enterprises often use different operating systems on their infrastructure. The cloud-native approach means it is a relatively straightforward process to rebuild systems within hours in the event of an urgent outage.
Alternatively, you could consider building redundancy into the architecture of the system from the outset. This involves having different approaches within an architecture; this can provide an audit trail if a failure occurs and is critical. d2c66b5586