Hi,
we are running the Data Broker 1.0.1D for our vCenter backups. All fine except of a restore from secondary.
During the restore, the snap shot gets cloned and a export policy conaining all IP adresses of the vCenter is created and attached to the volume clone.
Data Broker discovers all storage interfaces.
[DBG] SDGetNetworkInterfacesResponse : SDGetNetworkInterfacesResult :
Network Interface : Name - SecondaryNetapp-576, Address - 15.16.16.28, StorageSystem - SecondaryNetapp, Protocols - null
Network Interface : Name - SecondaryNetapp-st408, Address - 192.168.5.209, StorageSystem - SecondaryNetapp, Protocols - Nfs
Network Interface : Name - SecondaryNetapp-st801, Address - 50.142.0.22, StorageSystem - SecondaryNetapp, Protocols - Nfs
[INF] End SDGetNetworkInterfaces
Now it takes the first useable lif and modifies the mount parameter:
[DBG] Get network NFS lif for owning VServer SecondaryNetapp
[DBG] NFS lif found 192.168.5.209
[DBG] NFS lif found 192.168.5.209
[DBG] Replacing vserver name of clone.FullPath: SecondaryNetapp:/vol/sv_n970340404272009464219816 with IP address 192.168.5.209
[INF] Begin ReplaceSVM
[INF] End ReplaceSVM
[DBG] Replacing vserver name of clone.ResourceName: SecondaryNetapp:/vol/sv_n970340404272009464219816 with IP address 192.168.5.209
But the export policy does not contain the IP that fits to the export of 192.*
export-policy rule show -policyname ExportPolicye09bad2ea81540f193f6becd24990b5d
Policy Rule Access Client RO
Vserver Name Index Protocol Match Rule
------------ --------------- ------ -------- --------------------- ---------
sv57sko9746 ExportPolicye09bad2ea81540f193f6becd24990b5d 1
any 50.142.0.210 any
I also this entry in the logs:
[INF] Begin Get_SVM_Lif_Mapping
[DBG] INFO: Preferred SVM LIF MAPPING not found.
[INF] End Get_SVM_Lif_Mapping
[DBG] NFS lif is not configured. Will process live check.
Is there a way to influence the lif selection?
Marcus