BACKUP EAGLE. Release Notes. Version: Date: 05/07/2012

Transkript

1 BACKUP EAGLE Release Notes Version: Date: 05/07/2012 Schmitz RZ Consult GmbH BACKUP EAGLE Release Notes Seite 1 von 8 Date

2 Contents 1. Improvements Improved servercheck reporting Improved servercheck management New report template - compliance with two markers Minor improvements Migration notes Common notes Release key change Requirements Migration from version 5 or version Uninstall an installed version Rename the installation directory Installing the new release Package existing protocols into ZIP containers... 6 Schmitz RZ Consult GmbH BACKUP EAGLE Release Notes Seite 2 von 8

3 1. Improvements With this release the following improvements were introduced to BACKUP EAGLE Improved servercheck reporting The creation process of servercheck reports was completely redesigned and integrated in report management. You can now define multiple individually configurable servercheck reports. For every servercheck the results of multiple TSM-/NetWorker servers can be combined in on table. For every servercheck report you can define: the result grouping by TSM-/NetWorker server and/or servercheck the serverchecks to show up in the report (*1) the TSM-/NetWorker servers to show up in the report For every servercheck can be definied: when to display the results of the check in the report (always/on error in the last collected data set/on error in the last 24 hours) (*1) which data to show (failed items/all) (*1) which fields to show (*1) sorting order of the fields (*1) (*1) Might be not be configurable using the graphical user interface. May require to edit the XML based reporting template. [BE-1283] 1.2. Improved servercheck management Servercheck management was redesigned. The old servercheck management dialog was split up into multiple, simpler dialogs. Servercheck management was redesigned provide better performance and usability. [BE-1344] Schmitz RZ Consult GmbH BACKUP EAGLE Release Notes Seite 3 von 8

4 1.3. New report template - compliance with two markers The following new report template was added in this release: Report Template Backup results compliance (with two compliance markers) Description List and chart of the number of successful and failed backups per day. Two compliance markers can be defined. When the percentage of successful backups is lower than the specified compliance markers this is indicated by yellow (1st marker) and red (2nd marker) colors. [BE-1358] 1.4. Minor improvements This BACKUP EAGLE release contains the following minor improvements: Description Reporting: Improved error message when a report name is already in use. In previous releases the error reason was not clearly visible. Reporting/Selfcheck: A selfcheck was added to report damaged report definitions. Previously there was no indication when a report was not created due to a damaged report definition. Id [BE-1304] [BE-1305] DOC: Report "Client Schedules" does not show information regarding enhanced schedules [BE-1329] Actlog analysis: Non registred nodes can cause thousands auf session messages in the actlog. This may drastically reduce the performance of the actlog analysis. [BE-1332] Schmitz RZ Consult GmbH BACKUP EAGLE Release Notes Seite 4 von 8

5 2. Migration notes Please read the following migration notes when updating to this version Common notes Please make sure that the following actions where take before the migration: - A current backup of the BACKUP EAGLE database was created - A current backup of the BACKUP EAGLE directories was created Release key change Starting with BACKUP EAGLE version 6.3 new release keys are required. Release keys from previous versions like 6.2 are no longer compatible to the new version. The required release keys are provided by Schmitz RZ Consult GmbH. You can import the new release keys using "Settings" => "License Management" => "Import". Notice: The new release keys are required only on the BACKUP EAGLE server. It is not necessary to change the release keys on any BACKUP EAGLE client components Requirements The migration to BACKUP EAGLE 6 is supported from the following BACKUP EAGLE 5 version: Migration from version 5 or version 6 With BACKUP EAGLE version 6.x the installation directory was changed from backupeagle5_server to backupeagle_server. To migrate the data the following procedure is recommended Uninstall an installed version Windows: The installed version has to be removed using the uninstall program. The remaining directory "backupeagle5_server" must not be deleted! Unix: The BACKUP EAGLE processes have to be stopped using BackupEagleServer.ksh, BackupEagleAgent.ksh und BackupEagleDB.ksh. Schmitz RZ Consult GmbH BACKUP EAGLE Release Notes Seite 5 von 8

