Rman backup schedule in windows

Similar Questions

• We can schedule with rman backup in the windows platform?

  My question is about the backup settings of my
  
  the idea is to all on the windows platform
  
  a weekly full backup (compressed backupset level 0)
  daily incremental backup of (cumulative) (even, level 1)
  an incremental backup every hour (bonus) (level 1)
  
  
  
  could you please tell me if the following examples will be adapted to my needs
  Thanks to you all

  I think you would need to do a .cmd file plan and then using the Windows Task Scheduler. I suggest you do a cmd simple backup file, try to plan and see how it goes.

  HTH
  Aman...

• RMAN backup schedule

  Hello world
  
  How to schedule the backup RMAN automatically with a condition of scheduling. Please can someone help me.
  
  Thanks in advance

  You may have to re-create the repository:

  EMCA - deconfig dbcontrol db
  EMCA - config dbcontrol db-rest recreate

• Automate the RMAN backup Windows

  I'm working on automation RMAN backup under windows, how can I do, I know dbconsole do that, but its does not not for me for now...
  
  Step by step, scripts & windows scheduler would contribute to

  cmd script and plan with Windows scheduled tasks.

• Lack of backup scheduled Windows 7.

  A few questions about the built-in Windows 7 backup program. If my computer is turned off during the time I have a scheduled backup is him asking to postpone that backup when the computer is turned on or the next backup? The second question is after the initial backup are the following additional backups? Thanks in advance.

  Hello

  Please contact Microsoft Community.

  Method 1:

  I suggest you have a look at the scheduled backup job. I also suggest you to run the task as soon as possible after a scheduled task is not respected. I suggest you check out the article below.

  http://Windows.Microsoft.com/en-us/Windows7/schedule-a-task

  Follow the steps below and check, if it helps.

  1. go the Task Scheduler: start > all programs > Accessories > system tools > Task Scheduler
   
  2. in the Task Scheduler, navigate to the CURRENT BACKUP TASK THAT WINDOWS has ALREADY CREATED: in the left pane, select: Task Scheduler > Task Scheduler Library > Microsoft > Windows > WindowsBackup
   
  3. in the middle pane, right click on AutomaticBackup and THEN YOU CAN SELECT THE CONDITIONS TAB AND SET IT to WAKE UP the COMPUTER.

  I would also change automatic return parameters.

  See the link below:

  http://Windows.Microsoft.com/en-us/Windows7/set-up-or-change-automatic-backup-settings

  Method 2:

   

  I suggest you to show the section How to display the contents of my backup in the link below and check if it helps.

  http://Windows.Microsoft.com/en-us/Windows7/back-up-and-restore-frequently-asked-questions

  Method 3:

   

  I suggest you to show the section storage space should I back up the files in the link below and check if it helps.

  http://Windows.Microsoft.com/en-us/Windows7/back-up-and-restore-frequently-asked-questions

• RMAN: we have a window of recovery of 130 days defined and we use a catalog of recovery, but report need backup doesn't report anything.

  Our first backup was made on April 28, 2015. Some how report need backup don't recount everything that needs to be backed up. Please let me know why it is like that.

  Hello

  When you run rman phrase 'report need backup '?. just after completing a backup complete (including the arch files)?

  If you made a backup today,"report needed backup; ' returns 0.

  I tested in oracle 10 and oracle 11, with the default of 60 days and archivelog retention policy backup every 3 hours.

  * "report need backup 300 recovery window days."

  Returns the value 0.

  * "list backupset summary"

  return values of 60 days so far.

  I reproduced with and without connecting to the catalog.

  Please read the old note:

  How does the REPORT the WINDOW to RETRIEVE NEED BACKUP? (Doc ID 301704.1)

  This is for oracle 9i, but I think you can always apply on oracle 11g

