Oracle Backup - Database must not contain any data files that are in backup mode.
Dear online team, Since upgrading from NetBackup 9.1 to NetBackup 10.4 we I have errors with Oracle backups if two jobs are run simultaneously. Let's say large database that needs 10 hours for the FULL backup to complete. During the time this backup is running, another Archive Log backup starts. (we have archive log backups running every half hour) This Archive Log backup fails with following error that was not the case previously: (5457) Database must not contain any data files that are in backup mode. This was not the case before and you could run as many jobs as you want at the same time.. This only happens to container databases that has pluggable databases inside the container. CDBs Has anyone experienced anything similar? Any help would be really appreciated. I even updated to NetBackup 10.5 but issue still remains..
NetBackup Enhancements for Oracle VLDBs (Very Large Databases)
In this day and age, data tends to only increase in size. For our customers with ever-growing Oracle databases (DB), timely backups and restores are a challenge. We have many existing features within NetBackup to protect Oracle, and now we have added a solution for Oracle Very Large DBs (VLDB). Figure 1. Oracle policy option to select multiple MSDP storage units The designation of “Very Large” is arbitrary, but a widely accepted definition is a database that is too large for the data protection to succeed in the desired time window. Oracle DB protection struggles are focused on completing backups faster, but the ability to restore within the expected time frame is often ignored, resulting in missed Restore Time Objectives (RTOs). This new Oracle policy option allows segmenting the Oracle backup across multiple NetBackup MSDPs (Media Server Deduplication Pools) storage units with the ability to choose which storage units are used (see Figure 1). For a single stream, this results in a backup image that is in the catalog as a single image, with the image’s fragments tracked in the catalog on each storage unit selected. A single backupid makes tracking and reporting streamlined. You can also increase the number of parallel streams. Allowing simultaneous writes to multiple disk pools increases the efficiency of the streaming backup. The number of storage units to use for the best results will vary from one database to the next. Further, take advantage of multiple parallel streams to further tune your Oracle backup. Storage units are linked to disk pools, and the most effective use of this option will leverage multiple storage units that are linked to multiple unique disk pools hosted on different media servers. This solution also works with where the nodes of a single Flex Scale are managed independently and only one storage unit is presented to NetBackup. There will be affinity for the database backup to write the same file, or piece, of the database backup to the same MSDP storage unit, so do not change this configuration often. Some of the considerations will be: Number of nodes in a RAC (Real Application Cluster), Number of instances, Number of parallel streams As more parallel streams and storage units are configured for the policy, the gain in performance is geometric improvements in the backup times. This must be aligned to your backup and restore goals and your existing infrastructure to avoid creating bottlenecks in the performance. To meet the desired goals, there may be a need to add more MSDP pools rather than having a few large pools each with a single node. Additionally, consider more load balancing media servers to also share data movement responsibilities. This solution can also use Storage Lifecycle Policies (SLPs) as multiple storage targets, enabling you to maintain your current business continuity and DR (Disaster Recovery) plans for your Oracle data. When selecting multiple storage units, you would select a different SLP (Service Lifecycle Policy) for each destination. If the desired SLP is not shown, confirm that it is using supported MSDP storage units. It is key that the SLPs for this use-case all be designed and configured with the same goals, including retention levels, and different source and target storage units. For example, if splitting the Oracle backup across 2 SLPs, each SLP would use a different backup storage unit, and a different secondary operation storage unit. In the case of replications (AIR (Auto Image Replication)), the replication relationship between the on-prem MSDP and the target MSDP each needs to be under the same target primary server (see Figure 2). It is possible to replicate many-to-one, but this would remove the benefit of segmenting the image across multiple disk pools. If the replication targets of only a portion of the database went to a different NB domain or were not retained for the same period, the image would not be complete and a restore would not be possible. Figure 2. SLP configuration requirement for multiple MSDP storage units with replication When the need for a restore arises, NetBackup takes advantage of multiple sources to read and stream back to the destination, with each disk pool reading a piece of the database image simultaneously. This results in a faster restore time for a large amount of data. The Disk Pool’s Maximum I/O streams setting will need to be adjusted according to the peak performance of the disks and the potential number of restore and backup streams. This setting can be changed dynamically, without a restart of services, to meet changing needs. Consider, also, the impact of load balancing media servers in such a configuration. If all media servers have credentials to all storage servers, they can potentially perform the requested read action during a replication or restore operation. In circumstances where some media servers are already busy doing other jobs, such as backups, NetBackup will choose the next-least-busy media server to perform the requested action. For most situations, it will be best to configure only the media servers needed for these repetitive actions to have access to the disk pools in-use. Plan disk pool deployment to maximize the throughput from the Oracle clients to multiple media servers and their NetBackup deduplication volumes. Take advantage of this new parallelism to improve throughput performance for both your backup and recovery operations for your Very Large Oracle databases to meet your strict RTOs.
Oracle RMAN backup status 13, timer expired
Hi all Sometimes, but not regularly, we experience one of our large Oracle backup ending with status 13. Archive logs is always successful, so is the FULLs. This applies to our diffs. We have a few thousand jobs that backup to a 5330HA cluster. Our Oracle backups runs NBU 8.1.2 on RHEL 7. Mediaserver is Appliance 3.1.2, with latest MSDP EEB bundle. Here is from Job Details of Parent job: 16.mar.2020 03:39:20 - Info bphdb (pid=120725) INF - input datafile file number=00029 name=+DATA1/PXCDBL_DBM/82CDF1F23C1993F2E053C443F80AE973/DATAFILE/datex_lob.2830.1001260637 16.mar.2020 03:39:20 - Info bphdb (pid=120725) INF - input datafile file number=00024 name=+DATA1/PXCDBL_DBM/82CDF1F23C1993F2E053C443F80AE973/DATAFILE/system.2824.1001259231 16.mar.2020 03:39:21 - Info bphdb (pid=120725) INF - input datafile file number=00027 name=+DATA1/PXCDBL_DBM/82CDF1F23C1993F2E053C443F80AE973/DATAFILE/users.2828.1001259241 16.mar.2020 07:25:50 - Info bphdb (pid=120725) INF - released channel: ch00 16.mar.2020 07:25:50 - Info bphdb (pid=120725) INF - released channel: ch01 16.mar.2020 07:25:50 - Info bphdb (pid=120725) INF - RMAN-00571: =========================================================== 16.mar.2020 07:25:50 - Info bphdb (pid=120725) INF - RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== 16.mar.2020 07:25:50 - Info bphdb (pid=120725) INF - RMAN-00571: =========================================================== 16.mar.2020 07:25:50 - Info bphdb (pid=120725) INF - RMAN-03009: failure of backup command on ch00 channel at 03/16/2020 07:25:33 16.mar.2020 07:25:50 - Info bphdb (pid=120725) INF - ORA-27192: skgfcls: sbtclose2 returned error - failed to close file 16.mar.2020 07:25:50 - Info bphdb (pid=120725) INF - ORA-19511: non RMAN, but media manager or vendor specific failure, error text: 16.mar.2020 07:25:50 - Info bphdb (pid=120725) INF - Failed to process backup file <bk_dPXCDBL_un2ur6tn8_s29410_p1_t1035171560> 16.mar.2020 07:25:50 - Info bphdb (pid=120725) INF - ORA-19502: write error on file "bk_dPXCDBL_un2ur6tn8_s29410_p1_t1035171560", block number 1 (block size=8192) 16.mar.2020 07:25:50 - Info bphdb (pid=120725) INF - ORA-27030: skgfwrt: sbtwrite2 returned error 16.mar.2020 07:25:50 - Info bphdb (pid=120725) INF - ORA-19511: non RMAN, but media manage 16.mar.2020 07:25:50 - Info bphdb (pid=120725) INF - Recovery Manager complete. 16.mar.2020 07:25:55 - Info bphdb (pid=120725) INF - End of Recovery Manager output. 16.mar.2020 07:25:55 - Info bphdb (pid=120725) INF - End Oracle Recovery Manager. Here is from job details of the failing job: 16.mar.2020 03:39:35 - Info bptm (pid=233514) start backup 16.mar.2020 03:40:38 - Info bptm (pid=233514) backup child process is pid 235121 16.mar.2020 03:40:38 - begin writing 16.mar.2020 06:40:39 - Error bpbrm (pid=233505) socket read failed: errno = 62 - Timer expired 16.mar.2020 06:40:41 - Error bptm (pid=233514) media manager terminated by parent process Obviousley there is a timeout involved here, but where? The backup job shows always timeout after exactly 3 hrs.
Replication director with Oracle
Hi, I am asking about certain setup for Replication director.. and if it is applicable because i am building a use case to use the replication director with the NetApp.. first.. the environment is a clustered master server NBU 8.1.2 on win 2012R2..with 4 media servers same NBU and windows version as master and one Veritas appliance 5230. we have a lot of Oracle DB on AIX. what i am thinking about is as follows To get the NetApp.. and have Oracle replicated using date guard to new environment hosted on NetApp as a NAS.. question here.. how to host it as a NAS not san.. using NFS or iscsi? next is to have snapshots taken from NetApp.. and then NBU will take backup from the snapshot..is it possible to take incremental backup from the snapshot? and how can i restore from the snapshot? Thanks for any help..
Error message in sap oracle detail log.
Error message occurs in the detail log during sap backup. What should I check? 2019. 12. 27 오후 3:42:03 - Info nbjm (pid=13885) starting backup job (jobid=23683) for client bxddev, policy bxddev_SAP, schedule Default-Application-Backup 2019. 12. 27 오후 3:42:03 - Info nbjm (pid=13885) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=23683, request id:{FE1420F4-2873-11EA-87DC-C738CC064B28}) 2019. 12. 27 오후 3:42:03 - requesting resource stu_adv_hkpbma2 2019. 12. 27 오후 3:42:03 - requesting resource hkpbaka1.NBU_CLIENT.MAXJOBS.bxddev 2019. 12. 27 오후 3:42:03 - requesting resource hkpbaka1.NBU_POLICY.MAXJOBS.bxddev_SAP 2019. 12. 27 오후 3:42:04 - granted resource hkpbaka1.NBU_CLIENT.MAXJOBS.bxddev 2019. 12. 27 오후 3:42:04 - granted resource hkpbaka1.NBU_POLICY.MAXJOBS.bxddev_SAP 2019. 12. 27 오후 3:42:04 - granted resource MediaID=@aaaab;DiskVolume=/advanceddisk/dp1/advol;DiskPool=dp_adv_hkpbma2;Path=/advanceddisk/dp1/advol;StorageServer=hkpbma2;MediaServer=hkpbma2 2019. 12. 27 오후 3:42:04 - granted resource stu_adv_hkpbma2 2019. 12. 27 오후 3:42:04 - granted resource TRANSPORT 2019. 12. 27 오후 3:42:04 - estimated 0 kbytes needed 2019. 12. 27 오후 3:42:04 - Info nbjm (pid=13885) started backup (backupid=bxddev_1577428924) job for client bxddev, policy bxddev_SAP, schedule Default-Application-Backup on storage unit stu_adv_hkpbma2 2019. 12. 27 오후 3:42:04 - started process bpbrm (pid=301944) 2019. 12. 27 오후 3:42:05 - connecting 2019. 12. 27 오후 3:42:08 - connected; connect time: 0:00:00 2019. 12. 27 오후 3:42:09 - Info bpbrm (pid=301944) bxddev is the host to backup data from 2019. 12. 27 오후 3:42:09 - Info bpbrm (pid=301944) reading file list for client 2019. 12. 27 오후 3:42:10 - Info bpbrm (pid=301944) listening for client connection 2019. 12. 27 오후 3:42:11 - Opening Fibre Transport connection, Backup Id: bxddev_1577428924 2019. 12. 27 오후 3:42:12 - Info bpbrm (pid=301944) INF - Client read timeout = 3600 2019. 12. 27 오후 3:42:12 - Info bpbrm (pid=301944) accepted connection from client 2019. 12. 27 오후 3:42:12 - Info bpbrm (pid=301944) start bpbkar on client 2019. 12. 27 오후 3:42:12 - begin writing 2019. 12. 27 오후 3:42:13 - Info dbclient (pid=20932) Backup started 2019. 12. 27 오후 3:42:13 - Info dbclient (pid=20884) Backup started 2019. 12. 27 오후 3:42:13 - Info bpbrm (pid=301944) bptm pid: 301952 2019. 12. 27 오후 3:42:13 - Info bptm (pid=301952) start 2019. 12. 27 오후 3:42:14 - Info bptm (pid=301952) using 262144 data buffer size 2019. 12. 27 오후 3:42:14 - Info bptm (pid=301952) using 16 data buffers 2019. 12. 27 오후 3:42:14 - Info bptm (pid=301952) USING 262144 data buffer size for FT 2019. 12. 27 오후 3:42:15 - Info bptm (pid=301952) start backup 2019. 12. 27 오후 3:42:18 - Error bpbrm (pid=301944) from client bxddev: ERROR: V-3-20003: Cannot open /dev/sapvg01/lvol6: Permission denied 2019. 12. 27 오후 3:42:28 - end writing; write time: 0:00:16 2019. 12. 27 오후 3:42:30 - Info dbclient (pid=20884) bpbkar waited 133 times for empty buffer, delayed 149 times 2019. 12. 27 오후 3:42:30 - Info dbclient (pid=20884) done. status: 0 2019. 12. 27 오후 3:42:30 - Info bptm (pid=301952) waited for full buffer 1445 times, delayed 11337 times 2019. 12. 27 오후 3:42:32 - Info bptm (pid=301952) EXITING with status 0 <---------- 2019. 12. 27 오후 3:42:32 - Info bpbrm (pid=301944) validating image for client bxddev 2019. 12. 27 오후 3:42:32 - Info dbclient (pid=20884) done. status: 0: the requested operation was successfully completed the requested operation was successfully completed (0)Backup Oracle keep connection status
Hi everyone, Good day, i just want to know, how netbackup progress backup oracle database, because i have issue my job backup details keep connecting, i'm not sure that mean keep connecting, 1 server oracel have many instance, the rest instance success 'm backup.i'm waiting almost 5hour for see the result, in the end, parent job show error code 6 and 2 job child show error 54, so i don't have any idea to solve this.
