Reverting to old array 1

[nashcom]

I’ve got an HP ProLiant ML370 G4 with a SmartArray 6400 controller. It’s running Windows Server 2003.

The C: (system) drive is on one mirrored array.

The E: (data) drive is on a RAID 5 array.

I’ve installed three larger capacity hard disk drives for the E: drive. When I installed them I pressed F8 on the SmartArray BIOS and created a new Array. In Windows I then prepared and formatted the volume, then restored everything back from a backup. It worked fine, but I’ve got a problem with the restoration of the SQL master.mdf file which was on the E: drive.

Basically, I need to safely get the old data array installed back into the server, and I’d like to know how to do that. Is there a safe way to swap between the old and the new hard disks? What will the raid controller do if I plug in the old drives? Also, the Windows Server OS (C: drive) currently thinks drive E: is 580GB, whereas the old E: was only 72GB. I’m not sure I can simply plug in the old hard drives, and I’m worried in case I lose either one or both array configurations.

Thanks very much!

 

[SteveRoadWarrior]

This is a case for being extremely careful. You'll want to image the server (Acronis, Backup Exec System Recovery) before starting. Also (not OR, this is an AND), have a full backup with all unneeded services stopped (this may be why your SQL didn't come back). You'll probably get better results with Windows Backup than Symantec Backup Exec b/c there is no need for SQL.

In theory, you can swap the drives out and back. The array information is supposed to be stored in both the array controller memory and the hard disks themselves. However, bad backplanes (the things the HDD plug into) and weak array controller batteries can wreak havoc with your plan. Also, getting the disk drives inserted in the wrong order can spell trouble. Be sure to answer any array controller questions before the OS boots.

So, go slow and take lots of precautions. In theory what you want to do should work. In practice, you'll want to be careful.

 

[nashcom]

Thanks very much for that. I was very nervous about this. In the end I managed to sort it using a different method, and didn’t have to re-instate the old array. I looked through the BackupExec logs and saw that the contents of the SQL DATA folder had been successfully backed-up a few days ago. I then temporarily re-installed the old tape backup unit and restored the SQL stuff from that backup. After this the SQL services loaded fine, but the data was obviously out of date. The application vendor had set up a scheduled task which regularly backed-up the SQL database to a file. I was then able to launch SQL Studio Manager and restore the database from the last backup (after close of play on Friday night).

I’m not sure why BackupExec didn’t say it had failed to backup any files. I’ve now done a full system backup with the SQL services stopped, updated the Disaster Recovery image, and I’ve also amended the scheduled daily backup to backup the SQL databases using the SQL Agent which seems to work fine (after patching BackupExec).

I’d still like to know if anyone has any tips for re-instating an old (non-faulty) array. I imagine it’s one of those jobs where you need your wits about you – the messages displayed by the BIOS can flash past pretty quickly, and it would be useful to know how to answer any questions that might pop up.

 

[SteveRoadWarrior]

Glad to hear you were able to get a version of the database back.

I'm hesitant to say exactly how to answer, the different array controllers have slightly different messages. Just protect yourself and go slow, think about the answers before making them. Call HP before answering if you're unsure, also the online manuals for the array controller will explain what's going on.

There is one configuration where *extreme* caution is required (not yours). Anyone in the sound of my voice who is considering using an HP MSA (SATA cage) attached to a SCSI array controller (a supported configuration), please don't. There's a lot which can go wrong.