• RMAN backup Linux drivers shared on windows 2008 Server.

  Hi all
  
  I want to know is - it possible to rman backup to shared disk windows 2008 for a database of runnig under Linux.
  
  I tried it and getting rman-03002 followed by ORA-19504, error Ora-27040 and linux-x86_64.
  
  I used the following command to mount my windows share
  Mount-t cifs/o username = administrator, password = "XXXXXX" //172.16.1.50/files/MNT
  
  
  Concerning
  Nidsh
  
  Edited by: 883687 August 15, 2012 23:08

  Hello;

  It should be possible. The ORA-27040 is

  "O/S-Error: (OS 3) The system cannot find the path specified."
  

  and the second error ORA-27040 seems to be an effect of the first.

   File create error, unable to create file
  

  Could be a permissions problem, so if you can mount the disk space windows, but cannot write to it (yet)

  There is a note of support Oracle that covers this:

  ORA-19504 ORA-27040 during Rman backup in a Directory Windows mounted under Linux [464267.1 ID]

  Which confirms, in my view, the answer is Yes.

  Further that:

  RMAN fail with ORA-19504 ORA-27040 when backup remote server linux [726858.1 ID] Windows Mount Volume

  Best regards

  mseberg

  Published by: mseberg on August 16, 2012 04:33

• recover the database on windows xp linux rman backup

  Hi guys,.
  
  I am recovering a xp database that runs on Centos 5.3 on windows xp.
  
  That's what I did.
  backup database
  Run {}
  maxcorrupt for the data file the value 2 to 1;
  
  CONFIGURE REDUNDANCY 5 RETENTION STRATEGY;
  CONFIGURE BACKUP OPTIMIZATION
  SET UP DEFAULT DISK DEVICE TYPE; # by default
  CONFIGURE CONTROLFILE AUTOBACKUP ON;
  CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO "%F" # by default
  SET UP THE DEVICE TYPE DISK PARALLELISM 1 BACKUP BACKUPSET TYPE; # by default
  CONFIGURE BACKUP OF DATA TO DISK FILE TYPE DEVICE TO 1; # by default
  CONFIGURE BACKUP ARCHIVELOG FOR DEVICE TYPE DISK TO 1; # by default
  CONFIGURE MAXSETSIZE TO UNLIMITED; # by default
  CONFIGURE ENCRYPTION OF DATABASE # by default
  CONFIGURE THE ENCRYPTION ALGORITHM "AES128"; # by default
  CONFIGURE THE NONE ARCHIVELOG DELETION POLICY; # by default
  CONFIGURE SNAPSHOT CONTROLFILE NAME TO ' / usr/lib/oracle/xe/app/oracle/product/10.2.0/server/dbs/snapcf_XE.f'; # by default
  compressed backup backupset database;
  backup current controlfile;
  backup SPFile;
  }
  
  FTP files on Windows
  SQL > startup mount restrict exclusive;
  SQL > drop database;
  
  SQL > startup nomount;
  RMAN > set dbid = 7898909
  RMAN > recover automatic backup controlfile;
  
  And then the problems begin.
  because the controlfile contains the former locations of tablespaces (linux).
  I try with set newname for data file does not work because old tablespaces are not there.
  If I try to backup the controlfile to find and change the locations, it still does not because I don't have the files of data in place.
  
  In short; How to restore and recover the database from a backup of linux on windows?

  Hello

  Rman backups are not portable between operating system platforms.
  You must use the convert command.
  Please follow the link which explains the controls and the procedure below.
  http://download.Oracle.com/docs/CD/B19306_01/backup.102/b14191/dbxptrn.htm#CHDCFFDI

  Kind regards
  Tycho

