Scheduled Backups on OEM

I suspect this is a silly question, but, I've always done backups using scripts from the OS. I recently set up one using OEM and it worked. I have two questions:
1. Is there a backup schedule page that shows the next time it will run?
2. How do I delete this backup job if I should choose to use OS scripts?
Thanks,
John

1.<< Is there a backup schedule page that shows the next time it will run? >>
--Log into the Grid control
--Click on the Jobs tab on the top right hand side
--select the Job activity subtab on the Jobs home page.
-- select the status value to "Active" and hit the Go button .. It should list all the
backup jobs which are running currently and the ones which are scheduled.
2. How do I delete this backup job if I should choose to use OS scripts?
-- Under the Job activity page, select the job you want to stop/delete and hit the
stop/delete button based on what you want to do.

Similar Messages

Scheduled backups on oem disappear after hardware crash

I am using OEM12c 12.1.0.3 to manage 12 databases (11.2.0.3 and 11.2.0.4) on several suse11 linux machines.
We schedule the backups thru oem (availability->backup&recovery->schedule backups)
Last friday the hardware crashed, and once we got everything backup and running we noticed all of the scheduled backups
were missing and we had to reschedule everything. Has anyone seen this behavior before or know how to prevent the schedules from disappearing,.
It's a pain to have to reschedule everything.

What had to be restored? OMS/Repository? Or target databases?
If you look in EM at Enterprise -> Jobs -> Job Activity, be sure to go to advanced search, look for all Scheduled and see if they're there?
If they were a group backup, might be scheduled as a Deployment Procedure instead.

Error when scheduling backup job in OEM

We have Oracle 11.2 RAC on Redhat Linux. I was creating an customized backup job and get the errorsORA-01476: divisor is equal to zero
ORA-06512: at "SYSMAN.MGMT_JOB_ENGINE", line 7544
ORA-06512: at "SYSMAN.MGMT_JOB_ENGINE", line 7699
ORA-06512: at "SYSMAN.MGMT_JOB_ENGINE", line 8211
ORA-06512: at "SYSMAN.MGMT_JOB_ENGINE", line 8342
ORA-06512: at "SYSMAN.MGMT_JOB_ENGINE", line 8503
ORA-06512: at "SYSMAN.MGMT_JOB_ENGINE", line 8570
ORA-06512: at "SYSMAN.MGMT_JOBS", line 273
ORA-06512: at "SYSMAN.MGMT_JOBS", line 86
ORA-06512: at line 1 The backup command is created by OEM as backup incremental level 0 cumulative device type disk filesperset = 5 tag '%TAG' section size 500 M database;
backup device type disk filesperset = 500 tag '%TAG' section size 500 M archivelog all not backed up;
allocate channel for maintenance type disk;
delete noprompt obsolete device type disk;
release channel; Actually using other ommand also get the same error.
What is wrong? I scheduled backup job before on this server and it worked.

This may be due to that the schedule frequecy is not set. Make sure Frequency Type and Repeat Every boxes get filled properly.

Schedule Hot backup via OEM

Hello all,
We have a realtively small system running Oracle 10G on Windows 2003 O/S. I've scheduled a full offiline (cold) backup of the whole db to run once weekly via OEM. Every night we run a script to do a 'logical' backup by EXPORTing the 2 main schemas in the DB out to .DMP files. However this now may not be enough to satisfy DB recovery requirements.
Is there an easy way to schedule a 'Hot' backup via OEM, that could replace the EXPORT scripts mentioned above, or would we have to write an RMAN script to do this ?? The requirement is really to allow the database to be updateable whilst any daily backup is running. I realise that the DB needs to be in ARCHIVELOG mode for anything like this to work.
Any advice would be greatly appreciated.
Thanks,
Shaun.

hi,
on the OEM main page, click on targets, you should see your databse there. click on the database and then on the maintenance tab.
from here you can schedule jobs and you have the option to schedule a online rman backup of your database. However, to do an online backup your database needs to have archiving turned on. Is this the case as you currently carry out offline backups which might indicate that archiving is turned off.
regards
Alan
Edited by: alanm on Sep 5, 2008 11:47 AM

Anyone using OEM for scheduling backups?

