Quantcast
Channel: File Services and Storage forum
Viewing all articles
Browse latest Browse all 13565

iSCSI-Target 2012R2 - back to life

$
0
0

In my test- environment, i've used Win 2012 R2 as an iSCSI-Target-Server:
- cheap motherboard with onboard SATA-Ports, 16GB RAM ...
- 1st SATA-Port for hd with operating system,
- 6 SATA-Ports for "Storage-HDs").
- pool out off 6 Storage-HDs and max. space and volume-size as/in 2-way mirror
- max. size for dynamic-iSCSI-VHDX on this volume.

After operating-system-HD-crash, i've installed OS on a new one as before (same hardware, same name etc.) . I was exited, because i was able to import my existing pool, add space and volume, import and point to my iSCSI-vhdx and connect my iSCSI-Initiator to my now repaired iSCSI-target (data OK).
BUT, after a iSCSI-Target-reboot volume on iSCSI-Initiator was gone.

Problem 1:
After a reboot i've (always) to add my space but can't import my iscsi-vhdx -> neither see it in the UI nor import possible (System says: already there ...).

(no-)Solution:
delete everything (target, volume, space, pool) and build up from scratch.
(new) Problem 2: i can't use the same target-name as before (wmi throws unknown error ...). Only with a fresh iscsi-target-name, i was able to build a new vhdx-file and connection.

Conclusion:
- UI is good for first configuration, maybe there are some powershell-commands to solve problem 1 and 2 (or MS has to do some homework for the UI ...).
- i can't bring up an (OS-) damaged iscsi-target-server back to life without loosing data ... (done somthing wrong or only possible with (shared-)SAS-Pools etc. ?)
- iSCSI-Target-role is only a second-class storage-option and not for enterprise use (24/7) ?

thanks for answers


Viewing all articles
Browse latest Browse all 13565

Trending Articles