Actions taken during Disaster Recovery for client whose IBM Megaraid controller has failed

[Teo En Ming]

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

 

[Mike]

Glad that things are going smooth for you now. What are your current full server specs and OS version? Is there any virtualization in use or is this bare metal? You want to look at the amount of RAM, processor, and read/write IO currently in use and likely base over a foreseeable increase in that usage based on your current scenario.

 

[ussnorway]

2. Install Windows Server 2022 Standard evaluation copy on the new temporary server.

ime this is a mistake, your client has no clue and will assume this server keeps working forever which is not the case

a much better option is to install a free hever-V server on the hard metal and then put the 2022 evaluation copy on that as this gives you many more backup and testing options

the key issue is how much time you want to spend fine tunning this server as years go by and for that you need the details Mike asked for above + a better understanding of your usage towards their server i.e, are you going to physically travel to this server whenever it needs something done ... how secure does their data need to be?

 

[Teo En Ming]

Good day from Singapore,

We are proposing the Lenovo ThinkSystem SR550 Rack Server to our client in Singapore.

Specs
=======

- 2U rack server

- 1 piece of 2nd generation Intel® Xeon® Platinum 8253 Processor, 16 cores, 22M Cache, 2.20 GHz

- 1 piece of 64 GB 2666 MHz TruDDR4 RAM

- 16x hot-swap 2.5 inch drive bay

- Ask for Hardware RAID with flash cache

- 2x 500 GB 2.5 inch SSD in RAID 1 configuration for Windows Server installation

- 4x 1.2 TB SAS 2.5 inch 15K harddisks in RAID 5 configuration for data

- 2x 1GbE ports + 1x dedicated 1GbE management port (standard)

- 2x hot-swap/redundant 750W 80 PLUS Titanium Power Supply Units

- License for XClarity Controller

- Windows Server 2022 Standard with Desktop Experience

- Warranty: 3-year customer replaceable unit and onsite service, next business day 9x5

I am wondering if this propostal is too expensive for the customer in terms of Singapore dollars.

Regards,

Mr. Turritopsis Dohrnii Teo En Ming
Singapore

 

[ussnorway]

i personally would not consider Lenovo but reliability is worth more to me than cheap