Yay, that makes me a very happy bunny, thankyouyo don't need to "remirror" when windows start ti read the disk, detect the mirror and load with no problem.
Yay, that makes me a very happy bunny, thankyouyo don't need to "remirror" when windows start ti read the disk, detect the mirror and load with no problem.
Nothing unusual about my setup other than im mirroring, something the majority of home users dont, just people like us outside of the corporate worldIt's interesting to understand your arrangement, what I do is install my OS exclusive to a harddrive (or partition.) When I need a new install, I simply create a brand new partition, and leave the old one behind. It's a "wasteful" practice, but data becomes cheaper and cheaper to simply abandon.
My mirroring is done using the Built in windows option, not using anything 3rd party or within bios.I mean, typically RAID setups are dependent on your bios configuration as well as your OS, plus its just an R1 type, so nothing really needs any worry.
Honestly though it sounds like you should just use drive cloning software and do a clone of your drives every now and again so you have the latest up to date data on each drive. RAID mirroring is useful in case a drive starts dying, outside of that data configurations are almost instantaneous between both drives unless you have some sort of setting that prevents that from always happening (such as to prevent an event of ransomware or the like).
I have done enough of these setups in the past for clients (and myself with my synology) most of the time its not as big of a deal unless you are doing a storage pool scenario between multiple drives, which is always best to have a hot spare in the occasion of drive failure in one of your drives.
Also are you using HDD's or SSD's? If the former how old are they and how many times have you reinstalled windows on them? Finally why don't you use 10 with classic shell if you want to retain the 7 experience?
The issue is with mirroring (perhaps I'm not remembering correctly) if data (file) corruption happens via software side not hardware faults, then that file corruptions carries it across all mirrored data and may not even know of it until too late. Where manual cloning, you may have a chance to recover a known good file from your backup.My mirroring is done using the Built in windows option, not using anything 3rd party or within bios.
I get what your saying about manually cloning, i used the built in drive mirroring because i thought it would be an easy automated way of having data backed up to a second drive but now its left me in a situation where i have never reinstalled the O.S having mirrored storage drives and biting my nails to the bone over the reinstall ha ha.
My O.S is currently on a HDD but the new install will be on SSD, i have gone for a 256gb drive which is way bigger than i need for the O.S drive, im currently using 80gb of my O.S drive but went for a bigger SSD than i need for the wear leveling capacity.
I did not buy an SSD because i even wanted an SSD, i want to migrate to a different case i have at some point and the stupid thing only has rails for two 3.5" hard drives and two mounts for SSD/2.5" HDD, i have had to 3D print a tray to mount two of the 4 storage drives, it has bags of room for hard drives where the two rails are but only has two rails, so stupid
This can happen. In fact I am dealing with a few users at the moment who have corrupted Windows/profiles and my only solution to them is to back up the personal data and doing a fresh install. Since corruption happens on a software/data level and not a hardware level there really is not a difference between what has happened on your front end and on your mirrored backup. That is the whole point of what a mirror is, for better or for worse. The same would happen if you had someone zero out your drive or if you had gotten ransomware'd. The only benefit of Mirroring is immediate failure recovery once the main drive starts to struggle/die. Outside of that a better method is cloning, and depending on the storage medium for that there are technically better solutions than hard drives for that. That said this starts ending the consumer level solutions and enters into enterprise level solutions such as tape drive archive backup systems.The issue is with mirroring (perhaps I'm not remembering correctly) if data (file) corruption happens via software side not hardware faults, then that file corruptions carries it across all mirrored data and may not even know of it until too late. Where manual cloning, you may have a chance to recover a known good file from your backup.
Perhaps someone can confirm this or not.
My mirroring is done using the Built in windows option, not using anything 3rd party or within bios.
I get what your saying about manually cloning, i used the built in drive mirroring because i thought it would be an easy automated way of having data backed up to a second drive but now its left me in a situation where i have never reinstalled the O.S having mirrored storage drives and biting my nails to the bone over the reinstall ha ha.
My O.S is currently on a HDD but the new install will be on SSD, i have gone for a 256gb drive which is way bigger than i need for the O.S drive, im currently using 80gb of my O.S drive but went for a bigger SSD than i need for the wear leveling capacity.
I did not buy an SSD because i even wanted an SSD, i want to migrate to a different case i have at some point and the stupid thing only has rails for two 3.5" hard drives and two mounts for SSD/2.5" HDD, i have had to 3D print a tray to mount two of the 4 storage drives, it has bags of room for hard drives where the two rails are but only has two rails, so stupid
No, My two mirrored volumes are storage, my O.S is on a separate non mirrored drive and my worry is what a fresh install of windows would make of two mirrors being presented to it that were made in a previous windows install, i wont be doing anything to the mirrored drives during the reinstall other than disconnecting the 4 drives till the install is complete.This can happen. In fact I am dealing with a few users at the moment who have corrupted Windows/profiles and my only solution to them is to back up the personal data and doing a fresh install. Since corruption happens on a software/data level and not a hardware level there really is not a difference between what has happened on your front end and on your mirrored backup. That is the whole point of what a mirror is, for better or for worse. The same would happen if you had someone zero out your drive or if you had gotten ransomware'd. The only benefit of Mirroring is immediate failure recovery once the main drive starts to struggle/die. Outside of that a better method is cloning, and depending on the storage medium for that there are technically better solutions than hard drives for that. That said this starts ending the consumer level solutions and enters into enterprise level solutions such as tape drive archive backup systems.
So with what you are trying to say is you are fresh installing the OS on the mirror, but you are afraid that the mirror will wipe out both drives with the fresh install? I do not entirely understand. If this is the case you should unplug your mirrored drive right before install as the mirror could do what it is designed to do and mirror the fresh install on both drives, losing your archived data on both.
Outside of this if your solution that you are seeking is a data archive backup or a rescue image of your OS/Data it would be beneficial and even cheap to invest into an external HDD and use a cloning program or even windows built in back up system that will make backups periodically on your external drive in the event of failure, virus or ransomware attack. That is something we have set up on *a lot* of our clients. At least the cheaper ones who cannot afford cloud backup/enterprise solutions.
Thank you for confirming and also never thought of that scenario. That would be pretty bad for that to happen.This can happen. In fact I am dealing with a few users at the moment who have corrupted Windows/profiles and my only solution to them is to back up the personal data and doing a fresh install. Since corruption happens on a software/data level and not a hardware level there really is not a difference between what has happened on your front end and on your mirrored backup. That is the whole point of what a mirror is, for better or for worse. The same would happen if you had someone zero out your drive or if you had gotten ransomware'd. The only benefit of Mirroring is immediate failure recovery once the main drive starts to struggle/die. Outside of that a better method is cloning, and depending on the storage medium for that there are technically better solutions than hard drives for that. That said this starts ending the consumer level solutions and enters into enterprise level solutions such as tape drive archive backup systems.
So with what you are trying to say is you are fresh installing the OS on the mirror, but you are afraid that the mirror will wipe out both drives with the fresh install? I do not entirely understand. If this is the case you should unplug your mirrored drive right before install as the mirror could do what it is designed to do and mirror the fresh install on both drives, losing your archived data on both.
Outside of this if your solution that you are seeking is a data archive backup or a rescue image of your OS/Data it would be beneficial and even cheap to invest into an external HDD and use a cloning program or even windows built in back up system that will make backups periodically on your external drive in the event of failure, virus or ransomware attack. That is something we have set up on *a lot* of our clients. At least the cheaper ones who cannot afford cloud backup/enterprise solutions.