This was intended as a disaster recovery solution. In either case you will still be bound by the DSM rule of “not going back to an earlier version” as it is not officially supported.įor your case of updating to 7.3 and then something went wrong with your mail, I don’t think this would save you in terms it would allow you to restore to an earlier version of dsm, as a roll back. So even if you get a new sets of drives (or not, depending on the damage) you will have to be either a) in a fresh installation that has phase 2 ahead of it (configuration of dsm, pools, apps the works) or b) an already up and running dsm installation that you want to recover to an earlier state. You have to have a running DSM up and running before you can restore. But what I mean by that is that even as with ABB bare metal recovery same goes here.

for example, replacing a 4x4TB SHR set, with new 4x16TB drives, can a 'full bare metal backup' be restored, resulting in a larger volume.Ĭlick to expand.Excellent question but I still have to test this out but I would say no.

In a situation where I've replaced all drives with new larger drives.

After a drive has been added, or replaced with a new drive.

Is 'full bare metal backup' restoration possible. Can this be done? If that's covered in the article I missed it.ĭoes the 'full bare metal backup' restore all drive partitions to an earlier state? A second question.

Rather than wait for a possible patch, I choose to rollback my NAS to v7.2-10000, for which a 'full bare metal backup' exists. Subsequently, I upgrade my NAS to DSM v7.3-10000 (or v7.2-12334, for example), and discover that my MailPlus Server has lost its functionality. Let's presume I am running DSM v7.2-10000, and have made a 'full bare metal backup' which resides on a second Synology NAS (ideally this would be on an external drive set, or user-chosen cloud service.). Yet I'm still confused how Synology has defined 'full bare metal backup'.

For iphone instal YT Saver 7.2.0