Copyright (C) 1999-2009 Storix, Inc. All rights reserved **************************************************** * STORIX SYSTEM BACKUP ADMINISTRATOR FOR LINUX * * -------------------------------------------- * * CHANGE HISTORY * **************************************************** The following details the changes appleed to the current version and release (7.1) since its initial availability (July 1, 2009). Refer to the RELEASE NOTES for details on changes and enhancements added to this release from prior releases. VERSION MM/DD/YY DESCRIPTION ------- -------- ------------------------------------------------- 7.1.0.0 07/01/09 VERSION 7.1 GENERAL AVAILABILITY NEW FEATURES 1. GROUPS Multiple backup groups can be configured with separate sets of clients, servers, jobs, and any application or backup settings. Allows the same admin system to have multiple interfaces used (each with a separate group) concurrently. 2. USER LEVELS At least one "admin" user must be configured when installing V7. A user may defined as one of 4 levels, "roles", determining access within the applicattion or access to commands. "System admin" users are allowed full access to all functions for all groups (including configuring groups and users) while a "backup user" can only to run and monitor backup jobs. If not logged onto the system as root of if multiple users exist, user is prompted for a username/password when running any command or starting the GUI. The same username/password is required when using the web interface. 3. SHARED SERVERS Servers are configured within a backup groupp, but may allow access to different groups, either managed by the same "admin system" or from remote admin systems, thus allowing groups managed by different departments or companies to backup to the same remote server. Disk backups may be shared or securely stored in directories securely accessible only by the original group or client system. 4. BOOT MEDIA MANAGEMENT Management of network and CDROM boot media. Ability to view/update/remove boot media. Ability to copy CDROM boot media to configured server for central retention. 5. CLIENT LOCAL BACKUP MEDIA Clients (and standalone workstations) may not backup to local tape or disk (directories) without configuring each client as a backup server. Options not provided for backup jobs, verifies, restores, etc for "Local Tape/Disk". Backups are then written to local media on the client with no network traffic. 6. LOCAL SYSTEM BACKUP DISK MANAGEMENT Local system backup disks can be configured for each client (or standalone workstation). The backup disks and directories can be configured, imported (from portable media), and unconfigured for each client. Local system backup disks will be automatically detected during the system installation process. 7. AUTOMATIC CREATE/UPDATE BOOT MEDIA New backup job setting for system backups allows boot media (CDROM/Network) to be automatically created and placed on the client or a shared boot media server (see BOOT MEDIA MANAGEMENT). 8. SOLARIS ZFS SUPPORT - Support for backup, recovery and migration to Solaris systems with "ZFS on root". - ZFS Snapshot backups may be performed for any backup type containing ZFS filesystems. Provides point-in-time backup of all ZFS filesystem data. CHANGES/ENHANCEMENTS 1. WEB INTERFACE - New color schemes to match GUI interface - Authentication log - All features of GUI added (except Copy Backup option coming soon) - Enhanced look and feel of pop-up windows/messages 1. New "Campfire"color scheme. 2. Global Backup Retention Policies may be overridden for each backup "profile". Backup retention no longer specified in backup job settings, but a customized profile can be applied to each backup job. 3. Global backup Process Priority may be overridden for each backup "profile". Backup priority no longer specified in backup job settings, but a customized profile can be applied to each backup job. 4. Support for Linux ext4 filesystems. 5. AIX "split-mirror" backups no longer supported, but replaced with Snapshot Backups for AIX, supporting point-in-time backups of all JFS2 filesystems on AIX Version 5.2 and later systems. 6. Original permissions of filesystem mount points retained after system recovery. 7. Support added for Linux on PowerPC (PPC) systems using a VFAT boot filesystem (typically SuSe). NOTES 1. A "main" backup group is automatically created when installing or updating to V7 for the first time. Any existing confiuration is moved into this group. 2. An "admin" user is created and password must be provided the first time V7 is installed or updated. This user will be required to access the GUI interface if not executed from a "root" system login. 3. Prior GUI interface option to allow "non-root" system users access to the application is no longer supported. Prior users configured are no longer recognized and must be re-added using the new Users options. WITHDRAWN 1. AIX "Power" (raw device) System Backups are no longer supported. 2. Oracle Database Backup optional feature is no longer available. 3. Window (SMB) Shares optional feature is no longer avaialble. 7.1.0.1 07/06/09 UPDATE TO V7 MIGRATION 1. Migrate previous cron files for scheduled jobs to include group id. Cron prompted for username if more than one user configured, failing to start scheduled jobs. 2. Added NSS support in boot media for 64-bit Linux systems with 32-bit compatibility libraries in /lib32. Caused failure with remote install management on these systems. 3. Syntax error initializing random tape libraries. 4. Backup admins may now enable clients for network boot. 7.1.0.2 07/16/09 FIXES 1. Error reading snapshot configuration saved via the web interface. 2. Syntax error in GUI when saving preferences, and Network Options contains a hostname or IP address. 3. Adding a client would hang when performed from the GUI. This would only hang on first client added following the initial software installation. CHANGES/ENHANCEMENTS 1. GUI now indicates if client is enabled for network boot. 2. When enabling a client for network boot, if the boot server for the selected client has been changed, then the network boot configuration on the previous server will be disabled. 7.1.0.3 08/06/09 FIXES 1. When configuring a backup job using "stjob", the cron-style schedule string will be validated. 2. When booting from CDROM boot media, making multiple attempts to find the CDROM device that contains the SBAdmin boot media. Previously, it was possible that the boot process would not find the appropriate CDROM device and drop to a shell. 3. Error when enabling optional license feature options (data encryption and TSM client backups) to new clients. 4. Fixed possible internal program error when backup fails that is configured to use snapshots. 5. System installation menus crashed when configuring network device, RIM, or TSM and restoring from directory using %G notation. 6. Failed to configure TSM clients from the command line using "stconfigtsm". 7.1.0.4 08/31/09 ADDED 1. Web Interface support for Internet Explorer 8. FIXES 1. The "stprofile" command improperly handled resetting values (by using "none") for backup process priority, number of days to retain, and number of backups to retain. This would cause backups to fail with an internal program error. 2. Fixed profile select box for Backup Process Priority (Web Interface only). 3. Boot media with TSM support now supports node names longer than 20 characters. 4. Fixed snapshot backups to backup proper logical volume when performing snapshot backup. 5. When creating CDROM or network boot media, making unnecessary calls to the server when entering a boot image name (GUI only). 6. When creating CDROM, disk or tape boot media, unable to select a TSM backup when setting default backup to restore from (GUI only). 7.1.1.0 10/19/09 NEW MODIFICATION LEVEL 1. Added support for Device-Mapper Multipath devices. 2. Added support for TSM API version 6.1. 3. New software installation package for x86_64 systems. FIXES 1. Incorrectly translated UNIX date used for backup labels on some RHEL systems. (Web Interface Only) 2. Prevent client name from being configured if already configured using varying capitalization. 3. Error in config file when enabling a client for network boot with RIM. Causes kernel panic on boot. (Web IF Only) 4. No longer necessary to refresh stqdaemon when updating status notification settings. 5. In some cases, unable to select backup to restore from when configuring a client for network boot. (Web IF Only) 6. Non-system backup directory not set correctly on Workstation Edition. (Web IF only) 7. Install server not set properly when configuring a client for network boot. (Web IF only) 8. Error creating boot disk boot media for Workstation Edition. (Web IF only) 9. In some cases, tape drives not available when configuring Workstation Edition. (Web IF only) 10. Module aar81xx (Adaptec 1430SA RAID Controller) added to modules to include on boot media if available. 7.1.1.1 10/22/09 FIXES 1. Network boot images created from the command line were not listed properly. (Web IF only) 2. Fixed improper priority setting in profile configuration when saving with the default. (Web IF only) 3. When creating boot media from GUI, improperly listed clients to choose from if device list in server configuration was not set to "all". 7.1.1.2 11/13/09 FIXES 1. Backups run from non-primary admin/group did not support alternate hostname/IP for backups and restores. This only applies to servers that are shared by multiple administrators and configured with an alternate hostname/IP for backups and restores. 2. When creating cdrom boot media on IA64 systems, increased the size of vfat boot filesystem from 8MB to 9MB to support larger kernels and necessary boot files. 3. When installing client software, create group definition file if it does not already exist. 4. When installing software, creating appropriate link to libstorix.so in /usr/lib32 if installing 32-bit (i386) version onto x86_64 bit system. 5. When configuring backup job of type FULL_SYSTEM only list configured directories. (Web IF / Workstation only) 6. Added validation of backup directories and profiles when running stjob from the CLI. 7. Produce a warning during boot media creation if process is unable to verify initrd/initramfs or CDROM ISO image because the system used to create the boot media does not have support for loop devices or iso9660 filesystems. Previously, the boot media creation process would fail. 8. Remove old exclude list configuration files prior to running the backup. Previously, the exclude lists could have been inadvertantly applied because they existed. 9. When using terminal type of "linux" for menus during system recovery, disable utf8-mode on console. This will prevent problems some distributions (ie RHEL5) have with ncurses and utf8-mode consoles. 10. Prevent users from restoring a PPC system with more than one bootable partition on the bootdisk. 11. When performing a filesytem or directory backup with exclude lists, items in the datalist will be excluded if then are found in the exclude list. 12. Status output not updating properly using the MSIE browser. (Web IF only) 13. In some cases, radio buttons not working properly with the Apple Safari browser. (Web IF only) 14. During system recovery, produce warning message if the kernel release level of the boot media differs from the selected backup. 7.1.2.0 01/04/10 FIXES 1. In some circumstances, backup jobs could be scheduled multiple times during software update. 2. The megasr module will be loaded before the ahci module when booting from boot media. Some users have reported problems when the order is reversed. 3. Corrected detection of libncurses during software install. 4. When creating CDROM boot media, loading the loop module prior to validating the ISO for systems that do not already have it loaded. 5. Fixed UDEV issue with systems that link udevtrigger to udevadm. During system recovery device nodes would have not been created. 6. Writing to a parallel virtual device with more than 3 physical devices sometimes hung. 7. Restore from network backup hung in some instances. Data was restored for a filesystem but command would not exit. This problem only occurred since 7.1.1.2 update. 8. Possible error when attempting to configure a new client for network boot. (Web IF Only) 9. In some cases, unable to change install image for configured network boot clients. (Web IF Only) 10. Possible error when attempting to configure a new client for network boot. (Web IF Only) 11. In some cases, unable to change install image for configured network boot clients. (Web IF Only) 12. Update look of alert messages and prompts. (Web IF Only) CHANGES/ENHANCEMENTS 1. No longer creating desktop icons for launching SBAdmin GUI because they could not be guaranteed to work. 2. Added hwclock utility to boot media. 3. Added feature to copy and rename backup jobs. 4. Added feature to remove a client when it is assigned to configured backup jobs. 7.1.2.1 01/22/10 FIXES 1. TSM options specific to a client/node (ie. PASSWORDDIR) may be added to the tsmclient:CLIENT configuration file on the administrator so that the options are applied to the dsm.sys file on the client that is used by SBAdmin. This will not effect the dsm.sys file used by the native TSM backup/archive client. 2. When configuring random tape libraries, limiting the number of tape drives that may be configured to 4 and limiting the number of tapes per drive to 20. Previously, there were no limits. 3. Multiple tape libraries listed improperly. (Web IF Only) 4. Unable to set tape library counter for libraries with multiple drives if previously unset. (Web IF Only) 5. Bonded ethernet devices were not disabled following system recovery of SuSE systems. 6. Headings incorrect when listing backup labels by client when viewing status/output messages. (Web IF Only) 7. Update from v6 to v7 did not properly migrate server configuration files. This would cause newly added clients to not be updated in the server access file. 8. Device-mapper multipath driver for EMC devices (dm-emc) was not included in boot media.