• RMAN backup to the remote disk in Windows

  Hello
  
  I'm under Oracle 9.2.0.1 with Windows Server 2003 in Server A and Server B. My first DB is stored in the server a in the meantime my catalog RMAN is to Server B. I'm under RMAN to do the backup of the DB in Server A, which is short of space. So, I decided to put my backupsets to Server B since I got here a few hundred Gs. Overall, I will push the catalog RMAN backup script to Server B and store the backupsets to Server B.
  My problem is when I run the script, what either him or from a server or Server B, I get the following error. Tied together correspond to the configuration of RMAN settings.
  
  Error:
  
  ***********************************************************************************
  RMAN > backup database;
  
  From backup 20 August 09
  allocated channel: ORA_DISK_1
  channel ORA_DISK_1: sid = 13 devtype = DISK
  allocated channel: ORA_DISK_2
  channel ORA_DISK_2: sid = 9 = DISC devtype
  allocated channel: ORA_DISK_3
  channel ORA_DISK_3: sid = 14 devtype = DISK
  channel ORA_DISK_1: from full datafile backupset
  channel ORA_DISK_1: specifying datafile (s) in backupset
  input datafile fno = 00012 name = F:\ORADATA\DRDB\DATA\DATA01. DBF
  channel ORA_DISK_1: starting piece 1 at 20 August 09
  channel ORA_DISK_2: from full datafile backupset
  channel ORA_DISK_2: specifying datafile (s) in backupset
  input datafile fno = name 00002 = F:\ORADATA\DRDB\DATA\DATA07. DBF
  channel ORA_DISK_2: starting piece 1 at 20 August 09
  channel ORA_DISK_3: from full datafile backupset
  channel ORA_DISK_3: specifying datafile (s) in backupset
  input datafile fno = name 00006 = E:\ORADATA\DRDB\INDEX\INDX01. DBF
  channel ORA_DISK_3: starting piece 1 at 20 August 09
  RMAN-00571: ===========================================================
  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
  RMAN-00571: ===========================================================
  RMAN-03009: failure of the backup command on the channel ORA_DISK_1 at 2009-08-20 17:06:
  56
  ORA-19504: cannot create the file '\\ServerB\f$\drdb\backupset\BackupDRDB_DB_39k '.
  n665g_105_1 ".
  ORA-27040: skgfrcre: error, unable to create the file
  04002 - OSD: could not open the file
  S/O-error: (OS 5) access denied.
  
  RMAN > show all.
  
  RMAN configuration parameters are:
  CONFIGURE REDUNDANCY 10 RETENTION STRATEGY;
  CONFIGURE BACKUP OPTIMIZATION # by default
  SET UP DEFAULT DISK DEVICE TYPE; # by default
  CONFIGURE CONTROLFILE AUTOBACKUP ON;
  CONFIGURE CONTROLFILE AUTOBACKUP FOR DEVICE TYPE DISK FORMAT to ' \\ServerB\f$\d
  rdb\controlfile\Backup%d_CTL_%F';
  SET UP THE DEVICE TYPE DISK PARALLELISM 3;
  CONFIGURE BACKUP OF DATA TO DISK FILE TYPE DEVICE TO 1; # by default
  CONFIGURE BACKUP ARCHIVELOG FOR DEVICE TYPE DISK TO 1; # by default
  CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT ' \\ServerB\f$\drdb\backupset\Backup
  % d_DB_ % %%p s_ u_ ';
  CONFIGURE MAXSETSIZE TO UNLIMITED; # by default
  CONFIGURE the SNAPSHOT CONTROLFILE NAME to ' \\ServerB\f$\drdb\controlfile\SNCFDRDB.
  CTL';
  
  **********************************************************************************
  
  My login ID exists in the administrator and ORA_DBA group in Server A and Server B. I can manually run the path '\\ServerB\f$\drdb\backupset\' on server A and able to create/modify/delete a file inside this folder. But I don't understand why the error "access denied"? In any case, is it a proper way to do remote disk backup? I am quite new to Oracle and just attended courses RMAN with the OU. I have Google-ed this problem but no one can help me. Please help me or share your knowledge to solve this problem.
  
  Thank you and best regards,
  Nsiala

  Hi nsiala.

  Under windows, the oracle process runs as a service. By default, this service runs under the Local System account. This account is fairly low privileged when it comes to remote network privileges and therefore cannot see the directory you are trying to write your backups to.

  You can change the user that the service is running as, there are a few notes on metalink for this and I remember well find some info usually using google.

  Concerning
  André

