Hoping you can help.
Our organisation has had Veeam installed but not running for a period of time. Our infrastructure was put into place just prior to my arrival and as such I'm not privvy to the conversations that were had in terms of the setup. It seems nobody was really(!)
Anyway, the way in which VM's have been setup in the past are as per the below procedure.
- Provision LUN on our Dell Equalogic SAN ensuring that the correct iSCSI access has been given to all hosts (to aid vMotion)
- Rescan then add Datastore on vCenter>Host
- Create a VM hightlighing the datastore previously created to use as a base for the Guest OS Files.
- Once installed, provision a second LUN (if required) for Data
- Rescan then Add datastore in vCenter ensuring the ISCSI settings allow the VM or Host (or both/multiple) access.
- Use the MS iSCSI initiator to connect to the LUN and deploy as additional disk
My issue is this.
As I'm new to Veeam, I created a new VM, added an additional disk, this time using RDM (virtual) method, and then backed up. All worked fine. The backup took into account the 2GB test vRDM I'd created. Great!
I then restored to a new VM and a new Datastore (a sandbox) to check it had backed up correctly. The Guest OS powers on absolutely fine...all is well, but the 2GB vRDM I had created, whilst possibly obviously, has been restored as a flat VMDK file (it obviously couldn't create a vRDM as in a restoration you might not have that LUN!). Furthermore, it's not "active". I can mark as active but do no more....I cannot assign it a letter as I get told the Disk Management pane is out of date and it needs refreshing. Numerous refreshes and reboots later...no difference.
1) Can anyone tell me why we would have been using the original iSCSI method? Is this a normal method to use rather than RDMs?
2) Why can't I see the restored vRDM (now a flat VMDK) in my Guest OS?
If anyone can help me, I'd not only appreciate it, I'd consider giving you the princely sum of "mucho respect" for your efforts
Thanks in advance.