I'd like to see a poll for the number of users using OEM for taking database backups. Had some interesting conversations with some colleagues via social media and it seems like some DBAs don't trust OEM for their backups even though the feature works IMO.
Are you using OEM to do backups?
Edited by: DBA on May 3, 2012 1:02 PM

I have 91 scheduled recurring backup jobs running through OEM 12c BP1. They work quite well. I've only noticed a few problems and nitpicks:
1) Occasionally, for unknown reasons, a backup job against a newly-added database target will fail stating that the backup cannot be run since the database is closed. The database is not closed, it's up and running fine. Changing the backup job to run using SYS as SYSDBA credentials resolves this problem.
2) Identification of failed backups is not as customizable as I would like. For example, if I have a full "backup database plus archivelog" running, and during the course of that backup an archivelog backup runs and deletes archived logs, OEM will report that the backup job has failed since RMAN throws an error about not being able to backup an archivelog it expected to find. I dealt with this by adding SKIP INACCESSIBLE to the backup statement. I'm not totally comfortable about that but I monitor for offline datafiles so I consider this only a minimal risk. Our custom backup scripts used to catch this warning and ignore it.
3) It's really annoying that, after creating a backup job through the target Availability -> Schedule Backup tool, I cannot then run a 'Create Like' against that backup job to create a nearly identical one against a different database target. You have to schedule each of them from the Schedule Backup tool. Clicky clicky clicky clicky.
4) A backup job created through the 'Schedule Backup' tool has a job type of 'Database Backup', therefore when the job fails a high-availability incident is created, so you can configure incident rules to receive notification of this event. This is good. Unfortunately a backup job created from the Jobs page has a job type of 'RMAN Script' does NOT create an incident on job failure out of the box. I've had difficulty configuring incident rules to catch failures for RMAN Script job types. This is not good.
5) The repeating schedule options for jobs are limited compared even to something like cron. I can schedule a job for a day of the week, or a day of the month, but cannot easily schedule a job for "the first Tuesday of each month". This can be worked around.
6) After creating and submitting a backup job through the Schedule Backup tool, you cannot edit the RMAN script without recreating the job. You can only edit the RMAN script before submitting the job. I deal with this by having my backups run stored scripts in the recovery catalog, and make the changes there if I need to change something.
7) It is very annoying that if I 'stop' a repeating job (instead of suspend), there is no way to resume that job. It has to be recreated. This is my own user error -- I just don't click the stop button. Not OEM's fault but I'd rather not even have that button.
8) No ability to sequence jobs. You can sequence steps within a job, but then the entire job succeeds or fails as a unit. If you want to back up database A then immediately back up database B afterwards, you have to create a multi-task job. The multi-task job has the same problem as item #4 above such that it does not create a "backup failed" incident when the backup fails.
Even with all of these gripes, I am quite pleased with the backups I have running through OEM.

Which are the required roles/privs for viewing all scheduler jobs in OEM?

Platform: Oracle 11.1.0.6 Enterprise Edition (64) Windows 2008 R2 Server
- I've created a new Admin user in "OEM>Setup>Adminstrators>Create"
- I checked the user in "OEM>Server>Users":
CREATE USER "SA_ADMIN"
PROFILE "DEFAULT"
INDENTIFIED BY "saadminsa"
DEFAULT TABLESPACE "SYSAUX"
TEMPORARY TABLESPACE "TEMP"
ACCOUNT UNLOCK;
GRANT SELECT ANY DICTIONARY TO "SA_ADMIN";
GRANT "MGMT_USER" TO "SA_ADMIN"
- "SA_ADMIN" was granted only the permissions above.
- I can log in OEM as "SA_ADMIN"
- I can see OEM backup jobs and the history
- But I cannot see any "scheduler" jobs in "OEM>Server>Jobs"
- I get a lists of the jobs in "OEM>Scheduler Central" but I cannot display any more information of "scheduler jobs"
- I logged off from OEM
- I granted SCHEDULER_ADMIN role to "SA_ADMIN"
GRANT SCHEDULER_ADMIN TO "SA_ADMIN";
- I logged back in OEM as "SA_ADMIN
- I can now see some scheduler jobs, but not all of the jobs, I still cannot see any of the new jobs I created logged in OEM as SYS.
Which are the required roles/privs for viewing all scheduler jobs in OEM?