• RMAN backup error

  Hello

  I get an error when you try to run an Oracle database backup using a windows batch file that calls a settings file to execute RMAN commands. This is handled by the windows scheduler.

  It's been in place for several months and worked fine until today.

  Oracle Version - 11G 11.2.0.2.0

  OS - Windows server 2008 R2

  * Note *-I have changed for security reasons password and company information.

  Here are the contents of the batch file:

  echo: [email protected] > > \\CCCODS09\c$\Support\DB_Backup\Max.log

  echo to: [email protected] > > \\CCCODS09\c$\Support\DB_Backup\Max.log

  Echo subject: Max Backup log > > \\CCCODS09\c$\Support\DB_Backup\Max.log

  RMAN @\\CCCODS09\c$\Support\DB_Backup\Max.txt > > \\CCCODS09\c$\Support\DB_Backup\Max.log

  copy \\CCCODS09\c$\Support\DB_Backup\Max.log \\ccvmds51\c$\inetpub\mailroot\Pickup\email.txt

  del \\CCCODS09\c$\Support\DB_Backup\Max.log

  Here is the content of the Max.txt settings file:

  connect sys/password@maxof target;

  Run {}

  backup as compressed backupset actual additional database tag 0 = = "format='\\cccobu02\oracle\cccods09\Max\%T_Max-HOT-BACKUP-OF-FULL-DATABASE-AND-LOGS-DATAFILE-%U.BKP';

  backup as compressed backupset archivelog all delete tag all input = "format='\\cccobu02\oracle\cccods09\Max\%T_Max-HOT-BACKUP-OF-FULL-DATABASE-AND-LOGS-LOGFILE-%U.BKP';

  backup as compressed backupset current controlfile tag = "format='\\cccobu02\oracle\cccods09\Max\%T_Max-HOT-BACKUP-OF-FULL-DATABASE-AND-LOGS-CONTROLFILE-%U.BKP";

  }

  "exit";

  And here is the log file:

  Recovery Manager: release 11.2.0.2.0 - Production on Mon Nov 17 05:30 2014

  Copyright (c) 1982, 2009, Oracle and/or its affiliates.  All rights reserved.

  RMAN > Connect target *.

  2 > run {}

  3>           = backup as compressed backupset actual additional database tag 0 = "format='\\cccobu02\oracle\cccods09\Max\%T_Max-HOT-BACKUP-OF-FULL-DATABASE-AND-LOGS-DATAFILE-%U.BKP';

  4>           backup as compressed backupset archivelog all delete tag all input = "format='\\cccobu02\oracle\cccods09\Max\%T_Max-HOT-BACKUP-OF-FULL-DATABASE-AND-LOGS-LOGFILE-%U.BKP';

  5>           as a compressed backupset backup current controlfile tag = "format='\\cccobu02\oracle\cccods09\Max\%T_Max-HOT-BACKUP-OF-FULL-DATABASE-AND-LOGS-CONTROLFILE-%U.BKP ';

  {6 >}

  7 > exit;

  connected to target database: MAX (DBID = 1234567890)

  From backup 17 November 14

  DBGSQL: TARGET > select nvl (max (al.recid), '0'), nvl (max (al.recid), 0) in : txtparmvalue,: parmvalue of al v$ archived_log where in al.status ('X', 'A') and al.is_recovery_dest_file = 'YES' and al.creator = "RMAN"

  DBGSQL: SQLCODE = 1008

  RMAN-00571: ===========================================================

  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.

  RMAN-00571: ===========================================================

  RMAN-03002: failure of the backup at 17/11/2014 05:30:16 command

  RMAN-03014: implicit recovery catalog Resync failed

  ORA-01008: not all variables

  Complete recovery manager.

  If you need more information please let me know.

  Any help to fix this would be appreciated.

  Thank you

  Hello

  This is considered to be a bug for 11.2.0.2 version.

  Please see this document of MOS

  ORA-01008: RMAN backup does not work with assorted errors 11.2.0.2 If cursor sharing is turned on (Doc ID 1472116.1)

  Kind regards

  Shivananda

