Dell PowerVault NX1950 Önemli Bilgiler Kılavuzu - Sayfa 11

Depolama Dell PowerVault NX1950 için çevrimiçi göz atın veya pdf Önemli Bilgiler Kılavuzu indirin. Dell PowerVault NX1950 26 sayfaları. For vmware esx server software
Ayrıca Dell PowerVault NX1950 için: Dağıtım Kılavuzu (34 sayfalar), Başlarken (49 sayfalar), Kurulum ve Sorun Giderme Kılavuzu (48 sayfalar), Dağıtım Kılavuzu (38 sayfalar), Yükseltme Kılavuzu (18 sayfalar), Referans Kılavuzu (4 sayfalar), Kurulum (2 sayfalar), Kullanma (2 sayfalar), Yapılandırma Kılavuzu (11 sayfalar)

•

VDS errors are reported in the Win Application log while creating

or deleting LUNs.

While creating or deleting LUNs, the following error message displays

in the Win Application log:

Storage Manager for SANs encountered the

following error(s) while loading information

from Virtual Disk Service (VDS) or VDS hardware

provider(s). Some of the functionality may not

be available on the hardware provider(s).

Lun - 'www' IVdsDisk.QueryExtents

'System.Runtime.InteropServices.COMException -

'Exception from HRESULT: 0x80042444

This issue occurs because the password on the array is not set using the

SMRegTool. To work around this issue, set the password manually

using the SMRegTool.

•

With two disks of different sizes, the Storage Manager for SANs

snap-in does not support striped or mirrored LUNs.

The VDS provider for the Dell PowerVault MD3000 does not support

mixed capacity drives. If the system has two disks with different sizes,

the Storage Manager for SANs snap-in does not support the drives to

be used for striped or mirrored LUNs. There is no workaround for

this issue.

•

VDS/volume shadow copy service (VSS) combo installer does not

prompt the user to reboot the system.

While installing VDS/VSS provider on the PowerVault NX1950 and

PowerVault MD3000 integrated solution, the installer does not prompt

the user to reboot the system and causes the Storage Management

snap-in to behave unexpectedly. To workaround this issue, reboot the

system after installing the VDS/VSS provider.

•

The domain name is not validated in the Microsoft Services for

NFS Properties window.

The Active Directory Domain field in the Microsoft Services for

NFS Properties window can take any value. The value in this field is

not validated to ensure that the domain name exists. This issue causes

Important Information