EMC Unity SAN Snapshot Backups

[mmcd1983]

Hi there,

We currently run an EMC Unity SAN and have our Veeam server successfully taking SAN Snapshot backups. There are a few things that make me uncomfortable however, maybe someone can clear them up.

1. When I first logged Veeam into the Unity, it created a host "VeeamAU_XXXXXXX_VeeamInitiator" even though I had my server configured in the Unity. This host "has no initiators logged into the system".

2. Some LUNs(4) are always present in the diskmgmt on the Veeam Server performing the SAN backup, these match up with the LUNS the initiator above seems to have access to.

3. The host I created seems to have access to ALL LUNS which are partaking in snapshot baackups, all working OK and those other than the 4 mentioned, do not appear in diskmgmt.

I am wondering if I remove the LUNs from the host Veeam created, will they disappear from my diskmgmt? It would be odd seeing as it has no initiators logged in but the 4 in diskmgmt are the same 4 this Veeam host has access to.

Any help is much appreciated, apologies if the above is confusing.

M

[foggy]

Hi Martin, this is Veeam B&R iSCSI initiator, not a WIndows one. We're working on better cleaning these mappings up in the future update, to prevent such warnings. There's a chance that rescan process is continuously working resulting in the initiator being always mapped to the host, I recommend checking this with the help of support. Thanks.

[mmcd1983]

Thank you Foggy,

What I ideally don't want is to have the SAN LUNs always mapped into the Veeam (Windows) Server. I had assumed that only the snapshots would be mounted during the backup operation and not the actual LUNs?

Any suggestions?

[foggy]

I'd try to unmount them and see if they show up again.