RimFire007
asked on
How to move HP Proliant MK350 G8 HardDisks from failed Server to new Server without loosing data
Quote likely the disk array controller is failed at the HP ML350pT08 E5-2620v2 server, P/N: 736978-425 (7/2014). We are replacing the server to new one but wonder can we access the data stored on the disks, There are two arrays 3x300GB RAID5 and 3x900GB RAID 5. This failed server doesn't boot.
We have a spare HP ProLiant ML350p Gen8 E5-2609 server, P/N: 669045-425 (11/2012) where we can try to house the disks but what do we need to do have this working? I'm worried that when we try to create array at the spare server it will wipe all data away.
The OS (Win Server Essentials 2012R2) is at the 3x300GB RAID5 and data is at the 3x900GB RAID5.
Warning-Lights.JPG
Error-Messages.JPG
We have a spare HP ProLiant ML350p Gen8 E5-2609 server, P/N: 669045-425 (11/2012) where we can try to house the disks but what do we need to do have this working? I'm worried that when we try to create array at the spare server it will wipe all data away.
The OS (Win Server Essentials 2012R2) is at the 3x300GB RAID5 and data is at the 3x900GB RAID5.
Warning-Lights.JPG
Error-Messages.JPG
ASKER
Thanks Andrew
But I think that replacing the disk won't solve the problem. Usually these things boot up if they only one failed disk of three. On the left bank the failed disk should be the middle one (amber light) and it should boot up if nothing else. Did you check the picture of boot up warnings? Not sure what all those warnings mean.
"If you insert the disks in a new HPE server in the correct order, in a Smart Array controller it will read the configuration from the disks. " What should we do in order to prepare the spare server for this? Some kind of reset to defaults perhaps?
But I think that replacing the disk won't solve the problem. Usually these things boot up if they only one failed disk of three. On the left bank the failed disk should be the middle one (amber light) and it should boot up if nothing else. Did you check the picture of boot up warnings? Not sure what all those warnings mean.
"If you insert the disks in a new HPE server in the correct order, in a Smart Array controller it will read the configuration from the disks. " What should we do in order to prepare the spare server for this? Some kind of reset to defaults perhaps?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Great!
Will try this tomorrow morning then we will have a spare 300GB disk. Hmm. The spare disk comes from a retaired server and it has been a part of a 2x300GB RAID. What should we do to the disk in order to prepare it for replacement?
Will try this tomorrow morning then we will have a spare 300GB disk. Hmm. The spare disk comes from a retaired server and it has been a part of a 2x300GB RAID. What should we do to the disk in order to prepare it for replacement?
pull the failed disk, and insert the new disk.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks A and a!
We are still in process of restoring the data from the NAS iSCSI (where the win image BUs were) to USB disk. Should be ready after apx. 10 hours. We use the spare server for this - installed a Essentials 2012 to it in order to be able restore from iscsi/Win-Imagebackup. Tomorrow we can start working with the broken server.
BTW, maybe we can use the iSCSI image backup to restore the AD to for example VMware (which we have too). In that way we can migrate to new hardware and have the AD transferred. The new OS will be Server Essentials 2016.
The backup we have is apx 1 month old but for AD it should be fine. Hopefully we get the datadisk (3x900GB) live for example using some kind of boot from DVD and repair option as andyalder hints. Will check if the spare server has the cache module.
We are still in process of restoring the data from the NAS iSCSI (where the win image BUs were) to USB disk. Should be ready after apx. 10 hours. We use the spare server for this - installed a Essentials 2012 to it in order to be able restore from iscsi/Win-Imagebackup. Tomorrow we can start working with the broken server.
BTW, maybe we can use the iSCSI image backup to restore the AD to for example VMware (which we have too). In that way we can migrate to new hardware and have the AD transferred. The new OS will be Server Essentials 2016.
The backup we have is apx 1 month old but for AD it should be fine. Hopefully we get the datadisk (3x900GB) live for example using some kind of boot from DVD and repair option as andyalder hints. Will check if the spare server has the cache module.
Restoring images of AD is not recommended but if that is all you have it will have to do if you can't repair the OS. All the PCs will have to leave the domain and rejoin it since their passwords will have changed.
in fact ALL the trusts will FAIL, because you've technically ROLLED BACK THE DOMAIN IN TIME!
e.g. the PCs and DOMAIN will not match... because the PC will have a later number than the domain.
https://support.microsoft.com/en-gb/help/875495/how-to-detect-and-recover-from-a-usn-rollback-in-windows-server-2003-w
https://blogs.msmvps.com/acefekay/2013/10/17/windows-server-2012-ad-cloning-snapshot-support-preventing-usn-rollbacks/
e.g. the PCs and DOMAIN will not match... because the PC will have a later number than the domain.
https://support.microsoft.com/en-gb/help/875495/how-to-detect-and-recover-from-a-usn-rollback-in-windows-server-2003-w
https://blogs.msmvps.com/acefekay/2013/10/17/windows-server-2012-ad-cloning-snapshot-support-preventing-usn-rollbacks/
ASKER
Hi
Moving on. The old server is now at our site, We placed the HDs to spare server but we were forced to restore OS form image backup apx. 1 months old.
The AD is not complex. Only about 15 users and nothing special in there. Would it be wisest just to create New Server and AD (different domain name than previously) form scratch and manually create users to it? We are familiar with Profwiz which has been a great tool manipulating user profiles.
One challenge would be to find correct data now when they have used temp NAS. Maybe we will use robocopy with mirror option.
We have find out that fastcopy is great tool to copy data (handles too long paths/file names) but it is quote slow. Any hints for that?
Moving on. The old server is now at our site, We placed the HDs to spare server but we were forced to restore OS form image backup apx. 1 months old.
The AD is not complex. Only about 15 users and nothing special in there. Would it be wisest just to create New Server and AD (different domain name than previously) form scratch and manually create users to it? We are familiar with Profwiz which has been a great tool manipulating user profiles.
One challenge would be to find correct data now when they have used temp NAS. Maybe we will use robocopy with mirror option.
We have find out that fastcopy is great tool to copy data (handles too long paths/file names) but it is quote slow. Any hints for that?
Has the restore worked ?
ASKER
Yes. It seems to be fine. No domain computers here at out site But the old server seems to be fine.
If/then we can't migrate the AD I'm very tempted to keep:
DC old IP address
DC computer name
And only change the domain name. Is it a good idea?
There could be plenty of .ini files (related to CAD SW / licenses) etc. which may refer to the old server IP/name. Keeping IP and DC's name should help a lot.
If/then we can't migrate the AD I'm very tempted to keep:
DC old IP address
DC computer name
And only change the domain name. Is it a good idea?
There could be plenty of .ini files (related to CAD SW / licenses) etc. which may refer to the old server IP/name. Keeping IP and DC's name should help a lot.
So the failed DC has been restored.
Time to check Users and Workstations for errors, before you change anything else.
Time to check Users and Workstations for errors, before you change anything else.
ASKER
The AD really seems to have everything. Computers are there, User Accounts are there. The GPOs are there (and drive maps). Scheduled tasks are there, etc.
We are not changing anything in the old server now when it has been restored.
We are really eager to setup the new server. Copying Data Files to it right now using FastCopy. The work flow would be greater if we can decide the new server name and the domain name and the DCPromo it.
We are not changing anything in the old server now when it has been restored.
We are really eager to setup the new server. Copying Data Files to it right now using FastCopy. The work flow would be greater if we can decide the new server name and the domain name and the DCPromo it.
Okay, I think your original question has been answered, please select solutions, and award points.
and please post a new question on setting up a new Domain Controller and File Server.
and please post a new question on setting up a new Domain Controller and File Server.
ASKER
Yes. You I right.. Thanks everybody for help. I mark now the best solutions.
ASKER
Thank you both. Great assistance.
This were very helpful case for us to understand ProLiant HW and also iSCSI Win Image Restore.
This were very helpful case for us to understand ProLiant HW and also iSCSI Win Image Restore.
Why not replace the failed disk ?
If you insert the disks in a new HPE server in the correct order, in a Smart Array controller it will read the configuration from the disks.