Issues with SAN Transfer
I've had a crap ton of issues recently. I attempted to upgrade to 8.1 and I didn't read the fine print that it required vCenter 5.1 or better. I then had to revert to 7.01.
When I reverted to 7.01, many issues occured, but for the most part everything is working OKAY. I cannot upgrade to 7.03 as it breaks Data Protector for some reason. I have my VMFS volumes being delivered from my StoreVirtual system to my Cell Manager. In the StoreVirtual system, I have only EVER had them delivered read-only to the Cell Manager and this has worked well. When I need to restore, I then switch to read/write for restoring.
Currently I have one VM that sits on 4 different VMFS volumes. The new issue that I am seeing is that the disks are in the Cell Manager but they are delivered as "unknown." The system attempts to "initialze" the disks but it cannot do so because they are "read-only." Again, this is weird as when my 7.03 (previous version when upgraded to 8.1) was working, I didn't have this issue. Anyway, the VM I am attempting to backup, will only go NBD right now and I have a feeling it's because the disks for this VM are the "unknown" disks listed in the Storage Management snap in in Windows 2008 R2.
Can anyone provide insight? Should I switch my LUNs from the StoreVirtual to Read/Write? If I do, is it okay to allow Windows 2008 R2 to initialize them (not Format/assign drive letter)?
If a LUN with VMFS on it is initialized from a Windows host, you will most ilkely destroy pieces or the whole VMFSS datastore. This sounds like your datastores have some issues. Could you create a new LUN, create VMFS on it, make it visible on the backup host and try to backup a VM that has been migrated there? If this works, you might need to repair the signature on the VMFS datastores. Just came across such an issue.
The only thing you're allowed to do in Windows disk maangement is to make the disk "Online". Everything else will break something.
Please use the Like button below, if you find this post useful.