Data Storage Software V6 2011-11-09 6.0 up90 build 5845 IMPORTANT NOTE: FOR UPDATE via WEB GUI in menu: MAINTENANCE-> software update -> Function: System software update, PLEASE use ISO image ONLY! The ZIP image can be used for installing or running quick trial. This is installable version. The built-in installer can install the Data Storage Software V6 on any bootable media. You can use the following media types: USB DOM (with Wear-Leveling support), IDE (ATA) DOM, SATA DOM, IDE (ATA) Hard Disk, SATA Hard Disk, SCSI Hard Disk or 2GB small LUN on a Hardware RAID (recommended). In order to install the software on separate LUN, please use RAID controllers with multiple LUN support. Please create a small 2GB logical unit for DSS V6. When Running DSS V6 installer you will need to select the 2GB logical unit as the boot media. The rest of the RAID space please create second LUN for the user data. The following RAID controllers are supported as a bootable media: MegaRAID, Smart Array, 3ware, Adaptec, ICP vortex, Areca. For Smart Array please use the RAID management CD as the RAID BIOS does not support LUN management. The provided software can be used for evaluation for 60 days with TRIAL product key. This software must be installed on a USB-stick first. In the ISO subdirectory there is same software available as an ISO image that can be placed on a CD-ROM. Since In order to install this version please proceed with the following steps: 1. Download and uncompress the file dss6.0upXX_xxxx.oe_i.zip 2. Format a USB-stick partitioned as a FAT or FAT32 for the root directory (at least 512MB media size) 3. Copy the uncompressed directories and files onto USB-stick Directories: bxxxx and boot Files: mmenu_upd.sh 4. After copying the directories and files please verify that in the root directory resides: bxxxx boot mmenu_upd.sh 5. Access the directory called "boot" then run the bootinst.exe (for Windows only) or bootinst.sh (for Linux only). 6. Boot your storage server with the USB-stick. (please set the BIOS to boot form USB-stick, or in boot menu select USB-stick to boot) 7. In first menu there is choice to start current version or run memory test. Please press enter to run current version. 8. In the second menu there is 3 menu options: 32bit system TRIAL (2.6.27) 64bit system TRIAL (2.6.27) Run Software Installer In order to boot DSS V6 and run TRIAL version at once please select 32bit or 64 bit accordingly to your current system architecture. The TRIAL will recognize your current volume groups and volumes even if you had a previous version of DSS, but keep in mind that this will start with factory defaults settings. In order to restore your current settings, please go to menu: MAINTENANCE->miscellaneous and check the SETUP and CONFIGURATION check-boxes and then select the green action button. It will prompt for system re-boot. After re-boot you can test how your storage system works with the new software. If all is working properly we recommend to update. In order to install DSS V6 on other bootable media, in second menu please select: Run software update installer Please follow all steps until reboot. PLEASE NOTE: After sixty (60) days of the creation of the first volume group, the free trial version of the software will expire, and the connection to all logical volumes will be lost. Thus, all data stored on logical volumes created on the test system will no longer be accessible. However, if you purchase a license for the full version of the software and activate it on the test system before the expiration of sixty (60) days, all of the data will become available again. The trial version supports unlimited storage size. The full version supports 4, 8 or 16TB out of the box - this storage capacity can be further extended by purchasing additional storage licenses. Once your product reaches a licensed capacity of 48TB, it will automatically be extended to unlimited storage. IMPORTANT NOTE: Each 16TB of replicated capacity requires an additional 1GB RAM over minimal requirements. For example, a system with 32TB of replicated capacity requires 1GB RAM as per minimal requirements as well as additional 2GB RAM for the replication, which makes 3GB in total. IMPORTANT NOTE: In case you experience a problem with the availability of iSCSI / FC volumes after the upgrade from version <= 4622, please change the Identification Device (VPD) compatibility to SCST 1.0. You can do it in console tools (CTRL+ALT+W -> Tuning options -> SCST subsystem options -> Device Identification (VPD) compatibility -> SCST). Important notes regarding updating a system with failover in use: This procedure is only applicable to a system with an individual product key (trial versions are excluded). In case of upgrade from version <= 4622 please use following instructions - Update the Secondary system first using the software update functionality and reboot. * In case of using VMware ESX(i) or MS Hyper-V Initiator system, you need to change the Identification Device (VPD) compatibility to SCST 1.0 on the secondary node. This is located in the Console tools (CTRL+ALT+W -> Tuning options -> SCST subsystem options -> Device Identification (VPD) compatibility -> SCST VPD) - Then once the Secondary is running click on the start button in the Failover manager. - Now update the Primary system using the software update functionality and reboot. * In case of using VMware ESX(i) or MS Hyper-V as Initiator system, change the Identification Device (VPD) compatibility to SCST 1.0 on the Primary node. This is located in the Console tools (CTRL+ALT+W-> Tuning options -> SCST subsystem options -> Device Identification (VPD) compatibility -> SCST VPD) - Once the Primary is running go to the Secondary and click on the Sync volumes button in the Failover manager. - Then click on the Failback button in the Secondary system. - The Primary system now be go back to the active mode and ready for another failover. NOTE: - In case you are experiencing a problem with the availability of volumes iSCSI or FC after the upgrade from version <=4622, please change the Identification Device (VPD) compatibility to SCST 1.0. This is located in Console the tools (CTRL+ALT+W -> Tuning options -> SCST subsystem options -> Device Identification (VPD) compatibility -> SCST VPD) - In order to run system in rescue mode please add proper parameter to kernel command line. This can be done while system booting by following steps below : 1. reboot the system 2. while the system booting press "Tab" key on "Architecture selection" screen 3. type "rescue_mode" and press "Enter" key (in order to run the system without splash) or 4. type "rescue_mode=no_mount_lv" and press "Enter" key (in order to run the system without mounting logical volumes) NOTE: A few steps in case of changing TRIAL to FULL when Failover functionality is enabled: Assuming there is working Failover configuration where: - Primary node is Active, - Secondary node is Passive, - only NFS service is enabled. Following procedure describes necessary steps for continuing Failover activity with enabled NFS service. Please perform following steps: On Secondary node: 1. Enter Product Key. 2. Reboot server. 3. Enter License Key for NAS Failover. 4. Reboot server. 5. Start Failover clicking Start in Failover Manager After above please perform following steps on Primary node: 6. Perform Manual Failover. After it Secondary node has to be in Secondary/Active mode. 7. Enter Product Key. 8. Reboot server. 8. Enter License Key for NAS Failover. 10. Reboot server. At the end please perform Synchronize and Failback actions on Secondary node: 11. Click Synchronize button in Failover Manager. 12. Check if volume replication tasks are running and consistent and click Failback button. At this moment your Failover should have status Primary/Active - Secondary/Passive Assuming there is working Failover configuration where: - Primary node is Active, - Secondary node is Passive, - both NFS and iSCSI services are enabled. Following procedure describes necessary steps for continuing Failover activity without enabled NFS service (only iSCSI service will be used). On Primary node: 1. Stop Failover in Failover Manager. 2. Remove all NAS tasks from Failover Tasks. 3. Disable NFS service in Failover Services. 4. Start Failover in Failover Manager. On Secondary node: 5. Enter Product Key. 6. Reboot server. 7. Start Failover clicking Start in Failover Manager After above please perform following steps on Primary node: 8. Perform Manual Failover. After it Secondary node has to be in Secondary/Active mode. 9. Enter Product Key. 10. Reboot server. At the end please perform Synchronize and Failback actions on Secondary node: 11. Click Synchronize button in Failover Manager on Secondary node 12. Check if volume replication tasks are running and consistent and click Failback button. At this moment your Failover should have status Primary/Active - Secondary/Passive NEW: - Support for oplocks in SMB protocol UPDATED: - Simplified registration process doesn't require turn off pop-up blocker in web browser FIXED: - Irqbalance doesn't share IRQ between all cores - ACL settings while authorization set to PDC are lost during reboot (erasing tdb database) - Can't add SSL certificate used in FTPS because it has expired - Write access for NFS doesn't work if access for read only mode is also configured - White screen on GUI while PK contains dashes TESTING: - Infiniband tuning - possible to switch to connected mode (console tools ctrl-alt-w -> Infiniband tuning) - Disk performance test under console (console tools ctrl-alt-w -> System benchmarks -> Disk performance test) - API function to manage iSCSI Cluster (broadcast mode only) - Possibility of turning on and off TCP offload engine (console tools ctrl-alt-w -> Tuning options -> TCP offload options) - NDMP server provides incremental backup functionality in combination with NetBackup - Support for more than 27 units in Software RAID function KNOWN ISSUES: - Synchronize UID and GID database with NIS server does not work properly - In case of pairing NAS volumes with different names in volume replication tasks while NAS (NFS) Failover configuration (i.e. lv0000 on primary node -> lv0001 on secondary node) NAS (NFS) Failover functionality may not work properly. This problem will be resolved in future releases. - NAS (NFS) Failover functionality does not work properly with Mac OS - Windows Services for UNIX are not supported in NAS (NFS) Failover functionality - In some environments connection to ADS is possible with second connection attempt via GUI - In the case of more than one Domain Controller (DC) in the same forest, the connection to the one of those DC's can sometimes be lost - In the event of a very slow storage adapter rescan in VMware, please use Static Discovery instead of Dynamic Discovery in VMware settings - In a large Active Directory with tens of thousands of USERS and GROUPS, some USERS or GROUPS may not appear on the listed interface - The Promise Array Manager tool has been temporarily removed; it will be implemented in its newest version in future builds - MPIO mode with FC HBA's in INITIATOR mode does not work. MPIO will function in FC TARGET mode. Only QLOGIC FC HBA's are supported in TARGET mode - Snapshot overflow may occur when working with a virtual backup device - Rescan function is not working properly when resizing storage connected via iSCSI Initiator - after rescan changes will not be visible. In this event please restart the system - With a Chelsio network interface card, the system may not be stable when using the built-in iSCSI initiator - Neteffect cards show unstable behavior - In case you are facing a performance related issue with network bandwidth, please try to disable TCP offload engine in Hardware console tools (Alt + Ctrl + w) -> Tuning options -> TCP offload options - The TX-check-summing cannot be changed for nVidia based network controllers - High Point array management tool does not work - WWW configuration tool for Promise controllers does not work - After changing the default volume group (Select Default Volume Group) the current settings will not be kept. To keep the current settings, use the Save settings function in the Web GUI before switching the VG and restoring these settings afterwards, system will need to reboot - If you are using ADS authentication, the 'All Squash' option for NFS will not work correctly - After changing a user password via the WebGUI, this user will no longer be able to access password-protected shares published via AFP to which they previously had access. In such a case, deleting the user and re-creating the same user with a new password works - VMware ESX systems are sensitive to changes of the iSCSI Target. When switching between IET and SCST (both directions) VMware will not recognize the volumes. See http://kb.vmware.com/kb/9453805 - With ixgb network interface card, the system may not be stable when using the built-in iSCSI initiator - System cannot be installed on storage attached to an ICP Vortex controller - When using DSS V6 in windows 2008 cluster environment a failover event on DSS V6 will break i/o operation performed on the DSS V6 iSCSI target e.g. copying of files - Remote and console tools for managing FC do not work - In case of downgrade it is necessary to configure Volume Replication tasks and Failover service again. Otherwise, it may not work correctly. P R E V I O U S V E R S I O N S Data Storage Software V6 2011-10-07 6.0 up85 build 5794 IMPORTANT NOTE: FOR UPDATE via WEB GUI in menu: MAINTENANCE-> software update -> Function: System software update, PLEASE use ISO image ONLY! The ZIP image can be used for installing or running quick trial. This is installable version. The built-in installer can install the Data Storage Software V6 on any bootable media. You can use the following media types: USB DOM (with Wear-Leveling support), IDE (ATA) DOM, SATA DOM, IDE (ATA) Hard Disk, SATA Hard Disk, SCSI Hard Disk or 2GB small LUN on a Hardware RAID (recommended). In order to install the software on separate LUN, please use RAID controllers with multiple LUN support. Please create a small 2GB logical unit for DSS V6. When Running DSS V6 installer you will need to select the 2GB logical unit as the boot media. The rest of the RAID space please create second LUN for the user data. The following RAID controllers are supported as a bootable media: MegaRAID, Smart Array, 3ware, Adaptec, ICP vortex, Areca. For Smart Array please use the RAID management CD as the RAID BIOS does not support LUN management. The provided software can be used for evaluation for 60 days with TRIAL product key. This software must be installed on a USB-stick first. In the ISO subdirectory there is same software available as an ISO image that can be placed on a CD-ROM. Since In order to install this version please proceed with the following steps: 1. Download and uncompress the file dss6.0upXX_xxxx.oe_i.zip 2. Format a USB-stick partitioned as a FAT or FAT32 for the root directory (at least 512MB media size) 3. Copy the uncompressed directories and files onto USB-stick Directories: bxxxx and boot Files: mmenu_upd.sh 4. After copying the directories and files please verify that in the root directory resides: bxxxx boot mmenu_upd.sh 5. Access the directory called "boot" then run the bootinst.exe (for Windows only) or bootinst.sh (for Linux only). 6. Boot your storage server with the USB-stick. (please set the BIOS to boot form USB-stick, or in boot menu select USB-stick to boot) 7. In first menu there is choice to start current version or run memory test. Please press enter to run current version. 8. In the second menu there is 3 menu options: 32bit system TRIAL (2.6.27) 64bit system TRIAL (2.6.27) Run Software Installer In order to boot DSS V6 and run TRIAL version at once please select 32bit or 64 bit accordingly to your current system architecture. The TRIAL will recognize your current volume groups and volumes even if you had a previous version of DSS, but keep in mind that this will start with factory defaults settings. In order to restore your current settings, please go to menu: MAINTENANCE->miscellaneous and check the SETUP and CONFIGURATION check-boxes and then select the green action button. It will prompt for system re-boot. After re-boot you can test how your storage system works with the new software. If all is working properly we recommend to update. In order to install DSS V6 on other bootable media, in second menu please select: Run software update installer Please follow all steps until reboot. PLEASE NOTE: After sixty (60) days of the creation of the first volume group, the free trial version of the software will expire, and the connection to all logical volumes will be lost. Thus, all data stored on logical volumes created on the test system will no longer be accessible. However, if you purchase a license for the full version of the software and activate it on the test system before the expiration of sixty (60) days, all of the data will become available again. The trial version supports unlimited storage size. The full version supports 4, 8 or 16TB out of the box - this storage capacity can be further extended by purchasing additional storage licenses. Once your product reaches a licensed capacity of 48TB, it will automatically be extended to unlimited storage. IMPORTANT NOTE: Each 16TB of replicated capacity requires an additional 1GB RAM over minimal requirements. For example, a system with 32TB of replicated capacity requires 1GB RAM as per minimal requirements as well as additional 2GB RAM for the replication, which makes 3GB in total. IMPORTANT NOTE: In case you experience a problem with the availability of iSCSI / FC volumes after the upgrade from version <= 4622, please change the Identification Device (VPD) compatibility to SCST 1.0. You can do it in console tools (CTRL+ALT+W -> Tuning options -> SCST subsystem options -> Device Identification (VPD) compatibility -> SCST). Important notes regarding updating a system with failover in use: This procedure is only applicable to a system with an individual product key (trial versions are excluded). In case of upgrade from version <= 4622 please use following instructions - Update the Secondary system first using the software update functionality and reboot. * In case of using VMware ESX(i) or MS Hyper-V Initiator system, you need to change the Identification Device (VPD) compatibility to SCST 1.0 on the secondary node. This is located in the Console tools (CTRL+ALT+W -> Tuning options -> SCST subsystem options -> Device Identification (VPD) compatibility -> SCST VPD) - Then once the Secondary is running click on the start button in the Failover manager. - Now update the Primary system using the software update functionality and reboot. * In case of using VMware ESX(i) or MS Hyper-V as Initiator system, change the Identification Device (VPD) compatibility to SCST 1.0 on the Primary node. This is located in the Console tools (CTRL+ALT+W-> Tuning options -> SCST subsystem options -> Device Identification (VPD) compatibility -> SCST VPD) - Once the Primary is running go to the Secondary and click on the Sync volumes button in the Failover manager. - Then click on the Failback button in the Secondary system. - The Primary system now be go back to the active mode and ready for another failover. NOTE: - In case you are experiencing a problem with the availability of volumes iSCSI or FC after the upgrade from version <=4622, please change the Identification Device (VPD) compatibility to SCST 1.0. This is located in Console the tools (CTRL+ALT+W -> Tuning options -> SCST subsystem options -> Device Identification (VPD) compatibility -> SCST VPD) - In order to run system in rescue mode please add proper parameter to kernel command line. This can be done while system booting by following steps below : 1. reboot the system 2. while the system booting press "Tab" key on "Architecture selection" screen 3. type "rescue_mode" and press "Enter" key (in order to run the system without splash) or 4. type "rescue_mode=no_mount_lv" and press "Enter" key (in order to run the system without mounting logical volumes) NOTE: A few steps in case of changing TRIAL to FULL when Failover functionality is enabled: Assuming there is working Failover configuration where: - Primary node is Active, - Secondary node is Passive, - only NFS service is enabled. Following procedure describes necessary steps for continuing Failover activity with enabled NFS service. Please perform following steps: On Secondary node: 1. Enter Product Key. 2. Reboot server. 3. Enter License Key for NAS Failover. 4. Reboot server. 5. Start Failover clicking Start in Failover Manager After above please perform following steps on Primary node: 6. Perform Manual Failover. After it Secondary node has to be in Secondary/Active mode. 7. Enter Product Key. 8. Reboot server. 8. Enter License Key for NAS Failover. 10. Reboot server. At the end please perform Synchronize and Failback actions on Secondary node: 11. Click Synchronize button in Failover Manager. 12. Check if volume replication tasks are running and consistent and click Failback button. At this moment your Failover should have status Primary/Active - Secondary/Passive Assuming there is working Failover configuration where: - Primary node is Active, - Secondary node is Passive, - both NFS and iSCSI services are enabled. Following procedure describes necessary steps for continuing Failover activity without enabled NFS service (only iSCSI service will be used). On Primary node: 1. Stop Failover in Failover Manager. 2. Remove all NAS tasks from Failover Tasks. 3. Disable NFS service in Failover Services. 4. Start Failover in Failover Manager. On Secondary node: 5. Enter Product Key. 6. Reboot server. 7. Start Failover clicking Start in Failover Manager After above please perform following steps on Primary node: 8. Perform Manual Failover. After it Secondary node has to be in Secondary/Active mode. 9. Enter Product Key. 10. Reboot server. At the end please perform Synchronize and Failback actions on Secondary node: 11. Click Synchronize button in Failover Manager on Secondary node 12. Check if volume replication tasks are running and consistent and click Failback button. At this moment your Failover should have status Primary/Active - Secondary/Passive NEW: - Support for MAC OS X 10.7 (LION) UPDATED: - Simplified installation process by reducing number of steps - Updated remove logs mechanism to prevent a situation when the system volume is overfilled - Updated igb driver to version 3.1.16 FIXED: - Logs from LSI RAID controller contains internal system errors about undefined paths TESTING: - Infiniband tuning - possible to switch to connected mode (console tools ctrl-alt-w -> Infiniband tuning) - Disk performance test under console (console tools ctrl-alt-w -> System benchmarks -> Disk performance test) - API function to manage iSCSI Cluster (broadcast mode only) - Possibility of turning on and off TCP offload engine (console tools ctrl-alt-w -> Tuning options -> TCP offload options) - NDMP server provides incremental backup functionality in combination with NetBackup - Support for more than 27 units in Software RAID function KNOWN ISSUES: - Synchronize UID and GID database with NIS server does not work properly - In case of pairing NAS volumes with different names in volume replication tasks while NAS (NFS) Failover configuration (i.e. lv0000 on primary node -> lv0001 on secondary node) NAS (NFS) Failover functionality may not work properly. This problem will be resolved in future releases. - NAS (NFS) Failover functionality does not work properly with Mac OS. - Windows Services for UNIX are not supported in NFS Failover functionality, - In some environments connection to ADS is possible with second connection attempt via GUI - In the case of more than one Domain Controller (DC) in the same forest, the connection to the one of those DC's can sometimes be lost - In the event of a very slow storage adapter rescan in VMware, please use Static Discovery instead of Dynamic Discovery in VMware settings - In a large Active Directory with tens of thousands of USERS and GROUPS, some USERS or GROUPS may not appear on the listed interface - The Promise Array Manager tool has been temporarily removed; it will be implemented in its newest version in future builds - MPIO mode with FC HBA's in INITIATOR mode does not work. MPIO will function in FC TARGET mode. Only QLOGIC FC HBA's are supported in TARGET mode - Snapshot overflow may occur when working with a virtual backup device - Rescan function is not working properly when resizing storage connected via iSCSI Initiator - after rescan changes will be not visible. In this event please restart the system - With a Chelsio network interface card, the system may not be stable when using the built-in iSCSI initiator - Neteffect cards show unstable behavior - In case you are facing a performance related issue with network bandwidth, please try to disable TCP offload engine in Hardware console tools (Alt + Ctrl + w) -> Tuning options -> TCP offload options - The TX-check-summing cannot be changed for nVidia based network controllers - High Point array management tool does not work - Infiniband interfaces cannot be configured over the Web GUI - WWW configuration tool for Promise controllers does not work - After changing the default volume group (Select Default Volume Group) the current settings will not be kept. To keep the current settings, use the Save settings function in the Web GUI before switching the VG and restoring these settings afterwards, system will need to reboot - If you are using ADS authentication, the 'All Squash' option for NFS will not work correctly - After changing a user password via the WebGUI, this user will no longer be able to access password-protected shares published via AFP to which they previously had access. In such a case, deleting the user and re-creating the same user with a new password works - VMware ESX systems are sensitive to changes of the iSCSI Target. When switching between IET and SCST (both directions) VMware will not recognize the volumes. See http://kb.vmware.com/kb/9453805 - With ixgb network interface card, the system may not be stable when using the built-in iSCSI initiator - System cannot be installed on storage attached to an ICP Vortex controller - When using DSS V6 in windows 2008 cluster environment a failover event on DSS V6 will break i/o operation performed on the DSS V6 iSCSI target e.g. copying of files - Remote and console tools for managing FC do not work - In the case of downgrade it is necessary to configure Volume Replication tasks and Failover service again. Otherwise, it may not work correctly. Data Storage Software V6 2011-08-18 6.0 up80 build 5626 IMPORTANT NOTE: FOR UPDATE via WEB GUI in menu: MAINTENANCE-> software update -> Function: System software update, PLEASE use ISO image ONLY! The ZIP image can be used for installing or running quick trial. This is installable version. The built-in installer can install the Data Storage Software V6 on any bootable media. You can use the following media types: USB DOM (with Wear-Leveling support), IDE (ATA) DOM, SATA DOM, IDE (ATA) Hard Disk, SATA Hard Disk, SCSI Hard Disk or 2GB small LUN on a Hardware RAID (recommended). In order to install the software on separate LUN, please use RAID controllers with multiple LUN support. Please create a small 2GB logical unit for DSS V6. When Running DSS V6 installer you will need to select the 2GB logical unit as the boot media. The rest of the RAID space please create second LUN for the user data. The following RAID controllers are supported as a bootable media: MegaRAID, Smart Array, 3ware, Adaptec, ICP vortex, Areca. For Smart Array please use the RAID management CD as the RAID BIOS does not support LUN management. The provided software can be used for evaluation for 60 days with TRIAL product key. This software must be installed on a USB-stick first. In the ISO subdirectory there is same software available as an ISO image that can be placed on a CD-ROM. Since In order to install this version please proceed with the following steps: 1. Download and uncompress the file dss6.0upXX_xxxx.oe_i.zip 2. Format a USB-stick partitioned as a FAT or FAT32 for the root directory (at least 512MB media size) 3. Copy the uncompressed directories and files onto USB-stick Directories: bxxxx and boot Files: mmenu_upd.sh 4. After copying the directories and files please verify that in the root directory resides: bxxxx boot mmenu_upd.sh 5. Access the directory called "boot" then run the bootinst.exe (for Windows only) or bootinst.sh (for Linux only). 6. Boot your storage server with the USB-stick. (please set the BIOS to boot form USB-stick, or in boot menu select USB-stick to boot) 7. In first menu there is choice to start current version or run memory test. Please press enter to run current version. 8. In the second menu there is 3 menu options: 32bit system TRIAL (2.6.27) 64bit system TRIAL (2.6.27) Run Software Installer In order to boot DSS V6 and run TRIAL version at once please select 32bit or 64 bit accordingly to your current system architecture. The TRIAL will recognize your current volume groups and volumes even if you had a previous version of DSS, but keep in mind that this will start with factory defaults settings. In order to restore your current settings, please go to menu: MAINTENANCE->miscellaneous and check the SETUP and CONFIGURATION check-boxes and then select the green action button. It will prompt for system re-boot. After re-boot you can test how your storage system works with the new software. If all is working properly we recommend to update. In order to install DSS V6 on other bootable media, in second menu please select: Run software update installer Please follow all steps until reboot. PLEASE NOTE: After sixty (60) days of the creation of the first volume group, the free trial version of the software will expire, and the connection to all logical volumes will be lost. Thus, all data stored on logical volumes created on the test system will no longer be accessible. However, if you purchase a license for the full version of the software and activate it on the test system before the expiration of sixty (60) days, all of the data will become available again. The trial version supports unlimited storage size. The full version supports 4, 8 or 16TB out of the box - this storage capacity can be further extended by purchasing additional storage licenses. Once your product reaches a licensed capacity of 48TB, it will automatically be extended to unlimited storage. IMPORTANT NOTE: In case of using failover functionality please be aware that in build 5626 each interface with virtual IP must have auxiliary connection enabled. IMPORTANT NOTE: Each 16TB of replicated capacity requires an additional 1GB RAM over minimal requirements. For example, a system with 32TB of replicated capacity requires 1GB RAM as per minimal requirements as well as additional 2GB RAM for the replication, which makes 3GB in total. IMPORTANT NOTE: In case you experience a problem with the availability of iSCSI / FC volumes after the upgrade from version <= 4622, please change the Identification Device (VPD) compatibility to SCST 1.0. You can do it in console tools (CTRL+ALT+W -> Tuning options -> SCST subsystem options -> Device Identification (VPD) compatibility -> SCST). Important notes regarding updating a system with failover in use: This procedure is only applicable to a system with an individual product key (trial versions are excluded). In case of upgrade from version <= 4622 please use following instructions - Update the Secondary system first using the software update functionality and reboot. * In case of using VMware ESX(i) or MS Hyper-V Initiator system, you need to change the Identification Device (VPD) compatibility to SCST 1.0 on the secondary node. This is located in the Console tools (CTRL+ALT+W -> Tuning options -> SCST subsystem options -> Device Identification (VPD) compatibility -> SCST VPD) - Then once the Secondary is running click on the start button in the Failover manager. - Now update the Primary system using the software update functionality and reboot. * In case of using VMware ESX(i) or MS Hyper-V as Initiator system, change the Identification Device (VPD) compatibility to SCST 1.0 on the Primary node. This is located in the Console tools (CTRL+ALT+W-> Tuning options -> SCST subsystem options -> Device Identification (VPD) compatibility -> SCST VPD) - Once the Primary is running go to the Secondary and click on the Sync volumes button in the Failover manager. - Then click on the Failback button in the Secondary system. - The Primary system now be go back to the active mode and ready for another failover. NOTE: - In case you are experiencing a problem with the availability of volumes iSCSI or FC after the upgrade from version <=4622, please change the Identification Device (VPD) compatibility to SCST 1.0. This is located in Console the tools (CTRL+ALT+W -> Tuning options -> SCST subsystem options -> Device Identification (VPD) compatibility -> SCST VPD) - In order to run system in rescue mode please add proper parameter to kernel command line. This can be done while system booting by following steps below : 1. reboot the system 2. while the system booting press "Tab" key on "Architecture selection" screen 3. type "rescue_mode" and press "Enter" key (in order to run the system without splash) or 4. type "rescue_mode=no_mount_lv" and press "Enter" key (in order to run the system without mounting logical volumes) NOTE: A few steps in case of changing TRIAL to FULL when Failover functionality is enabled: Assuming there is working Failover configuration where: - Primary node is Active, - Secondary node is Passive, - only NFS service is enabled. Following procedure describes necessary steps for continuing Failover activity with enabled NFS service. Please perform following steps: On Secondary node: 1. Enter Product Key. 2. Reboot server. 3. Enter License Key for NAS Failover. 4. Reboot server. 5. Start Failover clicking Start in Failover Manager After above please perform following steps on Primary node: 6. Perform Manual Failover. After it Secondary node has to be in Secondary/Active mode. 7. Enter Product Key. 8. Reboot server. 8. Enter License Key for NAS Failover. 10. Reboot server. At the end please perform Synchronize and Failback actions on Secondary node: 11. Click Synchronize button in Failover Manager. 12. Check if volume replication tasks are running and consistent and click Failback button. At this moment your Failover should have status Primary/Active - Secondary/Passive Assuming there is working Failover configuration where: - Primary node is Active, - Secondary node is Passive, - both NFS and iSCSI services are enabled. Following procedure describes necessary steps for continuing Failover activity without enabled NFS service (only iSCSI service will be used). On Primary node: 1. Stop Failover in Failover Manager. 2. Remove all NAS tasks from Failover Tasks. 3. Disable NFS service in Failover Services. 4. Start Failover in Failover Manager. On Secondary node: 5. Enter Product Key. 6. Reboot server. 7. Start Failover clicking Start in Failover Manager After above please perform following steps on Primary node: 8. Perform Manual Failover. After it Secondary node has to be in Secondary/Active mode. 9. Enter Product Key. 10. Reboot server. At the end please perform Synchronize and Failback actions on Secondary node: 11. Click Synchronize button in Failover Manager on Secondary node 12. Check if volume replication tasks are running and consistent and click Failback button. At this moment your Failover should have status Primary/Active - Secondary/Passive NEW: - Tips on GUI which works as guide (optional) - I/O errors cause failover action - Support for booting system via QLOGIC FC HBA H/W initiator UPDATED: - Updated lm-sensors to version 3.3.0 - Improved XFS performance and stability also as memory consumption for filesystem consistency check and repair - Improved performance for volume replication over 10Gb/s Ethernet (updated DRBD to version 8.3.10) - Updated drivers for Intel's Ethernet cards 10Gb/s (ixgbe - v3.3.9-NAPI) - Updated drivers for Intel's Ethernet cards 1Gb/s (e1000e - v1.3.10a-NAPI, e1000 - v8.0.30-NAPI) - Updated driver for LSI RAID controllers (megaraid_sas - v5.30) - Updated driver for Broadcom NetXtreme ethernet cards (bnx2 -v2.0.23b, bnx2x - v1.62.1) FIXED: - Fixed problems with timeouts for Volume Manager and Snapshots Assignments functions on GUI for 20 snapshots - Fixed problem with performance of volume replication in resync mode (problem occured only in build 5605) TESTING: - Infiniband tuning - possible to switch to connected mode (console tools ctrl-alt-w -> Infiniband tuning) - Disk performance test under console (console tools ctrl-alt-w -> System benchmarks -> Disk performance test) - API function to manage iSCSI Cluster (broadcast mode only) - Possibility of turning on and off TCP offload engine (console tools ctrl-alt-w -> Tuning options -> TCP offload options) - NDMP server provides incremental backup functionality in combination with NetBackup - Support for more than 27 units in Software RAID function KNOWN ISSUES: - Synchronize UID and GID database with NIS server does not work properly - In case of pairing NAS volumes with different names in volume replication tasks while NAS (NFS) Failover configuration (i.e. lv0000 on primary node -> lv0001 on secondary node) NAS (NFS) Failover functionality may not work properly. This problem will be resolved in future releases. - NAS (NFS) Failover functionality does not work properly with Mac OS. - Windows Services for UNIX are not supported in NFS Failover functionality, - In some environments connection to ADS is possible with second connection attempt via GUI - In the case of more than one Domain Controller (DC) in the same forest, the connection to the one of those DC's can sometimes be lost - In the event of a very slow storage adapter rescan in VMware, please use Static Discovery instead of Dynamic Discovery in VMware settings - In a large Active Directory with tens of thousands of USERS and GROUPS, some USERS or GROUPS may not appear on the listed interface - The Promise Array Manager tool has been temporarily removed; it will be implemented in its newest version in future builds - MPIO mode with FC HBA's in INITIATOR mode does not work. MPIO will function in FC TARGET mode. Only QLOGIC FC HBA's are supported in TARGET mode - Snapshot overflow may occur when working with a virtual backup device - Rescan function is not working properly when resizing storage connected via iSCSI Initiator - after rescan changes will be not visible. In this event please restart the system - With a Chelsio network interface card, the system may not be stable when using the built-in iSCSI initiator - Neteffect cards show unstable behavior - In case you are facing a performance related issue with network bandwidth, please try to disable TCP offload engine in Hardware console tools (Alt + Ctrl + w) -> Tuning options -> TCP offload options - The TX-check-summing cannot be changed for nVidia based network controllers - High Point array management tool does not work - Infiniband interfaces cannot be configured over the Web GUI - WWW configuration tool for Promise controllers does not work - After changing the default volume group (Select Default Volume Group) the current settings will not be kept. To keep the current settings, use the Save settings function in the Web GUI before switching the VG and restoring these settings afterwards, system will need to reboot - If you are using ADS authentication, the 'All Squash' option for NFS will not work correctly - After changing a user password via the WebGUI, this user will no longer be able to access password-protected shares published via AFP to which they previously had access. In such a case, deleting the user and re-creating the same user with a new password works - VMware ESX systems are sensitive to changes of the iSCSI Target. When switching between IET and SCST (both directions) VMware will not recognize the volumes. See http://kb.vmware.com/kb/9453805 - With ixgb network interface card, the system may not be stable when using the built-in iSCSI initiator - System cannot be installed on storage attached to an ICP Vortex controller - When using DSS V6 in windows 2008 cluster environment a failover event on DSS V6 will break i/o operation performed on the DSS V6 iSCSI target e.g. copying of files - Remote and console tools for managing FC do not work - In the case of downgrade it is necessary to configure Volume Replication tasks and Failover service again. Otherwise, it may not work correctly. Data Storage Software V6 2011-08-11 6.0 up80 build 5605 IMPORTANT NOTE: FOR UPDATE via WEB GUI in menu: MAINTENANCE-> software update -> Function: System software update, PLEASE use ISO image ONLY! The ZIP image can be used for installing or running quick trial. This is installable version. The built-in installer can install the Data Storage Software V6 on any bootable media. You can use the following media types: USB DOM (with Wear-Leveling support), IDE (ATA) DOM, SATA DOM, IDE (ATA) Hard Disk, SATA Hard Disk, SCSI Hard Disk or 2GB small LUN on a Hardware RAID (recommended). In order to install the software on separate LUN, please use RAID controllers with multiple LUN support. Please create a small 2GB logical unit for DSS V6. When Running DSS V6 installer you will need to select the 2GB logical unit as the boot media. The rest of the RAID space please create second LUN for the user data. The following RAID controllers are supported as a bootable media: MegaRAID, Smart Array, 3ware, Adaptec, ICP vortex, Areca. For Smart Array please use the RAID management CD as the RAID BIOS does not support LUN management. The provided software can be used for evaluation for 60 days with TRIAL product key. This software must be installed on a USB-stick first. In the ISO subdirectory there is same software available as an ISO image that can be placed on a CD-ROM. Since In order to install this version please proceed with the following steps: 1. Download and uncompress the file dss6.0upXX_xxxx.oe_i.zip 2. Format a USB-stick partitioned as a FAT or FAT32 for the root directory (at least 512MB media size) 3. Copy the uncompressed directories and files onto USB-stick Directories: bxxxx and boot Files: mmenu_upd.sh 4. After copying the directories and files please verify that in the root directory resides: bxxxx boot mmenu_upd.sh 5. Access the directory called "boot" then run the bootinst.exe (for Windows only) or bootinst.sh (for Linux only). 6. Boot your storage server with the USB-stick. (please set the BIOS to boot form USB-stick, or in boot menu select USB-stick to boot) 7. In first menu there is choice to start current version or run memory test. Please press enter to run current version. 8. In the second menu there is 3 menu options: 32bit system TRIAL (2.6.27) 64bit system TRIAL (2.6.27) Run Software Installer In order to boot DSS V6 and run TRIAL version at once please select 32bit or 64 bit accordingly to your current system architecture. The TRIAL will recognize your current volume groups and volumes even if you had a previous version of DSS, but keep in mind that this will start with factory defaults settings. In order to restore your current settings, please go to menu: MAINTENANCE->miscellaneous and check the SETUP and CONFIGURATION check-boxes and then select the green action button. It will prompt for system re-boot. After re-boot you can test how your storage system works with the new software. If all is working properly we recommend to update. In order to install DSS V6 on other bootable media, in second menu please select: Run software update installer Please follow all steps until reboot. PLEASE NOTE: After sixty (60) days of the creation of the first volume group, the free trial version of the software will expire, and the connection to all logical volumes will be lost. Thus, all data stored on logical volumes created on the test system will no longer be accessible. However, if you purchase a license for the full version of the software and activate it on the test system before the expiration of sixty (60) days, all of the data will become available again. The trial version supports unlimited storage size. The full version supports 4, 8 or 16TB out of the box - this storage capacity can be further extended by purchasing additional storage licenses. Once your product reaches a licensed capacity of 48TB, it will automatically be extended to unlimited storage. IMPORTANT NOTE: Each 16TB of replicated capacity requires an additional 1GB RAM over minimal requirements. For example, a system with 32TB of replicated capacity requires 1GB RAM as per minimal requirements as well as additional 2GB RAM for the replication, which makes 3GB in total. IMPORTANT NOTE: In case you experience a problem with the availability of iSCSI / FC volumes after the upgrade from version <= 4622, please change the Identification Device (VPD) compatibility to SCST 1.0. You can do it in console tools (CTRL+ALT+W -> Tuning options -> SCST subsystem options -> Device Identification (VPD) compatibility -> SCST). Important notes regarding updating a system with failover in use: This procedure is only applicable to a system with an individual product key (trial versions are excluded). In case of upgrade from version <= 4622 please use following instructions - Update the Secondary system first using the software update functionality and reboot. * In case of using VMware ESX(i) or MS Hyper-V Initiator system, you need to change the Identification Device (VPD) compatibility to SCST 1.0 on the secondary node. This is located in the Console tools (CTRL+ALT+W -> Tuning options -> SCST subsystem options -> Device Identification (VPD) compatibility -> SCST VPD) - Then once the Secondary is running click on the start button in the Failover manager. - Now update the Primary system using the software update functionality and reboot. * In case of using VMware ESX(i) or MS Hyper-V as Initiator system, change the Identification Device (VPD) compatibility to SCST 1.0 on the Primary node. This is located in the Console tools (CTRL+ALT+W-> Tuning options -> SCST subsystem options -> Device Identification (VPD) compatibility -> SCST VPD) - Once the Primary is running go to the Secondary and click on the Sync volumes button in the Failover manager. - Then click on the Failback button in the Secondary system. - The Primary system now be go back to the active mode and ready for another failover. NOTE: - In case you are experiencing a problem with the availability of volumes iSCSI or FC after the upgrade from version <=4622, please change the Identification Device (VPD) compatibility to SCST 1.0. This is located in Console the tools (CTRL+ALT+W -> Tuning options -> SCST subsystem options -> Device Identification (VPD) compatibility -> SCST VPD) - In order to run system in rescue mode please add proper parameter to kernel command line. This can be done while system booting by following steps below : 1. reboot the system 2. while the system booting press "Tab" key on "Architecture selection" screen 3. type "rescue_mode" and press "Enter" key (in order to run the system without splash) or 4. type "rescue_mode=no_mount_lv" and press "Enter" key (in order to run the system without mounting logical volumes) NOTE: A few steps in case of changing TRIAL to FULL when Failover functionality is enabled: Assuming there is working Failover configuration where: - Primary node is Active, - Secondary node is Passive, - only NFS service is enabled. Following procedure describes necessary steps for continuing Failover activity with enabled NFS service. Please perform following steps: On Secondary node: 1. Enter Product Key. 2. Reboot server. 3. Enter License Key for NAS Failover. 4. Reboot server. 5. Start Failover clicking Start in Failover Manager After above please perform following steps on Primary node: 6. Perform Manual Failover. After it Secondary node has to be in Secondary/Active mode. 7. Enter Product Key. 8. Reboot server. 8. Enter License Key for NAS Failover. 10. Reboot server. At the end please perform Synchronize and Failback actions on Secondary node: 11. Click Synchronize button in Failover Manager. 12. Check if volume replication tasks are running and consistent and click Failback button. At this moment your Failover should have status Primary/Active - Secondary/Passive Assuming there is working Failover configuration where: - Primary node is Active, - Secondary node is Passive, - both NFS and iSCSI services are enabled. Following procedure describes necessary steps for continuing Failover activity without enabled NFS service (only iSCSI service will be used). On Primary node: 1. Stop Failover in Failover Manager. 2. Remove all NAS tasks from Failover Tasks. 3. Disable NFS service in Failover Services. 4. Start Failover in Failover Manager. On Secondary node: 5. Enter Product Key. 6. Reboot server. 7. Start Failover clicking Start in Failover Manager After above please perform following steps on Primary node: 8. Perform Manual Failover. After it Secondary node has to be in Secondary/Active mode. 9. Enter Product Key. 10. Reboot server. At the end please perform Synchronize and Failback actions on Secondary node: 11. Click Synchronize button in Failover Manager on Secondary node 12. Check if volume replication tasks are running and consistent and click Failback button. At this moment your Failover should have status Primary/Active - Secondary/Passive NEW: - Tips on GUI which works as guide (optional) - I/O errors cause failover action - Support for booting system via QLOGIC FC HBA H/W initiator UPDATED: - Updated lm-sensors to version 3.3.0 - Improved XFS performance and stability also as memory consumption for filesystem consistency check and repair - Improved performance for volume replication over 10Gb/s Ethernet (updated DRBD to version 8.3.10) - Updated drivers for Intel's Ethernet cards 10Gb/s (ixgbe - v3.3.9-NAPI) - Updated drivers for Intel's Ethernet cards 1Gb/s (e1000e - v1.3.10a-NAPI, e1000 - v8.0.30-NAPI) - Updated driver for LSI RAID controllers (megaraid_sas - v5.30) - Updated driver for Broadcom NetXtreme ethernet cards (bnx2 -v2.0.23b, bnx2x - v1.62.1) FIXED: - Fixed problems with timeouts for Volume Manager and Snapshots Assignments functions on GUI for 20 snapshots TESTING: - Infiniband tuning - possible to switch to connected mode (console tools ctrl-alt-w -> Infiniband tuning) - Disk performance test under console (console tools ctrl-alt-w -> System benchmarks -> Disk performance test) - API function to manage iSCSI Cluster (broadcast mode only) - Possibility of turning on and off TCP offload engine (console tools ctrl-alt-w -> Tuning options -> TCP offload options) - NDMP server provides incremental backup functionality in combination with NetBackup - Support for more than 27 units in Software RAID function KNOWN ISSUES: - Synchronize UID and GID database with NIS server does not work properly - In case of pairing NAS volumes with different names in volume replication tasks while NAS (NFS) Failover configuration (i.e. lv0000 on primary node -> lv0001 on secondary node) NAS (NFS) Failover functionality may not work properly. This problem will be resolved in future releases. - NAS (NFS) Failover functionality does not work properly with Mac OS. - Windows Services for UNIX are not supported in NFS Failover functionality, - In some environments connection to ADS is possible with second connection attempt via GUI - In the case of more than one Domain Controller (DC) in the same forest, the connection to the one of those DC's can sometimes be lost - In the event of a very slow storage adapter rescan in VMware, please use Static Discovery instead of Dynamic Discovery in VMware settings - In a large Active Directory with tens of thousands of USERS and GROUPS, some USERS or GROUPS may not appear on the listed interface - The Promise Array Manager tool has been temporarily removed; it will be implemented in its newest version in future builds - MPIO mode with FC HBA's in INITIATOR mode does not work. MPIO will function in FC TARGET mode. Only QLOGIC FC HBA's are supported in TARGET mode - Snapshot overflow may occur when working with a virtual backup device - Rescan function is not working properly when resizing storage connected via iSCSI Initiator - after rescan changes will be not visible. In this event please restart the system - With a Chelsio network interface card, the system may not be stable when using the built-in iSCSI initiator - Neteffect cards show unstable behavior - In case you are facing a performance related issue with network bandwidth, please try to disable TCP offload engine in Hardware console tools (Alt + Ctrl + w) -> Tuning options -> TCP offload options - The TX-check-summing cannot be changed for nVidia based network controllers - High Point array management tool does not work - Infiniband interfaces cannot be configured over the Web GUI - WWW configuration tool for Promise controllers does not work - After changing the default volume group (Select Default Volume Group) the current settings will not be kept. To keep the current settings, use the Save settings function in the Web GUI before switching the VG and restoring these settings afterwards, system will need to reboot - If you are using ADS authentication, the 'All Squash' option for NFS will not work correctly - After changing a user password via the WebGUI, this user will no longer be able to access password-protected shares published via AFP to which they previously had access. In such a case, deleting the user and re-creating the same user with a new password works - VMware ESX systems are sensitive to changes of the iSCSI Target. When switching between IET and SCST (both directions) VMware will not recognize the volumes. See http://kb.vmware.com/kb/9453805 - With ixgb network interface card, the system may not be stable when using the built-in iSCSI initiator - System cannot be installed on storage attached to an ICP Vortex controller - When using DSS V6 in windows 2008 cluster environment a failover event on DSS V6 will break i/o operation performed on the DSS V6 iSCSI target e.g. copying of files - Remote and console tools for managing FC do not work - In the case of downgrade it is necessary to configure Volume Replication tasks and Failover service again. Otherwise, it may not work correctly. Data Storage Software V6 2011-05-06 6.0 up75 build 5377 IMPORTANT NOTE: FOR UPDATE via WEB GUI in menu: MAINTENANCE-> software update -> Function: System software update, PLEASE use ISO image ONLY! The ZIP image can be used for installing or running quick trial. This is installable version. The built-in installer can install the Data Storage Software V6 on any bootable media. You can use the following media types: USB DOM (with Wear-Leveling support), IDE (ATA) DOM, SATA DOM, IDE (ATA) Hard Disk, SATA Hard Disk, SCSI Hard Disk or 2GB small LUN on a Hardware RAID (recommended). In order to install the software on separate LUN, please use RAID controllers with multiple LUN support. Please create a small 2GB logical unit for DSS V6. When Running DSS V6 installer you will need to select the 2GB logical unit as the boot media. The rest of the RAID space please create second LUN for the user data. The following RAID controllers are supported as a bootable media: MegaRAID, Smart Array, 3ware, Adaptec, ICP vortex, Areca. For Smart Array please use the RAID management CD as the RAID BIOS does not support LUN management. The provided software can be used for evaluation for 60 days with TRIAL product key. This software must be installed on a USB-stick first. In the ISO subdirectory there is same software available as an ISO image that can be placed on a CD-ROM. Since In order to install this version please proceed with the following steps: 1. Download and uncompress the file dss6.0upXX_xxxx.oe_i.zip 2. Format a USB-stick partitioned as a FAT or FAT32 for the root directory (at least 512MB media size) 3. Copy the uncompressed directories and files onto USB-stick Directories: bxxxx and boot Files: mmenu_upd.sh 4. After copying the directories and files please verify that in the root directory resides: bxxxx boot mmenu_upd.sh 5. Access the directory called "boot" then run the bootinst.exe (for Windows only) or bootinst.sh (for Linux only). 6. Boot your storage server with the USB-stick. (please set the BIOS to boot form USB-stick, or in boot menu select USB-stick to boot) 7. In first menu there is choice to start current version or run memory test. Please press enter to run current version. 8. In the second menu there is 3 menu options: 32bit system TRIAL (2.6.27) 64bit system TRIAL (2.6.27) Run Software Installer In order to boot DSS V6 and run TRIAL version at once please select 32bit or 64 bit accordingly to your current system architecture. The TRIAL will recognize your current volume groups and volumes even if you had a previous version of DSS, but keep in mind that this will start with factory defaults settings. In order to restore your current settings, please go to menu: MAINTENANCE->miscellaneous and check the SETUP and CONFIGURATION check-boxes and then select the green action button. It will prompt for system re-boot. After re-boot you can test how your storage system works with the new software. If all is working properly we recommend to update. In order to install DSS V6 on other bootable media, in second menu please select: Run software update installer Please follow all steps until reboot. PLEASE NOTE: After sixty (60) days of the creation of the first volume group, the free trial version of the software will expire, and the connection to all logical volumes will be lost. Thus, all data stored on logical volumes created on the test system will no longer be accessible. However, if you purchase a license for the full version of the software and activate it on the test system before the expiration of sixty (60) days, all of the data will become available again. The trial version supports unlimited storage size. The full version supports 4, 8 or 16TB out of the box - this storage capacity can be further extended by purchasing additional storage licenses. Once your product reaches a licensed capacity of 48TB, it will automatically be extended to unlimited storage. IMPORTANT NOTE: Each 16TB of replicated capacity requires an additional 1GB RAM over minimal requirements. For example, a system with 32TB of replicated capacity requires 1GB RAM as per minimal requirements as well as additional 2GB RAM for the replication, which makes 3GB in total. IMPORTANT NOTE: In case you experience a problem with the availability of iSCSI / FC volumes after the upgrade from version <= 4622, please change the Identification Device (VPD) compatibility to SCST 1.0. You can do it in console tools (CTRL+ALT+W -> Tuning options -> SCST subsystem options -> Device Identification (VPD) compatibility -> SCST). Important notes regarding updating a system with failover in use: This procedure is only applicable to a system with an individual product key (trial versions are excluded). In case of upgrade from version <= 4622 please use following instructions - Update the Secondary system first using the software update functionality and reboot. * In case of using VMware ESX(i) or MS Hyper-V Initiator system, you need to change the Identification Device (VPD) compatibility to SCST 1.0 on the secondary node. This is located in the Console tools (CTRL+ALT+W -> Tuning options -> SCST subsystem options -> Device Identification (VPD) compatibility -> SCST VPD) - Then once the Secondary is running click on the start button in the Failover manager. - Now update the Primary system using the software update functionality and reboot. * In case of using VMware ESX(i) or MS Hyper-V as Initiator system, change the Identification Device (VPD) compatibility to SCST 1.0 on the Primary node. This is located in the Console tools (CTRL+ALT+W-> Tuning options -> SCST subsystem options -> Device Identification (VPD) compatibility -> SCST VPD) - Once the Primary is running go to the Secondary and click on the Sync volumes button in the Failover manager. - Then click on the Failback button in the Secondary system. - The Primary system now be go back to the active mode and ready for another failover. NOTE: - In case you are experiencing a problem with the availability of volumes iSCSI or FC after the upgrade from version <=4622, please change the Identification Device (VPD) compatibility to SCST 1.0. This is located in Console the tools (CTRL+ALT+W -> Tuning options -> SCST subsystem options -> Device Identification (VPD) compatibility -> SCST VPD) - In order to run system in rescue mode please add proper parameter to kernel command line. This can be done while system booting by following steps below : 1. reboot the system 2. while the system booting press "Tab" key on "Select kernel" screen 3. type "rescue_mode" and press "Enter" key (in order to run the system without splash) or 4. type "rescue_mode=no_mount_lv" and press "Enter" key (in order to run the system without mounting logical volumes) NOTE: A few steps in case of changing TRIAL to FULL when Failover functionality is enabled: Assuming there is working Failover configuration where: - Primary node is Active, - Secondary node is Passive, - only NFS service is enabled. Following procedure describes necessary steps for continuing Failover activity with enabled NFS service. Please perform following steps: On Secondary node: 1. Enter Product Key. 2. Reboot server. 3. Enter License Key for NAS Failover. 4. Reboot server. 5. Start Failover clicking Start in Failover Manager After above please perform following steps on Primary node: 6. Perform Manual Failover. After it Secondary node has to be in Secondary/Active mode. 7. Enter Product Key. 8. Reboot server. 8. Enter License Key for NAS Failover. 10. Reboot server. At the end please perform Synchronize and Failback actions on Secondary node: 11. Click Synchronize button in Failover Manager. 12. Check if volume replication tasks are running and consistent and click Failback button. At this moment your Failover should have status Primary/Active - Secondary/Passive Assuming there is working Failover configuration where: - Primary node is Active, - Secondary node is Passive, - both NFS and iSCSI services are enabled. Following procedure describes necessary steps for continuing Failover activity without enabled NFS service (only iSCSI service will be used). On Primary node: 1. Stop Failover in Failover Manager. 2. Remove all NAS tasks from Failover Tasks. 3. Disable NFS service in Failover Services. 4. Start Failover in Failover Manager. On Secondary node: 5. Enter Product Key. 6. Reboot server. 7. Start Failover clicking Start in Failover Manager After above please perform following steps on Primary node: 8. Perform Manual Failover. After it Secondary node has to be in Secondary/Active mode. 9. Enter Product Key. 10. Reboot server. At the end please perform Synchronize and Failback actions on Secondary node: 11. Click Synchronize button in Failover Manager on Secondary node 12. Check if volume replication tasks are running and consistent and click Failback button. At this moment your Failover should have status Primary/Active - Secondary/Passive NEW: - Limited bandwidth after trial/activation/subscription time has expired (reduces ethernet cards to 100Mb/s and FC cards to 1 or 2 Gb/s) - Support for the Adaptec RAID Controllers series 6 UPDATED: - Updated language packs for German and Russian FIXED: - High number of Volumes cause timeouts in function Create Share on WebGUI - Infiniband interfaces cannot be configured over the WebGUI TESTING: - API function to manage iSCSI Cluster - Possibility of turning on and off TCP offload engine (console tools ctrl-alt-w -> Tuning options -> TCP offload options) - NDMP server provides incremental backup functionality in combination with NetBackup - Support for up to 27 units for each Software RAID device KNOWN ISSUES: - In case of pairing NAS volumes with different names in volume replication tasks while NAS (NFS) Failover configuration (i.e. lv0000 on primary node -> lv0001 on secondary node) NAS (NFS) Failover functionality may not work properly. This problem will be resolved in future releases. - NFS Failover functionality does not work properly with Mac OS. - NAS (NFS) Failover functionality will not work properly if Volume Replication task used in this functionality has the same name as another task in the system (independent of task type). Please make sure the Volume Replication task name for the NAS (NFS) Failover configuration is different than any other task name. - Windows Services for UNIX are not supported in NFS Failover functionality, - In some environments connection to ADS is possible with second connection attempt via GUI - In the case of more than one Domain Controller (DC) in the same forest, the connection to the one of those DC's can sometimes be lost - In the event of a very slow storage adapter rescan in VMware, please use Static Discovery instead of Dynamic Discovery in VMware settings - In a large Active Directory with tens of thousands of USERS and GROUPS, some USERS or GROUPS may not appear on the listed interface - The Promise Array Manager tool has been temporarily removed; it will be implemented in its newest version in future builds - MPIO mode with FC HBA's in INITIATOR mode does not work. MPIO will function in FC TARGET mode. Only QLOGIC FC HBA's are supported in TARGET mode - Snapshot overflow may occur when working with a virtual backup device - Rescan function is not working properly when resizing storage connected via iSCSI Initiator - after rescan changes will be not visible. In this event please restart the system - With a Chelsio network interface card, the system may not be stable when using the built-in iSCSI initiator - Neteffect cards show unstable behavior - In case you are facing a performance related issue with network bandwidth, please try to disable TCP offload engine in Hardware console tools (Alt + Ctrl + w) -> Tuning options -> TCP offload options - The TX-check-summing cannot be changed for nVidia based network controllers - High Point array management tool does not work - Infiniband interfaces cannot be configured over the Web GUI - WWW configuration tool for Promise controllers does not work - After changing the default volume group (Select Default Volume Group) the current settings will not be kept. To keep the current settings, use the Save settings function in the Web GUI before switching the VG and restoring these settings afterwards, system will need to reboot - If you are using ADS authentication, the 'All Squash' option for NFS will not work correctly - After changing a user password via the WebGUI, this user will no longer be able to access password-protected shares published via AFP to which they previously had access. In such a case, deleting the user and re-creating the same user with a new password works - VMware ESX systems are sensitive to changes of the iSCSI Target. When switching between IET and SCST (both directions) VMware will not recognize the volumes. See http://kb.vmware.com/kb/9453805 - With ixgb network interface card, the system may not be stable when using the built-in iSCSI initiator - System cannot be installed on storage attached to an ICP Vortex controller - When using DSS V6 in windows 2008 cluster environment a failover event on DSS V6 will break i/o operation performed on the DSS V6 iSCSI target e.g. copying of files - Remote and console tools for managing FC do not work - In the case of downgrade it is necessary to configure Failover service again. Otherwise, it may not work correctly Data Storage Software V6 2011-03-01 6.0 up65 build 5217 IMPORTANT NOTE: FOR UPDATE via WEB GUI in menu: MAINTENANCE-> software update -> Function: System software update, PLEASE use ISO image ONLY! The ZIP image can be used for installing or running quick trial. This is installable version. The built-in installer can install the Data Storage Software V6 on any bootable media. You can use the following media types: USB DOM (with Wear-Leveling support), IDE (ATA) DOM, SATA DOM, IDE (ATA) Hard Disk, SATA Hard Disk, SCSI Hard Disk or 2GB small LUN on a Hardware RAID (recommended). In order to install the software on separate LUN, please use RAID controllers with multiple LUN support. Please create a small 2GB logical unit for DSS V6. When Running DSS V6 installer you will need to select the 2GB logical unit as the boot media. The rest of the RAID space please create second LUN for the user data. The following RAID controllers are supported as a bootable media: MegaRAID, Smart Array, 3ware, Adaptec, ICP vortex, Areca. For Smart Array please use the RAID management CD as the RAID BIOS does not support LUN management. The provided software can be used for evaluation for 60 days with TRIAL product key. This software must be installed on a USB-stick first. In the ISO subdirectory there is same software available as an ISO image that can be placed on a CD-ROM. Since In order to install this version please proceed with the following steps: 1. Download and uncompress the file dss6.0upXX_xxxx.oe_i.zip 2. Format a USB-stick partitioned as a FAT or FAT32 for the root directory (at least 512MB media size) 3. Copy the uncompressed directories and files onto USB-stick Directories: bxxxx and boot Files: mmenu_upd.sh 4. After copying the directories and files please verify that in the root directory resides: bxxxx boot mmenu_upd.sh 5. Access the directory called "boot" then run the bootinst.exe (for Windows only) or bootinst.sh (for Linux only). 6. Boot your storage server with the USB-stick. (please set the BIOS to boot form USB-stick, or in boot menu select USB-stick to boot) 7. In first menu there is choice to start current version or run memory test. Please press enter to run current version. 8. In the second menu there is 3 menu options: 32bit system TRIAL (2.6.27) 64bit system TRIAL (2.6.27) Run Software Installer In order to boot DSS V6 and run TRIAL version at once please select 32bit or 64 bit accordingly to your current system architecture. The TRIAL will recognize your current volume groups and volumes even if you had a previous version of DSS, but keep in mind that this will start with factory defaults settings. In order to restore your current settings, please go to menu: MAINTENANCE->miscellaneous and check the SETUP and CONFIGURATION check-boxes and then select the green action button. It will prompt for system re-boot. After re-boot you can test how your storage system works with the new software. If all is working properly we recommend to update. In order to install DSS V6 on other bootable media, in second menu please select: Run software update installer Please follow all steps until reboot. PLEASE NOTE: After sixty (60) days of the creation of the first volume group, the free trial version of the software will expire, and the connection to all logical volumes will be lost. Thus, all data stored on logical volumes created on the test system will no longer be accessible. However, if you purchase a license for the full version of the software and activate it on the test system before the expiration of sixty (60) days, all of the data will become available again. The trial version supports unlimited storage size. The full version supports 4, 8 or 16TB out of the box - this storage capacity can be further extended by purchasing additional storage licenses. Once your product reaches a licensed capacity of 48TB, it will automatically be extended to unlimited storage. IMPORTANT NOTE: Each 16TB of replicated capacity requires an additional 1GB RAM over minimal requirements. For example, a system with 32TB of replicated capacity requires 1GB RAM as per minimal requirements as well as additional 2GB RAM for the replication, which makes 3GB in total. IMPORTANT NOTE: In case you experience a problem with the availability of iSCSI / FC volumes after the upgrade from version <= 4622, please change the Identification Device (VPD) compatibility to SCST 1.0. You can do it in console tools (CTRL+ALT+W -> Tuning options -> SCST subsystem options -> Device Identification (VPD) compatibility -> SCST). Important notes regarding updating a system with failover in use: This procedure is only applicable to a system with an individual product key (trial versions are excluded). In case of upgrade from version <= 4622 please use following instructions - Update the Secondary system first using the software update functionality and reboot. * In case of using VMware ESX(i) or MS Hyper-V Initiator system, you need to change the Identification Device (VPD) compatibility to SCST 1.0 on the secondary node. This is located in the Console tools (CTRL+ALT+W -> Tuning options -> SCST subsystem options -> Device Identification (VPD) compatibility -> SCST VPD) - Then once the Secondary is running click on the start button in the Failover manager. - Now update the Primary system using the software update functionality and reboot. * In case of using VMware ESX(i) or MS Hyper-V as Initiator system, change the Identification Device (VPD) compatibility to SCST 1.0 on the Primary node. This is located in the Console tools (CTRL+ALT+W-> Tuning options -> SCST subsystem options -> Device Identification (VPD) compatibility -> SCST VPD) - Once the Primary is running go to the Secondary and click on the Sync volumes button in the Failover manager. - Then click on the Failback button in the Secondary system. - The Primary system now be go back to the active mode and ready for another failover. NOTE: - In case you are experiencing a problem with the availability of volumes iSCSI or FC after the upgrade from version <=4622, please change the Identification Device (VPD) compatibility to SCST 1.0. This is located in Console the tools (CTRL+ALT+W -> Tuning options -> SCST subsystem options -> Device Identification (VPD) compatibility -> SCST VPD) - In order to run system in rescue mode please add proper parameter to kernel command line. This can be done while system booting by following steps below : 1. reboot the system 2. while the system booting press "Tab" key on "Select kernel" screen 3. type "rescue_mode" and press "Enter" key (in order to run the system without splash) or 4. type "rescue_mode=no_mount_lv" and press "Enter" key (in order to run the system without mounting logical volumes) NOTE: A few steps in case of changing TRIAL to FULL when Failover functionality is enabled: Assuming there is working Failover configuration where: - Primary node is Active, - Secondary node is Passive, - only NFS service is enabled. Following procedure describes necessary steps for continuing Failover activity with enabled NFS service. Please perform following steps: On Secondary node: 1. Enter Product Key. 2. Reboot server. 3. Enter License Key for NAS Failover. 4. Reboot server. 5. Start Failover clicking Start in Failover Manager After above please perform following steps on Primary node: 6. Perform Manual Failover. After it Secondary node has to be in Secondary/Active mode. 7. Enter Product Key. 8. Reboot server. 8. Enter License Key for NAS Failover. 10. Reboot server. At the end please perform Synchronize and Failback actions on Secondary node: 11. Click Synchronize button in Failover Manager. 12. Check if volume replication tasks are running and consistent and click Failback button. At this moment your Failover should have status Primary/Active - Secondary/Passive Assuming there is working Failover configuration where: - Primary node is Active, - Secondary node is Passive, - both NFS and iSCSI services are enabled. Following procedure describes necessary steps for continuing Failover activity without enabled NFS service (only iSCSI service will be used). On Primary node: 1. Stop Failover in Failover Manager. 2. Remove all NAS tasks from Failover Tasks. 3. Disable NFS service in Failover Services. 4. Start Failover in Failover Manager. On Secondary node: 5. Enter Product Key. 6. Reboot server. 7. Start Failover clicking Start in Failover Manager After above please perform following steps on Primary node: 8. Perform Manual Failover. After it Secondary node has to be in Secondary/Active mode. 9. Enter Product Key. 10. Reboot server. At the end please perform Synchronize and Failback actions on Secondary node: 11. Click Synchronize button in Failover Manager on Secondary node 12. Check if volume replication tasks are running and consistent and click Failback button. At this moment your Failover should have status Primary/Active - Secondary/Passive NEW: - NAS (NFS) Failover functionality (additional License Extension sold separately for this feature) - Possibility to switch off/on access to share via SMB protocol (SMB protocol is turned on by default for each Share) FIXED: - Remote Console Access password is now preserved after software update - In the LITE version it is now possible to change architecture to 32bit permanently TESTING: - API function to manage iSCSI Cluster - Possibility of turning on and off TCP offload engine (console tools ctrl-alt-w -> Tuning options -> TCP offload options) - NDMP server provides incremental backup functionality in combination with NetBackup - Support for more than 27 units in Software RAID function KNOWN ISSUES: - NFS Failover functionality does not work properly with Mac OS, - Windows Services for UNIX are not supported in NFS Failover functionality, - In some environments connection to ADS is possible with second connection attempt via GUI - In the case of more than one Domain Controller (DC) in the same forest, the connection to the one of those DC's can sometimes be lost - In the event of a very slow storage adapter rescan in VMware, please use Static Discovery instead of Dynamic Discovery in VMware settings - In a large Active Directory with tens of thousands of USERS and GROUPS, some USERS or GROUPS may not appear on the listed interface - The Promise Array Manager tool has been temporarily removed; it will be implemented in its newest version in future builds - MPIO mode with FC HBA's in INITIATOR mode does not work. MPIO will function in FC TARGET mode. Only QLOGIC FC HBA's are supported in TARGET mode - Snapshot overflow may occur when working with a virtual backup device - Rescan function is not working properly when resizing storage connected via iSCSI Initiator - after rescan changes will be not visible. In this event please restart the system - With a Chelsio network interface card, the system may not be stable when using the built-in iSCSI initiator - Neteffect cards show unstable behavior - Netxen cards show unstable behavior - In case you are facing a performance related issue with network bandwidth, please try to disable TCP offload engine in Hardware console tools (Alt + Ctrl + w) -> Tuning options -> TCP offload options - The TX-check-summing cannot be changed for nVidia based network controllers - High Point array management tool does not work - Infiniband interfaces cannot be configured over the Web GUI - WWW configuration tool for Promise controllers does not work - After changing the default volume group (Select Default Volume Group) the current settings will not be kept. To keep the current settings, use the Save settings function in the Web GUI before switching the VG and restoring these settings afterwards, system will need to reboot - If you are using ADS authentication, the 'All Squash' option for NFS will not work correctly - After changing a user password via the WebGUI, this user will no longer be able to access password-protected shares published via AFP to which they previously had access. In such a case, deleting the user and re-creating the same user with a new password works - VMware ESX systems are sensitive to changes of the iSCSI Target. When switching between IET and SCST (both directions) VMware will not recognize the volumes. See http://kb.vmware.com/kb/9453805 - With ixgb network interface card, the system may not be stable when using the built-in iSCSI initiator - System cannot be installed on storage attached to an ICP Vortex controller - When using DSS V6 in windows 2008 cluster environment a failover event on DSS V6 will break i/o operation performed on the DSS V6 iSCSI target e.g. copying of files - Tools for Managing FC on the console do not work - In the case of downgrade it is necessary to configure Failover service again. Otherwise, it may not work correctly 2011-01-12 6.0 up55 build 5087 IMPORTANT NOTE: FOR UPDATE via WEB GUI in menu: MAINTENANCE-> software update -> Function: System software update, PLEASE use ISO image ONLY! The ZIP image can be used for installing or running quick trial. This is installable version. The built-in installer can install the Data Storage Software V6 on any bootable media. You can use the following media types: USB DOM (with Wear-Leveling support), IDE (ATA) DOM, SATA DOM, IDE (ATA) Hard Disk, SATA Hard Disk, SCSI Hard Disk or 2GB small LUN on a Hardware RAID (recommended). In order to install the software on separate LUN, please use RAID controllers with multiple LUN support. Please create a small 2GB logical unit for DSS V6. When Running DSS V6 installer you will need to select the 2GB logical unit as the boot media. The rest of the RAID space please create second LUN for the user data. The following RAID controllers are supported as a bootable media: MegaRAID, Smart Array, 3ware, Adaptec, ICP vortex, Areca. For Smart Array please use the RAID management CD as the RAID BIOS does not support LUN management. The provided software can be used for evaluation for 60 days with TRIAL product key. This software must be installed on a USB-stick first. In the ISO subdirectory there is same software available as an ISO image that can be placed on a CD-ROM. Since In order to install this version please proceed with the following steps: 1. Download and uncompress the file dss6.0upXX_xxxx.oe_i.zip 2. Format a USB-stick partitioned as a FAT or FAT32 for the root directory (at least 512MB media size) 3. Copy the uncompressed directories and files onto USB-stick Directories: bxxxx and boot Files: mmenu_upd.sh 4. After copying the directories and files please verify that in the root directory resides: bxxxx boot mmenu_upd.sh 5. Access the directory called "boot" then run the bootinst.exe (for Windows only) or bootinst.sh (for Linux only). 6. Boot your storage server with the USB-stick. (please set the BIOS to boot form USB-stick, or in boot menu select USB-stick to boot) 7. In first menu there is choice to start current version or run memory test. Please press enter to run current version. 8. In the second menu there is 3 menu options: 32bit system TRIAL (2.6.27) 64bit system TRIAL (2.6.27) Run Software Installer In order to boot DSS V6 and run TRIAL version at once please select 32bit or 64 bit accordingly to your current system architecture. The TRIAL will recognize your current volume groups and volumes even if you had a previous version of DSS, but keep in mind that this will start with factory defaults settings. In order to restore your current settings, please go to menu: MAINTENANCE->miscellaneous and check the SETUP and CONFIGURATION check-boxes and then select the green action button. It will prompt for system re-boot. After re-boot you can test how your storage system works with the new software. If all is working properly we recommend to update. In order to install DSS V6 on other bootable media, in second menu please select: Run software update installer Please follow all steps until reboot. PLEASE NOTE: After sixty (60) days of the creation of the first volume group, the free trial version of the software will expire, and the connection to all logical volumes will be lost. Thus, all data stored on logical volumes created on the test system will no longer be accessible. However, if you purchase a license for the full version of the software and activate it on the test system before the expiration of sixty (60) days, all of the data will become available again. The trial version supports unlimited storage size. The full version supports 4, 8 or 16TB out of the box - this storage capacity can be further extended by purchasing additional storage licenses. Once your product reaches a licensed capacity of 48TB, it will automatically be extended to unlimited storage. IMPORTANT NOTE: Each 16TB of replicated capacity requires an additional 1GB RAM over minimal requirements. For example, a system with 32TB of replicated capacity requires 1GB RAM as per minimal requirements as well as additional 2GB RAM for the replication, which makes 3GB in total. IMPORTANT NOTE: In case you experience a problem with the availability of iSCSI / FC volumes after the upgrade from version <= 4622, please change the Identification Device (VPD) compatibility to SCST 1.0. You can do it in console tools (CTRL+ALT+W -> Tuning options -> SCST subsystem options -> Device Identification (VPD) compatibility -> SCST). Important notes regarding updating a system with failover in use: This procedure is only applicable to a system with an individual product key (trial versions are excluded). In case of upgrade from version <= 4622 please use following instructions - Update the Secondary system first using the software update functionality and reboot. * In case of using VMware ESX(i) or MS Hyper-V Initiator system, you need to change the Identification Device (VPD) compatibility to SCST 1.0 on the secondary node. This is located in the Console tools (CTRL+ALT+W -> Tuning options -> SCST subsystem options -> Device Identification (VPD) compatibility -> SCST VPD) - Then once the Secondary is running click on the start button in the Failover manager. - Now update the Primary system using the software update functionality and reboot. * In case of using VMware ESX(i) or MS Hyper-V as Initiator system, change the Identification Device (VPD) compatibility to SCST 1.0 on the Primary node. This is located in the Console tools (CTRL+ALT+W-> Tuning options -> SCST subsystem options -> Device Identification (VPD) compatibility -> SCST VPD) - Once the Primary is running go to the Secondary and click on the Sync volumes button in the Failover manager. - Then click on the Failback button in the Secondary system. - The Primary system now be go back to the active mode and ready for another failover. NOTE: - In case you are experiencing a problem with the availability of volumes iSCSI or FC after the upgrade from version <=4622, please change the Identification Device (VPD) compatibility to SCST 1.0. This is located in Console the tools (CTRL+ALT+W -> Tuning options -> SCST subsystem options -> Device Identification (VPD) compatibility -> SCST VPD) - In order to run system in rescue mode please add proper parameter to kernel command line. This can be done while system booting by following steps below : 1. reboot the system 2. while the system booting press "Tab" key on "Select kernel" screen 3. type "rescue_mode" and press "Enter" key (in order to run the system without splash) or 4. type "rescue_mode=no_mount_lv" and press "Enter" key (in order to run the system without mounting logical volumes) NEW: - Notify for unclean shutdown/restart of the system - Possibility to run system in rescue mode without mounting any volumes during start - it allow to check volumes consistency and repair volumes using extended tools on console - Support for Adaptec maxCache SSD Caching - SWAP is supported on local storage (Reserved for pool space is automatically converted to SWAP volume) - Possibility of turning on and off Unix extension for SMB protocol (default is set to off) UPDATED: - LSI SAS driver megaraid_sas ver 4.31 - Tools for managing Intel RAID ver 8.10-04 (via Intel RAID Web Console2) - It is necessary to upgrade Intel RAID controller firmware using Intel RAID Web Console2 tools before starts managing this controller. - Tools for managing LSI RAID ver 8.10-04 (via LSI MegaRAID Storage Manager) - It is necessary to upgrade LSI RAID controller firmware using LSI MegaRAID Storage Manager tools before starts managing this controller. - Tools for managing Adaptec RAID ver 6.50.18579 (Adaptec Storage Manager) - Prevent for changing jumbo frames while failover environment is active - Backward compatibility of iSCSI and FC LUN's available on console (VPD) - In case you are experiencing a problem with the availability of volumes iSCSI / FC after the upgrade from version <=4622, please change the Identification Device (VPD) compatibility to SCST 1.0. This is located in the Console tools (CTRL+ALT+W -> Tuning options -> SCST subsystem options -> Device Identification (VPD) compatibility -> SCST VPD 1.0). - FTP server configuration options: UseReverseDNS and IdentLookups are set to OFF - Inactive connection of AFP are kept by one week - Possibility to install the system on LSI 2008 RAID controller FIXED: - Losing access to ping nodes from secondary/active node doesn't switch this node into suspend mode - Solved the problem with overfilling rootfs causing "Low space!..." warning - Using Intel RAID Web Console2 or LSI MegaRAID Storage Manager is possible to established connection with server via all Ethernet cards - OEM mechanism preserve limitation for product Menu and Submenu - Solved the problem with listing large number of users and groups on WebUI - Brute force attack doesn't cause blocking login on the GUI - Local DNS checking doesn't cause notification that DNS server is wrong - FC and iSCSI target manager supports Persistent Reservation for LUN's bigger than 2TB - Remote Support is working even if memory leak occurs - Removed message in console about detected metadata of FakeRAID when disks doesn't keep such metadata - Manipulating a share with a nested AFP share doesn't cause remove nested share from AFP configuration - Web browser cache is refreshed if some H/W will be change on server side e.g. FC HBA has been inserted - Improved logging system to prevent situation when system volume will be overfill - Improved memory usage of Data Replication functionality TESTING: - Management ISCSI Cluster using API functionality - Possibility of turning on and off TCP offload engine (console tools ctrl-alt-w -> Tuning options -> TCP offload options) - NDMP server provide incremental backup functionality in combination with NetBackup - Support for more than 27 units in s/w raid KNOWN ISSUES: - In case of existing more than one Domain Controller (DC) in the same forest, connection to the one of those DC can sometimes be lost - In case a problem with very slow storage adapter rescan in VMware, please use Static Discovery instead of Dynamic Discovery in VMware settings - In a large Active Directory with tens of thousands of USERS and GROUPS, some USERS or GROUPS may not appear on the listed interface - The Promise Array Manager tool has been temporarily removed; it will be implemented in its newest version in future builds - MPIO mode with FC HBA?s in INITIATOR mode does not work. MPIO will function in FC TARGET mode. Only QLOGIC FC HBA?s are supported in TARGET mode - Snapshot overflow may occur when working with a virtual backup device - Rescan function is not working properly when resizing storage connected via iSCSI Initiator - after rescan changes will be not visible. In such a case please restart the system - In case of Chelsio network interface card, the system may not run stable when using the built-in iSCSI initiator - Neteffect cards show unstable behavior - Netxen cards show unstable behavior - In case you are facing performance related issue with network bandwidth, please try to disable TCP offload engine in Hardware console tools (Alt + Ctrl + w) -> Tuning options -> TCP offload options - The TX-checksumming cannot be changed for nVidia based network controllers - High Point array management tool does not work - Infiniband interfaces cannot be configured over the Web GUI - WWW configuration tool for Promise controllers does not work - After changing the default volume group using (Select Default Volume Group) the current settings will not be kept. To keep the current settings, use the Save settings function in the Web GUI before switching the VG and restore these settings afterwards, system will need to reboot - If you are using ADS authentication, the 'All Squash' option for NFS will not work correctly - After changing a user password via the WebGUI, this user will no longer be able to access password-protected shares published via AFP to which they previously had access. In such case, deleting the user and re-creating the same user with new password works - VMware ESX systems are sensitive to change of the iSCSI Target. In case of switch between IET and SCST (both directions) VMware will not recognize the volumes. See http://kb.vmware.com/kb/9453805 - In case of ixgb network interface card, the system may not run stable when using the build-in iSCSI initiator - System cannot be installed on storage attached to an ICP Vortex controller - In case of using DSS V6 in windows 2008 cluster environment failover event on DSS V6 level will break i/o operation performed on DSS V6 iSCSI target eg. copying of files - Tools for Management FC on the console does not work - Remote Console Access password is not preserved after software update and must be set one more time. P R E V I O U S V E R S I O N S 2010-09-30 v6.0 up50 build 4786 IMPORTANT NOTE: FOR UPDATE via WEB GUI in menu: MAINTENANCE-> software update -> Function: System software update, PLEASE use ISO image ONLY! The ZIP image can be used for installing or running quick trial. This is installable version. The built-in installer can install the Data Storage Software V6 on any bootable media. You can use the following media types: USB DOM (with Wear-Leveling support), IDE (ATA) DOM, SATA DOM, IDE (ATA) Hard Disk, SATA Hard Disk, SCSI Hard Disk or 2GB small LUN on a Hardware RAID (recommended). In order to install the software on separate LUN, please use RAID controllers with multiple LUN support. Please create a small 2GB logical unit for DSS V6. When Running DSS V6 installer you will need to select the 2GB logical unit as the boot media. The rest of the RAID space please create second LUN for the user data. The following RAID controllers are supported as a bootable media: MegaRAID, Smart Array, 3ware, Adaptec, ICP vortex, Areca. For Smart Array please use the RAID management CD as the RAID BIOS does not support LUN management. The provided software can be used for evaluation for 60 days with TRIAL product key. This software must be installed on a USB-stick first. In the ISO subdirectory there is same software available as an ISO image that can be placed on a CD-ROM. Since In order to install this version please proceed with the following steps: 1. Download and uncompress the file dss6.0upXX_xxxx.oe_i.zip 2. Format a USB-stick partitioned as a FAT or FAT32 for the root directory (at least 512MB media size) 3. Copy the uncompressed directories and files onto USB-stick Directories: bxxxx and boot Files: mmenu_upd.sh 4. After copying the directories and files please verify that in the root directory resides: bxxxx boot mmenu_upd.sh 5. Access the directory called "boot" then run the bootinst.exe (for Windows only) or bootinst.sh (for Linux only). 6. Boot your storage server with the USB-stick. (please set the BIOS to boot form USB-stick, or in boot menu select USB-stick to boot) 7. In first menu there is choice to start current version or run memory test. Please press enter to run current version. 8. In the second menu there is 3 menu options: 32bit system TRIAL (2.6.27) 64bit system TRIAL (2.6.27) Run Software Installer In order to boot DSS V6 and run TRIAL version at once please select 32bit or 64 bit accordingly to your current system architecture. The TRIAL will recognize your current volume groups and volumes even if you had a previous version of DSS, but keep in mind that this will start with factory defaults settings. In order to restore your current settings, please go to menu: MAINTENANCE->miscellaneous and check the SETUP and CONFIGURATION check-boxes and then select the green action button. It will prompt for system re-boot. After re-boot you can test how your storage system works with the new software. If all is working properly we recommend to update. In order to install DSS V6 on other bootable media, in second menu please select: Run software update installer Please follow all steps until reboot. PLEASE NOTE: After sixty (60) days of the creation of the first volume group, the free trial version of the software will expire, and the connection to all logical volumes will be lost. Thus, all data stored on logical volumes created on the test system will no longer be accessible. However, if you purchase a license for the full version of the software and activate it on the test system before the expiration of sixty (60) days, all of the data will become available again. The trial version supports unlimited storage size. The full version supports 4, 8 or 16TB out of the box - this storage capacity can be further extended by purchasing additional storage licenses. Once your product reaches a licensed capacity of 48TB, it will automatically be extended to unlimited storage. IMPORTANT NOTE: Each 16TB of replicated capacity requires an additional 1GB RAM over minimal requirements. For example, a system with 32TB of replicated capacity requires 1GB RAM as per minimal requirements as well as additional 2GB RAM for the replication, which makes 3GB in total. Release Notes NEW: - Possibility to dynamic switch between FC initiator and FC target without system restarting for Qlogic 2/4/8 Gb. - Support for Automatic Session Reassignment (ASR) for Fibre Channel and iSCSI protocols - Support for more than 8 Qlogic HBAs in target mode - Advanced options for Samba shares (Inherit owner, Inherit ACL's, Inherit permissions, Locking, Map ACL inherit) - Support for expander in build-in LSI RAID manager UPDATED: - iSCSI and Fibre Channel target architecture (SCST 2.0) - iSCSI target architecture (IETD v1.4.20.2) - iSCSI initiator architecture (Open-iSCSI v2.0-871) - Adaptec driver (1.1-5[26400]) and CLI tool (v6.50) NOTE: The Adaptec Storage Manager 6.5 was not updated. A small update will be available 14 business days after this release and will be in the next following release ETA end of October 2010. - AFP framework (Netatalk 2.1.3) - Data Replication (rsync ver. 3.0.7) - Backup Exec Agent ver. 13.0 (support for Symantec Backup Exec 2010 R2) FIXED: - Solved the problem with accessing to shares in Windows using DSS server name in case of using ADS authentication method - Solved the problem with displaying large number of elements on WebUI in ACL settings forms - Solved the problem with listing large number of users and groups on WebUI - Solved the problem with routing to local network in case of using a few IP addresses in the same subnet when not all links are plugged in - Solved the problem with status monitor for Intel SSR212CC server - Solved the problem with mounting symlinks in shares via NFS - Solved the problem with AFP configuration in case of using nested shares - Solved the problem with FTP and AFP authentication for users with multi part names - Solved the problem with saving 3ware 3dm2 configuration during system update TESTING: - Support for Adaptec MaxIQ SSD caching - Management ISCSI Cluster using API functionality KNOWN ISSUES: - New tools for XFS present in beta releases build 4710 till 4750 were removed from final release version. If you have created any NEW Logical Volumes on the beta version please backup your data first then remove Logical Volumes and re-create again. - In case of using bonding in modes balance-rr, balance-xor or broadcast there is no possiblity to turn on "AppleTalk (AFP) settings" function which activate Apple Filing Protocol (AFP). - Enabling/disabling replication functionality for NAS volume is not possible when the share exported via NFS is created on this volume. - A very large Active Directory with tens of thousands of USERS and GROUPS, some USERS or GROUPS may be not listed on the GUI. - The Promise Array Manager tool has been temporarily removed; it will be implemented in its newest version in future builds. - Intel RAID Web Console2 may not operate correctly due to tool bug (Only the highest Ethernet port position will work. Example: with Eth0,Eth1, Eth2 and Eth3, only Eth3 will work). As a workaround establish connection to the tool with the highest network card connected to the Open-E system or disable all except one controller (e.g. disable Eth1,Eth2 and Eth3 to force Eth0 to function). See http://www.intel.com/support/motherboards/server/sb/CS-028365.htm - LSI MegaRAID Storage Manager show the same issue as Intel RAID Web Console2 - MPIO mode with FC HBA's in INITIATOR mode does not work. MPIO will function in FC TARGET mode. Only QLOGIC FC HBA?s are supported in TARGET mode. - Snapshot overflow may occur when working with a virtual backup device. - Rescan function is not working properly when resizing storage connected via iSCSI Initiator - after rescan changes will be not visible. In such a case please restart the system. - In case of Chelsio network interface card, the system may not run stable when using the built-in iSCSI initiator. - Neteffect cards show unstable behavior. - Netxen cards show unstable behavior. - High Point array management tool does not work. - Infiniband interfaces cannot be configured over the Web GUI. - WWW configuration tool for Promise controllers does not work. - After changing the default volume group using (Select Default Volume Group) the current settings will not be kept. To keep the current settings, use the Save settings function in the Web GUI before switching the VG and restore these settings afterwards, system will need to reboot. - If you are using ADS authentication, the 'All Squash' option for NFS will not work correctly. - After changing a user password via the WebGUI, this user will no longer be able to access password-protected shares published via AFP to which they previously had access. In such case, deleting the user and re-creating the same user with new password works. - VMWare ESX systems are sensitive to change of the iSCSI Target. In case of switch between IET and SCST (both directions) VMWare will not recognize the volumes. iSCSI daemon options - > iSCSI solution and reboot the system. - In case of ixgb network interface card, the system may not run stable when using the build-in iSCSI initiator. - System cannot be installed on storage attached to an ICP Vortex controller. - In case of using DSS V6 in windows 2008 cluster environment failover event on DSS V6 level will break i/o operation performed on DSS V6 iSCSI target eg. copying of files. - Tools for Management FC on the console does not work. P R E V I O U S V E R S I O N S 2010-07-26 v6.0 up45 build 4622 IMPORTANT NOTE: FOR UPDATE via WEB GUI in menu: MAINTENANCE-> software update -> Function: System software update, PLEASE use ISO image ONLY! The ZIP image can be used for installing or running quick trial. This is installable version. The built-in installer can install the Data Storage Software V6 on any bootable media. You can use the following media types: USB DOM (with Wear-Leveling support), IDE (ATA) DOM, SATA DOM, IDE (ATA) Hard Disk, SATA Hard Disk, SCSI Hard Disk or 2GB small LUN on a Hardware RAID (recommended). In order to install the software on separate LUN, please use RAID controllers with multiple LUN support. Please create a small 2GB logical unit for DSS V6. When Running DSS V6 installer you will need to select the 2GB logical unit as the boot media. The rest of the RAID space please create second LUN for the user data. The following RAID controllers are supported as a bootable media: MegaRAID, Smart Array, 3ware, Adaptec, ICP vortex, Areca. For Smart Array please use the RAID management CD as the RAID BIOS does not support LUN management. The provided software can be used for evaluation for 60 days with TRIAL product key. This software must be installed on a USB-stick first. In the ISO subdirectory there is same software available as an ISO image that can be placed on a CD-ROM. Since In order to install this version please proceed with the following steps: 1. Download and uncompress the file dss6.0upXX_xxxx.oe_i.zip 2. Format a USB-stick partitioned as a FAT or FAT32 for the root directory (at least 512MB media size) 3. Copy the uncompressed directories and files onto USB-stick Directories: bxxxx and boot Files: mmenu_upd.sh 4. After copying the directories and files please verify that in the root directory resides: bxxxx boot mmenu_upd.sh 5. Access the directory called "boot" then run the bootinst.exe (for Windows only) or bootinst.sh (for Linux only). 6. Boot your storage server with the USB-stick. (please set the BIOS to boot form USB-stick, or in boot menu select USB-stick to boot) 7. In first menu there is choice to start current version or run memory test. Please press enter to run current version. 8. In the second menu there is 3 menu options: 32bit system TRIAL (2.6.27) 64bit system TRIAL (2.6.27) Run Software Installer In order to boot DSS V6 and run TRIAL version at once please select 32bit or 64 bit accordingly to your current system architecture. The TRIAL will recognize your current volume groups and volumes even if you had a previous version of DSS, but keep in mind that this will start with factory defaults settings. In order to restore your current settings, please go to menu: MAINTENANCE->miscellaneous and check the SETUP and CONFIGURATION check-boxes and then select the green action button. It will prompt for system re-boot. After re-boot you can test how your storage system works with the new software. If all is working properly we recommend to update. In order to install DSS V6 on other bootable media, in second menu please select: Run software update installer Please follow all steps until reboot. PLEASE NOTE: After sixty (60) days of the creation of the first volume group, the free trial version of the software will expire, and the connection to all logical volumes will be lost. Thus, all data stored on logical volumes created on the test system will no longer be accessible. However, if you purchase a license for the full version of the software and activate it on the test system before the expiration of sixty (60) days, all of the data will become available again. The trial version supports unlimited storage size. The full version supports 4, 8 or 16TB out of the box - this storage capacity can be further extended by purchasing additional storage licenses. Once your product reaches a licensed capacity of 48TB, it will automatically be extended to unlimited storage. IMPORTANT NOTE: Each 16TB of replicated capacity requires an additional 1GB RAM over minimal requirements. For example, a system with 32TB of replicated capacity requires 1GB RAM as per minimal requirements as well as additional 2GB RAM for the replication, which makes 3GB in total. Release Notes NEW: - System volume size for each new created volume group will be 4GB UPDATED: - Samba (v.3.5.4) FIXED: - ADS authorization is now possible also in case of use special characters in administrator password - Solved problem with reading workgroup name in case of use ADS authentication method - Entered routing rule is now correctly displayed on Web GUI - AFP log is now correctly rotated KNOWN ISSUES: - Enabling/disabling replication functionality for NAS volume is not possible when the share exported via NFS is created on this volume. - A very large Active Directory with tens of thousands of USERS and GROUPS, some USERS or GROUPS may be not listed on the GUI. - The Promise Array Manager tool has been temporarily removed; it will be implemented in its newest version in future builds. - The FTP protocol offers no possibility to authenticate with a multipart username. - Intel RAID Web Console2 may not operate correctly due to tool bug (Only the highest Ethernet port position will work. Example: with Eth0,Eth1, Eth2 and Eth3, only Eth3 will work). As a workaround establish connection to the tool with the highest network card connected to the Open-E system or disable all except one controller (e.g. disable Eth1,Eth2 and Eth3 to force Eth0 to function). See http://www.intel.com/support/motherboards/server/sb/CS-028365.htm - LSI MegaRAID Storage Manager show the same issue as Intel RAID Web Console2 - MPIO mode with FC HBA?s in INITIATOR mode does not work. MPIO will function in FC TARGET mode. Only QLOGIC FC HBA?s are supported in TARGET mode. - Snapshot overflow may occur when working with a virtual backup device. - Rescan function is not working properly when resizing storage connected via iSCSI Initiator - after rescan changes will be not visible. In such a case please restart the system. - In case of Chelsio network interface card, the system may not run stable when using the built-in iSCSI initiator. - Neteffect cards show unstable behavior. - Netxen cards show unstable behavior. - High Point array management tool does not work. - Infiniband interfaces cannot be configured over the Web GUI. - WWW configuration tool for Promise controllers does not work. - After changing the default volume group using (Select Default Volume Group) the current settings will not be kept. To keep the current settings, use the Save settings function in the Web GUI before switching the VG and restore these settings afterwards, system will need to reboot. - If you are using ADS authentication, the 'All Squash' option for NFS will not work correctly. - After changing a user password via the WebGUI, this user will no longer be able to access password-protected shares published via AFP to which they previously had access. In such case, deleting the user and re-creating the same user with new password works. - VMWare ESX systems are sensitive to change of the iSCSI Target. In case of switch between IET and SCST (both directions) VMWare will not recognize the volumes. - iSCSI daemon options - > iSCSI solution and reboot the system. - In case of ixgb network interface card, the system may not run stable when using the build-in iSCSI initiator. - System cannot be installed on storage attached to an ICP Vortex controller. - In case of using DSS V6 in windows 2008 cluster environment failover event on DSS V6 level will break i/o operation performed on DSS V6 iSCSI target eg. copying of files. - Tools for Management FC on the console does not work. P R E V I O U S V E R S I O N S 2010-06-11 v6.0 up40 build 4550 IMPORTANT NOTE: FOR UPDATE via WEB GUI in menu: MAINTENANCE-> software update -> Function: System software update, PLEASE use ISO image ONLY! The ZIP image can be used for installing or running quick trial. This is installable version. The built-in installer can install the Data Storage Software V6 on any bootable media. You can use the following media types: USB DOM (with Wear-Leveling support), IDE (ATA) DOM, SATA DOM, IDE (ATA) Hard Disk, SATA Hard Disk, SCSI Hard Disk or 2GB small LUN on a Hardware RAID (recommended). In order to install the software on separate LUN, please use RAID controllers with multiple LUN support. Please create a small 2GB logical unit for DSS V6. When Running DSS V6 installer you will need to select the 2GB logical unit as the boot media. The rest of the RAID space please create second LUN for the user data. The following RAID controllers are supported as a bootable media: MegaRAID, Smart Array, 3ware, Adaptec, ICP vortex, Areca. For Smart Array please use the RAID management CD as the RAID BIOS does not support LUN management. The provided software can be used for evaluation for 60 days with TRIAL product key. This software must be installed on a USB-stick first. In the ISO subdirectory there is same software available as an ISO image that can be placed on a CD-ROM. Since In order to install this version please proceed with the following steps: 1. Download and uncompress the file dss6.0upXX_xxxx.oe_i.zip 2. Format a USB-stick partitioned as a FAT or FAT32 for the root directory (at least 512MB media size) 3. Copy the uncompressed directories and files onto USB-stick Directories: bxxxx and boot Files: mmenu_upd.sh 4. After copying the directories and files please verify that in the root directory resides: bxxxx boot mmenu_upd.sh 5. Access the directory called "boot" then run the bootinst.exe (for Windows only) or bootinst.sh (for Linux only). 6. Boot your storage server with the USB-stick. (please set the BIOS to boot form USB-stick, or in boot menu select USB-stick to boot) 7. In first menu there is choice to start current version or run memory test. Please press enter to run current version. 8. In the second menu there is 3 menu options: 32bit system TRIAL (2.6.27) 64bit system TRIAL (2.6.27) Run Software Installer In order to boot DSS V6 and run TRIAL version at once please select 32bit or 64 bit accordingly to your current system architecture. The TRIAL will recognize your current volume groups and volumes even if you had a previous version of DSS, but keep in mind that this will start with factory defaults settings. In order to restore your current settings, please go to menu: MAINTENANCE->miscellaneous and check the SETUP and CONFIGURATION check-boxes and then select the green action button. It will prompt for system re-boot. After re-boot you can test how your storage system works with the new software. If all is working properly we recommend to update. In order to install DSS V6 on other bootable media, in second menu please select: Run software update installer Please follow all steps until reboot. PLEASE NOTE: After sixty (60) days of the creation of the first volume group, the free trial version of the software will expire, and the connection to all logical volumes will be lost. Thus, all data stored on logical volumes created on the test system will no longer be accessible. However, if you purchase a license for the full version of the software and activate it on the test system before the expiration of sixty (60) days, all of the data will become available again. The trial version supports unlimited storage size. The full version supports 4, 8 or 16TB out of the box - this storage capacity can be further extended by purchasing additional storage licenses. Once your product reaches a licensed capacity of 48TB, it will automatically be extended to unlimited storage. IMPORTANT NOTE: Each 16TB of replicated capacity requires an additional 1GB RAM over minimal requirements. For example, a system with 32TB of replicated capacity requires 1GB RAM as per minimal requirements as well as additional 2GB RAM for the replication, which makes 3GB in total. General Important note: NEW - Communication between failover nodes using unicast - Possibility of setting the default gateway on the console and the WebUI - Possibility of configuring static routing on the WebUI - Possibility of setting more than one ping node for failover purposes - Volume replication tuning tools under the console (ctrl + alt + w) UPDATED - CA Brighstor 12.5 support - AFP framework (Netatalk 2.1) FIXED - iSCSI volumes no longer freeze under very heavy load with 10Gbit Ethernet - Using the restore network settings function now resets the network card listing order - The reset network settings to factory default function is now blocked if failover is configured and working - Editing routing rules is now blocked if failover is configured and running - Secondary node no longer shuts down its failover processes and enters suspend mode if it loses connectivity to the ping node TESTING - Support for Marvell SATA - LSI 3ware SAS RAID controllers (3w-sas v10.0) - Broadcom 10Gb ethernet cards (bnx2x v1.50.13) KNOWN ISSUES: - The Promise Array Manager tool has been temporarily removed; it will be implemented in its newest version in future builds. - The FTP protocol offers no possibility to authenticate with a multipart username. - Intel RAID Web Console2 may not operate correctly due to tool bug (Only the highest Ethernet port position will work. Example: with Eth0,Eth1, Eth2 and Eth3, only Eth3 will work). As a workaround establish connection to the tool with the highest network card connected to the Open-E system or disable all except one controller (e.g. disable Eth1,Eth2 and Eth3 to force Eth0 to function). See http://www.intel.com/support/motherboards/server/sb/CS-028365.htm - LSI MegaRAID Storage Manager show the same issue as Intel RAID Web Console2 - MPIO mode for the QLOGIC HBA FC does not work. - Snapshot overflow may occur when working with a virtual backup device. - Rescan function is not working properly when resizing storage connected via iSCSI Initiator - after rescan changes will be not visible. In such a case please restart the system. - In case of Chelsio network interface card, the system may not run stable when using the built-in iSCSI initiator. - Neteffect cards show unstable behavior. - Netxen cards show unstable behavior. - High Point array management tool does not work. - Infiniband interfaces cannot be configured over the Web GUI. - WWW configuration tool for Promise controllers does not work. - After changing the default volume group using (Select Default Volume Group) the current settings will not be kept. To keep the current settings, use the Save settings function in the Web GUI before switching the VG and restore these settings afterwards, system will need to reboot. - If you are using ADS authentication, the 'All Squash' option for NFS will not work correctly. - After changing a user password via the WebGUI, this user will no longer be able to access password-protected shares published via AFP to which they previously had access. In such case, deleting the user and re-creating the same user with new password works. - VMWare ESX systems are sensitive to change of the iSCSI Target. In case of switch between IET and SCST (both directions) VMWare will not recognize the volumes. - > iSCSI daemon options - > iSCSI solution and reboot the system. - In case of ixgb network interface card, the system may not run stable when using the build-in iSCSI initiator. - System cannot be installed on storage attached to an ICP Vortex controller. - In case of using DSS V6 in windows 2008 cluster environment failover event on DSS V6 level will break i/o operation performed on DSS V6 iSCSI target eg. copying of files. - Tools for Management FC on the console does not work. P R E V I O U S V E R S I O N S 2010-05-07 v6.0 up35 build 4452 IMPORTANT NOTE: FOR UPDATE via WEB GUI in menu: MAINTENANCE-> software update -> Function: System software update, PLEASE use ISO image ONLY! The ZIP image can be used for installing or running quick trial. This is installable version. The built-in installer can install the Data Storage Software V6 on any bootable media. You can use the following media types: USB DOM (with Wear-Leveling support), IDE (ATA) DOM, SATA DOM, IDE (ATA) Hard Disk, SATA Hard Disk, SCSI Hard Disk or 2GB small LUN on a Hardware RAID (recommended). In order to install the software on separate LUN, please use RAID controllers with multiple LUN support. Please create a small 2GB logical unit for DSS V6. When Running DSS V6 installer you will need to select the 2GB logical unit as the boot media. The rest of the RAID space please create second LUN for the user data. The following RAID controllers are supported as a bootable media: MegaRAID, Smart Array, 3ware, Adaptec, ICP vortex, Areca. For Smart Array please use the RAID management CD as the RAID BIOS does not support LUN management. The provided software can be used for evaluation for 60 days with TRIAL product key. This software must be installed on a USB-stick first. In the ISO subdirectory there is same software available as an ISO image that can be placed on a CD-ROM. Since In order to install this version please proceed with the following steps: 1. Download and uncompress the file dss6.0upXX_xxxx.oe_i.zip 2. Format a USB-stick partitioned as a FAT or FAT32 for the root directory (at least 512MB media size) 3. Copy the uncompressed directories and files onto USB-stick Directories: bxxxx and boot Files: mmenu_upd.sh 4. After copying the directories and files please verify that in the root directory resides: bxxxx boot mmenu_upd.sh 5. Access the directory called "boot" then run the bootinst.exe (for Windows only) or bootinst.sh (for Linux only). 6. Boot your storage server with the USB-stick. (please set the BIOS to boot form USB-stick, or in boot menu select USB-stick to boot) 7. In first menu there is choice to start current version or run memory test. Please press enter to run current version. 8. In the second menu there is 3 menu options: 32bit system TRIAL (2.6.27) 64bit system TRIAL (2.6.27) Run Software Installer In order to boot DSS V6 and run TRIAL version at once please select 32bit or 64 bit accordingly to your current system architecture. The TRIAL will recognize your current volume groups and volumes even if you had a previous version of DSS, but keep in mind that this will start with factory defaults settings. In order to restore your current settings, please go to menu: MAINTENANCE->miscellaneous and check the SETUP and CONFIGURATION check-boxes and then select the green action button. It will prompt for system re-boot. After re-boot you can test how your storage system works with the new software. If all is working properly we recommend to update. In order to install DSS V6 on other bootable media, in second menu please select: Run software update installer Please follow all steps until reboot. PLEASE NOTE: After sixty (60) days of the creation of the first volume group, the free trial version of the software will expire, and the connection to all logical volumes will be lost. Thus, all data stored on logical volumes created on the test system will no longer be accessible. However, if you purchase a license for the full version of the software and activate it on the test system before the expiration of sixty (60) days, all of the data will become available again. The trial version supports unlimited storage size. The full version supports 4, 8 or 16TB out of the box - this storage capacity can be further extended by purchasing additional storage licenses. Once your product reaches a licensed capacity of 48TB, it will automatically be extended to unlimited storage. IMPORTANT NOTE: Each 16TB of replicated capacity requires an additional 1GB RAM over minimal requirements. For example, a system with 32TB of replicated capacity requires 1GB RAM as per minimal requirements as well as additional 2GB RAM for the replication, which makes 3GB in total. General Important note: NEW: * Initial settings wizard UPDATED: * Samba (v.3.5.2) * Antivirus (v.0.96) FIXED: * Support for Windows 2008 and Windows 2008 R2 as Domain Controller * Solved problem with system shutdown in case of using UPS * Fix for very slow iSCSI Failover initial configuration in case of problem with DNS * Fix for stopping snapshot of NAS logical volume * Fix for data replication during system update * Fix for memory leak problem TESTING: * Volume Replication tuning tools under console * Support for ATTO FC/SATA * Support for Marvell SATA * LSI 3ware SAS RAID controllers (3w-sas v10.0) * Broadcom 10Gb ethernet cards (bnx2x v1.50.13) KNOWN ISSUES: - The FTP protocol offers no possibility to authenticate with a multipart username. - Intel RAID Web Console2 may not operate correctly due to tool bug (Only the highest Ethernet port position will work. Example: with Eth0,Eth1, Eth2 and Eth3, only Eth3 will work). As a workaround establish connection to the tool with the highest network card connected to the Open-E system or disable all except one controller (e.g. disable Eth1,Eth2 and Eth3 to force Eth0 to function). See http://www.intel.com/support/motherboards/server/sb/CS-028365.htm - LSI MegaRAID Storage Manager show the same issue as Intel RAID Web Console2 - MPIO mode for the QLOGIC HBA FC does not work. - Snapshot overflow may occur when working with a virtual backup device. - Rescan function is not working properly when resizing storage connected via iSCSI Initiator - after rescan changes will be not visible. In such a case please restart the system. - In case of Chelsio network interface card, the system may not run stable when using the built-in iSCSI initiator. - Neteffect cards show unstable behavior. - Netxen cards show unstable behavior. - High Point array management tool does not work. - Infiniband interfaces cannot be configured over the Web GUI. - WWW configuration tool for Promise controllers does not work. - After changing the default volume group using (Select Default Volume Group) the current settings will not be kept. To keep the current settings, use the Save settings function in the Web GUI before switching the VG and restore these settings afterwards, system will need to reboot. - If you are using ADS authentication, the 'All Squash' option for NFS will not work correctly. - After changing a user password via the WebGUI, this user will no longer be able to access password-protected shares published via AFP to which they previously had access. In such case, deleting the user and re-creating the same user with new password works. - VMWare ESX systems are sensitive to change of the iSCSI Target. In case of switch between IET and SCST (both directions) VMWare will not recognize the volumes. - > iSCSI daemon options - > iSCSI solution and reboot the system. - In case of ixgb network interface card, the system may not run stable when using the build-in iSCSI initiator. - System cannot be installed on storage attached to an ICP Vortex controller. - In case of using DSS V6 in windows 2008 cluster environment failover event on DSS V6 level will break i/o operation performed on DSS V6 iSCSI target eg. copying of files. - Tools for Management FC on the console does not work. P R E V I O U S V E R S I O N S 2010-04-012 v6.0 up30 build4362 IMPORTANT NOTE: FOR UPDATE via WEB GUI in menu: MAINTENANCE-> software update -> Function: System software update, PLEASE use ISO image ONLY! The ZIP image can be used for installing or running quick trial. This is installable version. The built-in installer can install the Data Storage Software V6 on any bootable media. You can use the following media types: USB DOM (with Wear-Leveling support), IDE (ATA) DOM, SATA DOM, IDE (ATA) Hard Disk, SATA Hard Disk, SCSI Hard Disk or 2GB small LUN on a Hardware RAID (recommended). In order to install the software on separate LUN, please use RAID controllers with multiple LUN support. Please create a small 2GB logical unit for DSS V6. When Running DSS V6 installer you will need to select the 2GB logical unit as the boot media. The rest of the RAID space please create second LUN for the user data. The following RAID controllers are supported as a bootable media: MegaRAID, Smart Array, 3ware, Adaptec, ICP vortex, Areca. For Smart Array please use the RAID management CD as the RAID BIOS does not support LUN management. The provided software can be used for evaluation for 60 days with TRIAL product key. This software must be installed on a USB-stick first. In the ISO subdirectory there is same software available as an ISO image that can be placed on a CD-ROM. Since In order to install this version please proceed with the following steps: 1. Download and uncompress the file dss6.0upXX_xxxx.oe_i.zip 2. Format a USB-stick partitioned as a FAT or FAT32 for the root directory (at least 512MB media size) 3. Copy the uncompressed directories and files onto USB-stick Directories: bxxxx and boot Files: mmenu_upd.sh 4. After copying the directories and files please verify that in the root directory resides: bxxxx boot mmenu_upd.sh 5. Access the directory called ?boot? then run the bootinst.exe (for Windows only) or bootinst.sh (for Linux only). 6. Boot your storage server with the USB-stick. (please set the BIOS to boot form USB-stick, or in boot menu select USB-stick to boot) 7. In first menu there is choice to start current version or run memory test. Please press enter to run current version. 8. In the second menu there is 3 menu options: 32bit system TRIAL (2.6.27) 64bit system TRIAL (2.6.27) Run Software Installer In order to boot DSS V6 and run TRIAL version at once please select 32bit or 64 bit accordingly to your current system architecture. The TRIAL will recognize your current volume groups and volumes even if you had a previous version of DSS, but keep in mind that this will start with factory defaults settings. In order to restore your current settings, please go to menu: MAINTENANCE->miscellaneous and check the SETUP and CONFIGURATION check-boxes and then select the green action button. It will prompt for system re-boot. After re-boot you can test how your storage system works with the new software. If all is working properly we recommend to update. In order to install DSS V6 on other bootable media, in second menu please select: Run software update installer Please follow all steps until reboot. PLEASE NOTE: After sixty (60) days of the creation of the first volume group, the free trial version of the software will expire, and the connection to all logical volumes will be lost. Thus, all data stored on logical volumes created on the test system will no longer be accessible. However, if you purchase a license for the full version of the software and activate it on the test system before the expiration of sixty (60) days, all of the data will become available again. The trial version supports unlimited storage size. The full version supports 4, 8 or 16TB out of the box - this storage capacity can be further extended by purchasing additional storage licenses. Once your product reaches a licensed capacity of 48TB, it will automatically be extended to unlimited storage. IMPORTANT NOTE: Each 16TB of replicated capacity requires an additional 1GB RAM over minimal requirements. For example, a system with 32TB of replicated capacity requires 1GB RAM as per minimal requirements as well as additional 2GB RAM for the replication, which makes 3GB in total. General Important note: NEW : * Newly created replicated volumes are now consistent once the replication task has started. There no initializing during this process. If volume was created without the volume replication and modified later to use volume replication, then initialization will be required. * Support for background image around the login screen in OEM-DATA * Support for multiple Network Interface Controller in the same subnet UPDATED : * Driver for Broadcom ethernet cards (bnx2 v1.9.20b) * Driver for LSI 3ware RAID controllers (3w-9xxx v9.5.3) * Tool for LSI 3ware * New Symantec Backup Exec Agent 2010 * New version of iSCSI target architecture (SCST) FIXED : * Fix for releasing resources on secondary node during failback * Fix for samba log rotate * Fix for task log rotate * Fix for software installer problem with copying all versions from source device * Fix for FC target mode after update * Fix for update TRIAL versions with failover * Support for ethernet cards working on IGB driver in Lite version and Lite SE version TESTING : * Support for ATTO FC/SATA * Support for Marvell SATA * LSI 3ware SAS RAID controllers (3w-sas v10.0) * Broadcom 10Gb ethernet cards (bnx2x v1.50.13) KNOWN ISSUES: - The FTP protocol offers no possibility to authenticate with a multipart username. - Intel RAID Web Console2 may not operate correctly due to tool bug (Only the highest Ethernet port position will work. Example: with Eth0,Eth1, Eth2 and Eth3, only Eth3 will work). As a workaround establish connection to the tool with the highest network card connected to the Open-E system or disable all except one controller (e.g. disable Eth1,Eth2 and Eth3 to force Eth0 to function). See http://www.intel.com/support/motherboards/server/sb/CS-028365.htm - LSI MegaRAID Storage Manager show the same issue as Intel RAID Web Console2 - MPIO mode for the QLOGIC HBA FC does not work. - Snapshot overflow may occur when working with a virtual backup device. - Rescan function is not working properly when resizing storage connected via iSCSI Initiator - after rescan changes will be not visible. In such a case please restart the system. - In case of Chelsio network interface card, the system may not run stable when using the built-in iSCSI initiator. - Neteffect cards show unstable behavior. - Netxen cards show unstable behavior. - High Point array management tool does not work. - Infiniband interfaces cannot be configured over the Web GUI. - WWW configuration tool for Promise controllers does not work. - After changing the default volume group using (Select Default Volume Group) the current settings will not be kept. To keep the current settings, use the Save settings function in the Web GUI before switching the VG and restore these settings afterwards, system will need to reboot. - If you are using ADS authentication, the 'All Squash' option for NFS will not work correctly. - After changing a user password via the WebGUI, this user will no longer be able to access password-protected shares published via AFP to which they previously had access. In such case, deleting the user and re-creating the same user with new password works. - VMWare ESX systems are sensitive to change of the iSCSI Target. In case of switch between IET and SCST (both directions) VMWare will not recognize the volumes. - XEN systems cannot recognize new default iSCSI targets architecture (SCST). As workaround, please switch back to previous iSCSI target(architecture) (IET). To change the iSCSI target (architecture) please access the Console, enter hot-key: ctrl-alt-w - > Tuning Options - > iSCSI daemon options - > iSCSI solution and reboot the system. - In case of ixgb network interface card, the system may not run stable when using the build-in iSCSI initiator. - System cannot be installed on storage attached to an ICP Vortex controller. - In case of using DSS V6 in windows 2008 cluster environment failover event on DSS V6 level will break i/o operation performed on DSS V6 iSCSI target eg. copying of files. - Tools for Management FC on the console does not work. - MaxOutstandingR2T iSCSI parameter is set to the value of 1. This value is needed to reduce issues related to iSCSI connectivity. This will be resolved in future releases. P R E V I O U S V E R S I O N S 2010-02-26 v6.0 up14 build4221 IMPORTANT NOTE: FOR UPDATE via WEB GUI in menu: MAINTENANCE-> software update -> Function: System software update, PLEASE use ISO image ONLY! The ZIP image can be used for installing or running quick trial. This is installable version. The built-in installer can install the Data Storage Software V6 on any bootable media. You can use the following media types: USB DOM (with Wear-Leveling support), IDE (ATA) DOM, SATA DOM, IDE (ATA) Hard Disk, SATA Hard Disk, SCSI Hard Disk or 2GB small LUN on a Hardware RAID (recommended). In order to install the software on separate LUN, please use RAID controllers with multiple LUN support. Please create a small 2GB logical unit for DSS V6. When Running DSS V6 installer you will need to select the 2GB logical unit as the boot media. The rest of the RAID space please create second LUN for the user data. The following RAID controllers are supported as a bootable media: MegaRAID, Smart Array, 3ware, Adaptec, ICP vortex, Areca. For Smart Array please use the RAID management CD as the RAID BIOS does not support LUN management. The provided software can be used for evaluation for 60 days with TRIAL product key. This software must be installed on a USB-stick first. In the ISO subdirectory there is same software available as an ISO image that can be placed on a CD-ROM. Since In order to install this version please proceed with the following steps: 1. Download and uncompress the file dss6.0upXX_xxxx.oe_i.zip 2. Format a USB-stick partitioned as a FAT or FAT32 for the root directory (at least 512MB media size) 3. Copy the uncompressed directories and files onto USB-stick Directories: bxxxx and boot Files: mmenu_upd.sh 4. After copying the directories and files please verify that in the root directory resides: bxxxx boot mmenu_upd.sh 5. Access the directory called ?boot? then run the bootinst.exe (for Windows only) or bootinst.sh (for Linux only). 6. Boot your storage server with the USB-stick. (please set the BIOS to boot form USB-stick, or in boot menu select USB-stick to boot) 7. In first menu there is choice to start current version or run memory test. Please press enter to run current version. 8. In the second menu there is 3 menu options: 32bit system TRIAL (2.6.27) 64bit system TRIAL (2.6.27) Run Software Installer In order to boot DSS V6 and run TRIAL version at once please select 32bit or 64 bit accordingly to your current system architecture. The TRIAL will recognize your current volume groups and volumes even if you had a previous version of DSS, but keep in mind that this will start with factory defaults settings. In order to restore your current settings, please go to menu: MAINTENANCE->miscellaneous and check the SETUP and CONFIGURATION check-boxes and then select the green action button. It will prompt for system re-boot. After re-boot you can test how your storage system works with the new software. If all is working properly we recommend to update. In order to install DSS V6 on other bootable media, in second menu please select: Run software update installer Please follow all steps until reboot. PLEASE NOTE: After sixty (60) days of the creation of the first volume group, the free trial version of the software will expire, and the connection to all logical volumes will be lost. Thus, all data stored on logical volumes created on the test system will no longer be accessible. However, if you purchase a license for the full version of the software and activate it on the test system before the expiration of sixty (60) days, all of the data will become available again. The trial version supports unlimited storage size. The full version supports 4, 8 or 16TB out of the box - this storage capacity can be further extended by purchasing additional storage licenses. Once your product reaches a licensed capacity of 48TB, it will automatically be extended to unlimited storage. IMPORTANT NOTE: Each 16TB of replicated capacity requires an additional 1GB RAM over minimal requirements. For example, a system with 32TB of replicated capacity requires 1GB RAM as per minimal requirements as well as additional 2GB RAM for the replication, which makes 3GB in total. General Important note: NEW : * Support for volume replication with logical volumes up to 16 TB * Support for iSCSI failover with logical volumes up to 16 TB * Russian language version * 3Ware/LSI MegaRAID logs are now part of the log package available after clicking "Download" under STATUS -> hardware -> Logs * After starting the failover functionality, a check is now initiated to make sure target names, LUNs and SCSI IDs match on both nodes * Support for 8 Gbit FC Qlogic HBAs as initiators and targets UPDATED : * New kernel (2.6.27.39) * Intel PCI Express NIC driver (e1000e v1.0.15) * Myricom 10Gb NIC driver (myri10ge v1.5.1) FIXED : * Remote support connection no longer timeouts after 30 seconds * File I/O iSCSI volumes and FC volumes no longer overload the system during initialization * System now shuts down correctly when connected to an iSCSI target via the built-in iSCSI initiator TESTING : * Support for Accusys * Support for ATTO FC/SATA * Support for Marvell SATA KNOWN ISSUES: IF YOU USE FIBRE CHANNEL IN TARGET MODE, PLEASE NOTE THIS SETTING WILL BE RESET AFTER UPDATING THE SYSTEM OR RESTORING A PREVIOUS CONFIGURATION, AND YOU WILL NEED TO REBOOT THE SYSTEM TWICE FOR THE TARGET TO START FUNCTIONING PROPERLY. REMAINING SETTINGS WILL BE PRESERVED. - If you use Fibre Channel in target mode, please note this setting will be reset after you apply the update, and you will need to manually switch back to target mode. Remaining settings will be preserved - Displaying more than 50 users or groups in the NAS resources -> Users/Groups tree does not work. To edit the users/groups missing from the display, enter their names in the search box above the list. - Intel RAID Web Console2 may not operate correctly due to tool bug (Only the highest Ethernet port position will work. Example: with Eth0,Eth1, Eth2 and Eth3, only Eth3 will work). As a workaround establish connection to the tool with the highest network card connected to the Open-E system or disable all except one controller (e.g. disable Eth1,Eth2 and Eth3 to force Eth0 to function). See http://www.intel.com/support/motherboards/server/sb/CS-028365.htm - LSI MegaRAID Storage Manager show the same issue as Intel RAID Web Console2 - MPIO mode for the QLOGIC HBA FC does not work. - Snapshot overflow may occur when working with a virtual backup device. - Rescan function is not working properly when resizing storage connected via iSCSI Initiator - after rescan changes will be not visible. In such a case please restart the system. - In case of Chelsio network interface card, the system may not run stable when using the built-in iSCSI initiator. - Neteffect cards show unstable behavior. - Netxen cards show unstable behavior. - High Point array management tool does not work. - Infiniband interfaces cannot be configured over the Web GUI. - WWW configuration tool for Promise controllers does not work. - After changing the default volume group using (Select Default Volume Group) the current settings will not be kept. To keep the current settings, use the Save settings function in the Web GUI before switching the VG and restore these settings afterwards, system will need to reboot. - If you are using ADS authentication, the 'All Squash' option for NFS will not work correctly. - After changing a user password via the WebGUI, this user will no longer be able to access password-protected shares published via AFP to which they previously had access. In such case, deleting the user and re-creating the same user with new password works. - VMWare ESX systems are sensitive to change of the iSCSI Target. In case of switch between IET and SCST (both directions) VMWare will not recognize the volumes. See http://www.kb.open-e.com/entry/672/ - XEN systems cannot recognize new default iSCSI targets architecture (SCST). As workaround, please switch back to previous iSCSI target (architecture) (IET). To change the iSCSI target (architecture) please access the Console, enter hot-key: ctrl-alt-w - > Tuning Options - > iSCSI daemon options - > iSCSI solution and reboot the system. - In case of ixgb network interface card, the system may not run stable when using the build-in iSCSI initiator. - System cannot be installed on a LUN of ICP Vortex RAID Array. - In case of using DSS V6 in windows 2008 cluster environment failover event on DSS V6 level will break i/o operation performed on DSS V6 iSCSI target eg. copying of files. - Tools for Management FC on the console does not work. 2010-01-14 v6.0 up13 build4023 IMPORTANT NOTE: FOR UPDATE via WEB GUI in menu: MAINTENANCE-> software update -> Function: System software update, PLEASE use ISO image ONLY! The ZIP image can be used for installing or running quick trial. This is installable version. The built-in installer can install the Data Storage Software V6 on any bootable media. You can use the following media types: USB DOM (with Wear-Leveling support), IDE (ATA) DOM, SATA DOM, IDE (ATA) Hard Disk, SATA Hard Disk, SCSI Hard Disk or 2GB small LUN on a Hardware RAID (recommended). In order to install the software on separate LUN, please use RAID controllers with multiple LUN support. Please create a small 2GB logical unit for DSS V6. When Running DSS V6 installer you will need to select the 2GB logical unit as the boot media. The rest of the RAID space please create second LUN for the user data. The following RAID controllers are supported as a bootable media: MegaRAID, Smart Array, 3ware, Adaptec, ICP vortex, Areca. For Smart Array please use the RAID management CD as the RAID BIOS does not support LUN management. The provided software can be used for evaluation for 60 days with TRIAL product key. This software must be installed on a USB-stick first. In the ISO subdirectory there is same software available as an ISO image that can be placed on a CD-ROM. Since In order to install this version please proceed with the following steps: 1. Download and uncompress the file dss6.0upXX_xxxx.oe_i.zip 2. Format a USB-stick partitioned as a FAT or FAT32 for the root directory (at least 512MB media size) 3. Copy the uncompressed directories and files onto USB-stick Directories: bxxxx and boot Files: mmenu_upd.sh 4. After copying the directories and files please verify that in the root directory resides: bxxxx boot mmenu_upd.sh 5. Access the directory called ?boot? then run the bootinst.exe (for Windows only) or bootinst.sh (for Linux only). 6. Boot your storage server with the USB-stick. (please set the BIOS to boot form USB-stick, or in boot menu select USB-stick to boot) 7. In first menu there is choice to start current version or run memory test. Please press enter to run current version. 8. In the second menu there is 3 menu options: 32bit system TRIAL (2.6.27) 64bit system TRIAL (2.6.27) Run Software Installer In order to boot DSS V6 and run TRIAL version at once please select 32bit or 64 bit accordingly to your current system architecture. The TRIAL will recognize your current volume groups and volumes even if you had a previous version of DSS, but keep in mind that this will start with factory defaults settings. In order to restore your current settings, please go to menu: MAINTENANCE->miscellaneous and check the SETUP and CONFIGURATION check-boxes and then select the green action button. It will prompt for system re-boot. After re-boot you can test how your storage system works with the new software. If all is working properly we recommend to update. In order to install DSS V6 on other bootable media, in second menu please select: Run software update installer Please follow all steps until reboot. PLEASE NOTE: After sixty (60) days of the creation of the first volume group, the free trial version of the software will expire, and the connection to all logical volumes will be lost. Thus, all data stored on logical volumes created on the test system will no longer be accessible. However, if you purchase a license for the full version of the software and activate it on the test system before the expiration of sixty (60) days, all of the data will become available again. The trial version supports unlimited storage size. The full version supports 4, 8 or 16TB out of the box - this storage capacity can be further extended by purchasing additional storage licenses. Once your product reaches a licensed capacity of 48TB, it will automatically be extended to unlimited storage. General Important note: UPDATED: - Chinese language version FIXED: - Fix for enabling/disabling replication functionality for NAS volume when the share is created on this volume - Fix problem with receive an IP Address in case of using Bonding (ALB/TLB mode) TESTING - Support for Qlogic 8Gb FC cards in target mode - Support for Accusys. - Support for ATTO FC/SATA. - Support for Marvell SATA. NOT SUPPORTED - RocketRAID 1740,2240 & 2310. KNOWN ISSUES: - If you use Fibre Channel in target mode, please note this setting will be reset after you apply the update, and you will need to manually switch back to target mode. Remaining settings will be preserved - Displaying more than 50 users or groups in the NAS resources -> Users/Groups tree does not work. To edit the users/groups missing from the display, enter their names in the search box above the list. - Intel RAID Web Console2 may not operate correctly due to tool bug (Only the highest Ethernet port position will work. Example: with Eth0,Eth1, Eth2 and Eth3, only Eth3 will work). As a workaround establish connection to the tool with the highest network card connected to the Open-E system or disable all except one controller (e.g. disable Eth1,Eth2 and Eth3 to force Eth0 to function). See http://www.intel.com/support/motherboards/server/sb/CS-028365.htm - LSI MegaRAID Storage Manager show the same issue as Intel RAID Web Console2 - MPIO mode for the QLOGIC HBA FC does not work. - Myricom does not work when using the 64bit kernel operating mode. - Snapshot overflow may occur when working with a virtual backup device. - Rescan function is not working properly when resizing storage connected via iSCSI Initiator - after rescan changes will be not visible. In such a case please restart the system. - In case of Chelsio network interface card, the system may not run stable when using the built-in iSCSI initiator. - Neteffect cards show unstable behavior. - Netxen cards show unstable behavior. - High Point array management tool does not work. - Infiniband interfaces cannot be configured over the Web GUI. - WWW configuration tool for Promise controllers does not work. - After changing the default volume group using (Select Default Volume Group) the current settings will not be kept. To keep the current settings, use the Save settings function in the Web GUI before switching the VG and restore these settings afterwards, system will need to reboot. - If you are using ADS authentication, the 'All Squash' option for NFS will not work correctly. - After changing a user password via the WebGUI, this user will no longer be able to access password-protected shares published via AFP to which they previously had access. In such case, deleting the user and re-creating the same user with new password works. - VMWare ESX systems are sensitive to change of the iSCSI Target. In case of switch between IET and SCST (both directions) VMWare will not recognize the volumes. - XEN systems cannot recognize new default iSCSI targets architecture (SCST). As workaround, please switch back to previous iSCSI target (architecture) (IET). To change the iSCSI target (architecture)please access the Console, enter hot-key: ctrl-alt-w - > Tuning Options - > iSCSI daemon options - > iSCSI solution and reboot the system. - In case of ixgb network interface card, the system may not run stable when using the build-in iSCSI initiator. - System cannot be installed on storage attached to an ICP Vortex controller. - In case of using DSS V6 in windows 2008 cluster environment failover event on DSS V6 level will break i/o operation performed on DSS V6 iSCSI target eg. copying of files. - Tools for Management FC on the console does not work. P R E V I O U S V E R S I O N S Release Notes 2009-12-08 v6.0 up13 build3902 IMPORTANT NOTE: FOR UPDATE via WEB GUI in menu: MAINTENANCE-> software update -> Function: System software update, PLEASE use ISO image ONLY! The ZIP image can be used for installing or running quick trial. This is installable version. The built-in installer can install the Data Storage Software V6 on any bootable media. You can use the following media types: USB DOM (with Wear-Leveling support), IDE (ATA) DOM, SATA DOM, IDE (ATA) Hard Disk, SATA Hard Disk, SCSI Hard Disk or 2GB small LUN on a Hardware RAID (recommended). In order to install the software on separate LUN, please use RAID controllers with multiple LUN support. Please create a small 2GB logical unit for DSS V6. When Running DSS V6 installer you will need to select the 2GB logical unit as the boot media. The rest of the RAID space please create second LUN for the user data. The following RAID controllers are supported as a bootable media: MegaRAID, Smart Array, 3ware, Adaptec, ICP vortex, Areca. For Smart Array please use the RAID management CD as the RAID BIOS does not support LUN management. The provided software can be used for evaluation for 60 days with TRIAL product key. This software must be installed on a USB-stick first. In the ISO subdirectory there is same software available as an ISO image that can be placed on a CD-ROM. Since In order to install this version please proceed with the following steps: 1. Download and uncompress the file dss6.0upXX_xxxx.oe_i.zip 2. Format a USB-stick partitioned as a FAT or FAT32 for the root directory (at least 512MB media size) 3. Copy the uncompressed directories and files onto USB-stick Directories: bxxxx and boot Files: mmenu_upd.sh 4. After copying the directories and files please verify that in the root directory resides: bxxxx boot mmenu_upd.sh 5. Access the directory called ?boot? then run the bootinst.exe (for Windows only) or bootinst.sh (for Linux only). 6. Boot your storage server with the USB-stick. (please set the BIOS to boot form USB-stick, or in boot menu select USB-stick to boot) 7. In first menu there is choice to start current version or run memory test. Please press enter to run current version. 8. In the second menu there is 3 menu options: 32bit system TRIAL (2.6.27) 64bit system TRIAL (2.6.27) Run Software Installer In order to boot DSS V6 and run TRIAL version at once please select 32bit or 64 bit accordingly to your current system architecture. The TRIAL will recognize your current volume groups and volumes even if you had a previous version of DSS, but keep in mind that this will start with factory defaults settings. In order to restore your current settings, please go to menu: MAINTENANCE->miscellaneous and check the SETUP and CONFIGURATION check-boxes and then select the green action button. It will prompt for system re-boot. After re-boot you can test how your storage system works with the new software. If all is working properly we recommend to update. In order to install DSS V6 on other bootable media, in second menu please select: Run software update installer Please follow all steps until reboot. PLEASE NOTE: After sixty (60) days of the creation of the first volume group, the free trial version of the software will expire, and the connection to all logical volumes will be lost. Thus, all data stored on logical volumes created on the test system will no longer be accessible. However, if you purchase a license for the full version of the software and activate it on the test system before the expiration of sixty (60) days, all of the data will become available again. The trial version supports unlimited storage size. The full version supports 4, 8 or 16TB out of the box - this storage capacity can be further extended by purchasing additional storage licenses. Once your product reaches a licensed capacity of 48TB, it will automatically be extended to unlimited storage. General Important note: NEW: * Additional activation port (25) in case the standard activation port (10444) cannot be opened * OEMKit: configuration for menu and submenu elements * New Samba (v3.2.15) * New Intel-e1000 driver (v8.0.16) * New ixgbe driver (v2.0.44.14) * New 3ware driver and tools (v9.5.2) * New firmware for Adaptec AIC-9410 * New firmware (v7.4.0) for Chelsio 10Gb * Chinese language version FIXED: * Fix for Windows trusted domain support * Fix for ACL inheritance problem in Windows * Failover and failback time optimization for multiple volumes in iSCSI failover * It is now impossible to set virtual IP in the same subnetwork as the physical IPs * Fix for initialization problem with Qlogic 4Gb * Fix for administrator password not being restored when restoring administration settings * Fix for block I/O iSCSI volume initialization problem under VMware ESX initiator * Fix for UPS status not being refreshed on the GUI * Fix for RAID1 units created with built-in software RAID not being available after reboot TESTING * Support for Qlogic 8Gb FC cards in target mode * Support for Accusys * Support for ATTO FC/SATA * Support for Marvell SATA NOT SUPPORTED * RocketRAID 1740,2240 & 2310 KNOWN ISSUES: - If you use Fibre Channel in target mode, please note this setting will be reset after you apply the update, and you will need to manually switch back to target mode. Remaining settings will be preserved -Displaying more than 50 users or groups in the NAS resources -> Users/Groups tree does not work. To edit the users/groups missing from the display, enter their names in the search box above the list. - Intel RAID Web Console2 may not operate correctly due to tool bug ( Only the highest Ethernet port position will work. Example: with Eth0, Eth1, Eth2 and Eth3, only Eth3 will work). As a workaround establish connection to the tool with the highest network card connected to the Open-E system or disable all except one controller (e.g. disable Eth1, Eth2 and Eth3 to force Eth0 to function). See http://www.intel.com/support/motherboards/server/sb/CS-028365.htm - LSI MegaRAID Storage Manager show the same issue as Intel RAID Web Console2 - MPIO mode for the QLOGIC HBA FC does not work. - Myricom does not work when using the 64bit kernel operating mode. - Snapshot overflow may occur when working with a virtual backup device. - Rescan function is not working properly when resizing storage connected via iSCSI Initiator - after rescan changes will be not visible. In such a case please restart the system. - In case of Chelsio network interface card, the system may not run stable when using the built-in iSCSI initiator. - Neteffect cards show unstable behavior. - Netxen cards show unstable behavior. - High Point array management tool does not work. - Infiniband interfaces cannot be configured over the Web GUI. - WWW configuration tool for Promise controllers does not work. - After changing the default volume group using (Select Default Volume Group) the current settings will not be kept. To keep the current settings, use the Save settings function in the Web GUI before switching the VG and restore these settings afterwards, system will need to reboot. - If you are using ADS authentication, the 'All Squash' option for NFS will not work correctly. - After changing a user password via the WebGUI, this user will no longer be able to access password-protected shares published via AFP to which they previously had access. In such case, deleting the user and re-creating the same user with new password works. - VMWare ESX systems are sensitive to change of the iSCSI Target. In case of switch between IET and SCST (both directions) VMWare will not recognize the volumes. - XEN systems cannot recognize new default iSCSI targets architecture (SCST). As workaround, please switch back to previous iSCSI target (architecture) (IET). To change the iSCSI target (architecture) please access the Console, enter hot-key: ctrl-alt-w - > Tuning Options - > iSCSI daemon options - > iSCSI solution and reboot the system. - In case of ixgb network interface card, the system may not run stable when using the build-in iSCSI initiator, - System cannot be installed on storage attached to an ICP Vortex controller. - In case of using DSS V6 in windows 2008 cluster environment failover event on DSS V6 level will break i/o operation performed on DSS V6 iSCSI target eg. copying of files - Tools for Management FC on the console does not work. P R E V I O U S V E R S I O N S 2009-11-17 v6.0 up12 build3836 NEW: * Unlimited storage (if purchased capacity is >= 48TB ) FIXED: * Fix for multi-volume in iSCSI Failover * Fix for Time Zone setting * Fix for online update (OEM) * Software Raid Event Notification improvements * Backup Improvements - Support for tapes in read only mode NOT SUPPORTED: . RocketRAID 1740,2240 & 2310. KNOWN ISSUES: - If you use Fibre Channel in target mode, please note this setting will be reset after you apply the update, and you will need to manually switch back to target mode. Remaining settings will be preserved -Displaying more than 50 users or groups in the NAS resources -> Users/Groups tree does not work. To edit the users/groups missing from the display, enter their names in the search box above the list. - Intel RAID Web Console2 may not operate correctly due to tool bug ( Only the highest Ethernet port position will work. Example: with Eth0, Eth1, Eth2 and Eth3, only Eth3 will work). As a workaround establish connection to the tool with the highest network card connected to the Open-E system or disable all except one controller (e.g. disable Eth1, Eth2 and Eth3 to force Eth0 to function). See http://www.intel.com/support/motherboards/server/sb/CS-028365.htm - LSI MegaRAID Storage Manager show the same issue as Intel RAID Web Console2 - MPIO mode for the QLOGIC HBA FC does not work. - Myricom does not work when using the 64bit kernel operating mode. - Snapshot overflow may occur when working with a virtual backup device. - Rescan function is not working properly when resizing storage connected via iSCSI Initiator - after rescan changes will be not visible. In such a case please restart the system. - In case of Chelsio network interface card, the system may not run stable when using the built-in iSCSI initiator. - Accusys does not work. - ATTO FC/SATA does not work. - Marvell SATA does not work. - Neteffect cards show unstable behavior. - Netxen cards show unstable behavior. - High Point array management tool does not work. - Infiniband interfaces cannot be configured over the Web GUI. - WWW configuration tool for Promise controllers does not work. - The trusted domains option for ADS and PDC sometimes does not work. - After changing FC group name and restarting both machines the initiator will connect to the default group instead of the newly renamed group. - After changing the default volume group using (Select Default Volume Group) the current settings will not be kept. To keep the current settings, use the Save settings function in the Web GUI before switching the VG and restore these settings afterwards, system will need to reboot. - If you are using ADS authentication, the 'All Squash' option for NFS will not work correctly. - After changing a user password via the WebGUI, this user will no longer be able to access password-protected shares published via AFP to which they previously had access. In such case, deleting the user and re-creating the same user with new password works. - VMWare ESX systems are sensitive to change of the iSCSI Target. In case of switch between IET and SCST (both directions) VMWare will not recognize the volumes. - XEN systems cannot recognize new default iSCSI targets architecture (SCST). As workaround, please switch back to previous iSCSI target (architecture) (IET). To change the iSCSI target (architecture) please access the Console, enter hot-key: ctrl-alt-w - > Tuning Options - > iSCSI daemon options - > iSCSI solution and reboot the system. - In case of ixgb network interface card, the system may not run stable when using the build-in iSCSI initiator, - Software Installer running from some USB CD-ROM drives may not work. We recommend to run the Software Installer from USB-Stick. - System cannot be installed on storage attached to an ICP Vortex controller. - In case of using DSS V6 in windows 2008 cluster environment failover event on DSS V6 level will break i/o operation performed on DSS V6 iSCSI target eg. copying of files - In case of using shares name with space (e.g "data share") access through the NFS protocol will be available only via share/data share (e.g. mount -t nfs IP_addr:/share/data share /local_mount_point). - Tools for Management FC on the console does not work. P R E V I O U S V E R S I O N S 2009-10-14 v6.0 up10 build3719 General Important note: NEW: * Add support for Email Notification for HP SMART Array * Add battery status for LSI Tools on GUI * Add Backup Improvement - Displaying retention time on GUI for each tape - Block ability to select share with virtual tape device as share for backup database and vice versa - Update slots for changer - Possibility to select drive from tapes library during tape labeling or using tape tools TESTING: * API command set for remote system control and monitoring including snapshot start, stop and status. In order to list the full command set, please issue the 'help' command. NOTE: API commands are non-interactive! A user script with API commands must be executed first on a testing system, not on a production system. FIXED: * Fixed problem with windows 2008 cluster during validation - Persistent Reservation * Fixed problem with on line update NOT SUPPORTED: . RocketRAID 1740,2240 & 2310. KNOWN ISSUES: -Displaying more than 50 users or groups in the NAS resources -> Users/Groups tree does not work. To edit the users/groups missing from the display, enter their names in the search box above the list. - Intel RAID Web Console2 may not operate correctly due to tool bug ( Only the highest Ethernet port position will work. Example: with Eth0, Eth1, Eth2 and Eth3, only Eth3 will work). As a workaround establish connection to the tool with the highest network card connected to the Open-E system or disable all except one controller (e.g. disable Eth1, Eth2 and Eth3 to force Eth0 to function). See http://www.intel.com/support/motherboards/server/sb/CS-028365.htm - LSI MegaRAID Storage Manager show the same issue as Intel RAID Web Console2 - MPIO mode for the QLOGIC HBA FC does not work. - Myricom does not work when using the 64bit kernel operating mode. - Snapshot overflow may occur when working with a virtual backup device. - Rescan function is not working properly when resizing storage connected via iSCSI Initiator - after rescan changes will be not visible. In such a case please restart the system. - In case of Chelsio network interface card, the system may not run stable when using the built-in iSCSI initiator. - Accusys does not work. - ATTO FC/SATA does not work. - Marvell SATA does not work. - Neteffect cards show unstable behavior. - Netxen cards show unstable behavior. - High Point array management tool does not work. - Infiniband interfaces cannot be configured over the Web GUI. - WWW configuration tool for Promise controllers does not work. - The trusted domains option for ADS and PDC sometimes does not work. - After changing FC group name and restarting both machines the initiator will connect to the default group instead of the newly renamed group. - After changing the default volume group using (Select Default Volume Group) the current settings will not be kept. To keep the current settings, use the Save settings function in the Web GUI before switching the VG and restore these settings afterwards, system will need to reboot. - If you are using ADS authentication, the 'All Squash' option for NFS will not work correctly. - After changing a user password via the WebGUI, this user will no longer be able to access password-protected shares published via AFP to which they previously had access. In such case, deleting the user and re-creating the same user with new password works. - VMWare ESX systems are sensitive to change of the iSCSI Target. In case of switch between IET and SCST (both directions) VMWare will not recognize the volumes. - XEN systems cannot recognize new default iSCSI targets architecture (SCST). As workaround, please switch back to previous iSCSI target (architecture) (IET). To change the iSCSI target (architecture) please access the Console, enter hot-key: ctrl-alt-w - > Tuning Options - > iSCSI daemon options - > iSCSI solution and reboot the system. - In case of ixgb network interface card, the system may not run stable when using the build-in iSCSI initiator, - Software Installer running from some USB CD-ROM drives may not work. We recommend to run the Software Installer from USB-Stick. - System cannot be installed on storage attached to an ICP Vortex controller. - In case of using DSS V6 in windows 2008 cluster environment failover event on DSS V6 level will break i/o operation performed on DSS V6 iSCSI target eg. copying of files - In case of using shares name with space (e.g "data share") access through the NFS protocol will be available only via share/data share (e.g. mount -t nfs IP_addr:/share/data share /local_mount_point). - Tools for Management FC on the console does not work. P R E V I O U S V E R S I O N S 2009-08-28 v6.0 up07 build3537 General Important note: NEW: * Support for SFTP * Support for OEM data * Japanese lanuguage version FIXED: * Fixed problem with activation in German language version NOT SUPPORTED: . RocketRAID 1740,2240 & 2310. KNOWN ISSUES: . Intel RAID Web Console2 may not operate correctly due to tool bug ( Only the highest Ethernet port position will work. Example: with Eth0, Eth1, Eth2 and Eth3, only Eth3 will work). As a workaround establish connection to the tool with the highest network card connected to the Open-E system or disable all except one controller (e.g. disable Eth1, Eth2 and Eth3 to force Eth0 to function). See http://www.intel.com/support/motherboards/server/sb/CS-028365.htm . LSI MegaRAID Storage Manager show the same issue as Intel RAID Web Console2 . MPIO mode for the QLOGIC HBA FC does not work. . Myricom does not work when using the 64bit kernel operating mode. . Snapshot overflow may occur when working with a virtual backup device. . Rescan function is not working properly when resizing storage connected via iSCSI Initiator - after rescan changes will be not visible. In such a case please restart the system. . In case of Chelsio network interface card, the system may not run stable when using the built-in iSCSI initiator. . Accusys does not work. . ATTO FC/SATA does not work. . Marvell SATA does not work. . Neteffect cards show unstable behavior. . Netxen cards show unstable behavior. . High Point array management tool does not work. . Infiniband interfaces cannot be configured over the Web GUI. . WWW configuration tool for Promise controllers does not work. . The trusted domains option for ADS and PDC sometimes does not work. . After changing FC group name and restarting both machines the initiator will connect to the default group instead of the newly renamed group. . After changing the default volume group using (Select Default Volume Group) the current settings will not be kept. To keep the current settings, use the Save settings function in the Web GUI before switching the VG and restore these settings afterwards, system will need to reboot. . If you are using ADS authentication, the 'All Squash' option for NFS will not work correctly. . After changing a user password via the WebGUI, this user will no longer be able to access password-protected shares published via AFP to which they previously had access. In such case, deleting the user and re-creating the same user with new password works. . VMWare ESX systems are sensitive to change of the iSCSI Target. In case of switch between IET and SCST (both directions) VMWare will not recognize the volumes. . XEN systems cannot recognize new default iSCSI targets architecture (SCST). As workaround, please switch back to previous iSCSI target (architecture) (IET). To change the iSCSI target (architecture) please access the Console, enter hot-key: ctrl-alt-w - > Tuning Options - > iSCSI daemon options - > iSCSI solution and reboot the system. . In case of ixgb network interface card, the system may not run stable when using the build-in iSCSI initiator, . Software Installer running from some USB CD-ROM drives may not work. We recommend to run the Software Installer from USB-Stick. . System cannot be installed on storage attached to an ICP Vortex controller. Release Notes 2009-07-24 v6.0 up00 build3535 General Important note: FIXED: * Fixed problem with logs overflow Backup Exec 12.5 * Fixed problem with download Hardware Stamp and Activation version for HP Smart Array * Fixed problem with copying large files under Windows UPDATED: * Update Driver e1000e for Intel Card * Update Driver igb for Intel Card NOT SUPPORTED: . RocketRAID 1740,2240 & 2310. KNOWN ISSUES: . MPIO mode for the QLOGIC HBA FC does not work. . Myricom does not work when using the 64bit kernel operating mode. . Snapshot overflow may occur when working with a virtual backup device. . Rescan function is not working properly when resizing storage connected via iSCSI Initiator - after rescan changes will be not visible. In such a case please restart the system. . LSI Logic Web Console tool for RAID controller configuration is not working under 64bit operating mode (with 32bit kernel the tool works correctly). Please use build-in GUI for LSI MegaRAID. . In case of Chelsio network interface card, the system may not run stable when using the built-in iSCSI initiator. . Accusys does not work. . ATTO FC/SATA does not work. . Marvell SATA does not work. . Neteffect cards show unstable behavior. . Netxen cards show unstable behavior. . High Point array management tool does not work. . Infiniband interfaces cannot be configured over the Web GUI. . WWW configuration tool for Promise controllers does not work. . The trusted domains option for ADS and PDC sometimes does not work. . After changing FC group name and restarting both machines the initiator will connect to the default group instead of the newly renamed group. . After changing the default volume group using (Select Default Volume Group) the current settings will not be kept. To keep the current settings, use the Save settings function in the Web GUI before switching the VG and restore these settings afterwards, system will need to reboot. . If you are using ADS authentication, the 'All Squash' option for NFS will not work correctly. . After changing a user password via the WebGUI, this user will no longer be able to access password-protected shares published via AFP to which they previously had access. In such case, deleting the user and re-creating the same user with new password works. . VMWare ESX systems are sensitive to change of the iSCSI Target. In case of switch between IET and SCST (both directions) VMWare will not recignize the volumes. . In case of ixgb network interface card, the system may not run stable when using the build-in iSCSI initiator, . Installator running on the usb does not work. We recommended use usb stick. P R E V I O U S V E R S I O N S Release Notes 2009-06-25 v6.0 up04 build3530 NEW: * Support for new backup agent - Backup Exec 12.5 * Support for NDMP v4.0 * Asynchronous Volume Replication over WAN * Dynamic and faster GUI, designed from ground up with pull-down menu * Installable version * System monitoring - SysCheck * Support for Windows Server 2008 Cluster (persistent reservation) * New default iSCSI target architecture (SCST), previous default iSCSI target (IET) is still available. To change the default iSCSI target solution please access the Console then enter hot-key: ctrl-alt-w - > Tuning Options - > iSCSI daemon options - > iSCSI solution * With new default iSCSI target there is no need to reset the target while adding or removing LUNs. * NFS aliases. Now new mount command does not need word "share" in the syntax. It can mount with: mount -t nfs IP_addr:/share_name /mount_point * API first limited command set for remote system control and monitoring. NOT SUPPORTED: . RocketRAID 1740,2240 & 2310. KNOWN ISSUES: . MPIO mode for the QLOGIC HBA FC does not work. . Myricom does not work when using the 64bit kernel operating mode. . Snapshot overflow may occur when working with a virtual backup device. . Rescan function is not working properly when resizing storage connected via iSCSI Initiator - after rescan changes will be not visible. In such a case please restart the system. . LSI Logic Web Console tool for RAID controller configuration is not working under 64bit operating mode (with 32bit kernel the tool works correctly). Please use build-in GUI for LSI MegaRAID. . In case of Chelsio network interface card, the system may not run stable when using the built-in iSCSI initiator. . Accusys does not work. . ATTO FC/SATA does not work. . Marvell SATA does not work. . Neteffect cards show unstable behavior. . Netxen cards show unstable behavior. . High Point array management tool does not work. . Infiniband interfaces cannot be configured over the Web GUI. . WWW configuration tool for Promise controllers does not work. . The trusted domains option for ADS and PDC sometimes does not work. . After changing FC group name and restarting both machines the initiator will connect to the default group instead of the newly renamed group. . After changing the default volume group using (Select Default Volume Group) the current settings will not be kept. To keep the current settings, use the Save settings function in the Web GUI before switching the VG and restore these settings afterwards, system will need to reboot. . If you are using ADS authentication, the 'All Squash' option for NFS will not work correctly. . After changing a user password via the WebGUI, this user will no longer be able to access password-protected shares published via AFP to which they previously had access. In such case, deleting the user and re-creating the same user with new password works.