Data Protector - Passion for Data Protection

data-protector.org

Author Archives: Sebastian

SYSBACKUP for Oracle 12c

Posted on by

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)

Posted on by 6 Comments

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)” »

Complex Schedules in Data Protector

Posted on by 6 Comments

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.

Continue reading “Complex Schedules in Data Protector” »

Effectively manage omnirc options

Posted on by

Data Protector is highly customizable product with a wide range of configuration options. While the any global options applies to the whole Cell, the omnirc configuration file allows the user to tweak a specific client or just a module on that client system. It you have to manage a large amount of individual clients this can become a management challenge to make sure the right omnirc options are present on the right the client system.

Over the years several ways to deal with this has been found, e.g. the script omnircsync.pl (available in the download section) using the util_cmd -setomnirc push functionality. This functionality is adopted with the release of Data Protector A.10.03 into the product. We want to share some pretty handy use cases and examples of the new omnicc -update_omnirc command.

It allows to push one omnirc option (key/value pair) at a time and you can select a specific operating system type, client systems with a specific agent installed or a set of hosts in a comma separated list or from a input file.

omnicc -update_omnirc omnircName -value omnircValue
        [{ {-module moduleName1 [,moduleName2,..]} |
        {-client_os osName1 [,osName2,..]} |
        {inputFile | {-hosts hostName[,hostName2,..]}} }]

Options:
moduleName = da, ma, cc, mssql70, oracle8, vepa, (as found in cell_info file)
osName = gpl, microsoft, sun, ... (as found in cell_info file)

Continue reading “Effectively manage omnirc options” »

Data Protector 9 – GR Patches 9.09 (Build 117)

Posted on by

The General Release Patches A.09.09 (Build 117) for Data Protector 9 has been released on April 4, 2018.

The 117 GR Patches must be installed on top of the 115 and 116 GR Patches (which requires Patch Bundle 9.09).

It is recommended to install all the GR Patches as a group regardless if the updated components are used or not. It should be applied on all Installation Servers (IS) and Cell Managers (CM) in the correct order. Then push the new packages from the IS to all relevant Data Protector client systems that have relevant components installed to get the latest fixes into effect.

This patches can also be installed locally on Windows Data Protector client systems if the Patch Bundle has been installed locally. 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 9 – GR Patches 9.09 (Build 117)” »