Plasmon Diamond Library Manager

Transcription

1 Plasmon Diamond Library Manager Release Details Product Release Notes Release Name: Diamond Library Manager Release Note Number: Note091 Release Version: Release Date: 1 st July 2005 Release Type: Full Supported Platforms for Windows 2003 (SP1), Windows 2000 Server (SP4) Libraries: Supported Platforms for Stand Alone Drives: Windows 2003 (SP1), Windows 2000 Server (SP4), Windows 2000 Professional (SP4), Windows XP Professional (SP1a or SP2) Release Summary: Plasmon Release of Diamond Library Management Software. Product Enhancements and Bug Fixes Enhancement Windows 2003 SP1 Support Auto Bus Configuration Mixed Media Support Area of Bug Fix: Backup and IBM Director (Bug ID 4275) Default pnode value (Bug ID 4507) Manager CPU usage when running backup (Bug ID 4789) Support for Windows 2003 Service Pack 1 has been introduced in this release. Multiple bus libraries will now be automatically configured when Diamond starts. Drive bus entries will no longer be required in manager.cfg G-Series libraries and Gx-Series libraries containing both MO and UDO media have been qualified for this release. An issue where backup would fail to complete on a system running the IBM Director agent has been resolved in this release. The default number of pnodes has been increased from 200 to 2000 in this release. This may in some cases improve performance of the file system. An intermittent issue where Manager could use 100% of the systems CPU when running the backup service has been resolved in this release. Known Issues and Product Notes Issue: Volume Group Properties (Bug ID 249) Details and Workaround: The date shown when viewing the properties of a Volume Group using Windows Explorer is set to 1/1/1970. This is caused by having different creation dates for each disk in the Volume Group Page 1 of 5

2 Cannot Support Changing Server IP Address (Bug ID 903) Deleting Directories from Volume Groups. (Bug ID 990) Activity Page (Bug ID 1028) Backup (Bug ID 1054) Errors While Deleting From MO Media (Bug ID 1113) Installation Can Cause GUI To Crash (Bug ID 1191) Font Size In Library Contents Page (Bug ID 1204) Operations Log Debug (Bug ID 1206, 1280) Renaming a Folder Within a Volume Group. (Bug ID 1223, 1333) Not Enough Space Error When Copying to a Volume Group. (Bug ID 1279) Evaluation Error (Bug ID 1283) Packet Writing (Bug ID 1305) Work Around: None After changing the Diamond Servers IP address The Administration GUI with fail to function. Work Around: After changing the IP address disable the web GUI, edit the three entries in the httpd.conf file manually and reenable the web GUI Directories are not removed from all disks in a volume group. This may cause attempts to recreate a directory that had been written to multiple disks in a volume group before being deleted to fail, as the directory already exists. Work Around: None During a Full Rescan of large numbers of media, the Administration GUI can time out returning a Windows request timed out error message. Work Around: Close the Administration interface during rescans of large numbers of media. An intermittent issue exists in the backup function. This can result in some of the data not being copied across. Work Around: Use a cache path such as c:/temp An Invalid MS-DOS Function error is intermittently reported when deleting files from MO Media using Windows explorer. Work Around: Fully rescan the disk and re-attempt the deletion When installing a new version of Diamond, with the Administration GUI open, errors can be seen although the installation is successful. Work Around: Ensure all instances of the Administration GUI are closed If the largest font size is selected in Internet Explorer, the header for the library contents page in the Administration GUI does not display correctly Work Around: Don t use the largest font size Should a media surface fill during a copy process, additional debug may be seen in the operations log. Work Around: Ignore. Due to the way Volume Groups work, it is possible to have the same directory name written to several disks, therefore when a rename is requested, not all instances of the folder will be renamed. When filling the surfaces within a volume group with files, Diamond will attempt to spread the data evenly across all media by only allowing disk utilisation to reach a 50% watermark before changing the media surface. Once all volume media is 50% full any attempt to write a file larger then the remaining space on the currently selected media surface will fail. The end user will see a disk full dialogue (with a defragmenter option) even though the other volume media may have enough space to accommodate the file. This problem is more likely to be seen when large files are written. The issue is worsened when multiple versions of the same file are written with each successive version increasing in size. When running Diamond in evaluation mode, an error may be seen in the Windows event Application log. Work Around: Ignore. When you write enough data onto a DVD-R/CD-R to fill the media, the last file can fail to write with the Windows error: Page 2 of 5

