Dear visitor,
on Februar 15, 2017 Daniel Braun, the owner and mastermind of this website passed away unexpectedly. This is an unbelievable shock and loss for everybody.
Access the Data Protector WebUI
Data Protector 10 features the new WebUI integrated in the Home context of the legacy MFC GUI. The WebUI in Data Protector A.10.03 includes the Dashboard, Telemetry, Scheduler, Missed Job Executions and Global Option Tuning. Did you know that it is possible to access the WebUI from outside the MFC GUI? The following quick guide demonstrates how to make it work.
Prepare a Web User
Connect to the MFC GUI. In the Users context select an existing user or create a new user. In A.10.03 and later each user also has a Web User Name based on the Name, Group and Domain. Select Reset Password for the user that should be used.
omniusers -add -type W -usergroup admin -name USER -group DOMAIN -client client.domain.com -setpass to create a new user and reset the password.
IMPORTANT: Starting with A.10.03 and later editing the UserList file manually with a text editor is no longer supported and may cause issues to the KeyCloak service.
SYSBACKUP for Oracle 12c
Starting with Oracle 12c three new administrative roles and users have been introduced to conform the principle of access to the least privilege. The users and roles named SYSBACKUP, SYSDG and SYSKM will be created when the database is created with their account in expired and locked status. SYSBACKUP is used to perform backup and recovery operations from either Oracle Recovery Manager (RMAN) and or through SQL*Plus – you can see all privileges within the Oracle documentation.
If a Oracle 12c is detected on the client system, Data Protector A.10.01 and later now automatically uses sqlplus user/password@SID AS SYSBACKUP as the connection string to the database. As a result you may encounter the following backup issue after a Data Protector client or a Oracle database upgrade.
ORA-01031: insufficient privileges CONNECT: sys/*****@SID [Major] From: ob2rman@oracle.domain.lan "" Time: 05/15/18 18:15:21 Backup of target database failed.
Older Oracle databases (10g, 11i) do not require changes as they will continue to use SYSDBA. Continue reading “SYSBACKUP for Oracle 12c” »
Data Protector 10 – Patch Bundle A.10.04 (Build 182)
The Patch Bundle A.10.04 (Build 182) for Data Protector 10 has been released on May 22, 2018.
Data Protector A.10.03 was released as a full install therefore the cumulative patch 10.04 can only be installed on top of A.10.03. A direct upgrade from A.10.00, A.10.01 or A.10.02 is not possible!
It is recommended to install it on all Installation Servers (IS) and the Cell Managers (CM). Then push the new packages from the IS to all Data Protector client systems to get the latest fixes into effect.
This patch can also be installed locally on Windows Data Protector client systems. In this case only components that were locally installed on the client will be updated. Linux and UNIX clients still require an Installation Server while updated packages can be extracted from the Linux or UNIX Installation server manually.
Continue reading “Data Protector 10 – Patch Bundle A.10.04 (Build 182)” »
Webinar [de] – DPzWs 2018/05
Sorry, this article is not available in your language due to the fact that the following Webinar is only in German language available.
Continue reading “Webinar [de] – DPzWs 2018/05” »
Complex Schedules in Data Protector
Transitioning to the new Consolidated Scheduler, introduced with Data Protector A.10.00, can be a challenge. Especially when customized schedules have been used in the Legacy Scheduler to overcome former product limitations. A common example are manually modified schedule files to execute jobs at the last weekend of the month.
Data Protector A.10.03 improves the overall upgrade experience from previous versions such as 8.1x and 9.x. During the upgrade existing Legacy- and Advanced Scheduler schedules are migrated into the new Consolidated Scheduler. Once the upgrade is complete a summary is displayed by the installer. Details on schedule migration are logged into the file migration.log on the Cell Manager.
Successfully migrated schedule files (Legacy Scheduler) are kept in the corresponding directories on the Cell Manager but are renamed to SpecName.migrate. Empty schedule files are skipped. This allows manual modifications to any non-successfully migrated schedule files and re-run the schedule migration at a later point in time using omnidbutil -migrate_schedules.