• RAC RMAN backup

  Hello
  
  DB is 10.2.0.4 OS = BSG (CARS with 2 nodes BD01, db02). Here are the types of automated RMAN backups taken on db01.
  
  -OCR
  -Voting record
  -Talespaces Snapshot
  -Archivelog (hourly)
  -Backup incremental level 0 (SUNDAY)
  -backup incremental level 1 (Mon - Sat)
  -Automatic backup of the control file and SPFILE (CONTROLFILE AUTOBACKUP ON)
  
  Two big questions please. First of all, are these types of backups/backup are enough to RESTORE FULL speaking of RMAN backup on a RAC environment with 2 nodes? Otherwise please suggest what I need to backup?
  
  Second, home backup location is /rman that I can see on db01 ONLY. This directory of /rman that I don't see on db02. My question is what db02 failure can I restore from directory /rman? or do I need to automate the backup also schedules on db02 separately?
  

  [root@db01~]# df -h
  Filesystem            Size  Used Avail Use% Mounted on
  /dev/mapper/VolGroup00-LogVol00
                        3.9G  2.9G  814M  79% /
  /dev/sda3             190M   34M  147M  19% /boot
  tmpfs                  16G     0   16G   0% /dev/shm
  /dev/mapper/VolGroup00-LogVol05
                        3.9G  137M  3.6G   4% /home
  /dev/mapper/VolGroup00-LogVol03
                        3.9G  225M  3.5G   6% /tmp
  /dev/mapper/VolGroup00-LogVol02
                        7.8G  3.7G  3.8G  50% /usr
  /dev/mapper/VolGroup00-LogVol04
                        3.9G  379M  3.4G  11% /var
  /dev/mapper/VolGroup00-ORACLE_BASE
                         12G  8.7G  2.6G  78% /oracle
  10.10.28.140:/vol/px4cinconso
                         40G  1.4G   39G   4% /inconso_px
  /dev/mapper/36001ec9000d5ea810000061349015d98
                        1.3T  551G  665G  46% /rman

  [root@db02~]# df -h
  Filesystem            Size  Used Avail Use% Mounted on
  /dev/mapper/VolGroup00-LogVol00
                        3.9G  887M  2.9G  24% /
  /dev/sda3             190M   34M  147M  19% /boot
  tmpfs                  16G     0   16G   0% /dev/shm
  /dev/mapper/VolGroup00-LogVol05
                        3.9G  137M  3.6G   4% /home
  /dev/mapper/VolGroup00-LogVol03
                        3.9G  261M  3.5G   7% /tmp
  /dev/mapper/VolGroup00-LogVol02
                        7.8G  3.7G  3.8G  50% /usr
  /dev/mapper/VolGroup00-LogVol04
                        3.9G  355M  3.4G  10% /var
  /dev/mapper/VolGroup00-ORACLE_BASE
                         12G  6.5G  4.8G  58% /oracle
  10.10.28.140:/vol/px4cinconso
                         40G  1.4G   39G   4% /inconso_px

  [oracle@db01~]$ rman target /
  
  Recovery Manager: Release 10.2.0.5.0 - Production on Fri Feb 24 11:49:59 2012
  
  Copyright (c) 1982, 2007, Oracle.  All rights reserved.
  
  connected to target database: F1 (DBID=1245145263)
  
  RMAN> show all;
  
  using target database control file instead of recovery catalog
  RMAN configuration parameters are:
  CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 28 DAYS;
  CONFIGURE BACKUP OPTIMIZATION ON;
  CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
  CONFIGURE CONTROLFILE AUTOBACKUP ON;
  CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/rman/f1/fullbackup/%F';
  CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO COMPRESSED BACKUPSET PARALLELISM 1;
  CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
  CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
  CONFIGURE MAXSETSIZE TO UNLIMITED; # default
  CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
  CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
  CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
  CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/oracle/product/10.2.0/db/dbs/snapcf_f11.f'; # default

  # Script for backup
  
  level0 ()
  run {
    allocate channel c1 type disk  maxpiecesize 2000M format '/rman/$ORACLE_SID/fullbackup/$ORACLE_SID-data-%U-%t';
    allocate channel c2 type disk  maxpiecesize 2000M format '/rman/$ORACLE_SID/archive/$ORACLE_SID-arch-%U-%t';
    backup incremental level 0 tag = weeklyfull database channel c1 
    plus archivelog tag = ARCH_$TODAY delete all input channel c2;
    release channel c1;
    release channel c2;
  }
  
  run {
    allocate channel c1 type disk;
    delete noprompt obsolete;
    release channel c1;
  }

  Bundle of thanks.
  
  Kind regards
  
  Published by: 910385 on February 24, 2012 03:00

  Hi 910385,
  The error on the node db02

  ORA-19504: cannot create the file ' / rman/fp1/backup/c-1245145263-20120210-11.

  is caused by your installation.
  You have a /rman of mount point visible only on the node db01.
  The controlfile autobackup setting triggers the creation of a backup of the controlfile:
  -during the rman backup (this seems to work only on db01)
  -in the case of a structural change in the database (eg. Adding a data file).
  Sessions to make a structural change can be connected to one of your two instances, but the instance on db02 cannot create controlfile autobackup in /rman.
  You must change the configuration and put the backup on a shared disk that is seen by the two systems.
  Strangely, you have a shared file system:

  10.10.28.140:/vol/px4cinconso 40G 1.4 G 39G 4% /inconso_px

  Better would be to make a second for rman...
  Kind regards
  Tycho