if you grant "SYSDBA" to the new Admin user then you can see the "scheduler" jobs.
GRANT SYSDBA TO "SA_ADMIN";
I wanted to grant "read" access in OEM for the new user.
This behaviour is strange.
Without the "SYSDBA" role the new user can see the OEM backup jobs that were create in as SYS, but it cannot see the "scheduler" jobs.

How to edit RMAN schedule script on OEM?

I created a schedule backup script on RMAN using OEM. But I didin't include the log error clause in the script. But now I can't find in OEM where can I change the script. I found only where the script is showed.
Someone could help me?

You need to create new backup schedule with corrected script and remove the old one.

Need help. Scheduled backup is killing the listener

I'm not sure what is going on. I scheduled a backup through the OEM and when the job kicked off, it shut down the listner, or killed it. The problem is that our startup/shutdown routines use the listener as a dependency, so when the listener dies, other Oracle servers also are shut down.
This server is in NOARCHIVELOG mode, so the backup has to happen offline, which I assumed meant simply shutting the database down, backing up and reopening it.
The main problem is that I can't seem to find the scheduled job, so everytime I restart the server, the job attempts to start again and kills the listener. I've done some searching, but I can't find the exact query/script to kill any scheduled backup job.

Is there software I can use to repair the boot record on my external HD?

How to view scheduled backups

When using the schedule backup wizard in maintenance and you create a recurring backup job. What tables does oem use to store the job definition and schedule. I cannot use the job library since it does not display backup type jobs.

Select is Manage Current Backups from Maintenance

ISE 1.2 scheduled backup not working

Hi all,
I have clean installation of ISE 1.2 (HA) Patch1 and tried to create scheduled backup from GUI. I can create it without problems but it does not start.
I have created manual backups which are working fine, so there is no problem with FTP server. I have checked CLI and there is no kron job in CLI as I would expect it from version 1.1.x.
Any idea or do you think its TAC case?
Thanks,
ML

There is known defect whereby if the timezone has more than 3 characters. Could you please check the timezone on the ISE CLI with "show timezone"
CSCui44324 ISE 1.2 scheduled backup can't be configured
Symptom:
Backup task can't be configured in ISE 1.2 UI
Conditions:
Install/Upgrade ISE to v.1.2
Login via GUI and try configure backup task under "Administration -> System -> Backup and restore".
ISE timezone shortname is more than 3 characters (e.g. CEST).
Workaround:
N/A
Further Problem Description:
Looks like patch 2 would fix this defect.
~BR
Jatin Katyal
**Do rate helpful posts**

Scheduling backups when wake from sleep is password protected

i'm just wondering if it's possible to wake a mac from sleep (at say 0200) in order to run a backup script, if a password is required to wake from sleep/screensaver ?
what's happening at the moment is that the computer wakes, the script starts to run, but then after about 1 minute, because the authentication dialog is not processed, it goes back to sleep, so interrupting the script
i had the same problem trying to sftp into a mac after using wake-on-lan to wake it from sleep remotely. i can successfully make the sftp connection and start file transfers, however it quickly goes back to sleep (as the authentication dialog is unanswered)
so does anyone know of a way to keep the security of require-password-from-sleep, as well as allowing useful things like running scheduled backup scripts ?
Powerbook Mac OS X (10.4.7)

I also had this problem and I worked with Apple Care. They are aware of the problem and apparently are working on a fix. The only way around this for now is to uncheck the option requiring a password to wake from sleep/screen saver in System Preferences/Security. I was amazed to find this problem, I can't believe Apple let this one past them because surely all those folks who use Backup with .Mac accounts have experienced this problem or don't realize their backup isn't happening. So, hopefully this is one item that will be fixed at some point.

App to schedule backups to WebDAV?

Looking for an app, please, to schedule backups to a WebDAV on a leased CPanel server.
Saw "Twin" in App Store but looking for something less.