3 Windows File Attributes (Bug ID 1383) WORM History Audit (Bug ID 1404) Trailing Spaces (Bug ID 1405) Login via HOSTNAME (Bug ID 1406) UNICODE Support (Bug ID 1407) Deletion of Directories (Bug ID 1408) Web Server log files can not be deleted via the GUI (Bug ID 1409) Enterprise D automatically OVMs media (Bug ID 1410) Formatting Media to Root (Bug ID 1417) Formatting Media With Extended ASCII Characters Via The Administration GUI. (Bug ID 1545) Moving Media (Bug ID 1546) UDF Image Creation (Bug ID 1667) GUI Server Error (Bug ID 1723) Cannot write file, disk is full. Work Around: Note free space before attempting writes. The Windows file attributes such as read only are not supported in this release. There is currently no way to view the history audit of WORM media via the Administration GUI. Work Around: Use the JCP history function Trailing spaces in media volume names can prevent access to HTML pages on the disk. Work Around: Remove the trailing space during the import process. Logging in via the server HOSTNAME can cause undesirable behaviour in the browser. Work Around: Use the server IP address or localhost. Some of the GUI Administration screens in Diamond do not currently support the use of UNICODE characters. Work Around: Use both ASCII and UNICODE characters in volume names when importing the media. Intermittently, due to the behaviour of Windows Explorer, when deleting directories from media, the directory itself can fail to be deleted although the contents are successfully removed. Work Around: Close all windows open on the directory, go to the level above on the directory tree and delete the required folder. The Web Server Access log and error log files can not currently be deleted via the GUI. Work Around: In the unlikely event that these files should require deletion, stop the GUI and delete the logs at the following paths: \NTMGR2\Apache\logs\access.log \NTMGR2\Apache\logs\error.log When a magazine is removed from an Enterprise D library, the all the media in the magazine is exported with OVM. Work Around: Should the OVM record need to be removed, select Purge from the disk management screen. When formatting media for use at the root of the library, only the volume name of \ is supported, regardless of this Diamond will allow the use of '/' as a volume name when importing media. Work Around: Ensure only '/' is used as a volume name when importing media for use at the root of the library. The use of extended ASCII characters in volume labels when formatting media is not supported in the Administration GUI. Work Around: Use standard ASCII characters or format via the commend line. When attempting a move disk with two libraries attached to the server, the operation can fail. Work Around: Retry the move process. The UDF image creation tool does not currently support source data with UNICODE characters in filenames. An intermittent problem exists where the following error may be seen in the Administration GUI: Sever error with IP :80 please take a note of the time and page. Can you report this error to your system administrator Shut down and reboot your system Work Around: Refresh the browser page and login in again if Page 3 of 5

4 Repairing Plasmon Media (Bug ID 1785, 3128) Windows Utility Support (Bug ID 1862) GX Library Keypad (Bug ID 2354) System Restart (Bug ID 3041) McAfee Anti Virus (Bug ID 4554) Modification of data from a remote system on the UDF File System (Bug ID 4584) Repair Utility (Bug ID 4988) History Utility (Bug ID 5094) Product Note: Clarifications for using Single-Sided Media in a Rotation-Station equipped D-Series necessary The repair of UDO media formatted with the Plasmon File System is not supported in this release. The repair operation will fail and in the case of Windows XP, may generate a Microsoft error report and cause the system to hang. Work Around: Should a Plasmon formatted UDO disk need to be repaired or have data recovered, please contact Plasmon Technical Support. Occasional problems have been encountered when using Notepad, Microsoft Paint, Microsoft PowerPoint, Microsoft Word, etc to directly edit files on optical media. Work Around: Edit the files on a local hard disk, and transfer to optical media once the changes are complete. During certain library operations, Diamond can temporarily lose control of the library keypad and display. An intermittent issue has been observed where the OS can lock up, often resulting in an automated reboot in the case of Windows An issue exists where McAfee Anti Virus can cause the system to hang when scanning the Diamond Library and/or database. Work Around: Exclude the Library and MGRCACHE directory from the scan. An issue exists where modifying a file on WORM media from a remote system on the UDF file system can cause explorer to hang. Work Around: Edit the files on a local hard disk, and transfer to optical media once the changes are complete. The repair utility will not operate correctly when using DVD-RAM media. The copy in the history utility only does not correctly copy a file when using the Plasmon file system. Work Around: Send media for recovery to Plasmon Technical Support. Note: For D-Series libraries without rotation stations the following clarifications DO NOT apply: Adding Single-Sided Media to a Double-Sided D-Series Library In a rotation-station equipped D-Series library, you may add single sided media, however the Side B of each single sided disk will show up as 'Side Not Scanned into the Database' and error 315 may be displayed. You may also receive ENOENT or EIO errors when attempting functions related to Side B (the label side) of single sided disks. Exporting Single-Sided Media from a Double-Sided D-Series Library In a rotation-station equipped D-Series library, you may export single sided media, but not OVM export single-sided media. In this configuration, if you attempt to OVM Export a single-sided disk, Diamond will only Export the disk and not retain any information about the disk. Single-Sided Media is not OVM exported when a Magazine is physically removed from the Library When you physically remove a magazine in a rotation-station equipped D-Series Page 4 of 5

5 UDF Image Creation Apple Extensions UDO Evaluation Media JAVA Virtual Machine Support Windows NT Support CD-R Media Support Windows Automatic Update Auto Bus Configuration Windows Service Packs library, Diamond will initiate an automatic OVM (Offline Volume Management ) process of all disks contained in that magazine. Double-sided media will be OVM exported, however single-sided disks will not be OVM exported. Instead, single sided disks will be exported which removes all knowledge of that disk from the Diamond database. When creating a UDF image, the data source path must not exceed 64 characters or contain UNICODE characters. When creating an ISO image with Apple extensions, the source data must not exceed 800Mb. Should evaluation UDO media be used, the following line will need to be added to the operations config file: use_udo_unique_media_id = 0 Suns "Java 2 Platform Standard Edition" JVM is not supported in this release. Diamond no longer supports the Windows NT platform. This release of Diamond does not support the use of CD-R media in a Diamond controlled library for packet-writing or image writing. Windows update can request a system reboot when set to install all updates automatically. When Diamond is running as a Service this can cause the OS to lock up. Plasmon recommends that the Windows Update Service is set to prompt the user before installing any updates. Diamonds auto bus configuration currently only supports Plasmon Libraries Plasmon recommends that Diamond is shut down during the application of Windows Service Packs. Failure to do this may result in database corruption. Page 5 of 5