Release Notes 2009-03-09 v5.0 up60 build3511 IMPORTANT NOTE: This is the first version with totally different boot loader then all previous versions. Provided software can be used for: Software update for previous versions (from build 3204 till 3278) or 60 days TRIAL This software must be installed on a USB-stick first. (there will be same software available as ISO version and can be placed on CD) In order to install this version please proceed with the following steps: 1. Download and uncompress the file atlanta_3511.tar.gz 2. Format a USB-stick partitioned as a FAT for the root directory (at least 512MB media size) 3. Copy the uncompressed directories and files onto USB-stick Directories: b3511 and boot Files: mmenu_upd.sh and prod.key 4. After copying the directories and files please verify that in the root directory resides the directories: b3511, boot and files mmenu_upd, sh and prod.key. 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 (2.6.27) 64bit system (2.6.27) Run software update installer In order to run TRIAL of new software v5.0 up60 build3511, please select 32bit or 64 bit accordingly to your current system architecture. The TRIAL will recognize your current volume groups and volumes, but will start with factory defaults settings. In order to restore your current settings, please go to menu: MAINTENANCE->miscellaneous and tick on SETUP and CONFIGURATION check-boxes and then on green action button. It will prompt for system re-boot. After re-boot you can test how your storage system works with new software. If all is OK, we do recommend to update. WE DO STRONGLY RECCOMEND TO RUN SUCH TRIAL BEFORE UPDATING YOUR CURENT VERSION, AS THERE IS NO DOWNGRADE POSSIBLE. RUNNING TRIAL PLEASE CHECK IF ALL YOUR INSTALLED HARDWARE COMPONENTS ARE FUNCTIONAL. In order to update your current DOM with new software v5.0 up60 build3511, please boot from the USB-stick and in second menu please select Run software update installer Please follow all steps until reboot. If you want to try new software with new hardware, please select 64bit system. This will run 60 days trial. If you want to continue to run trial after 60 days you need to re-format your volume groups. In order to do it, please select function: Delete content of units in console tools (ctrl-alt-x) PLEASE NOTE: all your data will be lost after re-formatting. General Important note: • Upgrade to this version is only possible for build 3204 to 3278. • After upgrading, there is NO possibility to downgrade to ANY previous version. • For bonding, it is recommended to use NICs using similar chipsets. Using different NICs with different chipsets may not work satisfactorily. If you want to use different chipsets in bonding, please run stress tests and check logs before going live. • It is recommended to use Internet Explorer v7.X. Previous versions are no longer tested. • Replication of volumes is not working between 32 and 64bit versions. • In case of problems when running the "Repair filesystem" function please disable all running tasks, including snapshots, data replication and backup, through the Web GUI. • WORM volumes have some limitations: share created on such volume cannot be published via AppleTalk, the volume also cannot be backed up with the local backup functionality. • VERITAS backup agent works only with VERITAS Backup Exec up to version 10. It does not work with SYMANTEC Backup Exec. • In 64bit system mode the VERITAS backup agent is not working. Please use 32bit system if you are going to run the VERITAS backup agent. • Intel IO/AT is working only in 64bit operating mode. • The SMB online Antivirus scanning function is no longer supported. NEW: • New kernel 2.6.27.10 (32 and 64 bit). o New kernel solves many stability and performance issues. o Kernel 64 bit as default. • New settings in the scheduler (odd and even weeks). • GUI improvements. FIXED: • Solved problem with bacula crashing. • Solved problem with checksys crashing. UPDATED: • Updated underlying operating system. NOT SUPPORTED: • RocketRAIDa 1740,2240,2310. KNOWN ISSUES: • It is not possible to mount NFS shares directly using the following schema: mount -t nfs IP_addr:/share_name /local_mount_point Instead, please use the following syntax: mount -t nfs IP_addr:/share/share_name /local_mount_point The keyword "Share" must always be added to the syntax. • MPIO mode for the QLOGIC HBA FC does not work. • Myricom is not working 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 Console tool for RAID controller configuration is not working under 64bit operating mode (with 32bit kernel the tool works correctly). • 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 behaviour. • 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 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. • If you are using ADS authentication, the 'All Squash' option for NFS will not work correctly. • The Remote Support Service sometimes may not restart automatically after a reboot, in such case please re-enable again to start the service. • 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.