Unsolved
This post is more than 5 years old
4 Posts
0
3030
May 10th, 2011 23:00
LUNs in unknown, not initialized state
hi all,
i've got the current setup:
vranger pro 4.5 on server2008 std R2 backing up from ESXi hosts
iSCSI connection to EMC AX4 via Microsoft iSCSI initiator
long story short, vizioncore suggested in order to have vranger backing up via iscsi, i need to make all LUNs visible and read-only to the vranger server. i've already read that you can't make the LUNs read-only with the CLARiiONs, so that leaves the other question. when i make the LUNs visible to the vranger server (from navisphere>>manage, virtual disks, select virtual disk to assign to vranger server), the LUNs show up in server2008 storage manager as unknown, not initialized disks. i've been advised that they should be unknown, healthy status.
can someone please advise how i can get them to the state i need?
thanks in advance
dynamox
11 Legend
•
20.4K Posts
•
87.4K Points
0
May 11th, 2011 10:00
is this for "VCB" type of backup , where you mount VMFS file system on a windows box and spin VM vmdk's to tape ?
kivenage
4 Posts
0
May 11th, 2011 15:00
yes, it's a VCB type backup, i've got a seperate NTFS LUN acting as a repository for the VM backups, this repository is then backed up to tape.
kivenage
4 Posts
0
May 11th, 2011 15:00
deconfigure MPIO as in via the MS iSCSI initiator? sorry if this all sounds too basic, but like i said earlier, i'm very new to this
dynamox
11 Legend
•
20.4K Posts
•
87.4K Points
0
May 12th, 2011 04:00
windows 2008 does not understand how to deal with VMFS file systems so that state and initialization does not surprose me. When you use VCB software, it's capable of reading VMFS file system (it installs a special driver) so it's up to vranger vcb plugin to handle this backup. I would concult your vranger documentation.
kivenage
4 Posts
0
May 12th, 2011 19:00
thanks, i will have to check that out. but just as a side note, i've seen various other setups that show the LUNs in an 'unknown, HEALTHY' state. i understand that VMFS will not be recognized (thus the unknown) by windows.
i've been to vranger support and they are indicating that the setup seems correct with the problem likely to be on the SAN/MS iSCSI initiator side of things, so i'm kinda stuck at the moment.