Production Database Backup

I have a replicated production database to which I cannot perform a backup very often. We have got a one-off window to take a backup.
What I would like to know is whch particular backup to take...cold backup or user managed backup. I can take both, howver, in case of disaster reovery, I would only have this backup mand the archived redo logs and maybe access to one or two ionline redo log group files.
o which backup should I take which will allow me to recover the database using there archived and redo log files? Cold backups or user-managed backups?
Basically what I am asking is which backups allow redo logs to be applied to recover database to point in time when it crashed since it is a replicated database?
OS Win2K As Svr, Oracle DB 9.2.0.6,
Thanks in advance

What do you mean by replicated database?
I would go for RMAN backups with open database (database must be in archivelog).
I think this is the best env for performing backups, I would also suggest using
RMAN catalog if you have an option to use it.
Best Regards
Krystian Zieja / mob

Similar Messages

  • Daily export backup (via datapump) of a 600GB production database

    Hi Guys,
    I have a 600GB DB.
    10G Database.
    Currently I have daily rman backup to tape.
    Based on your experience, should i bother to perform a daily export of production database of such size?
    Do u think it's useful?
    thanks

    Fran wrote:
    All depends, what do you want to do? Do you have enough space to save a backup and export daily?
    In my opinion with one backup is enough to save your database. I'm sorry, I can't agree with that. I've been in situations where the first, second and THIRD backup sources have been unavailable in the event of a Production restore. I had to go to Plan D and cross my fingers (and sweat a lot). That might be overkill, but you should never rely on just one backup method/source for Production data.
    Not only that, but, obviously, you can also use an export of the data and import into another database or a schema inside the database in case you need to address any logical corruption. We also use the exports to refresh test databases.
    We have many similar sizes of databases and we take exports weekly, instead of daily. An export will be an incomplete backup, obviously, though you can ensure consistency by giving it an SCN to use as a datapoint. You can also run Data Pump in parallel which does speed things up.
    If you use it as part of your backup strategy, I'd make sure I had regular backups of the parameter file and the controlfiles (both binary and trace). I'd also make sure I had regular txt files showing the necessary information for the tablespaces and the datafiles which you can use to recreate the files in case you needed to.
    Mark

  • SAP Production Systems Database backup failed

    Dear Guru,
    I have been facing a problem with our SAP Production system's oracle database backup for last three days. Our back up goes through TSM server. At night 10 pm we have schedule backup for whole offline + redo log backup,  11 pm check and update optimizer statistic and at 11:30 pm Check Database. For last three days above mentioned backup getting failed and we are not able to get such a details log by which i can understand the issue. But Our Development server and Quality server's backup which are scheduled at 12 am and 2 am, the both backup schedules finish successfully. And in morning all schedule backups of Production systems finish without any errors. The issues is coming only with Whole database backup + redo log Backup which schedule at night 10 pm. I have mentioned the log whatever i have got in below:
    07.02.2012     07:30:06     Job started
    07.02.2012     07:30:06     Job has exceeded its latest start date
    07.02.2012     07:30:06     Job cancelled after system exception ERROR_MESSAGE
    Above mentioned logs are showing 1day advance log where i have mentioned yesterdays log. That means it should shows 06.02.2012 instead of 07.02.2012 and time should be 22:00:00 instead of 07:20:06.
    Our Oracle version is 10.2.0.4.0/ kernel release 701/BRBACKUP 7.00 (40)
    Please Guide me.
    Regards,
    Samrat Chakraborty

    OK,
    this has nothing to do with brbackup or TSM.
    You batchjob starts at 07:30 !!!
    Means before that, you do not have any action at all.
    Then the job crosschecks it has passed its intended startdate and terminates,
    which is correct, since you do not like brbackup to shut down your DB at 07:30!
    No brbackup is started at all, which is why you get no log and no tsm connect takes place.
    I assume,  you misconfigured some operationmodes and at 07:30 an OP-modeconfiguration
    with batchjobs switches back in place so that the jobs do start too late.
    Check RZ04 and the OP mode timetable
    If it is not this, it has to be something else with the batch scheduler causing delay
    or may be all BTC processes are busy, but this seems unlikely with a start at 07:30 sharp..
    Volker

  • DBACockpit Configuration - Remote Database backup of Java Stack.

    Hi All,
    I am configuring remote database backup of my SAP Java stack system.
    I have successfully connected the system in dbacockpit. I have gateway installed also on the remote host system. but Database scheduling on DB13 failed.
    On the OS of CEN system, I can connect to the host system of the remote using the OPS$ logon and i.e
    sqlplus /@SID as sysdba  - (It connected, to confirm i querried the v$instance I was also able to shutdown the remote system)
    E:\>sqlplus /@SID as sysdba
    SQL*Plus: Release 10.2.0.4.0 - Production on Wed May 18 15:37:46 2011
    Copyright (c) 1982, 2007, Oracle.  All Rights Reserved.
    Connected to:
    Oracle Database 10g Enterprise Edition Release 10.2.0.2.0 - 64bit Production
    With the Partitioning, OLAP and Data Mining options
    But when I ran the brtools to perform the backup I got this error.
    "BR0301W SQL error -12560 at location BrDbConnect-2, SQL statement:

    Hi Niyi,
    This is a TNS error. The system is not able to connect TNS by using br*tools.
    Firstly, check your environment variables. They should be as same as java system environmnt variables.
    Secondly, check the link below;
    [BR0301W SQL error -1017;
    You need to create a synonym and SAPUSER table for the gateway installation <sid>adm user on Java database. By doing so, br*tools will be able to connect to the java database.
    Best regards,
    Orkun Gedik

  • Oracle 11g 64 bit on Linux - Restore failure in production database

    Hi guru,
    We used to take full hot backup with the help of BackupExec of Symantec in our production database.We have two different oracle database (not cluster).
    We defined same policy for both .We defined schedule on Symantec to take full hot backup every night of database on tap drive.At any point of time we maintain only 2 full backup for each database on tap and then recycle it.
    Yesterday suddenly storage of database failed for both.?It was complete failure so we did not have any option but to restore last night full backup.
    It has done successfully for one database but when we tried to restore second from last night backup it thrown error :
    channel ch0: ORA-19870: error while restoring backup piece BE_9kjsfol6_1_1
    ORA-19507: failed to retrieve sequential file, handle="BE_9kjsfol6_1_1", parms=""
    ORA-27029: skgfrtrv: sbtrestore returned error
    ORA-19511: Error received from media manager layer, error text
    then we tried to restore backup of last to last night and it gave again error :
    channel ch0: ORA-19870: error while restoring backup piece BE_9djsaman_1_1
    ORA-19507: failed to retrieve sequential file, handle="BE_9djsaman_1_1", parms=""
    ORA-27029: skgfrtrv: sbtrestore returned error
    ORA-19511: Error received from media manager layer, error text
    But we have seen log of Symantec at the time of backup and it said that backup has successfully completed.
    right now I am in big trouble I tried almost all possible combination of symantec to restore database but got no success.I used script generated by symantec and tried to run that on RMAN directly but it is throwing same error.
    Please help me if possible an throw some light on exception (as I understand it says it is not able to find some piece on tap but we have not touched tap and tap media is completely safe.)
    I am pasting complete text log generated by Symantec at the time of restore attempt:
    Recovery Manager: Release 11.1.0.6.0 - Production on Sun Oct 12 01:26:45 2008
    Copyright (c) 1982, 2007, Oracle. All rights reserved.
    # RMAN command section
    RUN {
    ALLOCATE CHANNEL ch0
    TYPE 'SBT_TAPE';
    SEND 'BSA_SERVICE_HOST=192.168.0.135,NBBSA_TOTAL_STREAMS=1,NBBSA_JOB_COOKIE={E8E38B61-7C1B-41A2-A2D7-8BB38A516AD3},NBBSA_DB_DEVICE_NAME=Oracle-Linux::\\G1-1-BLD-DSA2\sniffer2';
    RESTORE
    DATABASE
    UNTIL TIME "TO_DATE('10-08-2008:12:00:41', 'MM-DD-YYYY:HH24:MI:SS')";
    RECOVER
    DATABASE
    UNTIL TIME "TO_DATE('10-08-2008:12:00:41', 'MM-DD-YYYY:HH24:MI:SS')";
    RELEASE CHANNEL ch0;
    connected to target database: SNIFFER2 (DBID=3949735487, not open)
    using target database control file instead of recovery catalog
    allocated channel: ch0
    channel ch0: SID=316 device type=SBT_TAPE
    channel ch0: Symantec/BackupExec/1.1.0
    sent command to channel: ch0
    Starting restore at 12-OCT-08
    channel ch0: starting datafile backup set restore
    channel ch0: specifying datafile(s) to restore from backup set
    channel ch0: restoring datafile 00001 to /home/oracle/app/oracle/oradata/sniffer2/system01.dbf
    channel ch0: restoring datafile 00002 to /home/oracle/app/oracle/oradata/sniffer2/sysaux01.dbf
    channel ch0: restoring datafile 00003 to /home/oracle/app/oracle/oradata/sniffer2/undotbs01.dbf
    channel ch0: restoring datafile 00004 to /home/oracle/app/oracle/oradata/sniffer2/users01.dbf
    channel ch0: restoring datafile 00005 to /home/oracle/app/oracle/oradata/sniffer2/system02.dbf
    channel ch0: restoring datafile 00006 to /home/oracle/app/oracle/oradata/sniffer2/sysaux02.dbf
    channel ch0: restoring datafile 00007 to /Ora2Meta/metatab01.dbf
    channel ch0: restoring datafile 00008 to /home/oracle/app/oracle/oradata/sniffer2/UNDOTBS103.dbf
    channel ch0: restoring datafile 00009 to /Ora2Data/blobdata01.dbf
    channel ch0: restoring datafile 00010 to /Ora2Data/blobdata02.dbf
    channel ch0: restoring datafile 00013 to /Ora2BTreeIndex/bindtab02.dbf
    channel ch0: restoring datafile 00014 to /Ora2DomainIndex/domaintab01.dbf
    channel ch0: reading from backup piece BE_9kjsfol6_1_1
    channel ch0: ORA-19870: error while restoring backup piece BE_9kjsfol6_1_1
    ORA-19507: failed to retrieve sequential file, handle="BE_9kjsfol6_1_1", parms=""
    ORA-27029: skgfrtrv: sbtrestore returned error
    ORA-19511: Error received from media manager layer, error text
    channel ch0: starting datafile backup set restore
    channel ch0: specifying datafile(s) to restore from backup set
    channel ch0: restoring datafile 00011 to /Ora2Data/blobdata03.dbf
    channel ch0: restoring datafile 00015 to /Ora2DomainIndex/domaintab02.dbf
    channel ch0: reading from backup piece BE_9ljsfqm6_1_1
    channel ch0: piece handle=BE_9ljsfqm6_1_1 tag=TAG20081006T155830
    channel ch0: restored backup piece 1
    channel ch0: restore complete, elapsed time: 00:11:35
    channel ch0: starting datafile backup set restore
    channel ch0: specifying datafile(s) to restore from backup set
    channel ch0: restoring datafile 00012 to /Ora2Data/blobdata04.dbf
    channel ch0: reading from backup piece BE_9mjsfrcb_1_1
    channel ch0: piece handle=BE_9mjsfrcb_1_1 tag=TAG20081006T155830
    channel ch0: restored backup piece 1
    channel ch0: restore complete, elapsed time: 00:02:55
    failover to previous backup
    skipping datafile 1; already restored to file /home/oracle/app/oracle/oradata/sniffer2/system01.dbf
    channel ch0: starting datafile backup set restore
    channel ch0: specifying datafile(s) to restore from backup set
    channel ch0: restoring datafile 00002 to /home/oracle/app/oracle/oradata/sniffer2/sysaux01.dbf
    channel ch0: restoring datafile 00003 to /home/oracle/app/oracle/oradata/sniffer2/undotbs01.dbf
    channel ch0: restoring datafile 00004 to /home/oracle/app/oracle/oradata/sniffer2/users01.dbf
    channel ch0: restoring datafile 00005 to /home/oracle/app/oracle/oradata/sniffer2/system02.dbf
    channel ch0: restoring datafile 00006 to /home/oracle/app/oracle/oradata/sniffer2/sysaux02.dbf
    channel ch0: restoring datafile 00007 to /Ora2Meta/metatab01.dbf
    channel ch0: restoring datafile 00008 to /home/oracle/app/oracle/oradata/sniffer2/UNDOTBS103.dbf
    channel ch0: restoring datafile 00009 to /Ora2Data/blobdata01.dbf
    channel ch0: restoring datafile 00010 to /Ora2Data/blobdata02.dbf
    channel ch0: restoring datafile 00013 to /Ora2BTreeIndex/bindtab02.dbf
    channel ch0: restoring datafile 00014 to /Ora2DomainIndex/domaintab01.dbf
    channel ch0: reading from backup piece BE_9djsaman_1_1
    channel ch0: piece handle=BE_9djsaman_1_1 tag=TAG20081004T174806
    channel ch0: restored backup piece 1
    channel ch0: restore complete, elapsed time: 00:29:55
    Finished restore at 12-OCT-08
    Starting recover at 12-OCT-08
    starting media recovery
    Oracle Error:
    ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
    ORA-01194: file 2 needs more recovery to be consistent
    ORA-01110: data file 2: '/home/oracle/app/oracle/oradata/sniffer2/sysaux01.dbf'
    released channel: ch0
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of recover command at 10/12/2008 02:12:48
    RMAN-06053: unable to perform media recovery because of missing log
    RMAN-06025: no backup of archived log for thread 1 with sequence 34786 and starting SCN of 327309500 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34785 and starting SCN of 327301335 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34784 and starting SCN of 327293588 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34783 and starting SCN of 327283177 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34782 and starting SCN of 327276129 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34781 and starting SCN of 327270761 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34780 and starting SCN of 327259154 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34779 and starting SCN of 327247460 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34778 and starting SCN of 327238239 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34777 and starting SCN of 327230121 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34776 and starting SCN of 327221510 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34775 and starting SCN of 327215378 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34774 and starting SCN of 327212076 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34773 and starting SCN of 327211654 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34772 and starting SCN of 327211171 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34771 and starting SCN of 327202005 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34770 and starting SCN of 327194156 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34769 and starting SCN of 327183755 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34768 and starting SCN of 327182026 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34767 and starting SCN of 327179450 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34766 and starting SCN of 327172246 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34765 and starting SCN of 327161460 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34764 and starting SCN of 327157752 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34763 and starting SCN of 327149852 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34762 and starting SCN of 327142049 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34761 and starting SCN of 327134814 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34760 and starting SCN of 327128948 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34759 and starting SCN of 327029461 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34758 and starting SCN of 326986719 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34757 and starting SCN of 326981601 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34756 and starting SCN of 326978697 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34755 and starting SCN of 326978093 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34754 and starting SCN of 326977904 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34753 and starting SCN of 326976801 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34752 and starting SCN of 326973891 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34751 and starting SCN of 326970649 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34750 and starting SCN of 326962803 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34749 and starting SCN of 326958315 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34748 and starting SCN of 326955232 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34747 and starting SCN of 326951908 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34746 and starting SCN of 326943909 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34745 and starting SCN of 326935460 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34744 and starting SCN of 326922741 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34743 and starting SCN of 326910246 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34742 and starting SCN of 326905072 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34741 and starting SCN of 326901097 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34740 and starting SCN of 326900178 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34739 and starting SCN of 326899668 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34738 and starting SCN of 326899106 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34737 and starting SCN of 326891014 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34736 and starting SCN of 326875443 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34735 and starting SCN of 326863782 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34734 and starting SCN of 326842985 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34733 and starting SCN of 326838670 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34732 and starting SCN of 326823584 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34731 and starting SCN of 326821851 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34730 and starting SCN of 326820427 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34729 and starting SCN of 326816378 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34728 and starting SCN of 326812324 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34727 and starting SCN of 326802760 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34726 and starting SCN of 326790469 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34725 and starting SCN of 326779939 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34724 and starting SCN of 326771711 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34723 and starting SCN of 326757052 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34722 and starting SCN of 326739164 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34721 and starting SCN of 326730107 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34720 and starting SCN of 326721606 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34719 and starting SCN of 326718543 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34718 and starting SCN of 326715249 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34717 and starting SCN of 326709503 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34716 and starting SCN of 326693713 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34715 and starting SCN of 326680021 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34714 and starting SCN of 326674022 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34713 and starting SCN of 326664781 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34712 and starting SCN of 326648917 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34711 and starting SCN of 326637659 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34710 and starting SCN of 326633287 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34709 and starting SCN of 326632166 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34708 and starting SCN of 326621042 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34707 and starting SCN of 326617608 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34706 and starting SCN of 326613463 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34705 and starting SCN of 326611471 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34704 and starting SCN of 326610305 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34703 and starting SCN of 326602873 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34702 and starting SCN of 326601517 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34701 and starting SCN of 326593022 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34700 and starting SCN of 326577874 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34699 and starting SCN of 326567243 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34698 and starting SCN of 326553641 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34697 and starting SCN of 326544480 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34696 and starting SCN of 326531815 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34695 and starting SCN of 326528717 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34694 and starting SCN of 326522442 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34693 and starting SCN of 326515260 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34692 and starting SCN of 326504255 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34691 and starting SCN of 326494511 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34690 and starting SCN of 326484165 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34689 and starting SCN of 326475207 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34688 and starting SCN of 326470137 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34687 and starting SCN of 326463888 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34686 and starting SCN of 326456866 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34685 and starting SCN of 326415614 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34684 and starting SCN of 326398980 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34683 and starting SCN of 326385176 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34682 and starting SCN of 326373763 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34681 and starting SCN of 326365337 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34680 and starting SCN of 326352830 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34679 and starting SCN of 326351732 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34678 and starting SCN of 326351526 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34677 and starting SCN of 326351228 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34676 and starting SCN of 326350869 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34675 and starting SCN of 326350236 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34674 and starting SCN of 326344630 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34673 and starting SCN of 326336226 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34672 and starting SCN of 326334353 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34671 and starting SCN of 326332206 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34670 and starting SCN of 326325188 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34669 and starting SCN of 326323615 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34668 and starting SCN of 326317656 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34667 and starting SCN of 326304700 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34666 and starting SCN of 326296332 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34665 and starting SCN of 326283118 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34664 and starting SCN of 326270792 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34653 and starting SCN of 326183189 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34652 and starting SCN of 326175000 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34651 and starting SCN of 326159778 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34650 and starting SCN of 326154245 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34649 and starting SCN of 326148100 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34648 and starting SCN of 326142540 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34647 and starting SCN of 326136812 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34646 and starting SCN of 326124534 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34645 and starting SCN of 326118922 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34644 and starting SCN of 326111890 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34643 and starting SCN of 326108132 found to restore
    RMAN-06025: no backup of archived log for thread 1 with sequence 34642 and starting SCN of 326102908 found to restore
    RMAN-00567: Recovery Manager could not print some error messages
    Recovery Manager complete.

    see metalink note 465558.1
    https://metalink2.oracle.com/metalink/plsql/f?p=130:14:6831911279782618352::::p14_database_id,p14_docid,p14_show_header,p14_show_help,p14_black_frame,p14_font:NOT,465558.1,1,1,1,helveticaKhurram

  • Need some suggestion doing database backup

    Hi All,
    I am working on the 11gR2 RAC oracle database and below are the details.
    SQL>select * from gv$version;
    INST_ID BANNER
    2 Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
    2 PL/SQL Release 11.2.0.1.0 - Production
    2 CORE 11.2.0.1.0 Production
    2 TNS for Linux: Version 11.2.0.1.0 - Production
    2 NLSRTL Version 11.2.0.1.0 - Production
    1 Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
    1 PL/SQL Release 11.2.0.1.0 - Production
    1 CORE 11.2.0.1.0 Production
    1 TNS for Linux: Version 11.2.0.1.0 - Production
    1 NLSRTL Version 11.2.0.1.0 - Production
    3 Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
    3 PL/SQL Release 11.2.0.1.0 - Production
    3 CORE 11.2.0.1.0 Production
    3 TNS for Linux: Version 11.2.0.1.0 - Production
    3 NLSRTL Version 11.2.0.1.0 - Production
    ps -ef|grep pmonoracle 11077 11067 0 10:37 pts/0 00:00:00 grep pmon
    oracle 12383 1 0 2011 ? 00:16:18 ora_pmon_cc2crt2
    oracle 12432 1 0 2011 ? 00:07:43 ora_pmon_cc3crt2
    oracle 12437 1 0 2011 ? 00:07:11 ora_pmon_cc4crt2
    oracle 12814 1 0 2011 ? 00:06:01 ora_pmon_ccoreqal2
    oracle 12816 1 0 2011 ? 00:05:50 ora_pmon_ccorecrt2
    I have 5 databases in these three severs and having around 20 GB of size except one database. The size of the this database (ccoreqal2) is 7.5 TB. I have took the full database backup using expdp for all DB's except the BIG size DB. i am not able to use the expdp because of the size. Which way is best to do the backup for this big size DB.
    The purpose of taking the backup is, we are upgrading our oracle to 11.2.0.3 and We don't have any regular backups (RMAN or EXPORT) on these databases. these are QA databases.
    Please let me know, how i need to prepare for this DB backup.
    Thanks in advance for your help.

    >
    i am not able to use the expdp because of the size
    >
    Why not? You can have expdp create multiple files on export so that each file is no larger than the size you specify. This makes it easier to manage large exports.
    Using multiple files and a parallel export will handle this for you.
    See the DUMPFILE section of the database utilities doc - http://docs.oracle.com/cd/B19306_01/server.102/b14215/dp_export.htm
    It has this example of file splitting using PARALLEL
    >
    Example
    The following is an example of using the DUMPFILE parameter:
    expdp hr/hr SCHEMAS=hr DIRECTORY=dpump_dir1 DUMPFILE=dpump_dir2:exp1.dmp,exp2%U.dmp PARALLEL=3
    The dump file, exp1.dmp, will be written to the path associated with the directory object dpump_dir2 because dpump_dir2 was specified as part of the dump file name, and therefore overrides the directory object specified with the DIRECTORY parameter. Because all three parallel processes will be given work to perform during this job, the exp201.dmp and exp202.dmp dump files will be created and they will be written to the path associated with the directory object, dpump_dir1, that was specified with the DIRECTORY parameter.

  • Daily database backup runnig on RAC 10.2.0.3 with two Solaris nodes & ASM

    Hello,
    I'm confused about making daily incremental RMAN backup of a database runnig on Oracle RAC 10.2.0.3 on two Solaris nodes and ASM.
    Databases cannot be stopped for backup and point in time recovery is needed.
    Please correct me if I am doing wrong:
    1) Backup must be Weekly database Level 0 and Daily database Level 1 is appropriate.
    2) Is best to use a Flash Recovery Area (FRA) - I've setup one on a separate ASM volume. I have enough space to do the backup on FRA.
    3) I am confused about the number channels I need to use. Do I need to use separate RMAN backup channels for each node or I can just leave the default:
    CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
    4) Below are the RMAN scripts I plan to use for
    - Weekly database backup Level 0:
    #!/usr/bin/ksh
    echo BACKUP FULL: $ORACLE_HOME/bin/rman target / nocatalog log ${LOGFILE} append
    $ORACLE_HOME/bin/rman target / nocatalog log ${LOGFILE} append << eof
    run {
    backup incremental level 0 database TAG bkp_level0_200906010;
    SQL 'alter system archive log current';
    backup archivelog all;
    delete noprompt obsolete;
    exit;
    eof
    - Daily database backup Level 1:
    #!/usr/bin/ksh
    echo BACKUP INCREMENTAL: $ORACLE_HOME/bin/rman target / nocatalog log ${LOGFILE} append
    $ORACLE_HOME/bin/rman target / nocatalog log ${LOGFILE} append << eof
    run {
    backup incremental level 1 database TAG bkp_level1_20090611;
    SQL 'alter system archive log current';
    backup archivelog all;
    delete noprompt obsolete;
    exit;
    eof
    I'm I doing things wrong?

    Show also the parameter I have set for RMAN:
    node1:oracle$ rman target /
    Recovery Manager: Release 10.2.0.3.0 - Production on Tue Jun 9 23:46:05 2009
    connected to target database: ORCL (DBID=1198388159)
    RMAN> show all;
    RMAN configuration parameters are:
    CONFIGURE RETENTION POLICY TO REDUNDANCY 7;
    CONFIGURE BACKUP OPTIMIZATION ON;
    CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
    CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
    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 '/u01/oracle/product/10gr2/db/dbs/snapcf_orcl1.f'; # default
    Showing some instance parameters on node1:
    SQL> show parameter recovery;
    NAME                                 TYPE        VALUE
    db_recovery_file_dest                string      DGFRA+
    db_recovery_file_dest_size           big integer 300G
    recovery_parallelism                 integer     0
    SQL> show parameter archive;
    NAME                                 TYPE        VALUE
    archive_lag_target                   integer     0
    log_archive_config                   string
    log_archive_dest                     string
    log_archive_dest_1                   string
    log_archive_dest_10                  string      location=use_db_recovery_file_
    dest
    log_archive_dest_2                   string
    log_archive_dest_3                   string
    log_archive_dest_4                   string
    log_archive_dest_5                   string
    log_archive_dest_6                   string
    NAME                                 TYPE        VALUE
    log_archive_dest_7                   string
    log_archive_dest_8                   string
    log_archive_dest_9                   string
    log_archive_dest_state_1             string      enable
    log_archive_dest_state_10            string      enable
    log_archive_dest_state_2             string      enable
    log_archive_dest_state_3             string      enable
    log_archive_dest_state_4             string      enable
    log_archive_dest_state_5             string      enable
    log_archive_dest_state_6             string      enable
    log_archive_dest_state_7             string      enable
    NAME                                 TYPE        VALUE
    log_archive_dest_state_8             string      enable
    log_archive_dest_state_9             string      enable
    log_archive_duplex_dest              string
    log_archive_format                   string      %t_%s_%r.dbf
    log_archive_local_first              boolean     TRUE
    log_archive_max_processes            integer     2
    log_archive_min_succeed_dest         integer     1
    log_archive_start                    boolean     FALSE
    log_archive_trace                    integer     0
    remote_archive_enable                string      true
    standby_archive_dest                 string      ?/dbs/arch

  • Adding new column to production database

    I have to add a new timestamp column, that defaults to the current date/time, to an existing production database. The table is large - 150M records. I am trying to understand the ramifications of adding a new column to a table this large that gets hit often, mostly with inserts and reads. The column does allow null values and I am not going back and populating existing records with a value. Basically, I am looking for some best practice guidelines - how to prepare, what to expect, what other processes should be followed along with this schema update.

    Radiators wrote:
    Thanks, I have not found any %TYPE or %ROWTYPE dependencies on the table I am altering. But at the same time I do not understand how these types of dependencies would invalidate packages. I wouldn't be breaking any %TYPE dependency because I am not dropping columns, only adding a new one. And according to documentation for %ROWTYPE - "If columns are later added to or dropped from the table, your code can keep working without changes." Can you point me to Oracle documentation that describes your concern in detail? Thanks.you can test it yourself
    SQL> CREATE TABLE abc (c1 NUMBER);
    Table created.
    SQL> INSERT INTO abc
      2       VALUES (99);
    1 row created.
    SQL> CREATE OR REPLACE PROCEDURE test_proc
      2  AS
      3     v   abc%ROWTYPE;
      4  BEGIN
      5     SELECT c1
      6       INTO v
      7       FROM abc
      8       WHERE ROWNUM = 1;
      9  END;
    10  /
    Procedure created.
    SQL> SELECT object_name, status
      2    FROM user_objects
      3   WHERE object_name = 'TEST_PROC';
    OBJECT_NAME                STATUS
    TEST_PROC                    VALID
    SQL> ALTER TABLE abc ADD (c2 VARCHAR2(10));
    Table altered.
    SQL> SELECT object_name, status
      2    FROM user_objects
      3   WHERE object_name = 'TEST_PROC';
    OBJECT_NAME                 STATUS
    TEST_PROC                     INVALID
    SQL> you should also consider the chance that some where if people are using "select * into" using this table, which will fail since you added new column. i don't see any unusual performance bottlenecks by adding a new column. in case of the backups, yes the earlier backups will not have the column. if you restore it, you will see earlier table structure itself. i have one specific question. why are you not attempting this in development/test environment first? even if it is a simple insert, it's always important to do it in test environments before attempting on production db. one thing for sure i know is, after adding column, you will have to recompile all the invalid dependencies. i think, it's better if you attempt it in test db and come up with any issues you see rather than asking a general question where problematic scenarios are plenty and rarely unknown before hand.

  • Full Database Backup in DB13 for MS SQL Server databases

    Hello,
    We have some SAP systems using the MS SQL Server database. I want to know if it is possible to setup the Full Database Backup option in transaction DB13 to store the files in a hard disk space.
    I already did this type of configuration in SAP systems in Oracle databases and for this I used the init<SID>.sap where we can put all the configuration, for instance the disk path where we want to save the backup files! But for MS SQL Server databases, in DB13, I don´t know how to do that, when I add the "Full Database Backup" option in DB13, this show me some options but only for tape, but I don´t want to store the backup files in tapes, I want to store/save the files on the server disk itself or else to an external disk but I don´t see where I can set this way of storage!
    This is what you see in DB13 (when using a MS SQL Server database) in "Full Database Backup" and as you see I only have options for TAPE not for a disk or other type of storage! How can I do that? (if that is possible):
    Can you help me please?
    Kind regards,
    samid raif

    Hello Raja
    Sorry for the delay of my answer! Many thanks for that tip, it helps a lot and it solve the last error/problem that I reported here, in fact, the problem was we had named the device with two words containing a space. So we removed that space from the backup device (in SQL management studio) with one word only and the job runs successfully without any errors!
    It works in Development and Quality systems but in our Production system (AM1) the Full backup option in DB13 stopped with the following error, in fact the error is on verification of backup, it means that the Full backup finished with success, but when it does the backup verification, the job in DB13 stops with an error, the following one:
    ***************************** SQL Job information   ******************************
    Jobname:    SAP CCMS Full DB Backup of AM1 [20140417103726-4-103726]
    Type:       TSQL
    DB-Name:    AM1
    For Run:    20140417  10:37:26
    **************************** Job history information  *****************************
    Stepname:   CCMS-step 1
    Command:    declare @exeStmt nvarchar(2000) exec am1.sap_backup_databases @dbList=
                "AM1",@r3Db="AM1",@bDev="fullprd",@expDays= 27,@jobName= "SAP CCMS Ful
                l DB Backup of AM1 [20140417103726-4-103726]",@bkupChecksum="Y",@bkupT
                ype="F",@nativeBkup="N",@exeDate = "20140417103726",@bkupSim = "N",@fo
                rmat = 0,@init = 0,@bkupDb = "AM1",@unload = 0,@exeStmt = @exeStmt OUT
                PUT
    Status:     (success)
    Message:    3014
    Severity:                                                                                                                                                                                                                                                    0
    Duration:   4  hours(s)  41 min(s) 22 sec(s)
    Last msg:   Executed as user: am1. Processed 7434328 pages for database 'AM1', fil
                e 'A01DATA1' on file 1. [SQLSTATE 01000] (Message 4035)  Processed 315
                1504 pages for database 'AM1', file 'A01DATA2' on file 1. [SQLSTATE 01
                000] (Message 4035)  Processed 4574152 pages for database 'AM1', file
                'A01DATA3' on file 1. [SQLSTATE 01000] (Message 4035)  Processed 44363
                92 pages for database 'AM1', file 'A01DATA4' on file 1. [SQLSTATE 0100
                0] (Message 4035)  Processed 25598 pages for database 'AM1', file 'A01
                LOG1' on file 1. [SQLSTATE 01000] (Message 4035)  BACKUP DATABASE succ
                essfully processed 19621974 pages in 16881.638 seconds (9.521 MB/sec).
                 [SQLSTATE 01000] (Message 3014).  The step succeeded.
                        <------------- End of Job Step History --------------->
    Stepname:   CCMS-step 2
    Command:    declare @exeStmt nvarchar(2000) exec am1.sap_verify_backups @nativeBku
                p = "N",@bkupSim = "N",@bDev = "fullprd",@bkupChecksum = "Y",@exeDate
                = "20140417103726",@unload = 1,@dbCnt =1,@exeStmt = @exeStmt OUTPUT
    Status:     (failure)
    Message:    3201
    Severity:                                                                                                                                                                                                                                                   16
    Duration:   0  hours(s)  8  min(s) 30 sec(s)
    Last msg:   Executed as user: am1. Cannot open backup device 'fullprd(\\10.0.0.45\
                backupsap\prd\prdfullqua.bak)'. Operating system error 1265(error not
                found). [SQLSTATE 42000] (Error 3201).  The step failed.
                        <------------- End of Job Step History --------------->
    **************************** Job history information  *****************************
    Can you help me please with this one!? Can you tell me why in verification it stops with that error?
    Kind regards,
    samid raif

  • Create Primary Database from DR database backup

    Hi Experts
    I got the requirement as follows:
    Build Production database using DR backup.
    When I am creating the Production database(Primary Database),I tried with the Duplicate command to create the primary database using DR backup.It is failing at the control file creation.
    Script used:
    I am executing this script on Primary server:
    Rman target sys/***@DR auxiliary /
    run
    allocate channel c1 device type disk sbt_tape;
    allocate channel c2 device type disk sbt_tape;
    NB_ora_client...,nb_ora_policy.....,
    dupilicate target database to PR;
    relaease channel c1;
    exit
    So can any body tell me is there any way to create the Primary Database from DR backup.
    Also please refer me to some documents in cloning the Primary database from production database.
    Thanks
    Veera

    Please note that "So can any body tell me is there any way to create the Primary Database from DR backup" this is with Duplicate command.
    I know how to do with Restore command.If some body refers to the Documentation using Restore database is also highly appreciated.
    Thanks in advance
    Veera

  • Severe performance issues in production database

    Hi Experts,
    we have configured RMAN in our production database recently using some 3 party tool COMMVAULT.
    Problem is just 47 GB database taking around 6 hrs of time to complted the bakcup job. Please let me know what could be the reason.
    Further to this issues i found out some of few things, our application vendor commissioned this database server and it seems that they done some changes in TIMEZONE settings.
    when i query against some of few dictionary tables for example dba_schedular_jobs i am getting the following error.
    ORA-01882: timezone region %s not found
    when ever i connect the database , the connection itself is very slow and suffering severe performance issues in my production database.
    You help would be much appreciated.
    Regards,
    Salai

    Hi,
    also let us know if you use asm or local file system for datafiles.
    Your backup strategy will also be helpful:
    Do you make compressed backups?
    Full or incremental?
    To where do you backup the database? To the local filesystem, SAN Volume, Offsite Storage, Tape storage?
    Is there any other jobs running while the RMAN job is running?
    Please post the stats that you have gathered over the time period when the backup is running.
    Thanks.

  • Estimate database backup size

    Hi All,
    AIX 5.3
    oracle 10.2.0.3
    I have production database of 80 GB. I want to take a cold backup during the upgrade process. Now i want to know database backup size. so we can free space from some mount point accordingly.
    Is there any way to estimate database backup size?
    Thanks,
    Vishal

    Question: how did you establish that your database is actually 80G?
    Is that 80G of data in the database, or is it the sum of all data files, temp tablespace files, undo tablespace files, redo logs, oracle binary software files, control files, etc?
    If you intend to do an upgrade of the software, my recommendation is to shut the database down and do a full copy of:
    1) your entire oracle product tree (usually /oracle/product), including ORACLE_HOME.
    2) your entire 'oradata' structure which (should) include all of your Oracle database data files and all other associated files.

  • Urgent -- need to restore table from full database backup

    Hello,
    Can somebody tell me the process for restoring just a table from a full database backup?
    I did a full online database backup yesterday, and one of my tables got ruined today. I need to restore it as soon as possible, but I don't know how. When I tried flashback tables, it said that feature wasn't enabled. Should I restore the datafile or the tablespace?
    Thanks much,
    Nora

    If you only want to recover the table and not the other objects in the tablespace, and assuming the table was damaged by a user statement (and not, say, block corruption), you would need to recover your backup to a different system, export the table that was damaged, and import the table into your real production database. If you can recover the entire tablespace to an earlier point in time, or if you can lose some committed changes to other database objects, you may have other options.
    Justin
    Distributed Database Consulting, Inc.
    http://www.ddbcinc.com/askDDBC

  • Logical Database Backup

    Hi All,
    I Want to take Backup of my Schema (Using EXP ,Logical backup?) .i want only 10 Rows data for each table in my new schema.
    Can anyone tell how to do that .
    Thanks in Advance..

    What is the business purpose of trying to backup 1% of the data?
    If you care about the data, you would be doing a full physical database backup to protect all the data. Or you would at least be exporting all the data in particular tables to protect against human errors (i.e. deleting all the data in a table in production rather than development accidentally).
    If you don't care about the data, and you are just interested in the schema definition, you should be ignoring the data.
    I cannot imagine a backup and recovery scenario where having 1% of the data in your backup would be useful. If you are trying to create a smaller version of your production environment for development (i.e. you are not treating this as a backup, but an extract), there are commercial tools out there that can generate relationally consistent extracts of a few percent of the data in your database-- those would be far preferrable to trying to build your own via export.
    Justin

  • Database backup strategy(MS sql server 2005, Winodws 2003, SAP ECC 6.00)

    Hello gurus,
        I am confused, about the backup system i should go for(backup device, abckup software)?? Fllowing is my SAP Landscape.
    1) IDES
    2) Solution manager
    3) Development
    4) BIW
    no of users 25 max
    modules implemented
    MM
    HR
    FICO
    BIW
    <b>    I want to implemente before go live, backup system in my company.</b>
    We have received backup schedule from our implementation partner. Our backup system is as follows.
    Backup device is HP Surestore Autoloader.
    Cartridge capacity is 100/200GB
    Backup software is Veritas (version 8.6)
    Note: Through this we take backup of our legacy system and it takes around 3 1/2 hour to 4 hours to take backup of 60 GB of our legacy data.
         Right now the problem is our backup software version is old and i even believe, the hardware we have is not sufficient to take daily database backup and fortnightly, SAP system backup.
        The only solution to the problem i can see is
    1) to go for another backup device exclusively for SAP system
    2) Even go for SQL Agent software used to take backup of SAP system thorugh Veritas.
    3) Even upgrade my Veritas version.
    <b>   Its a request to GURUS</b>
    1) Is the solution, i am thinking to this issue is correct.?? If no then please advice me
    2) Please tell me the best backup system in your opinion for my above mentioned system.
    Thanks Gurus
    Rahul

    Hello,
    A indication of the size of each database would be helpful.
    However, its NOT a good idea to take only one on line backup a week. What if you have a tape error and cant recover a TL? You have no chance for recovery. This is not best practice. Can the business except a 4,5 or even 6 days loss of data - id guess not.
    This is what id do if you don't want to purchase a new device, I would take an online backups from SQL to disk every night - this would be a separate disk! From the disk you can the pick up the backup to take at a time to suit that wont impact the existing backup. Plus you always have two copies of the backup. One on disk, one on tape.
    My normal transaction log strategy is similar, again backup to disk, every hour on a production system. Then after midnight move the existing 24 logs into an archive folder. This folder would also be picked up by the existing device at a suitable time before being moved to a 'saved' folder and deleted the next day. Again you always have multiple copies of the data. two on disk, two on tape.

Maybe you are looking for