• RMAN backup and cross-checking script

  Hello
  
  I just joined a new company this week. As would any s/n, I was going just through the RMAN backup scripts used in the new environment.
  Here we run weekly RMAN backup complete for some of the databases that I am responsible for managing. The script and schedules are as follows.
  
  Every Sunday from 21:00, we organize a weekly job overlap
  
  Connect target username/pwd@DBNAME
  Connect catalog username/pwd@DBNAME
  
  Run {}
  CROSS-CHECKING OF BACKUP;
  DUPLICATION OF COPY;
  OVERLAP BACKUPSET;
  OVERLAP ARCHIVELOG ALL;
  DELETE NOPROMPT OBSOLETE;
  }
  
  Every Sunday from 9:30, we run the RMAN backup command which is
  
  Connect target username/pwd@DBNAME
  Connect catalog username/pwd@DBNAME
  
  run
  {
  CONFIGURE RETENTION POLICY TO RECOVERY OF 7-DAY WINDOW;
  SQL 'alter system archive log current';
  backup as backupset database include current controlfile;
  SQL 'alter system archive log current';
  ARCHIVELOG BACKUP of time ' SYSDATE-8';
  DELETE ARCHIVELOG ALL COMPLETED BEFORE ' SYSDATE-15';
  }
  
  
  A database that I will handle has been set up just over a week before I join.
  28 FEV 21:00 - no set of backup/copy/backup of overlap. I hope it will be cuts across all archive logs available in the database. No obsolete backup/copy/backup/archivelogs to remove.
  28 FEV 21:30 - sets the retention policy at 7 days, full backup of database backup and backup all archivelogs (sysdate-8). No newspaper archive to remove the database was created (migrated) less than 15 days back.
  
  7 March 21:00 - contre-vérifie the backupset (taking the 28 fev 21:30). No backup/copy of overlap.
  Question 1: Is there a backup obsolete here to delete?
  Own thought: Recovery window is 7 days. RMAN needs a backup in order to recover the database in any time-7 days to the present time (7 March 21:00 - 7 days = 28 fev 21:00). No obsolete backup to delete.
  
  7 March 21:30 - full database backup and fails to save all logs archiving (sysdate-8). No space in the Flash recovery disk group. As the archivelog backup failed and RMAN complete, it has not removed the archivelogs ' sysdate-15'.
  
  Backup is running again on 14 March. Of course, it will fail because there is no enough space in the Group of recovery disks.
  
  Future: I'm confused
  March 14, 21:00: contre-vérifie the backupset (supported March February 21:30). No backup/copy of overlap.
  Question 2: How do I know what is here obsolete? From the window of 7 days recovery, 14 March 21:00-7 days is March 7, 21:00. Last backup was taken on March 7, 21:30.
  To get back to 21:00, RMAN makes keep the backup of 28 March?... Does this mean whenever I'll have copies of backup 3?...
  
  14 March 21:30 - backup database... Log Archive backup will fail because there is no space. (I think to make a compressed backup).
  
  Question 3: How those wise commands?
  ARCHIVELOG BACKUP of time ' SYSDATE-8';
  DELETE ARCHIVELOG ALL COMPLETED BEFORE ' SYSDATE-15';
  
  If I take a successful backup of the archivelogs sysdate-8, why I need to keep the archivelogs before that? What could be the reason the previous DBA kept DELETE ARCHIVELOG COMPLETED BEFORE ANY 'SYSDATE-15 '; Rather than give DELETE ARCHIVELOG FINISHED FIRST and FOREMOST ' SYSDATE-8 "?
  
  Thanks in advance for your help.
  
  Published by: user8907052 on March 11, 2010 12:10

  If your database to 9i and above, then you don't need to pass - sql 'alter system archive log current;' before you perform the backup as RMAN automatically archives the log during recovery.