6 Rename the installation directory Notice: Please skip this step when migrating from Version 6 to a newer release of version 6. For example when migrating from 6.1 to 6.2. Rename the directory backupeagle5_server to backupeagle_server. Notice: On Windows it may not be possible to rename the directory because it is blocked by accesses from Windows processes. Usually the directory can be renamed after stopping the process "conime.exe" using the task manager. If it is still not possible to rename the directory after ending the process please reboot the computer BACKUP EAGLE is installed on and retry after the reboot Installing the new release Windows: Install the new BACKUP EAGLE version 6.x by running the installer. As installation directory backupeagle_server is suggested. Unix: Installation is done by unpacking the install tar archive in the directory "/usr/local". After unpacking change to backupeagle_server/scripts and run "install.ksh". After the installation process has been completed start the BACKUP EAGLE processes with BackupEagleDB.ksh start, BackupEagleServer.ksh start und BackupEagleAgent.ksh start. Notice: Before unpacking the install tar archive rename the directory "backupeagle_server/lib" to "backupeagle_server/lib_current_date". After unpacking the install tar archive copy custom database drivers (if used) like "ojdbc*.jar" (Oracle), "mysql-*.jar" (MySQL), "sqljdbc*.jar" (MS SQL) back to "lib". Unix: Please check the automatically start of the scripts used to start the BACKUP EAGLE processes. With the change in the installation directory calls in "inittab" an/or links in runlevel directories may need to be updated Package existing protocols into ZIP containers Notice: Skip this step when migrating from version x or higher to an newer version. Im Rahmen der Migration ist es möglich, die bereits im Dateisystem vorhandenen Textprotokolle, PDF- Protokolle und Scdbif-Dateien zu ZIP-Containern zusammenzufassen. Werden die bestehenden Dateien nicht während der Migration zusammengefasst, erfolgt das Zusammenfassen nach und nach durch einen BACKUP EAGLE internen Job. Dabei werden allerdings zur Ressourcenschonung nur ca. Schmitz RZ Consult GmbH BACKUP EAGLE Release Notes Seite 6 von 8

7 1000 Dateien pro Tag zusammengefasst, so dass es in Umgebungen mit vielen Dateien sehr lange dauern kann, bis alle Dateien in ZIP-Container verpackt wurden. During the migration it is possible to package already existing text protocols, PDF protocols and protocol base files (scdbif files) into ZIP containers. If these files are not packaged during the migration the packaging is done step by step controlled by an BACKUP EAGLE internal job. To reduce the resource utilization only 1,000 files are packaged per day. In environments with very much files this can result in a long time span needed to package all files. Windows: Stop the BACKUP EAGLE services Agent and Server. Do not stop the DB service. cd %ProgrammFiles%\srzc\backupeagle_server\scripts backupeagle_zip_data.bat Notice: The packaging of files in ZIP containers can last several hours. It can be stopped at any time and can be restarted later Start the BACKUP EAGLE services Unix/Linux: Stop the BACKUP EAGLE processes Agent and Server. Do not stop the DB service. cd /usr/local/srzc/backupeagle_server/scripts./backupeagle_zip_data.ksh Notice: The packaging of files in ZIP containers can last several hours. It can be stopped at any time and can be restarted later Start the BACKUP EAGLE processes Schmitz RZ Consult GmbH BACKUP EAGLE Release Notes Seite 7 von 8

8 Schmitz RZ Consult GmbH Das vorliegende Dokument steht gemäß 2 des Urheberrechtsgesetzes (UrhG) als persönliche geistige Schöpfung unter dem Schutz des UrhG. Geschützt ist der Urheber insbesondere vor einer unberechtigten Veröffentlichung, der Missachtung der Urheberschaft oder der Entstellung des Werkes sowie vor einer unberechtigten Verwertung, insbesondere durch Vervielfältigung, Verbreitung oder Ausstellung des Werkes. Die Verwendung des Werkes gleich in welcher Form und welchen Umfangs durch den Auftraggeber oder durch Dritte, welchen er das Werk unberechtigt überlassen hat ohne oder über die im Vertrag geregelte Nutzungsbefugnis hinaus ist unzulässig und berechtigt den Urheber zur Geltendmachung von Unter-lassungs- und Schadenersatzansprüchen. Dies gilt auch für den Fall, dass zwischen dem Urheber und dem Verwender keinerlei vertragliche Beziehungen bestehen. Daneben ist der Verstoß gegen ein Urheberrecht unter den Bedingungen der UrhG mit Freiheitsstrafe bis zu fünf Jahren oder Geldstrafe bedroht. Sämtliche dem Auftraggeber zur Verfügung gestellten Muster hat dieser an den Urheber auf Verlangen unverzüglich zurückzugeben. Ohne ausdrückliche Zustimmung des Urhebers ist eine Weitergabe der Muster an Dritte unzulässig und verletzt das Urheberrecht des Urhebers. Schmitz RZ Consult GmbH BACKUP EAGLE Release Notes Seite 8 von 8