"Twin" works great since it offers local encryption and compression as well.
We had quite a long list of apps tested for our offsite backup to CloudSafe (http://www.cloudsafe.com), but no other solution worked reliable.
If you want to switch to an Amazon S3 backup you could use ARQ (http://www.haystacksoftware.com/arq/)

EM Fails. Will scheduled backups be affected?

Hello.
I had a problem to our EM DBControl. It keeps on failing / or dying (issuing command emctl status dbconsole shows EM is not running). So i tried to drop all the repositories and recreate it. (+emca -create dbcontrol db -repos recreate -cluster+) Unfortunately, I wasn't able to complete it because it put our database to quiesce so i just kill the emca and unquiesce the DB. I planned to schedule it on low transactions. Now weird thing is when i try to use EM again the following day, its woking and its not failing anymore.
My major concern now is I used EM DBControl to facilitate backup and recovery. If ever EM will fail again, does the scheduled backup will also fail?
If during the process of backup the EM fails, will the datafiles,archives,control (whole DB) be corrupted?
Well I know that when I try prebackup that when I close the EM, the backup finished successfully, but I am not really sure if backup is done on all datafiles.
Hope someone would help.
Thanks,
Jay A

Thanks for the response, but I was referring more to where the metadata is stored. And unfortunately, the backup job is something associated with EM not the scheduler, as you will find no reference to these in dba_jobs. They are not visible in the administration > jobs page either. They are scheduled through the maintenance > schedule backup link, and can be viewed by selecting the scheduled,running,problem executions links on the homepage.
Thanks,
Jeremy

Schedule Backup on Oracle Enterprise Manager 10g

Hello All,
I am using Oracle enterprise manager 10g for schedule backup, i enter the user and password of operating system (windows XP) in Host Credentials part, but it return this error:
Connection to host as user khazaei failed: IOException in sending Request :: Connection refused: connect
khazaei is my windows username ,
any one can help me?
thanks in advance,
Hamzeh Khazaei

You need to add khazaei to the Local Security Policy "Logon as Batch Job". if you have already done so and you have logged on to a Domain, then add the domain to the username. e.g domain_name\khazaei.
BTW - you can get faster response to this issue in the EM forum
Enterprise Manager

Sleep, Passwords, and Scheduled Backups

Okay, I have a question that I've yet to find an answer to (and I've looked high and low). I would think it would be a common issue, but perhaps not.
I downloaded Deja Vu a few days ago to schedule backups for my computer. Ideally I'd like them to run at like 5am when I'm not near my computer. So far so good. The problem is that I would like my computer passworded, and there lies the trouble.
Ideally it would be nice if I could set it to sleep for the night, go to bed, schedule it to wakeup at 4:59am, start Deja Vu at 5am, make the backup and go back to sleep. The problem with that is that I originally had it set to ask for a password when coming out of sleep or a screen saver- when that's on and it comes on a scheduled wakeup, it prompts for password for 10-20 seconds, sees no password and goes back to sleep, bypassing my backup. Obviously that's not what I need.
I then thought, hey, that's fine, I guess I could just unpassword the sleep/screen saver functions and live with the need to lock my screen every time I'm away (I have it set up to lock my screen in a couple of keystrokes, so that's not that big of a deal). But then I realized that even if I did that, it would come back from sleep, perform the backup, head back to sleep, but at that point anyone could just come by, wake it back up from sleep and not need a password, because the screen doesn't get locked after the backup is made.
So here's the endpoint: I would like to keep my iMac secure throughout the day by requiring a password to use it, but on the same token I need it to be able to wake up from sleep in order to perform the backup.
I was thinking about never setting it to go to sleep and just locking my screen at night (with my monitor automatically turning off after X minutes), but I'm worried about keeping it on for a more than necessary amount of time- I figure that if I set it to sleep during the night it might theoretically prolong its life- can anyone comment on that? (I'm a recent OS X convert, so I'm still learning some things- and yes, I completely love OS X now!)
Thanks a lot for any insight you could provide.
Mac OS X (10.4.3)

Welcome to the Apple community:
You certainly don't need to worry about shortening your computer's life by leaving it on 24/7. I have my monitor set to sleep after a few minutes, but the computer never sleeps. One of the things that OS X does is run cron tasks (housekeeping, cleaning logs, caches and various mundane tasks) sometime early in the morning when you are unlikely to be using the computer. I think the latest iteration of 10.3 runs these at other times of the days, but the main thing is, don't fret about leaving your computer on, they are built to do this and you will save yourself a lot of fiddling about and accomplish what you want to do by simply leaving it on.
Miriam

Scheduled Backups on OEM

Similar Messages

Maybe you are looking for