• Backup cancelled in Windows 7 when the computer is turned off.

  I use Windows 7 Home Premium 64-bit operating system.

  Periodically, the Action Center will display a message saying that I have to do a backup, what I do before turning off the computer. However, when I reboot the computer, I discovered that the backup has been cancelled.

  I have searched the web but can't find information about how to make the computer shuts down automatically once the backup completed successfully.  Does anyone have a solution?

  The backup has been working in the past?

  Have you ever attempted an upgrade to Windows 10 and then back to Windows 7?

  For example let's say you have your backup scheduled task to run at midnight...

  If your computer is stopped at midnight, the backup does not - because the computer is stopped and the task was "missed" because the computer has been shut down.

  If you have the backup task configured on "Run as soon as possible after a regular departure was missed":

  

  When your computer working again missed backup task starts automatically.

  If you have your scheduled backup job to run at midnight and your computer is in "Sleep" mode, you have the task configured to wake the computer to run the backup:

  

  This won't work for wake up the computer if it is in "Sleep" mode  It will not work if the computer is in hibernation or if the computer is shut down.  As you can be awakened from sleep, the computer can be awakened from sleep, but you can't be awake if you're dead (stop).  You have to sleep to being awake.  You can be awake if you're dead or hibernation.

  The 'problem' with this approach is if the computer wakes up and runs the backup it will continue to function and you don't want that.   You can the computer to wake up, run the backup, and then click Stop (or to go back to sleep) when the backup is complete, and you can configure to occur in two different ways.  If that's how you think you want things to work ask the question in the right way, and describe how you want things to work.

  If your computer is in hibernation or stop the scheduled backup will not work until the computer working again and realizes that he has missed a task... then the backup will run - if you have the task set to do as the first example.

  Depending on certain factors that have nothing to do with Windows there are ways to make your computer start at a certain time of the hibernation or shutdown (mean 23:55) so it will be quick and then the backup will take place at midnight but will continue to operate your computer unless you include an additional step to stop the system again when the backup is complete.  These things are not exactly automatically built into Windows, but there might be ways to do things the way it works.  If that's how you think you want things to work ask the question in the right way, and describe how you want things to work.

  Find how to solve is often a matter of the question or stating the problem clearly there is no guess, no things difficult and none of these proceedings of the wild goose.

  What is the problem with the way your backup works now?

  What part doesn't work the way you think it should work?

  How do you think this should work?

  How it works?

  If your computer is turned off (off) do you want that it to wake up itself, run the backup and then stop when the backup he fill?  You can do it if you want, but it takes an extra effort and has a few requirements outside the Windows operating system.

  The task of the example above is set to run every Monday at 09:00.

  If my computer is running at 09:00 on Monday, the backup will start and run Monday at 09:00.

  If my computer doesn't work at 09:00 on Monday, the backup will run as soon as possible after the computer restart us and that's fine with me.

  I do not use sleep or Hibernate so I don't have to worry about how get the copy backup to run under these conditions.

• How plan 2 separate backup jobs using Windows 7 backup & restore?

  How plan 2 separate backup jobs using Windows 7 backup & restore? I would like to back up some files more frequently than others.

  Hello CasPhillips,

  Try to use Task Scheduler to schedule two separate backups.

  Otherwise, you may need to use a 3rd party backup solution.

  Thank you

  Marilyn

• RMAN backup location must change and remove obsolete

  Dear Experts,

  I'm working on the following environment,

  Operating system: Windows server 2012 R2

  Oracle version: 11.2.0.1.0 release

  Type of RMAN backup: Cumulative (preferred by the direction and I can't change it in differential backup)

  My current situation,

  I set up RMAN and H: drive for purposes of backup and G: for Archivelog.

  Recently, my city was covered by the flood waters and the server works not for a week so that we delete obsolete level 0 does not work.

  Currently there is not enough space to run a level 1 and level 0, while I should change the backup location.

  My Question is,

  (1) I need to change this location of drive H: to G: drive backup backup correctly without error not enough space.

  (2) after having taken a level 1 and level 0, depending on my 1 redundancy, RMAN mechanism should delete obsolete backup disk without failure G: and H:.

  Kindly help me how to get to my need. This will help me, thanks in advance

  You can

  1. replace the DB_RECOVERY_FILE_DEST G:

  2 run backups

  3. wait for the DELETE OBSOLETE delete obsolete backups of H:

  and then

  4. change the DB_RECOVERY_FILE_DEST return h as it was more early

  In this way, you don't have to use the FORMAT or CHANNEL of CONFIGURE commands (I was referring to CONFIGURE CHANNEL, not ALLOCATE CHANNEL) to change the destination of the backup

  Hemant K Collette