Geekly Articles each Day
📜 ⬆️ ⬇️

Would not spend a day trying to restore Windows Server 2008R2

Lyrical introduction


A few weeks ago, the following situation occurred: the 1C programmer asked me to update the platform and said that this was done using the “two clicks + on and on” method, without hesitation and having previously made a backup, installed the platform. Backup is done by standard means 2008r2 on a separate screw in addition. This screw was completely allocated by Windows itself for backups and hidden - the system itself suggested to do so in order to avoid wear and fragmentation, in the future such a disk can be connected as an NTFS folder. So it happened, after installing 1C, my eyes had a pristine clean 1C cluster, that is, the database was still alive in SQL, but I didn’t see the possibility to fasten it to 1C, and there was no time to study, as it was late Wednesday evening, and by morning everything should be tiptop. In perfect peace I rang the office - they left the keys on the watch. I arrived, rebooted the server in recovery mode, it is also the Windows 7 installation mode. The next thirty hours passed in sweat and panic, with the re-creation of RAID, killing the file system on the backup screw, restoring it, and so on.

How not to do when installing the OS


I want to note a small moment and give a small recommendation: when installing Windows, please be more careful with naming partitions. How do I see the rules of good tone: Floppy disks - A: - B:, local hard disks C:, D: and so on, then removable media E: - H: depending on the number, it is advisable to take out the CD / DVD drives to the end, since their number changes least of all, this is X:, Y:, Z:, in the remaining space H: - W: I recommend placing network drives.

So the thing is that I got this server ready, C: is the first local logical, D: is the drive, E: is the second local logical. Disk without label - our hard for backups. I'm not sure that the cause of the problem lies precisely in the order of the drive letters, but just in case I would like to warn.
')

We are trying to start a system restore


Since Windows Server 2008r2 already has a recovery.wim recovery image on its local disk (the name of the items may differ, I’m writing from memory), without inserting the DVD with Windows, we press F8 and choose the very first top recovery option. Select the recovery in the lower left corner of the graphical shell, the search for previously installed systems begins. Since this is a server and is used by RAID, it is advisable for us to have a carrier with
drivers thereof (I personally store them on the same backup disk), otherwise the system simply will not find what to restore.

Everything seemed fine and wonderful, the drivers were successfully installed, the recovery system was found, and recovery options were offered. Here I have to stop and remind: in this system, we cannot somehow use control points - they simply do not exist, only a complete rollback of the disk image.
We select the appropriate item for our goals - the hard drive starts to look for saved system images. I warn you: it will be impossible to manually specify the location of the image , as in this mode, I did not search on the network.

And so, after a long search, we see a rather unexpected sign: “Images for recovery were not found, insert a disk with the image and press Retry” .

Where did the time go


I will not describe the entire agonizing way through which I came to this method, I will say briefly how it is solved:


Have a good trip!

Source: https://habr.com/ru/post/149876/

More articles:


All Articles