Oracle to Netbackup Copilot
Hello, I'm trying to implement Copilot for Oracle. I've set up the SLPs and registered the test instance, but NBU is unable to perform a backup with the error: Unable to perform a manual backup with policy "test". The policy does not have a list of files to back up. The setup: Oracle Linux 7.7, NBU 10.2, StoreOnce 5260 (4.3.6), Catalyst 4.4.0. In short, I'm trying to implement NBU accelerator for faster backups. If there is another way, please refer to the guide. Thank you in advance.Solved829Views0likes6Comments"Rman Backup Error du to "ORA-12269: client uses weak encryption/crypto-checksumming version
When Taking backup for Oracle data base I keep getting the below error: RMAN-00571: ====================================================== RMAN-00569: ============ ERROR MASSAGE STACK FOLLOWS ============= RMAN-00571: ====================================================== RMAN - 12001: Could not open channel ch02 RMAN-10008: Could not create channel context RMAN: unable to connect to target database ORA-12269: client uses weak encryption/crypto-checksumming version861Views0likes0CommentsOracle redirected restore: bug from Netbackup version 8.3 still affecting version 10?
Hi folks. I'm not a Netbackup admin/engineer but a member of the database team trying to understand the issue. Platform and setup: Netbackup ver. 10 Oracle 19c, RAC with Dataguard. Netbackup-managed backup. Multiple databases in RAC Background: We are attempting a redirected restore via RMAN. The source client is the production RAC database, referred to in the RMAN command using the appropriate Netbackup host catalog name (NB_ORA_CLIENT=<DBNAME>_<DBID>). We are aware of the redirected restore procedure and are following it correctly, as far as we know. We would get errors in the restore where RMAN would abort with this message: ORA-19507: failed to retrieve sequential file, handle="bk_dBLAHPROD_u9g217066_s6448_p1_t1142128838", parms="" ORA-27029: skgfrtrv: sbtrestore returned error ORA-19511: non RMAN, but media manager or vendor specific failure, error text: Failed to open backup file for restore. We've enabled debugging information in Netbackup and we saw these messages in the dbclient logs: 00:47:07.541 [765266] <4> sendRequest: sending buf = 1689256954 1689256954 /bk_dBLAHPROD_u9g217066_s6448_p1_t1142128838 00:47:07.541 [765266] <4> sendRequest: Date range: <-s 07/14/23 2:02:34>, <-e 07/14/23 02:02:34> 00:47:07.541 [765266] <4> serverResponse: entering serverResponse. 00:47:07.541 [765266] <4> serverResponse: initial client_read_timeout = <900> 00:47:07.541 [765266] <4> readCommMessages: Entering readCommMessages 00:47:09.541 [765266] <4> serverResponse: read comm file:<00:47:08 INF - Server status = 227> 00:47:09.541 [765266] <16> serverResponse: ERR - server exited with status 227: no entity was found 00:47:09.541 [765266] <16> RestoreFileObjects: ERR - serverResponse() failed 00:47:09.541 [765266] <4> closeApi: entering closeApi. 00:47:09.541 [765266] <4> closeApi: INF - EXIT STATUS 5: the restore failed to recover the requested files 00:47:09.541 [765266] <8> VxBSAGetObject: WRN - RestoreFileObject was not able to find the object. Status: 26 00:47:09.541 [765266] <2> xbsa_ProcessError: INF - entering 00:47:09.541 [765266] <2> xbsa_ProcessError: INF - leaving 00:47:09.541 [765266] <16> xbsa_GetObject: ERR - VxBSAGetObject: Failed with error: There is no copy of the requested object. 00:47:09.541 [765266] <2> xbsa_GetObject: INF - leaving (26) 00:47:09.541 [765266] <16> int_StartJob: ERR - Failed to open backup file for restore. 00:47:09.541 [765266] <2> int_StartJob: INF - leaving 00:47:09.541 [765266] <2> sbtrestore: INF - leaving 00:47:09.541 [765266] <2> sbterror: INF - entering 00:47:09.541 [765266] <2> sbterror: INF - Error=7501: Failed to open backup file for restore. . 00:47:09.541 [765266] <2> sbterror: INF – leaving In researching this, we came across this Veritas KB article (100049320)which describes the same situation that we are experiencing along with similar debug messages, but for a lower version (excerpt below): When attempting an Oracle RAC restore with NetBackup 8.3, the restore fails with an an error 227, stating that the image needed for the restore cannot be found. A bplist of the oracle images will show that the image is actually present. This can occur on RAC clusters that have more than one database. In verifying the conditions relating to this bug, we indeed see the required backup piece via bplist: -rw-rw---- oracle asmadmin 700448768 Jul 14 02:00 /bk_dBLAHPROD_u9g217066_s6448_p1_t1142128838 But, as mentioned in the KB document: NetBackup will look for all possible images needed for the restore across all possible RAC catalog names associated with the client.The failure occurs when the last catalog name does not have any backup images in the requested time range and an error is returned. If you notice in the bplist output above, the timestamp for the backup piece is 02:00, but the time range it's being searched from the Netbackup catalog when doing the restore attempt is (as shown in the debug log): 00:47:07.541 [765266] <4> sendRequest: sending buf = 1689256954 1689256954 /bk_dBLAHPROD_u9g217066_s6448_p1_t1142128838 00:47:07.541 [765266] <4> sendRequest: Date range: <-s 07/14/23 2:02:34>, <-e 07/14/23 02:02:34> ... which obviously would preclude the backup piece it is interested in. Questions: is it possible that we are hitting this bug despite being in a different version than what is mentioned in the KB article? I'm aware that the KB document mentions:This issue has been seen in all present versions - just wanted to confirm it as the KB article doesn't clearly indicate that the bug has been resolved in versions post 8.3. the KB article refers to resorting to an EEB to workaround this issue - do we have any other options? Thank you all in advance.Solved1.5KViews0likes4CommentsProtecting Oracle Standard Edition High Availability (SEHA) with BackupExec v22
Dear all, We have a prospective customer usingOracle Standard Edition High Availability (SEHA) over Oracle Linux 8.6. After checking the Backup Exec v22 SCL file I don't see anything about the support for Oracle SEHA databases, is it supported? Being an Active/Passive cluster option for Oracle Standard, do we support the failover between nodes using our BE Agent for App and Databases from the active node to keep the backup service ready from the node alive? Best regards, Jose.517Views0likes0CommentsNetBackup 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.1.7KViews3likes0CommentsOracle 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.202003:39:20-Infobphdb(pid=120725)INF-inputdatafilefilenumber=00029name=+DATA1/PXCDBL_DBM/82CDF1F23C1993F2E053C443F80AE973/DATAFILE/datex_lob.2830.1001260637 16.mar.202003:39:20-Infobphdb(pid=120725)INF-inputdatafilefilenumber=00024name=+DATA1/PXCDBL_DBM/82CDF1F23C1993F2E053C443F80AE973/DATAFILE/system.2824.1001259231 16.mar.202003:39:21-Infobphdb(pid=120725)INF-inputdatafilefilenumber=00027name=+DATA1/PXCDBL_DBM/82CDF1F23C1993F2E053C443F80AE973/DATAFILE/users.2828.1001259241 16.mar.202007:25:50-Infobphdb(pid=120725)INF-releasedchannel:ch00 16.mar.202007:25:50-Infobphdb(pid=120725)INF-releasedchannel:ch01 16.mar.202007:25:50-Infobphdb(pid=120725)INF-RMAN-00571:=========================================================== 16.mar.202007:25:50-Infobphdb(pid=120725)INF-RMAN-00569:===============ERRORMESSAGESTACKFOLLOWS=============== 16.mar.202007:25:50-Infobphdb(pid=120725)INF-RMAN-00571:=========================================================== 16.mar.202007:25:50-Infobphdb(pid=120725)INF-RMAN-03009:failureofbackupcommandonch00channelat03/16/202007:25:33 16.mar.202007:25:50-Infobphdb(pid=120725)INF-ORA-27192:skgfcls:sbtclose2returnederror-failedtoclosefile 16.mar.202007:25:50-Infobphdb(pid=120725)INF-ORA-19511:nonRMAN,butmediamanagerorvendorspecificfailure,errortext: 16.mar.202007:25:50-Infobphdb(pid=120725)INF-Failedtoprocessbackupfile<bk_dPXCDBL_un2ur6tn8_s29410_p1_t1035171560> 16.mar.202007:25:50-Infobphdb(pid=120725)INF-ORA-19502:writeerroronfile"bk_dPXCDBL_un2ur6tn8_s29410_p1_t1035171560",blocknumber1(blocksize=8192) 16.mar.202007:25:50-Infobphdb(pid=120725)INF-ORA-27030:skgfwrt:sbtwrite2returnederror 16.mar.202007:25:50-Infobphdb(pid=120725)INF-ORA-19511:nonRMAN,butmediamanage 16.mar.202007:25:50-Infobphdb(pid=120725)INF-RecoveryManagercomplete. 16.mar.202007:25:55-Infobphdb(pid=120725)INF-EndofRecoveryManageroutput. 16.mar.202007:25:55-Infobphdb(pid=120725)INF-EndOracleRecoveryManager. Here is from job details of the failing job: 16.mar.202003:39:35-Infobptm(pid=233514)startbackup 16.mar.202003:40:38-Infobptm(pid=233514)backupchildprocessispid235121 16.mar.202003:40:38-beginwriting 16.mar.202006:40:39-Errorbpbrm(pid=233505)socketreadfailed:errno=62-Timerexpired 16.mar.202006:40:41-Errorbptm(pid=233514)mediamanagerterminatedbyparentprocess Obviousley there is a timeout involved here, but where? The backup job shows always timeout after exactly 3 hrs.1.5KViews0likes3CommentsOracle RMAN job starts another job (copied)
Hi, We have an Oracle job (Archive log, Full) set with an RMAN script which works fine and now we'd like to have another copy of this job in another storage. So I simply created a job from the original one and changed the storage destination to the new place. So, the Original job is : policy name: job1, RMAN script : mysc.sh, storage: site1_stg I create a copy : Second job : policy name : job2, RMAN script : mysc.sh, storage: site2_stg What happens is strange! When I run Job1, Job1 is also automatically launched and run. I looked into the script and there is nothing related to the job policy name which may cause this. I also used a different script (with the same content of course) but the result was the same. As this is not the case in other jobs I doubt the script or Oracle Linux OS or Netbackup settings on the OS should be the cause. Any help would be appreciated. ThanksSolved3.2KViews0likes12CommentsReplication 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..573Views0likes1CommentError 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-Infonbjm(pid=13885)startingbackupjob(jobid=23683)forclientbxddev,policybxddev_SAP,scheduleDefault-Application-Backup 2019.12.27오후3:42:03-Infonbjm(pid=13885)requestingSTANDARD_RESOURCEresourcesfromRBforbackupjob(jobid=23683,requestid:{FE1420F4-2873-11EA-87DC-C738CC064B28}) 2019.12.27오후3:42:03-requestingresourcestu_adv_hkpbma2 2019.12.27오후3:42:03-requestingresourcehkpbaka1.NBU_CLIENT.MAXJOBS.bxddev 2019.12.27오후3:42:03-requestingresourcehkpbaka1.NBU_POLICY.MAXJOBS.bxddev_SAP 2019.12.27오후3:42:04-grantedresourcehkpbaka1.NBU_CLIENT.MAXJOBS.bxddev 2019.12.27오후3:42:04-grantedresourcehkpbaka1.NBU_POLICY.MAXJOBS.bxddev_SAP 2019.12.27오후3:42:04-grantedresourceMediaID=@aaaab;DiskVolume=/advanceddisk/dp1/advol;DiskPool=dp_adv_hkpbma2;Path=/advanceddisk/dp1/advol;StorageServer=hkpbma2;MediaServer=hkpbma2 2019.12.27오후3:42:04-grantedresourcestu_adv_hkpbma2 2019.12.27오후3:42:04-grantedresourceTRANSPORT 2019.12.27오후3:42:04-estimated0kbytesneeded 2019.12.27오후3:42:04-Infonbjm(pid=13885)startedbackup(backupid=bxddev_1577428924)jobforclientbxddev,policybxddev_SAP,scheduleDefault-Application-Backuponstorageunitstu_adv_hkpbma2 2019.12.27오후3:42:04-startedprocessbpbrm(pid=301944) 2019.12.27오후3:42:05-connecting 2019.12.27오후3:42:08-connected;connecttime:0:00:00 2019.12.27오후3:42:09-Infobpbrm(pid=301944)bxddevisthehosttobackupdatafrom 2019.12.27오후3:42:09-Infobpbrm(pid=301944)readingfilelistforclient 2019.12.27오후3:42:10-Infobpbrm(pid=301944)listeningforclientconnection 2019.12.27오후3:42:11-OpeningFibreTransportconnection,BackupId:bxddev_1577428924 2019.12.27오후3:42:12-Infobpbrm(pid=301944)INF-Clientreadtimeout=3600 2019.12.27오후3:42:12-Infobpbrm(pid=301944)acceptedconnectionfromclient 2019.12.27오후3:42:12-Infobpbrm(pid=301944)startbpbkaronclient 2019.12.27오후3:42:12-beginwriting 2019.12.27오후3:42:13-Infodbclient(pid=20932)Backupstarted 2019.12.27오후3:42:13-Infodbclient(pid=20884)Backupstarted 2019.12.27오후3:42:13-Infobpbrm(pid=301944)bptmpid:301952 2019.12.27오후3:42:13-Infobptm(pid=301952)start 2019.12.27오후3:42:14-Infobptm(pid=301952)using262144databuffersize 2019.12.27오후3:42:14-Infobptm(pid=301952)using16databuffers 2019.12.27오후3:42:14-Infobptm(pid=301952)USING262144databuffersizeforFT 2019.12.27오후3:42:15-Infobptm(pid=301952)startbackup 2019.12.27오후3:42:18-Errorbpbrm(pid=301944)fromclientbxddev:ERROR:V-3-20003:Cannotopen/dev/sapvg01/lvol6:Permissiondenied 2019.12.27오후3:42:28-endwriting;writetime:0:00:16 2019.12.27오후3:42:30-Infodbclient(pid=20884)bpbkarwaited133timesforemptybuffer,delayed149times 2019.12.27오후3:42:30-Infodbclient(pid=20884)done.status:0 2019.12.27오후3:42:30-Infobptm(pid=301952)waitedforfullbuffer1445times,delayed11337times 2019.12.27오후3:42:32-Infobptm(pid=301952)EXITINGwithstatus0<---------- 2019.12.27오후3:42:32-Infobpbrm(pid=301944)validatingimageforclientbxddev 2019.12.27오후3:42:32-Infodbclient(pid=20884)done.status:0:therequestedoperationwassuccessfullycompleted therequestedoperationwassuccessfullycompleted (0)995Views0likes1Comment