Teo En Ming
Honorable Member
- Joined
- Aug 18, 2015
- Messages
- 3
- Thread Author
-
- #1
Subject: Actions taken during Disaster Recovery for client whose IBM Megaraid controller has failed
Good day from Singapore,
We have a client, an engineering company, in Woodlands Link Singapore. They have an old IBM System X server (hereinafter referred to as the Old Server).
Their IBM Megaraid controller (FRU 46C9111) malfunctioned recently.
This is the error message:
Critical Message
L2/L3 Cache error was detected on the RAID controller. Please contact technical support to resolve this issue. Press 'X' to
continue or else power off the system, replace the controller and reboot.
Enter Your Input Here:
As a result of the RAID controller malfunction, their Windows Server 2012 R2 cannot boot up.
On 21 Feb 2023 Tuesday, I had to prepare a new temporary server and perform data restore (aka Disaster Recovery).
Client has issued an Asus ExpertCenter D700SA SFF PC with Windows 10 Home.
However Veritas Backup Exec 22 Server cannot be installed on Windows 10 Home. It has to be installed on a Windows Server with a Domain Controller. Backup Exec cannot be installed in a Read Only Domain Controller (RODC).
These are the actions I have performed.
1. Format Windows 10 Home on Asus ExpertCenter D700SA SFF PC (this is the new temporary server).
2. Install Windows Server 2022 Standard evaluation copy on the new temporary server.
3. Install Active Directory Domain Services role on Windows Server 2022 Standard.
4. Promote Windows Server 2022 Standard to Domain Controller.
5. Install Veritas Backup Exec 22 Server in Windows Server 2022 Standard.
6. Unjoin Synology NAS DS920+ from Old domain controller since the ServerBackup folder cannot be accessed.
7. Turn off Windows Firewall in Windows Server 2022 Standard for simplicity.
8. Join Synology NAS DS920+ to the New domain controller. ServerBackup folder can now be accessed. Now we can go to the next step.
9. Import Backup Sets residing on Synology NAS DS920+ (this was created by Veritas Backup Exec Server on the Old Server).
10. Click Inventory and Catalog Now in Veritas Backup Exec 22 Server so that we can see the Backup Sets.
11. Perform data restore (this took 31 hours in total, restoring 1.48 TB of data).
12. Create shared folders on the new temporary server so that all users could access restored data in the interim.
13. Convert the new temporary server into a Print Server by installing printer drivers for all printers and sharing out the printers so that all users can print.
14. Install Microsoft SQL Server 2019 Standard trial version and SQL Server Management Studio version 19 so that Helen could restore WinPack database (15 GB) on the new temporary server.
15. By 23 Feb 2023 Thursday afternoon, users could access restored data on the new temporary server.
On 24 Feb 2023 Friday, the replacement RAID controller arrived. I reached the seller at Changi Business Park Central 2 Singapore to collect the replacement RAID controller at 9.00 AM in the morning. However, the replacement RAID controller came without an add-on card.
These are what I have done on the morning of 24 Feb 2023 Friday.
1. Remove FAULTY RAID controller from the Old Server.
2. Detach add-on card from the faulty RAID controller.
3. Install add-on card on the replacement RAID controller.
4. Install replacement RAID controller on the Old Server.
5. Power up the IBM System X server.
6. Windows Server 2012 R2 boots up automatically without any configuration on the replacement RAID controller.
7. Now all users can access the Old Server. Everyone is happy.
We are going to propose a new hardware server for the client. Please suggest specifications for the new hardware server and new operating system.
Thank you very much.
Regards,
Mr. Turritopsis Dohrnii Teo En Ming
Republic of Singapore
Good day from Singapore,
We have a client, an engineering company, in Woodlands Link Singapore. They have an old IBM System X server (hereinafter referred to as the Old Server).
Their IBM Megaraid controller (FRU 46C9111) malfunctioned recently.
This is the error message:
Critical Message
L2/L3 Cache error was detected on the RAID controller. Please contact technical support to resolve this issue. Press 'X' to
continue or else power off the system, replace the controller and reboot.
Enter Your Input Here:
As a result of the RAID controller malfunction, their Windows Server 2012 R2 cannot boot up.
On 21 Feb 2023 Tuesday, I had to prepare a new temporary server and perform data restore (aka Disaster Recovery).
Client has issued an Asus ExpertCenter D700SA SFF PC with Windows 10 Home.
However Veritas Backup Exec 22 Server cannot be installed on Windows 10 Home. It has to be installed on a Windows Server with a Domain Controller. Backup Exec cannot be installed in a Read Only Domain Controller (RODC).
These are the actions I have performed.
1. Format Windows 10 Home on Asus ExpertCenter D700SA SFF PC (this is the new temporary server).
2. Install Windows Server 2022 Standard evaluation copy on the new temporary server.
3. Install Active Directory Domain Services role on Windows Server 2022 Standard.
4. Promote Windows Server 2022 Standard to Domain Controller.
5. Install Veritas Backup Exec 22 Server in Windows Server 2022 Standard.
6. Unjoin Synology NAS DS920+ from Old domain controller since the ServerBackup folder cannot be accessed.
7. Turn off Windows Firewall in Windows Server 2022 Standard for simplicity.
8. Join Synology NAS DS920+ to the New domain controller. ServerBackup folder can now be accessed. Now we can go to the next step.
9. Import Backup Sets residing on Synology NAS DS920+ (this was created by Veritas Backup Exec Server on the Old Server).
10. Click Inventory and Catalog Now in Veritas Backup Exec 22 Server so that we can see the Backup Sets.
11. Perform data restore (this took 31 hours in total, restoring 1.48 TB of data).
12. Create shared folders on the new temporary server so that all users could access restored data in the interim.
13. Convert the new temporary server into a Print Server by installing printer drivers for all printers and sharing out the printers so that all users can print.
14. Install Microsoft SQL Server 2019 Standard trial version and SQL Server Management Studio version 19 so that Helen could restore WinPack database (15 GB) on the new temporary server.
15. By 23 Feb 2023 Thursday afternoon, users could access restored data on the new temporary server.
On 24 Feb 2023 Friday, the replacement RAID controller arrived. I reached the seller at Changi Business Park Central 2 Singapore to collect the replacement RAID controller at 9.00 AM in the morning. However, the replacement RAID controller came without an add-on card.
These are what I have done on the morning of 24 Feb 2023 Friday.
1. Remove FAULTY RAID controller from the Old Server.
2. Detach add-on card from the faulty RAID controller.
3. Install add-on card on the replacement RAID controller.
4. Install replacement RAID controller on the Old Server.
5. Power up the IBM System X server.
6. Windows Server 2012 R2 boots up automatically without any configuration on the replacement RAID controller.
7. Now all users can access the Old Server. Everyone is happy.
We are going to propose a new hardware server for the client. Please suggest specifications for the new hardware server and new operating system.
Thank you very much.
Regards,
Mr. Turritopsis Dohrnii Teo En Ming
Republic of Singapore