Your steps will work. You will also need to re-enter your product key and activate the install.
The settings and configuration will be restored properly.
I did the switch to the new boot media today, and it worked. Almost complete.
The network settings did not get restored when loading the saved config!!!
For the LAN address this is not a problem (as I remembered the correct address),
but the other network devices (NICs for iSCSI SAN) did not have the correct address
now. And I even do not know, where I could find the correct adresses now, to restore
them manually! Now my ESXi is missing these iSCSI devices. (I also looked in the ESXi
log files, but I found nothing here).
Is there any way, how I can get these adresses back??
Please help.
Also the e-mail setup in open-e was not restored, but that was also easy to restore manually.
Anything else that I should have a look at?
2 reasons why the settings(IPs) could not be restored; 1- Previous media was corrupted and they where not saved, 2- both the settings and configuration options were not selected when saving previous settings.
You can restore them manually by using any IP that is in the same subnet as the initiators, or you should be able to check the settings of the software initiator and see what had been previously entered on the Static discovery tab.
Thank you for that really fast reply.
Ok, I found the previous configured in the Static discovery tab, thank you for that hint.
But now, even after I did restore the addresses manually, the iSCSI volume does not get connected in ESXi.
After testing a little, the volumes now disappeared in ESXi, but the iSCSI device is still there.
When trying to "add new storage" I see the device, but when trying to find the partition table,
ESXi says "Loading..." and does not find anything for a long time... ???
On the DSS V6 side, be sure the LUNs are activated, even toggle them off/on.
Reboot the ESXi box.
If you are using the latest build of DSS V6(6335), check the SCST compatibility settings from the console. This is mentioned in the release notes.
Thanks again for help.
I hava a failover config with two paths and I put in the IP addresses in the wrong order. After switching these two the correct order, it's now back to work.