Protecting 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.
Oracle Backup failure following upgrade from 15 to 20 - ORA 19511
I upgraded our backup exec server from 15 through to 20.3, everything upgraded without any issues and all of the backups have been successful apart from 1 of our Oracle servers. We have another Oracle server with an almost idential set up which is working fine but this one is getting the below errors. It failed on Friday prior to me upgrading the agent but following an upgrade to the agent and reboot the issue still persists just the same. Version of Oracle is 12C Error in Job Log: Final error: 0xe0001405 - Unknown CORBA exception. Unable to contact the Backup Exec server. Confirm that the Backup Exec Job Engine service is running on the Backup Exec server. Final error category: Resource Errors Error from Debug monitor 2268 BEREMOTE 3588 10/02/2019 17:47:26 8060 [dbsb\dbsbora] - CDbsbOra::processMessage: BEError(0xe0001405) Unknown CORBA exception. Unable to contact the Backup Exec server. Confirm that the Backup Exec Job Engine service is running on the Backup Exec server. 2259 BEREMOTE 3588 10/02/2019 17:47:25 8060 2019-02-10T17:47:26.134 [dbsb\dbsbora] - CDbsbOra::processMessage: RMAN-03002: failure of backup plus archivelog command at 2260 BEREMOTE 3588 10/02/2019 17:47:26 8060 [dbsb\dbsbora] - end of linebuf 2261 BEREMOTE 3588 10/02/2019 17:47:26 8060 [dbsb\dbsbora] - CDbsbOra::processMessage: ORA-19506: failed to create sequential file, name="BE_7etpi21b_1_1", parms="" 2262 BEREMOTE 3588 10/02/2019 17:47:26 8060 [dbsb\dbsbora] - end of linebuf 2263 BEREMOTE 3588 10/02/2019 17:47:26 8060 [dbsb\dbsbora] - CDbsbOra::processMessage: ORA-27028: skgfqcre: sbtbackup returned error 2264 BEREMOTE 3588 10/02/2019 17:47:26 8060 [dbsb\dbsbora] - end of linebuf 2265 BEREMOTE 3588 10/02/2019 17:47:26 8060 [dbsb\dbsbora] - CDbsbOra::processMessage: ORA-19511: non RMAN, but media manager or vendor specific failure, error text: 2266 BEREMOTE 3588 10/02/2019 17:47:26 8060 [dbsb\dbsbora] - end of linebuf 2267 BEREMOTE 3588 10/02/2019 17:47:26 8060 [dbsb\dbsbora] - CDbsbOra::processMessage: Setting job level error from script output to (0xe0001405) I've been trying to access any related Veritas issue but there seems to be an issue with the site as every link i've followed from searches has come back saying that it no longer exists! Any help with solving this one would bemost appreciated.
agent stopped working when backup oracle database
i have backup exec 2014 i trying to backup oracle database installed in linux operating system with version 7, i can backup datafile from the operating system with no problem but when i try to backup oracle database the agent stopped the service in linux server automaticly and the communication disconnect between the backup exec and the linux server i collect the log file for the problem but i didnt found the solution for this problem can you help me to fix this problem 7dea07c0 Sun Dec 16 07:44:42 2018 : Requested no generation of log file 7dea07c0 Sun Dec 16 07:44:42 2018 : No configuration file specified. Using default. 7dea07c0 Sun Dec 16 07:44:42 2018 : Log to console: enabled 7dea07c0 Sun Dec 16 07:44:42 2018 : Successfully set the supplementary groups of the process 7dea07c0 Sun Dec 16 07:44:42 2018 : Initialized locks for SSL callbacks 7dea07c0 Sun Dec 16 07:44:42 2018 : DoSnapshotReconcile: Attempting Snapshot Reconcile ... 7dea07c0 Sun Dec 16 07:44:42 2018 : DoSnapshotReconcile: This installation does not supports snapshots. Skipping the Reconcile Operation ... 7dea07c0 Sun Dec 16 07:44:42 2018 : Starting NDMP processor 7dea07c0 Sun Dec 16 07:44:42 2018 : NDMPDMainThreadFunc spawned: grpid=1, tid=1955358464 748c6700 Sun Dec 16 07:44:42 2018 : FS_InitFileSys 748c6700 Sun Dec 16 07:44:42 2018 : libbedsnt5.so could not be loaded: 748c6700 Sun Dec 16 07:44:42 2018 : libbedssql2.so could not be loaded: 748c6700 Sun Dec 16 07:44:42 2018 : libbedsxchg.so could not be loaded: 748c6700 Sun Dec 16 07:44:42 2018 : libbedsxese.so could not be loaded: 748c6700 Sun Dec 16 07:44:42 2018 : libbedsmbox.so could not be loaded: 748c6700 Sun Dec 16 07:44:42 2018 : libbedspush.so could not be loaded: 748c6700 Sun Dec 16 07:44:42 2018 : libbedsnote.so could not be loaded: 748c6700 Sun Dec 16 07:44:42 2018 : libbedsmdoc.so could not be loaded: 748c6700 Sun Dec 16 07:44:42 2018 : libbedssps2.so could not be loaded: 748c6700 Sun Dec 16 07:44:42 2018 : libbedssps3.so could not be loaded: 748c6700 Sun Dec 16 07:44:42 2018 : libbedsupfs.so could not be loaded: 748c6700 Sun Dec 16 07:44:42 2018 : libbedsshadow.so could not be loaded: 748c6700 Sun Dec 16 07:44:42 2018 : libbedsoffhost.so could not be loaded: 748c6700 Sun Dec 16 07:44:42 2018 : loaded libbedsvx.so 748c6700 Sun Dec 16 07:44:42 2018 + engine/fsys/shared/initfsys.cpp (359): 748c6700 Sun Dec 16 07:44:42 2018 | libbedsvx.so loaded at index 22 748c6700 Sun Dec 16 07:44:42 2018 : loaded libbedsrman.so 748c6700 Sun Dec 16 07:44:42 2018 + engine/fsys/shared/initfsys.cpp (359): 748c6700 Sun Dec 16 07:44:42 2018 | libbedsrman.so loaded at index 14 748c6700 Sun Dec 16 07:44:42 2018 : loaded libbedssms.so 748c6700 Sun Dec 16 07:44:42 2018 + engine/fsys/shared/initfsys.cpp (359): 748c6700 Sun Dec 16 07:44:42 2018 | libbedssms.so loaded at index 1 748c6700 Sun Dec 16 07:44:42 2018 + engine/fsys/shared/initfsys.cpp (359): 748c6700 Sun Dec 16 07:44:42 2018 | libbedssms.so loaded at index 2 748c6700 Sun Dec 16 07:44:42 2018 + engine/fsys/shared/initfsys.cpp (359): 748c6700 Sun Dec 16 07:44:42 2018 | libbedssms.so loaded at index 3 748c6700 Sun Dec 16 07:44:42 2018 + engine/fsys/shared/initfsys.cpp (359): 748c6700 Sun Dec 16 07:44:42 2018 | libbedssms.so loaded at index 4 748c6700 Sun Dec 16 07:44:42 2018 : loaded libbedssmsp.so 748c6700 Sun Dec 16 07:44:42 2018 + engine/fsys/shared/initfsys.cpp (359): 748c6700 Sun Dec 16 07:44:42 2018 | libbedssmsp.so loaded at index 11 748c6700 Sun Dec 16 07:44:42 2018 : libbedsra.so could not be loaded: 748c6700 Sun Dec 16 07:44:42 2018 : libbedsdb2.so could not be loaded: 748c6700 Sun Dec 16 07:44:42 2018 : loaded libbedsedir.so 748c6700 Sun Dec 16 07:44:42 2018 + engine/fsys/shared/initfsys.cpp (359): 748c6700 Sun Dec 16 07:44:42 2018 | libbedsedir.so loaded at index 34 748c6700 Sun Dec 16 07:44:42 2018 : libbedsvmesx.so could not be loaded: 748c6700 Sun Dec 16 07:44:42 2018 : Initializing FSs 748c6700 Sun Dec 16 07:44:42 2018 : FS 1 failed to initialize: 0xE000FE46 748c6700 Sun Dec 16 07:44:42 2018 : Function called: RMAN_InitFileSys 748c6700 Sun Dec 16 07:44:42 2018 : Using 'UTF-8' Encoding. 748c6700 Sun Dec 16 07:44:42 2018 : Using vfm path /opt/VRTSralus/VRTSvxms from config. 748c6700 Sun Dec 16 07:44:42 2018 : Sucessfully set VFM_PRIVATE_ROOT env to /opt/VRTSralus/VRTSvxms. 748c6700 Sun Dec 16 07:44:42 2018 : VFM_PRIVATE_ROOT was set with value /opt/VRTSralus/VRTSvxms 748c6700 Sun Dec 16 07:44:42 2018 : VXMS Initialization OK. 748c6700 Sun Dec 16 07:44:42 2018 : Detected Mounted Filesystem: type <sysfs> mounted at </sys> 748c6700 Sun Dec 16 07:44:42 2018 : Detected Mounted Filesystem: type <proc> mounted at </proc> 748c6700 Sun Dec 16 07:44:42 2018 : Detected Mounted Filesystem: type <devtmpfs> mounted at </dev> 748c6700 Sun Dec 16 07:44:42 2018 : Detected Mounted Filesystem: type <securityfs> mounted at </sys/kernel/security> 748c6700 Sun Dec 16 07:44:42 2018 : Detected Mounted Filesystem: type <tmpfs> mounted at </dev/shm> 748c6700 Sun Dec 16 07:44:42 2018 : Detected Mounted Filesystem: type <devpts> mounted at </dev/pts> 748c6700 Sun Dec 16 07:44:42 2018 : Detected Mounted Filesystem: type <tmpfs> mounted at </run> 748c6700 Sun Dec 16 07:44:42 2018 : Detected Mounted Filesystem: type <tmpfs> mounted at </sys/fs/cgroup> 748c6700 Sun Dec 16 07:44:42 2018 : Detected Mounted Filesystem: type <cgroup> mounted at </sys/fs/cgroup/systemd> 748c6700 Sun Dec 16 07:44:42 2018 : Detected Mounted Filesystem: type <pstore> mounted at </sys/fs/pstore> 748c6700 Sun Dec 16 07:44:42 2018 : Detected Mounted Filesystem: type <cgroup> mounted at </sys/fs/cgroup/net_cls,net_prio> 748c6700 Sun Dec 16 07:44:42 2018 : Detected Mounted Filesystem: type <cgroup> mounted at </sys/fs/cgroup/cpu,cpuacct> 748c6700 Sun Dec 16 07:44:42 2018 : Detected Mounted Filesystem: type <cgroup> mounted at </sys/fs/cgroup/blkio> 748c6700 Sun Dec 16 07:44:42 2018 : Detected Mounted Filesystem: type <cgroup> mounted at </sys/fs/cgroup/devices> 748c6700 Sun Dec 16 07:44:42 2018 : Detected Mounted Filesystem: type <cgroup> mounted at </sys/fs/cgroup/hugetlb> 748c6700 Sun Dec 16 07:44:42 2018 : Detected Mounted Filesystem: type <cgroup> mounted at </sys/fs/cgroup/cpuset> 748c6700 Sun Dec 16 07:44:42 2018 : Detected Mounted Filesystem: type <cgroup> mounted at </sys/fs/cgroup/memory> 748c6700 Sun Dec 16 07:44:42 2018 : Detected Mounted Filesystem: type <cgroup> mounted at </sys/fs/cgroup/perf_event> 748c6700 Sun Dec 16 07:44:42 2018 : Detected Mounted Filesystem: type <cgroup> mounted at </sys/fs/cgroup/freezer> 748c6700 Sun Dec 16 07:44:42 2018 : Detected Mounted Filesystem: type <configfs> mounted at </sys/kernel/config> 748c6700 Sun Dec 16 07:44:42 2018 : Detected Mounted Filesystem: type <xfs> mounted at </> 748c6700 Sun Dec 16 07:44:42 2018 : Detected Mounted Filesystem: type <selinuxfs> mounted at </sys/fs/selinux> 748c6700 Sun Dec 16 07:44:42 2018 : Detected Mounted Filesystem: type <autofs> mounted at </proc/sys/fs/binfmt_misc> 748c6700 Sun Dec 16 07:44:42 2018 : Detected Mounted Filesystem: type <debugfs> mounted at </sys/kernel/debug> 748c6700 Sun Dec 16 07:44:42 2018 : Detected Mounted Filesystem: type <mqueue> mounted at </dev/mqueue> 748c6700 Sun Dec 16 07:44:42 2018 : Detected Mounted Filesystem: type <hugetlbfs> mounted at </dev/hugepages> 748c6700 Sun Dec 16 07:44:42 2018 : Detected Mounted Filesystem: type <binfmt_misc> mounted at </proc/sys/fs/binfmt_misc> 748c6700 Sun Dec 16 07:44:42 2018 : Detected Mounted Filesystem: type <ext3> mounted at </boot> 748c6700 Sun Dec 16 07:44:42 2018 : Detected Mounted Filesystem: type <rpc_pipefs> mounted at </var/lib/nfs/rpc_pipefs> 748c6700 Sun Dec 16 07:44:42 2018 : Detected Mounted Filesystem: type <tmpfs> mounted at </run/user/54321> 748c6700 Sun Dec 16 07:44:42 2018 : Detected Mounted Filesystem: type <fusectl> mounted at </sys/fs/fuse/connections> 748c6700 Sun Dec 16 07:44:42 2018 : Detected Mounted Filesystem: type <nfs4> mounted at </backup> 748c6700 Sun Dec 16 07:44:42 2018 : Detected Mounted Filesystem: type <tmpfs> mounted at </run/user/0> 748c6700 Sun Dec 16 07:44:42 2018 : INFORMATIONAL: Zero value found for 'DisableRMAL' from ralus.cfg, allowing RMAL to initialize 748c6700 Sun Dec 16 07:44:42 2018 : Successfully resolved the "ndmp" service to port: 10000 (host order) 748c6700 Sun Dec 16 07:44:42 2018 : BETCPListener successfully installed a signal handler for SIGTERM 748c6700 Sun Dec 16 07:44:42 2018 : BETCPListener::BETCPListener: This system appears to be a Dual IP system 748c6700 Sun Dec 16 07:44:42 2018 : BETCPListener::BETCPListener: Successfully set the IPV6_V6ONLY option, this listener may behave as Dual Stack listener 748c6700 Sun Dec 16 07:44:42 2018 : BETCPListener::Bind: Could not bind to port 10000 on IPv6, An error occurred during a socket bind operation: Error Code: 98, System Error Message: Address already in use 748c6700 Sun Dec 16 07:44:42 2018 : BETCPListener::Bind: Could not bind to port 10000 on IPv4, An error occurred during a socket bind operation: Error Code: 98, System Error Message: Address already in use 748c6700 Sun Dec 16 07:44:42 2018 : Could not start NDMP Listener on port 10000: An error occurred during a socket creation operation: Error Code: 98, System Error Message: Address already in use 748c6700 Sun Dec 16 07:44:42 2018 : ndmpRun: exiting [root@portal-test-11g bin]# 7dea07c0 Sun Dec 16 07:44:47 2018 : Stopping remote agent due to explicitly failed initialization 7dea07c0 Sun Dec 16 07:44:52 2018 : Startup failure detected 7dea07c0 Sun Dec 16 07:44:52 2018 : Remote agent exiting, cancelling 3 joinable threads 6933c700 Sun Dec 16 07:44:52 2018 : time to exit thread 68b3b700 Sun Dec 16 07:44:52 2018 : NrdsAdvertiserThread: exiting 63fff700 Sun Dec 16 07:44:57 2018 : NrdsAdvertiserThread: exiting 7dea07c0 Sun Dec 16 07:44:57 2018 : unloading libbedssms.so 7dea07c0 Sun Dec 16 07:44:57 2018 : unloading libbedssmsp.so 7dea07c0 Sun Dec 16 07:44:57 2018 : unloading libbedsrman.so 7dea07c0 Sun Dec 16 07:44:57 2018 : unloading libbedsvx.so 7dea07c0 Sun Dec 16 07:44:57 2018 : unloading libbedsedir.soSFHA Solutions 6.2: Symantec Storage plug-in for OEM 12c
Symantec Storage plug-in for OEM12c enables you to view and manage the Storage Foundation and VCS objects through the Oracle Enterprise Manager 12c (OEM), which has a graphical interface. It works with the Symantec Storage Foundation and High Availability 6.2 product suite. The Symantec Storage plug-in allows you to: SmartIO: manage Oracle database objects using SmartIO. Snapshot: create point-in-time copies (Storage Checkpoint, Database FlashSnap, Space-optimized Snapshot, and FileSnap) of Oracle databases using SFDB features Cluster: vew cluster-specific information. You can get the plug-in by downloading the attached file. For more information about installing and using the plug-in, download the attached Application Note. Terms of use for this information are found in Legal Notices.
How to check connection for backint?
Hello everybody, I have a landscape with SAP server separated by media server. I purchased SAP agent, installed it and copied to folder where SAP is installed. If I launch the backup job from DB13, it fails when executing the BACKINT program. The command line is this: backint.exe -u SID -f backup -i E:\oracle\SID\sapbackup\.bekiiuqx.lst -t file -p E:\usr\sap\SID\SYS\exe\nuc\NTAMD64\biparam.ini -c My content of biparam.ini is: [General] Server= SERVER-IP Job Name=Backup SAP side - [Backup] Backup Catalog=off Job Template=DEFAULT and this is located in the path specified before, in initSID.sap with the parameter "util_par_file" The return error code is 2, and it says me: "Unable to connect to Backup Exec server: \\SERVER-IP" I checkedthisdocument, and all that point are checked. So, how can I check the connection for backint and find the error? Thank youHow to configure biparam.ini for SAP
Hi all, I'm using Backup Exec 2010 to perform backup of my SAP installation. The media server and the SAP server are separated. I got the things working (from SAP I can submit database job), but I can't configure parameters of the backup jobs properly. Because I didn't find the config file installed (biparam.ini), i googled that to search the options and checked the manual, but I can't figure how to set thing like backup method, priority and so on, because in the DBA-initiated job settings there are no those. Also, I tried to create a policy with name "DEFAULT", but I can't see that in the job setup. Can anyone help me please? Thank you in advance Stefano
