Sybase cumulative backup vs traditional log backup

In ASE 15.7 SP100 or higher versions, cumulative backups are supported. My question is, can both cumulative backup and log backup run at the same time for a database?
For example, say, at time t1, we have a completed full backup (full1) of database foo, and
at time t2, we have the first log backup completed, log1.
Now, a cumulative backup is running, and another log backup (log2) starts, and finishes at time t3 while the cumulative backup is still running.
The cumulative backup (cml1) finishes at time t4.
Another log backup (log3) finishes at time t5.
Is it a valid scenario (to let log2 and cml1 run at the same time), or does an application (which performs Sybase backups using 3rd party API) need to prevent such concurrent cumulative and log backups?
If it is valid to run both concurrently (does not result in data corruption), then
to restore the database up to a time between t2 and t3, we will use full1 + log1 + log2 upto the target time.
to restore the database up to a time between t4 and t5, we will use full1 + cml1 + log3 upto the target time.
Please correct me if I am wrong.
Thanks,
Ali

Dear Mr Razib,
full dump and transaction log dump
full, cumulative dump and transaction log dump
Both of these approaches are ok and will allow you to restore a database including rollforward of transaction to the desired point in time. (cumulative dumps only will not work of course, you always need a full dump as a starting point). These backup strategies are suitable for a production system.
Wheras these backup strategies :
full dump and cumulative dump
multiple full dumps
are ok and supported , too, but it will not allow you to restore a database to any desired point in time. The point of recovery will in any case be the time of the last full or cumulative dump.
Taking only database dumps (full or cumulative) is propbaly not suitable for production systems. But this is a decision the system owner has to take.
With kind regards
Tilman Model-Bosch

Similar Messages

  • Which Backup server version is required for Sybase cumulative dump/load

    Hello,
    To perform cumulative dump and load (supported from ASE 15.7 SP100 and up) with 3rd party API, what backup server version is needed?
    We use backup server API version 2.1, and sybackup.h does not have any definition for cumulative dump. This header file only defines DATABASE and TRANSACTION as command_type, so when "dump database foo cumulative" is issued, command_type becomes UNKNOWN.
    Since we support all the ASE versions from 15.0.3 and up, we ideally need a backup server API that works for ASE versions from 15.0.3 and also works with cumulative backup. Is there such an API version?
    Thanks,
    Ali

    What I'm told is that the version wasn't bumped because the changes shouldn't really affect the API functionality; the API module would still receive a byte stream and be able to store and return it regardless of the command_type.
    However, you can easily modify your sybbackup.h to reflect the new command_types.
    Replace the current command_type definitions with the following:
    #define TRANSACTION 0 /* transaction log dump or load */
    #define DATABASE 1 /* database dump or load */
    #define CUMULATIVE 2 /* Cumulative dump to dump or load */
    #define UNKNOWN 3 /* Pre-API SQL Server in use. Backup Server
                         has received a DUMP/LOAD command from a
                         SQL Server which is not passing the
                         'Command Type' toBackup Server. Therefore,
                         the Command type can not be determined. */
    #define DELTA 4 /* Delta dump to dump or load */

  • Retention policy for incremental cumulative backup question

    Hi,
    I have a production database configured with retention policy for 30 days window. No catalog is used.
    The backup plan is:
    Sunday - Level 0 backup.
    Weekdays - Incremental 1 cumulative backup.
    I also noticed that some archive logs since Mar 07 2010 has become obsolete in the recent few days.
    Cannot figure out why the backup of Mar 07 2010 is going to be obsolete today.
    Thanks for your help!
    RMAN> list backup summary;
    using target database control file instead of recovery catalog
    List of Backups
    ===============
    Key TY LV S Device Type Completion Time #Pieces #Copies Compressed
    *14 B 0 A SBT_TAPE 07-MAR-10 5 1 NO*
    *15 B 0 A SBT_TAPE 07-MAR-10 5 1 NO*
    *17 B F A SBT_TAPE 07-MAR-10 1 1 NO*
    21 B F A SBT_TAPE 08-MAR-10 1 1 NO
    24 B 1 A SBT_TAPE 08-MAR-10 1 1 NO
    25 B 1 A SBT_TAPE 08-MAR-10 1 1 NO
    27 B F A SBT_TAPE 08-MAR-10 1 1 NO
    35 B 1 A SBT_TAPE 09-MAR-10 1 1 NO
    36 B 1 A SBT_TAPE 09-MAR-10 1 1 NO
    38 B F A SBT_TAPE 09-MAR-10 1 1 NO
    46 B 1 A SBT_TAPE 10-MAR-10 1 1 NO
    47 B 1 A SBT_TAPE 10-MAR-10 1 1 NO
    49 B F A SBT_TAPE 10-MAR-10 1 1 NO
    57 B 1 A SBT_TAPE 11-MAR-10 1 1 NO
    58 B 1 A SBT_TAPE 11-MAR-10 2 1 NO
    60 B F A SBT_TAPE 11-MAR-10 1 1 NO
    66 B A A SBT_TAPE 12-MAR-10 1 1 NO
    67 B A A SBT_TAPE 12-MAR-10 1 1 NO
    68 B 1 A SBT_TAPE 12-MAR-10 1 1 NO
    69 B 1 A SBT_TAPE 12-MAR-10 2 1 NO
    70 B A A SBT_TAPE 12-MAR-10 1 1 NO
    71 B F A SBT_TAPE 12-MAR-10 1 1 NO
    77 B A A SBT_TAPE 14-MAR-10 1 1 NO
    78 B A A SBT_TAPE 14-MAR-10 1 1 NO
    79 B 0 A SBT_TAPE 14-MAR-10 6 1 NO
    80 B 0 A SBT_TAPE 14-MAR-10 6 1 NO
    81 B A A SBT_TAPE 14-MAR-10 1 1 NO
    82 B F A SBT_TAPE 14-MAR-10 1 1 NO
    88 B A A SBT_TAPE 15-MAR-10 1 1 NO
    89 B A A SBT_TAPE 15-MAR-10 1 1 NO
    90 B 1 A SBT_TAPE 15-MAR-10 1 1 NO
    91 B 1 A SBT_TAPE 15-MAR-10 1 1 NO
    92 B A A SBT_TAPE 15-MAR-10 1 1 NO
    93 B F A SBT_TAPE 15-MAR-10 1 1 NO
    99 B A A SBT_TAPE 16-MAR-10 1 1 NO
    100 B A A SBT_TAPE 16-MAR-10 1 1 NO
    101 B 1 A SBT_TAPE 16-MAR-10 1 1 NO
    102 B 1 A SBT_TAPE 16-MAR-10 1 1 NO
    103 B A A SBT_TAPE 16-MAR-10 1 1 NO
    104 B F A SBT_TAPE 16-MAR-10 1 1 NO
    109 B A A SBT_TAPE 17-MAR-10 4 1 NO
    110 B F A SBT_TAPE 17-MAR-10 1 1 NO
    111 B A A SBT_TAPE 17-MAR-10 1 1 NO
    112 B F A SBT_TAPE 17-MAR-10 1 1 NO
    113 B A A SBT_TAPE 17-MAR-10 1 1 NO
    114 B A A SBT_TAPE 17-MAR-10 1 1 NO
    115 B 1 A SBT_TAPE 17-MAR-10 1 1 NO
    116 B 1 A SBT_TAPE 17-MAR-10 2 1 NO
    117 B A A SBT_TAPE 17-MAR-10 1 1 NO
    118 B F A SBT_TAPE 17-MAR-10 1 1 NO
    123 B A A SBT_TAPE 18-MAR-10 2 1 NO
    124 B F A SBT_TAPE 18-MAR-10 1 1 NO
    125 B A A SBT_TAPE 18-MAR-10 2 1 NO
    126 B F A SBT_TAPE 18-MAR-10 1 1 NO
    127 B A A SBT_TAPE 18-MAR-10 1 1 NO
    128 B F A SBT_TAPE 18-MAR-10 1 1 NO
    129 B A A SBT_TAPE 18-MAR-10 1 1 NO
    130 B F A SBT_TAPE 18-MAR-10 1 1 NO
    131 B A A SBT_TAPE 18-MAR-10 1 1 NO
    132 B A A SBT_TAPE 18-MAR-10 1 1 NO
    133 B 1 A SBT_TAPE 18-MAR-10 1 1 NO
    134 B 1 A SBT_TAPE 18-MAR-10 2 1 NO
    135 B A A SBT_TAPE 18-MAR-10 1 1 NO
    136 B F A SBT_TAPE 18-MAR-10 1 1 NO
    142 B A A SBT_TAPE 19-MAR-10 2 1 NO
    143 B F A SBT_TAPE 19-MAR-10 1 1 NO
    144 B A A SBT_TAPE 19-MAR-10 1 1 NO
    145 B F A SBT_TAPE 19-MAR-10 1 1 NO
    146 B A A SBT_TAPE 19-MAR-10 1 1 NO
    147 B F A SBT_TAPE 19-MAR-10 1 1 NO
    148 B A A SBT_TAPE 19-MAR-10 1 1 NO
    149 B F A SBT_TAPE 19-MAR-10 1 1 NO
    150 B A A SBT_TAPE 19-MAR-10 1 1 NO
    151 B A A SBT_TAPE 19-MAR-10 1 1 NO
    152 B 1 A SBT_TAPE 19-MAR-10 1 1 NO
    153 B 1 A SBT_TAPE 19-MAR-10 2 1 NO
    154 B A A SBT_TAPE 19-MAR-10 1 1 NO
    155 B F A SBT_TAPE 19-MAR-10 1 1 NO
    161 B A A SBT_TAPE 21-MAR-10 1 1 NO
    162 B 0 A SBT_TAPE 21-MAR-10 6 1 NO
    163 B 0 A SBT_TAPE 21-MAR-10 6 1 NO
    164 B A A SBT_TAPE 21-MAR-10 1 1 NO
    165 B F A SBT_TAPE 21-MAR-10 1 1 NO
    171 B A A SBT_TAPE 22-MAR-10 1 1 NO
    172 B F A SBT_TAPE 22-MAR-10 1 1 NO
    173 B A A SBT_TAPE 22-MAR-10 1 1 NO
    174 B F A SBT_TAPE 22-MAR-10 1 1 NO
    RMAN> show all;
    RMAN configuration parameters are:
    CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 30 DAYS;
    CONFIGURE BACKUP OPTIMIZATION ON;
    CONFIGURE DEFAULT DEVICE TYPE TO 'SBT_TAPE';
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE 'SBT_TAPE' TO '%F';
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
    CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 2 BACKUP TYPE TO BACKUPSET;
    CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
    CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
    CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE 'SBT_TAPE' TO 1;
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' PARMS 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt.ccbprod)' FORMAT '%d_inc_%T_%t_%U' MAXPIECESIZE 4608 M;
    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 '/orasw/app/oracle/product/10.2.0/dbs/snapcf_ccbprod.f'; # default
    RMAN> report obsolete;
    RMAN retention policy will be applied to the command
    RMAN retention policy is set to recovery window of 30 days
    Report of obsolete backups and copies
    Type Key Completion Time Filename/Handle
    Control File Copy 108 19-FEB-10 /ccbprod/oradata/ccbprod/arc/control.bak.100219.21.21
    Backup Set           8      07-MAR-10                                                                                     Backup Piece       19     07-MAR-10          CCBPROD_inc_20100307_713034799_07l8031f_5_1
    Backup Set           8      07-MAR-10                                                                                     Backup Piece       18     07-MAR-10          CCBPROD_inc_20100307_713034799_07l8031f_4_1
    Backup Set           8      07-MAR-10                                                                                     Backup Piece       17     07-MAR-10          CCBPROD_inc_20100307_713034799_07l8031f_3_1
    Backup Set           8      07-MAR-10                                                                                     Backup Piece       16     07-MAR-10          CCBPROD_inc_20100307_713034799_07l8031f_2_1
    Backup Set           8      07-MAR-10                                                                                     Backup Piece       15     07-MAR-10          CCBPROD_inc_20100307_713034799_07l8031f_1_1
    Backup Set           7      07-MAR-10                                                                                     Backup Piece       14     07-MAR-10          CCBPROD_inc_20100307_713034799_08l8031f_5_1
    Backup Set           7      07-MAR-10                                                                                     Backup Piece       13     07-MAR-10          CCBPROD_inc_20100307_713034799_08l8031f_4_1
    Backup Set           7      07-MAR-10                                                                                     Backup Piece       12     07-MAR-10          CCBPROD_inc_20100307_713034799_08l8031f_3_1
    Backup Set           7      07-MAR-10                                                                                     Backup Piece       11     07-MAR-10          CCBPROD_inc_20100307_713034799_08l8031f_2_1
    Backup Set           7      07-MAR-10                                                                                     Backup Piece       10     07-MAR-10          CCBPROD_inc_20100307_713034799_08l8031f_1_1
    Backup Set 10 07-MAR-10 Backup Piece 21 07-MAR-10 c-2894189962-20100307-00
    Edited by: user12019850 on 22-Mar-2010 10:53 AM

    Another database with the same configuration and same plan seems fine:
    RMAN> show all;
    using target database control file instead of recovery catalog
    RMAN configuration parameters are:
    CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 30 DAYS;
    CONFIGURE BACKUP OPTIMIZATION ON;
    CONFIGURE DEFAULT DEVICE TYPE TO 'SBT_TAPE';
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE 'SBT_TAPE' TO '%F';
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
    CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 2 BACKUP TYPE TO BACKUPSET;
    CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
    CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
    CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE 'SBT_TAPE' TO 1;
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
    CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' PARMS 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt.cisconf)' FORMAT '%d_inc_%T_%t_%U' MAXPIECESIZE 4608 M;
    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 '/orasw/app/oracle/product/10.2.0/dbs/snapcf_cisconf.f'; # default
    RMAN> list backup summary;
    List of Backups
    ===============
    Key TY LV S Device Type Completion Time #Pieces #Copies Compressed
    774 B 0 A SBT_TAPE 19-FEB-10 1 1 NO
    775 B 0 A SBT_TAPE 19-FEB-10 2 1 NO
    795 B 1 A SBT_TAPE 20-FEB-10 1 1 NO
    796 B 1 A SBT_TAPE 20-FEB-10 1 1 NO
    797 B A A SBT_TAPE 20-FEB-10 1 1 NO
    803 B A A SBT_TAPE 20-FEB-10 1 1 NO
    804 B F A SBT_TAPE 20-FEB-10 1 1 NO
    805 B A A SBT_TAPE 20-FEB-10 1 1 NO
    806 B F A SBT_TAPE 20-FEB-10 1 1 NO
    807 B A A SBT_TAPE 20-FEB-10 1 1 NO
    808 B F A SBT_TAPE 20-FEB-10 1 1 NO
    809 B A A SBT_TAPE 21-FEB-10 1 1 NO
    810 B 0 A SBT_TAPE 21-FEB-10 1 1 NO
    811 B 0 A SBT_TAPE 21-FEB-10 2 1 NO
    812 B A A SBT_TAPE 21-FEB-10 1 1 NO
    813 B F A SBT_TAPE 21-FEB-10 1 1 NO
    818 B A A SBT_TAPE 21-FEB-10 1 1 NO
    819 B F A SBT_TAPE 21-FEB-10 1 1 NO
    820 B A A SBT_TAPE 21-FEB-10 1 1 NO
    821 B F A SBT_TAPE 21-FEB-10 1 1 NO
    822 B A A SBT_TAPE 21-FEB-10 1 1 NO
    823 B F A SBT_TAPE 21-FEB-10 1 1 NO
    824 B A A SBT_TAPE 22-FEB-10 1 1 NO
    825 B 1 A SBT_TAPE 22-FEB-10 1 1 NO
    826 B 1 A SBT_TAPE 22-FEB-10 1 1 NO
    827 B A A SBT_TAPE 22-FEB-10 1 1 NO
    828 B F A SBT_TAPE 22-FEB-10 1 1 NO
    833 B A A SBT_TAPE 22-FEB-10 1 1 NO
    834 B F A SBT_TAPE 22-FEB-10 1 1 NO
    835 B A A SBT_TAPE 22-FEB-10 1 1 NO
    836 B F A SBT_TAPE 22-FEB-10 1 1 NO
    837 B A A SBT_TAPE 22-FEB-10 1 1 NO
    838 B F A SBT_TAPE 22-FEB-10 1 1 NO
    839 B A A SBT_TAPE 22-FEB-10 1 1 NO
    840 B F A SBT_TAPE 22-FEB-10 1 1 NO
    841 B A A SBT_TAPE 23-FEB-10 1 1 NO
    842 B 1 A SBT_TAPE 23-FEB-10 1 1 NO
    843 B 1 A SBT_TAPE 23-FEB-10 1 1 NO
    844 B A A SBT_TAPE 23-FEB-10 1 1 NO
    845 B F A SBT_TAPE 23-FEB-10 1 1 NO
    850 B A A SBT_TAPE 23-FEB-10 1 1 NO
    851 B F A SBT_TAPE 23-FEB-10 1 1 NO
    852 B A A SBT_TAPE 23-FEB-10 1 1 NO
    853 B F A SBT_TAPE 23-FEB-10 1 1 NO
    854 B A A SBT_TAPE 23-FEB-10 1 1 NO
    855 B F A SBT_TAPE 23-FEB-10 1 1 NO
    856 B A A SBT_TAPE 24-FEB-10 1 1 NO
    857 B 1 A SBT_TAPE 24-FEB-10 1 1 NO
    858 B 1 A SBT_TAPE 24-FEB-10 1 1 NO
    859 B A A SBT_TAPE 24-FEB-10 1 1 NO
    860 B F A SBT_TAPE 24-FEB-10 1 1 NO
    865 B A A SBT_TAPE 24-FEB-10 1 1 NO
    866 B F A SBT_TAPE 24-FEB-10 1 1 NO
    867 B A A SBT_TAPE 24-FEB-10 1 1 NO
    868 B F A SBT_TAPE 24-FEB-10 1 1 NO
    869 B A A SBT_TAPE 24-FEB-10 1 1 NO
    870 B F A SBT_TAPE 24-FEB-10 1 1 NO
    871 B A A SBT_TAPE 24-FEB-10 1 1 NO
    872 B 1 A SBT_TAPE 24-FEB-10 1 1 NO
    873 B 1 A SBT_TAPE 24-FEB-10 1 1 NO
    874 B A A SBT_TAPE 24-FEB-10 1 1 NO
    875 B F A SBT_TAPE 24-FEB-10 1 1 NO
    880 B A A SBT_TAPE 24-FEB-10 1 1 NO
    881 B F A SBT_TAPE 24-FEB-10 1 1 NO
    882 B A A SBT_TAPE 25-FEB-10 1 1 NO
    883 B 1 A SBT_TAPE 25-FEB-10 1 1 NO
    884 B 1 A SBT_TAPE 25-FEB-10 1 1 NO
    885 B A A SBT_TAPE 25-FEB-10 1 1 NO
    886 B F A SBT_TAPE 25-FEB-10 1 1 NO
    891 B A A SBT_TAPE 25-FEB-10 1 1 NO
    892 B F A SBT_TAPE 25-FEB-10 1 1 NO
    893 B A A SBT_TAPE 25-FEB-10 1 1 NO
    894 B F A SBT_TAPE 25-FEB-10 1 1 NO
    895 B A A SBT_TAPE 25-FEB-10 1 1 NO
    896 B F A SBT_TAPE 25-FEB-10 1 1 NO
    897 B A A SBT_TAPE 25-FEB-10 1 1 NO
    898 B F A SBT_TAPE 25-FEB-10 1 1 NO
    899 B A A SBT_TAPE 25-FEB-10 1 1 NO
    900 B F A SBT_TAPE 25-FEB-10 1 1 NO
    901 B A A SBT_TAPE 25-FEB-10 1 1 NO
    902 B F A SBT_TAPE 25-FEB-10 1 1 NO
    903 B A A SBT_TAPE 26-FEB-10 1 1 NO
    904 B 1 A SBT_TAPE 26-FEB-10 1 1 NO
    905 B 1 A SBT_TAPE 26-FEB-10 1 1 NO
    906 B A A SBT_TAPE 26-FEB-10 1 1 NO
    907 B F A SBT_TAPE 26-FEB-10 1 1 NO
    912 B A A SBT_TAPE 26-FEB-10 1 1 NO
    913 B F A SBT_TAPE 26-FEB-10 1 1 NO
    914 B A A SBT_TAPE 26-FEB-10 1 1 NO
    915 B F A SBT_TAPE 26-FEB-10 1 1 NO
    916 B A A SBT_TAPE 26-FEB-10 1 1 NO
    917 B F A SBT_TAPE 26-FEB-10 1 1 NO
    918 B A A SBT_TAPE 27-FEB-10 1 1 NO
    919 B 1 A SBT_TAPE 27-FEB-10 1 1 NO
    920 B 1 A SBT_TAPE 27-FEB-10 1 1 NO
    921 B A A SBT_TAPE 27-FEB-10 1 1 NO
    922 B F A SBT_TAPE 27-FEB-10 1 1 NO
    927 B A A SBT_TAPE 27-FEB-10 1 1 NO
    928 B F A SBT_TAPE 27-FEB-10 1 1 NO
    929 B A A SBT_TAPE 27-FEB-10 1 1 NO
    930 B F A SBT_TAPE 27-FEB-10 1 1 NO
    931 B A A SBT_TAPE 27-FEB-10 1 1 NO
    932 B F A SBT_TAPE 27-FEB-10 1 1 NO
    933 B A A SBT_TAPE 28-FEB-10 1 1 NO
    934 B 0 A SBT_TAPE 28-FEB-10 1 1 NO
    935 B 0 A SBT_TAPE 28-FEB-10 2 1 NO
    936 B A A SBT_TAPE 28-FEB-10 1 1 NO
    937 B F A SBT_TAPE 28-FEB-10 1 1 NO
    942 B A A SBT_TAPE 28-FEB-10 1 1 NO
    943 B F A SBT_TAPE 28-FEB-10 1 1 NO
    944 B A A SBT_TAPE 28-FEB-10 1 1 NO
    945 B F A SBT_TAPE 28-FEB-10 1 1 NO
    946 B A A SBT_TAPE 28-FEB-10 1 1 NO
    947 B F A SBT_TAPE 28-FEB-10 1 1 NO
    948 B A A SBT_TAPE 01-MAR-10 1 1 NO
    949 B 1 A SBT_TAPE 01-MAR-10 1 1 NO
    950 B 1 A SBT_TAPE 01-MAR-10 1 1 NO
    951 B A A SBT_TAPE 01-MAR-10 1 1 NO
    952 B F A SBT_TAPE 01-MAR-10 1 1 NO
    957 B A A SBT_TAPE 01-MAR-10 1 1 NO
    958 B F A SBT_TAPE 01-MAR-10 1 1 NO
    959 B A A SBT_TAPE 01-MAR-10 1 1 NO
    960 B F A SBT_TAPE 01-MAR-10 1 1 NO
    961 B A A SBT_TAPE 01-MAR-10 1 1 NO
    962 B F A SBT_TAPE 01-MAR-10 1 1 NO
    963 B A A SBT_TAPE 02-MAR-10 1 1 NO
    964 B 1 A SBT_TAPE 02-MAR-10 1 1 NO
    965 B 1 A SBT_TAPE 02-MAR-10 1 1 NO
    966 B A A SBT_TAPE 02-MAR-10 1 1 NO
    967 B F A SBT_TAPE 02-MAR-10 1 1 NO
    970 B A A SBT_TAPE 02-MAR-10 1 1 NO
    971 B F A SBT_TAPE 02-MAR-10 1 1 NO
    972 B A A SBT_TAPE 02-MAR-10 1 1 NO
    973 B F A SBT_TAPE 02-MAR-10 1 1 NO
    974 B A A SBT_TAPE 02-MAR-10 1 1 NO
    975 B F A SBT_TAPE 02-MAR-10 1 1 NO
    976 B A A SBT_TAPE 03-MAR-10 1 1 NO
    977 B 1 A SBT_TAPE 03-MAR-10 1 1 NO
    978 B 1 A SBT_TAPE 03-MAR-10 1 1 NO
    979 B A A SBT_TAPE 03-MAR-10 1 1 NO
    980 B F A SBT_TAPE 03-MAR-10 1 1 NO
    983 B A A SBT_TAPE 03-MAR-10 1 1 NO
    984 B F A SBT_TAPE 03-MAR-10 1 1 NO
    985 B A A SBT_TAPE 03-MAR-10 1 1 NO
    986 B F A SBT_TAPE 03-MAR-10 1 1 NO
    987 B A A SBT_TAPE 03-MAR-10 1 1 NO
    988 B F A SBT_TAPE 03-MAR-10 1 1 NO
    989 B A A SBT_TAPE 04-MAR-10 1 1 NO
    990 B 1 A SBT_TAPE 04-MAR-10 1 1 NO
    991 B 1 A SBT_TAPE 04-MAR-10 1 1 NO
    992 B A A SBT_TAPE 04-MAR-10 1 1 NO
    993 B F A SBT_TAPE 04-MAR-10 1 1 NO
    996 B A A SBT_TAPE 04-MAR-10 1 1 NO
    997 B F A SBT_TAPE 04-MAR-10 1 1 NO
    998 B A A SBT_TAPE 04-MAR-10 1 1 NO
    999 B F A SBT_TAPE 04-MAR-10 1 1 NO
    1000 B A A SBT_TAPE 04-MAR-10 1 1 NO
    1001 B F A SBT_TAPE 04-MAR-10 1 1 NO
    1002 B A A SBT_TAPE 05-MAR-10 1 1 NO
    1003 B 1 A SBT_TAPE 05-MAR-10 1 1 NO
    1004 B 1 A SBT_TAPE 05-MAR-10 1 1 NO
    1005 B A A SBT_TAPE 05-MAR-10 1 1 NO
    1006 B F A SBT_TAPE 05-MAR-10 1 1 NO
    1009 B A A SBT_TAPE 05-MAR-10 1 1 NO
    1010 B F A SBT_TAPE 05-MAR-10 1 1 NO
    1011 B A A SBT_TAPE 05-MAR-10 1 1 NO
    1012 B F A SBT_TAPE 05-MAR-10 1 1 NO
    1013 B A A SBT_TAPE 05-MAR-10 1 1 NO
    1014 B F A SBT_TAPE 05-MAR-10 1 1 NO
    1015 B A A SBT_TAPE 06-MAR-10 1 1 NO
    1016 B 1 A SBT_TAPE 06-MAR-10 1 1 NO
    1017 B 1 A SBT_TAPE 06-MAR-10 1 1 NO
    1018 B A A SBT_TAPE 06-MAR-10 1 1 NO
    1019 B F A SBT_TAPE 06-MAR-10 1 1 NO
    1022 B A A SBT_TAPE 07-MAR-10 1 1 NO
    1023 B 0 A SBT_TAPE 07-MAR-10 1 1 NO
    1024 B 0 A SBT_TAPE 07-MAR-10 2 1 NO
    1025 B A A SBT_TAPE 07-MAR-10 1 1 NO
    1026 B F A SBT_TAPE 07-MAR-10 1 1 NO
    1029 B A A SBT_TAPE 07-MAR-10 1 1 NO
    1030 B F A SBT_TAPE 07-MAR-10 1 1 NO
    1031 B A A SBT_TAPE 07-MAR-10 1 1 NO
    1032 B F A SBT_TAPE 07-MAR-10 1 1 NO
    1033 B A A SBT_TAPE 07-MAR-10 1 1 NO
    1034 B F A SBT_TAPE 07-MAR-10 1 1 NO
    1035 B A A SBT_TAPE 08-MAR-10 1 1 NO
    1036 B 1 A SBT_TAPE 08-MAR-10 1 1 NO
    1037 B 1 A SBT_TAPE 08-MAR-10 1 1 NO
    1038 B A A SBT_TAPE 08-MAR-10 1 1 NO
    1039 B F A SBT_TAPE 08-MAR-10 1 1 NO
    1042 B A A SBT_TAPE 08-MAR-10 1 1 NO
    1043 B F A SBT_TAPE 08-MAR-10 1 1 NO
    1044 B A A SBT_TAPE 08-MAR-10 1 1 NO
    1045 B 1 A SBT_TAPE 08-MAR-10 1 1 NO
    1046 B 1 A SBT_TAPE 08-MAR-10 1 1 NO
    1047 B A A SBT_TAPE 08-MAR-10 1 1 NO
    1048 B F A SBT_TAPE 08-MAR-10 1 1 NO
    1054 B A A SBT_TAPE 09-MAR-10 1 1 NO
    1055 B A A SBT_TAPE 09-MAR-10 1 1 NO
    1056 B 1 A SBT_TAPE 09-MAR-10 1 1 NO
    1057 B 1 A SBT_TAPE 09-MAR-10 1 1 NO
    1058 B A A SBT_TAPE 09-MAR-10 1 1 NO
    1059 B F A SBT_TAPE 09-MAR-10 1 1 NO
    1065 B A A SBT_TAPE 10-MAR-10 1 1 NO
    1066 B 1 A SBT_TAPE 10-MAR-10 1 1 NO
    1067 B 1 A SBT_TAPE 10-MAR-10 1 1 NO
    1068 B A A SBT_TAPE 10-MAR-10 1 1 NO
    1069 B F A SBT_TAPE 10-MAR-10 1 1 NO
    1075 B A A SBT_TAPE 11-MAR-10 1 1 NO
    1076 B 1 A SBT_TAPE 11-MAR-10 1 1 NO
    1077 B 1 A SBT_TAPE 11-MAR-10 1 1 NO
    1078 B A A SBT_TAPE 11-MAR-10 1 1 NO
    1079 B F A SBT_TAPE 11-MAR-10 1 1 NO
    1085 B A A SBT_TAPE 12-MAR-10 1 1 NO
    1086 B 1 A SBT_TAPE 12-MAR-10 1 1 NO
    1087 B 1 A SBT_TAPE 12-MAR-10 1 1 NO
    1088 B A A SBT_TAPE 12-MAR-10 1 1 NO
    1089 B F A SBT_TAPE 12-MAR-10 1 1 NO
    1094 B A A SBT_TAPE 13-MAR-10 1 1 NO
    1095 B A A SBT_TAPE 13-MAR-10 1 1 NO
    1096 B 1 A SBT_TAPE 13-MAR-10 1 1 NO
    1097 B 1 A SBT_TAPE 13-MAR-10 1 1 NO
    1098 B A A SBT_TAPE 13-MAR-10 1 1 NO
    1099 B F A SBT_TAPE 13-MAR-10 1 1 NO
    1105 B A A SBT_TAPE 14-MAR-10 1 1 NO
    1106 B 0 A SBT_TAPE 14-MAR-10 1 1 NO
    1107 B 0 A SBT_TAPE 14-MAR-10 2 1 NO
    1108 B A A SBT_TAPE 14-MAR-10 1 1 NO
    1109 B F A SBT_TAPE 14-MAR-10 1 1 NO
    1115 B A A SBT_TAPE 15-MAR-10 1 1 NO
    1116 B 1 A SBT_TAPE 15-MAR-10 1 1 NO
    1117 B 1 A SBT_TAPE 15-MAR-10 1 1 NO
    1118 B A A SBT_TAPE 15-MAR-10 1 1 NO
    1119 B F A SBT_TAPE 15-MAR-10 1 1 NO
    1125 B A A SBT_TAPE 16-MAR-10 1 1 NO
    1126 B A A SBT_TAPE 16-MAR-10 1 1 NO
    1127 B 1 A SBT_TAPE 16-MAR-10 1 1 NO
    1128 B 1 A SBT_TAPE 16-MAR-10 1 1 NO
    1129 B A A SBT_TAPE 16-MAR-10 1 1 NO
    1130 B F A SBT_TAPE 16-MAR-10 1 1 NO
    1136 B A A SBT_TAPE 17-MAR-10 1 1 NO
    1137 B A A SBT_TAPE 17-MAR-10 1 1 NO
    1138 B 1 A SBT_TAPE 17-MAR-10 1 1 NO
    1139 B 1 A SBT_TAPE 17-MAR-10 1 1 NO
    1140 B A A SBT_TAPE 17-MAR-10 1 1 NO
    1141 B F A SBT_TAPE 17-MAR-10 1 1 NO
    1147 B A A SBT_TAPE 18-MAR-10 1 1 NO
    1148 B A A SBT_TAPE 18-MAR-10 1 1 NO
    1149 B 1 A SBT_TAPE 18-MAR-10 1 1 NO
    1150 B 1 A SBT_TAPE 18-MAR-10 1 1 NO
    1151 B A A SBT_TAPE 18-MAR-10 1 1 NO
    1152 B F A SBT_TAPE 18-MAR-10 1 1 NO
    1158 B A A SBT_TAPE 19-MAR-10 1 1 NO
    1159 B A A SBT_TAPE 19-MAR-10 1 1 NO
    1160 B 1 A SBT_TAPE 19-MAR-10 1 1 NO
    1161 B 1 A SBT_TAPE 19-MAR-10 1 1 NO
    1162 B A A SBT_TAPE 19-MAR-10 1 1 NO
    1163 B F A SBT_TAPE 19-MAR-10 1 1 NO
    1169 B A A SBT_TAPE 20-MAR-10 1 1 NO
    1170 B 1 A SBT_TAPE 20-MAR-10 1 1 NO
    1171 B 1 A SBT_TAPE 20-MAR-10 1 1 NO
    1172 B A A SBT_TAPE 20-MAR-10 1 1 NO
    1173 B F A SBT_TAPE 20-MAR-10 1 1 NO
    1179 B A A SBT_TAPE 21-MAR-10 1 1 NO
    1180 B 0 A SBT_TAPE 21-MAR-10 1 1 NO
    1181 B 0 A SBT_TAPE 21-MAR-10 2 1 NO
    1182 B A A SBT_TAPE 21-MAR-10 1 1 NO
    1183 B F A SBT_TAPE 21-MAR-10 1 1 NO
    1189 B A A SBT_TAPE 22-MAR-10 1 1 NO
    1190 B 1 A SBT_TAPE 22-MAR-10 1 1 NO
    1191 B 1 A SBT_TAPE 22-MAR-10 1 1 NO
    1192 B A A SBT_TAPE 22-MAR-10 1 1 NO
    1193 B F A SBT_TAPE 22-MAR-10 1 1 NO
    RMAN> report obsolete;
    RMAN retention policy will be applied to the command
    RMAN retention policy is set to recovery window of 30 days
    Report of obsolete backups and copies
    Type Key Completion Time Filename/Handle
    Control File Copy 47 20-FEB-10 /dbbackup/cisconf/control.bak.20100220
    Backup Set 804 20-FEB-10
    Backup Piece 551 20-FEB-10 c-3316101807-20100220-01
    Edited by: user12019850 on 22-Mar-2010 11:03 AM

  • Error using rman with cumulative backup

    Hi,
    Can anyone help?
    Current system configuration : Oracle 8.0.4 & Veritas Netbackup.
    Encounter error when allocate 2 channel for cumulative backup using rman. Using a single channel works fine.
    RMAN-08010: channel t1: including datafile 1 in backupset
    RMAN-08008: channel t2: starting datafile backupset
    RMAN-08502: set_count=152 set_stamp=432319182
    RMAN-08010: channel t2: including datafile 7 in backupset
    RMAN-08010: channel t2: including datafile 20 in backupset
    RMAN-08010: channel t2: including datafile 13 in backupset
    RMAN-08010: channel t2: including datafile 15 in backupset
    RMAN-08010: channel t2: including datafile 16 in backupset
    RMAN-08011: channel t1: including current controlfile in backupset
    RMAN-00569: ================error message stack follows================
    RMAN-03007: retryable error occurred during execution of command: backup
    RMAN-07004: unhandled exception during command execution on channel t2
    RMAN-10032: unhandled exception during execution of job step 2: ORA-06512: at li
    ne 153
    RMAN-10035: exception raised in RPC: ORA-19624: operation failed, retry possible
    ORA-27015: skgfcls: failed to close the file
    Additional information: 7023
    ORA-19502: write error on file "bk_152_1_432319182", blockno 3713 (blocksize=512
    ORA-27010: skgfwrt: write to file failed
    Additional information: 7043
    ORA-06512: at "SYS.DBMS_BACKUP_RESTORE", line 408
    RMAN-10031: ORA-19624 occurred during call to DBMS_BACKUP_RESTORE.BACKUPPIECECRE
    ATE
    Thanks in advance
    null

    Hi,
    first of all you must have all the archivelogs since you want to recover your table from the previous backups.
    anyways if you want to recover your table then you need to perform incomplete recovery to the point where you loss the table for that you need to restore and recover your database.you likely to loose all the transcation which occurs to the point where you you loose your table.
    thanks..

  • Incremental cumulative backup ?

    Oracle 11.2.0.2 / Windows 2008
    Up till now, I've been running nightly 'full' backups but I've now decided to run Incremental Cumulative backups. What I plan to do is create a level '0' backup on a Monday night, and then run daily level '1' (cumulative) backups from Tuesday - Sunday and then for the whole process to start again for the following week. I've setup this up within enterprise manager (and I'm going to run them via enterprise manager) and it has produced the below scripts
    Level 0
    $rman_script="backup incremental level 0 cumulative device type disk tag '%TAG' database;
    backup device type disk tag '%TAG' archivelog all not backed up delete all input;
    allocate channel for maintenance type disk;
    delete noprompt obsolete device type disk;
    release channel;
    &br_save_agent_env();
    &br_prebackup($l_db_connect_string, $l_is_cold_backup, $l_use_rcvcat, $l_db_10_or_higher, $l_backup_strategy, "TRUE");
    my $result = &br_backup();
    exit($result);
    Level 1
    $rman_script="backup incremental level 1 cumulative device type disk tag '%TAG' database;
    backup device type disk tag '%TAG' archivelog all not backed up delete all input;
    allocate channel for maintenance type disk;
    delete noprompt obsolete device type disk;
    release channel;
    &br_save_agent_env();
    &br_prebackup($l_db_connect_string, $l_is_cold_backup, $l_use_rcvcat, $l_db_10_or_higher, $l_backup_strategy, "TRUE");
    my $result = &br_backup();
    exit($result);
    At the moment, my retention policy is set to 31 days and the 'Retain at least the specified number of full backups for each datafile is set to '1'. Do I have to change this to cater for the above ?
    Thanks in advance for any assistance

    >'Retain at least the specified number of full backups for each datafile is set to '1'.
    Are you referring to configuration in your MML -- NetBackup or Networker or the like ?
    RMAN's retention policy is in terms of either redundancy (number of copies) or days (number of days).  You've defined it to be 31 days so the oldest backup that would not be obsoleted would be the L0 backup closest to sysdate-31 at any time.
    Hemant K Chitale

  • Sybase Database Backup

    Dear Expert,
    I am using Sybase Database 15.0 with unix, as i new to Sybase please me  how to take backup of Sybase Database.
    i get the below error
    1> dump database pubs2 to 'd:\dump'
    2> go
    Msg 7205, Level 17, State 2:
    Server 'BHAVANIPC', Line 1:
    Can't open a connection to site 'SYB_BACKUP'. See the error log file in the ASE
    boot directory.
    Msg 7205, Level 18, State 3:
    Server 'BHAVANIPC', Line 1:
    Can't open a connection to site 'SYB_BACKUP'. See the error log file in the ASE
    boot directory.
    Also we opened the backup server
    Thanks & Regards,
    Akhila

    You mentioned 'Sybase Database 15.0 with unix' on you post,
    so you must make sure your backup server was started and working ok by following method:
    under unix command line, issue 'showserver' command to list servers online, and grep 'backupserver' only 
              $showserver |grep backupserver
              Example:
    /data/ase1570 > showserver |grep backupserver
    0 S sybase   19210 19209  0  80   0 -  5788 -      Aug01 ?        00:00:00 /data/ase1570/ASE-    15_0/bin/backupserver -SSYB_BACKUP -e/data/ase1570/ASE-15_0/install/SYB_BACKUP.log -N25 -C20 -    M/data/ase1570/ASE-15_0/bin/sybmultbuf
    isql to connect to ASE15 server, and issue 'sp_helpserver SYB_BACKUP' to check if SYB_BACKUP server host is available ?
              $isql -Usa -Psa_pwd -SASE15
              1> sp_helpserver SYB_BACKUP
              2> go
              Example:
    1> sp_helpserver SYB_BACKUP
    2> go
    name       network_name   security_mechanism   server_principal   class      
    status                                                                  
    id cost
    SYB_BACKUP SYB_BACKUP     NULL                 NULL               ASEnterprise
    timeouts, no net password encryption, writable , enable login redirection
    1 NULL
    isql to connect to ASE15 server, and issue 'SYB_BACKUP...sp_who' to test connection from ASE to Backup server is OK !!
               $isql -Usa -Psa_pwd -SASE15 
              1> SYB_BACKUP...sp_who
              2> go
              Example:
    1> SYB_BACKUP...sp_who
    2> go
    spid        status     loginame                       hostname     blk
    cmd             
         1      sleeping   NULL                           NULL         0 
    CONNECT HANDLER 
         2      sleeping   NULL                           NULL         0 
    DEFERRED HANDLER
         3      runnable   NULL                           NULL         0 
    SCHEDULER       
        11      runnable   NULL                           ASE1570      0 
    SITE HANDLER    
        12      running    sa                             sgsinvm0256  0 
    NULL           
    if the above checking is all ok, then you should be able to dump database without problem !!
    BTW, you must notice you are using SAP Sybase ASE 15.0 with Unix , so the dump directory should be Unix filesystem format such as '/backdir/pubs2.dmp' rather than Windows filesystem format such as 'd:\pubs2.dmp' !!
    HTH ! Thanks !!
    Regards,
    Robert

  • Incremental cumulative backup solution?

    Hi to all,
    I want to use rman cumulative incremental backup strategy i.e.I want to take one full database backup LEVEL0 every week (Sunday), and one incremental cumulative LEVEL1 database backup every day.
    RMAN configuration parameters are:
    CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
    CONFIGURE BACKUP OPTIMIZATION ON;* *// I did this to avoid doing backup on the same archivelogs files, in this case RMAN will backup only files that were not backed up.*
    CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
    CONFIGURE CONTROLFILE AUTOBACKUP OFF;# default
    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 'C:\ORACLE\PRODUCT\10.2.0\DB_1\DATABASE\SNCFORCL.ORA'; # default
    Here are my RMAN scripts:
    weekly.rman
    +run {+
    BACKUP AS COMPRESSED BACKUPSET
    INCREMENTAL LEVEL = 0 CUMULATIVE
    DEVICE TYPE DISK
    TAG = 'LEVEL0-SUNDAY'
    FORMAT 'D:\RMAN_BACKUP\DB_%d_%u_%s_%T'
    DATABASE;
    crosscheck archivelog all;
    delete expired archivelog all;
    BACKUP AS COMPRESSED BACKUPSET ARCHIVELOG ALL FORMAT 'D:\RMAN_BACKUP\arch_%d_%u_%s_%T';
    CROSSCHECK BACKUP;
    DELETE NOPROMPT OBSOLETE; // To delete backup (LEVEL0 and LEVEL1) and archivelogs files because RETENTION POLICY TO REDUNDANCY 1 and to make free space for new LEVEL0 backup.
    DELETE NOPROMPT EXPIRED BACKUP;
    crosscheck archivelog all;
    delete expired archivelog all;
    DELETE NOPROMPT ARCHIVELOG UNTIL TIME "SYSDATE-3";
    +}+
    daily.rman
    +run {+
    BACKUP AS COMPRESSED BACKUPSET
    INCREMENTAL LEVEL = 1 CUMULATIVE
    DEVICE TYPE DISK
    TAG = 'LEVEL1-MONDAY'
    FORMAT 'D:\RMAN_BACKUP\DB_%d_%u_%s_%T'
    DATABASE;
    BACKUP AS COMPRESSED BACKUPSET ARCHIVELOG ALL FORMAT 'D:\RMAN_BACKUP\arch_%d_%u_%s_%T';
    crosscheck archivelog all;
    delete expired archivelog all;
    DELETE NOPROMPT ARCHIVELOG UNTIL TIME "SYSDATE-3"; *//To delete archivelog files older than 3 days, I do not have enough space to store archive files from all week.*
    +}+
    What do you think about this RMAN scripts?
    Do you have a better solution?
    Thanks in advance for any proposal or suggestion!

    Your script looks good. As an alternative, you can also use the following command:
    Backup archivelog until time 'sysdate-3' backedup 1 times to 'sbt_tabe';
    Any suggestions are highly appreciated.
    Thanks,
    Sai.

  • Sybase Tape Backup

    Hi All,
    Could you please share the best practice for the database backup for Sybase . Our requirement is to take the backup through the Tape . Need to know the feasibility of taking the Tape backup and the recommendation / tools support for the backup or the feasibility take the individual tape backup instead of tape library .
    Regards,
    Ruchi

    Hi Ruchi,
    This is duplicate thread . refer to original thread http://scn.sap.com/thread/3595877
    Regards,
    Deepak Kori

  • Sybase Transcation log backup issue

    Hi All,
    I am trying to take backup for Sybase database and transcation log as per below link,
    http://scn.sap.com/thread/3245201
    I was successfully able to take the backup for database without any issues but when I try to take the transcations log backup I end up with below error,
    1> sp_dumptrans SBP
    2> go
    Msg 4208, Level 16, State 1:
    Server 'SBP', Line 1:
    DUMP TRANsaction to a dump device is not allowed while the trunc. log on chkpt.
    option is enabled.  Disable the option with sp_dboption, then use DUMP DATABASE,
    before trying again. (Return status = 4208)
    1>
    Later after checking the SAP guide for Sybase database we tried to setup below options,
    =====================================================================================
    Ensure that a complete sequence of transaction log archives is available at all times
    For your SAP database <DBSID> it is mandatory that you ensure that the archived log sequence
    remains unbroken.
    To ensure a complete log sequence, set the following database options:
    trunc log on chkpt, false
    full logging for all, true
    enforce dump tran sequence, true
    You have to set these options after a successful  DUMP DATABASE has been performed and before any
    Set these options using the stored procedure sp_dboption to change database options. (Syntax:sp_dboption [dbname, optname, {true | false}] ). You must change to the master database to be able to change options for a database
    ========================================================================
    My question is do I need to login to Master database to set this options because when I try to set the below option
    sp_dboption 'master', 'trunc. log on chkpt', 'false'
    I end up with below error,
    When I try to login to master database with sa user I could not,I gave the same password which i gave it during the installation
    Pelase advise on how to proceed further
    Regards
    Uday
    change is made to the database,

    Hello Selva,
    There are two main types of backups that are maintained
    in Sybase ASE;
    Dump Tran and Dump DB
    Quiesce Backup
    Dump Tran and Dump DB Backup
    The DUMP DATABASE command copies the entire database to an archive device. It does not prune
    (truncate) the transaction log (which is itself a table in the database). DUMP DATABASE is typically run on a daily or weekly basis. If the loss tolerance is 24 hours, then a single DUMP DATABASE every 24 hours is a reasonable choice for backup strategy and the transaction log can be kept pruned by either setting
    the database option “truncate log on checkpoint” or by regular use of the DUMP TRANSACTION command with the TRUNCATE_ONLY option.
    SAP Note 1588316 is a very good point to start in case you are thinking about configuring your SYBASE ASE DB and Transaction Log Backups.
    In addition I highly recommend going through the Technical Document stored in the below link;
    http://scn.sap.com/docs/DOC-29524
    Hope this helps,
    Regards
    Surajit

  • Backup incremental level 0  cumulative database

    On RMAN Level 0 backup when I say cumulative like below what the difference that command make;
    backup filesperset 1 format '<%d_%s:%t:%p:%f>.df' incremental level 0 cumulative database;Edited by: Sivaprasad S on Sep 1, 2012 12:42 AM
    Edited by: Sivaprasad S on Sep 1, 2012 12:44 AM

    In a cumulative level 1 backup, RMAN backs up all blocks used since the most recent level 0 incremental backup in either the current or parent incarnation. Cumulative incremental backups reduce the work needed for a restore by ensuring that you only need one incremental backup from any particular level. Cumulative backups require more space and time than differential backups because they duplicate the work done by previous backups at the same level.

  • Larger backups for cumulative incremental level 1 backups

    I am noticing some strange behaviour for backup of data files in the RMAN cumulative incremental level 1 backup for certain days. I would explain that with an elaboration- the cumulative backup sizes are around 2GB, 19GB, 19GB, 1GB for the dates of 10th Dec, 5th Dec, 3rd Dec and 28th Nov respectively.
    Can there be so much difference between the values of backup size for the RMAN cumulative incremental level 1 backup as they are fluctuating from 19GB->1GB?
    I hope, my question is clear.
    Please revert with the reply to my query.
    Regards

    975148 wrote:
    Thanks for your reply. Level 0 backup happened twice between 5th Dec and 10th Dec. I guess, a block which has changed multiple times would be backed up once with all the changes done in a backup on a particular day. The same changes should get reflected in the subsequent level 0 backup.
    Regards
    Yes, obviously any backup (of any kind, of any product) is only capable of backing up the state of things as they exist at the time of the backup.
    The recoverability of "intermediate" states (say a given block was modified 5 times between backups, the next backup only gets the 5th state of the block) is done by applying redo - archived or online, as is needed.
    So to make an example to replicate what you report
    Day 1 - backup level 0
    - block # 1 modified
    Day 2  - backup level 1 - backs up Block #1 - backup size 8k
    - block # 1 modified
    - block # 2 modified
    - block # 1 modified
    - block # 3 modified
    - block # 1 modified
    - block # 4 modified
    Day 3 - backup level 1 - backs up Blocks 1,2,3,4 - backup size 32k
    - block # 5 modified
    - block # 2 modified
    - block # 7 modified
    - block # 3 modified
    - block # 6 modified
    - block # 4 modified
    Day 4 - backup level 1 - backs up Blocks 1,2,3,4,5,6,7 - backup size 56k
    - block # 5 modified
    Day 4 - backup level 1 - backs up Blocks 1,2,3,4,5,6,7 - backup size 56k
    Day 6 - backup level 0 - all blocks - size ???
    - block # 3 modified
    Day 7 - backup level 1 - backs up block 3 - backup size 8 k

  • Database backup using RMAN

    Hello All,
    I am new to RMAN.
    I am trying to make some backups of my database using enterprise manager, so i choose to backup my database based on the Oracle-Suggested Backup schedule.
    I got the below command from EM:
    Daily Script:
    run {
    allocate channel oem_disk_backup device type disk;
    recover copy of database with tag 'ORA_OEM_LEVEL_0';
    backup incremental level 1 cumulative  copies=1 for recover of copy with tag 'ORA_OEM_LEVEL_0' database;
    }i have the below question:
    what does the above script do ? EM will create a job that will run it daily ? how can i check this job ? where is it logged?
    where and how can i check the already configured channels ? for ex: channel oem_disk_backup
    what does this script do ? recover copy of database with tag 'ORA_OEM_LEVEL_0' does it recover the database?
    What are the RMAN scripts (run block), to backup my database once per week (for ex on Sunday)as level 0 backup and every day as incremental level 1 cumulative backup ? Since I think that the above script will run a level 0 backup once on the first execution and then the remaining backups are level 1 Incremental backups
    Thanks and regards,

    NB wrote:
    Hello All,
    I am new to RMAN.
    I am trying to make some backups of my database using enterprise manager, so i choose to backup my database based on the Oracle-Suggested Backup schedule.
    I got the below command from EM:
    Daily Script:
    run {
    allocate channel oem_disk_backup device type disk;
    recover copy of database with tag 'ORA_OEM_LEVEL_0';
    backup incremental level 1 cumulative  copies=1 for recover of copy with tag 'ORA_OEM_LEVEL_0' database;
    }i have the below question:
    what does the above script do ? EM will create a job that will run it daily ? how can i check this job ? where is it logged?You can check the the view V$RMAN_BACKUP_JOB_DETAILS.
    where and how can i check the already configured channels ? for ex: channel oem_disk_backupConnect to RMAN and execute the command show all;
    what does this script do ? recover copy of database with tag 'ORA_OEM_LEVEL_0' does it recover the database?
    What are the RMAN scripts (run block), to backup my database once per week (for ex on Sunday)as level 0 backup and every day as incremental level 1 cumulative backup ? Since I think that the above script will run a level 0 backup once on the first execution and then the remaining backups are level 1 Incremental backupsYour script is doing a daily incremental updated backup. Every day, You are asking Oracle to update your image copy with latest changes of all redo as of yesterday. You are recovering your backup copies; see the following link;
    See http://download.oracle.com/docs/cd/B19306_01/backup.102/b14192/bkup004.htm#sthref408

  • Legato networker incremental backup hangs

    Hi All,
    I have once a week database level 0 backup and the rest of the days level 1 cumulative backup. Problem I am facing is level 1 backup always hangs, whereas level 0 backup finished in an hour. Here I am posting all possible info I know of to investigate why it hangs.
    Rman Script
    connect target sys/password@db
    connect catalog rman/password@catalog;
    run
    set command id to 'Inc1_Backup';
    allocate channel t1 type 'SBT_TAPE' parms 'ENV=(NSR_SERVER=nw1,NSR_CLIENT=db)';
    allocate channel t2 type 'SBT_TAPE' parms 'ENV=(NSR_SERVER=nw1,NSR_CLIENT=db)';
    allocate channel t3 type 'SBT_TAPE' parms 'ENV=(NSR_SERVER=nw1,NSR_CLIENT=db)';
    allocate channel t4 type 'SBT_TAPE' parms 'ENV=(NSR_SERVER=nw1,NSR_CLIENT=db)';
    sql 'alter database backup controlfile to trace';
    backup incremental level=1 cumulative
    filesperset 50
    tag 'Level 1 Backup'
    format 'secdb_%T_%s.bak'
    (database include current controlfile);
    backup archivelog all format 'secdb_arc_%T_%s.bak' ;
    delete archivelog until time 'sysdate -2';
    release channel t1;
    release channel t2;
    release channel t3;
    release channel t4;
    Part of rman log file
    connected to target database: db (DBID=<dbid>)
    connected to recovery catalog database
    executing command: SET COMMAND ID
    starting full resync of recovery catalog
    full resync complete
    allocated channel: t1
    channel t1: sid=252 devtype=SBT_TAPE
    channel t1: NMO v5.0.0.0
    sent command to channel: t1
    allocated channel: t2
    channel t2: sid=255 devtype=SBT_TAPE
    channel t2: NMO v5.0.0.0
    sent command to channel: t2
    allocated channel: t3
    channel t3: sid=523 devtype=SBT_TAPE
    channel t3: NMO v5.0.0.0
    sent command to channel: t3
    allocated channel: t4
    channel t4: sid=268 devtype=SBT_TAPE
    channel t4: NMO v5.0.0.0
    sent command to channel: t4
    sql statement: alter database backup controlfile to trace
    Starting backup at 27-SEP-10
    There is no information after "starting backup" even after 4, 5 hours. The most of the waits are being observed at "SQL*Net message from client". Also, there is no high load, no cpu usage or no disk activity going on. Everything on server appears to be idle. Also, catalog server is Oracle 9i where db server is 10g.
    Any idea ? ?

    Dear Tycho,
    The script executed fine for like more than a year, so that's not the syntax issue. Otherwise, it might have given a syntax error just in the beginning.
    The problem has been solved. Issue was the recovery catalog was having entries for many expired backups for more than a year and was never cleaned up. I crosschecked and removed all expired entries and backup now completes faster than even before.
    Cheers !

  • Data Warehouse Backups

    We want to keep our database up as much as possible due to the
    number of data feeds coming in and also so we can recover tablespaces at
    any given point in time. We tried running in archivelog mode but with
    nologging enabled so our archives would not grow enormously.
    When we recovered one of the tablespaces we got block corruption errors
    because it could not apply some of the redo information. We then tried doing a block recovery thru rman but it wasn't able to fix it.
    It looks like we only have the option of taking cold backups but we would like to
    recover tablespaces without doing a full recovery. It seems to me that doing periodic data pumps would be the only way to recover tablespaces without a full recovery.
    Does anyone have any ideas ? Is trying to run in archivelog mode futile ? How does everyone else run there backups for there warehouse ?

    For our DW (about 5 TB), we use archivelog mode with logging available for all tables. We take a weekly full level 0 backup, 3 x a week differential, 3 x a week cumulative backups. Our full backup takes 14 hours, our diff takes 6 hours, and our cum take about 6 hours. You could make the incremental backups faster if you are running 10g and enable block change logging. We haven't implemented that because it would take some time for us to test all senerios for recovery. Just haven't had time yet, and our backups run in an acceptable amount of time (for us).

  • Incremantal Backups with RMAN

    Hello, I was wondering if RMAN incremental backups are cumulative? If I do incrementals every night, would each night consist of every thing since the last full backup? Here is the script that I am using to perform my nightly incremental backups:
    Retention policy is 7 days.
    run{
    allocate channel c1 device type disk format 'F:\rman_backups\ incremental\rman_incr_%n_%T_%s_%p.bak';
    backup level 1 database plus archivelog;
    allocate channel for maintenance device type disk;
    delete archivelog until time 'sysdate - 7' backed up 2 times to disk;
    delete obsolete device type disk;
    Thank you

    Hi David
    What do you mean with "different backup levels"? The differences between the cumulative and the differential backup or what "has been backed up" after a level 1 (cumulative/differential) backup?
    http://download-east.oracle.com/docs/cd/B10501_01/server.920/a96565/rcmsynta9.htm#78484
    INCREMENTAL LEVEL = integer
    Copies only those data blocks that have changed since the last incremental integer backup, where integer is any integer from 0 to 4. For example, in a level 2 backup RMAN backs up all blocks used since the most recent level 2, level 1, or level 0 backup.
    This type of incremental backup is also called a differential backup to distinguish it from a cumulative backup.
    A level 0 backup must exist as the base backup for an incremental strategy. An incremental backup at level 0 is identical in content to a full backup, but unlike a full backup the level 0 backup is considered a part of the incremental strategy.
    If no level 0 backup exists when you run a level 1 or higher backup, then RMAN makes a level 0 backup automatically.
    Oracle performs checks when attempting to create an incremental backup at a level greater than 0.
    These checks ensure that the incremental backup is usable by a subsequent RECOVER command. Among the checks performed are:
        * A level 0 backup set must exist, or level 0 datafile copies must exist for each datafile in the BACKUP command. These backup sets must not be marked UNAVAILABLE.
    If no level 0 backup exists, then RMAN automatically generates one.
        * Sufficient incremental backups taken since the level 0 must exist and be available such that the incremental backup to be created is usable.
    If you specify INCREMENTAL, then in the backupSpec clause you must set one of the following parameters: DATAFILE, DATAFILECOPY, TABLESPACE, or DATABASE.
    RMAN does not support incremental backups of control files, archived redo logs, or backup sets.
    Note: You cannot make inconsistent incremental backups when the database is in NOARCHIVELOG mode.
    Hence, you cannot generate incremental backups when a NOARCHIVELOG database is open and in use.Here you can find the "top" description about "Incremental Backups";
    http://download-east.oracle.com/docs/cd/B10501_01/server.920/a96566/rcmconc1.htm#458838
    Bye, Aron

Maybe you are looking for

  • Multiple controlling area with same chart account

    Hi Experts, can we consolidate multiple controlling area with same chart account in SAP BI? for example, if in R3 I have 4 Controlling Areas with the same chart of accounts, I can get an standard BW reports summarizing  them.

  • Cant connect my database using net service_name

    Good Morning to all; I trying to connect my database using net service_name , but i am getting error. I have tnsnames.ora entry and listener.ora entry. Please help me to crack this error. SQL> select name from v$database; NAME ORCLTEST SQL> grant con

  • Named Queries

    Hi All, I am using TL 4.6 Build 418, Oracle 8.1 & WLS 7.0. I am having a hard time getting Named Queries working. Specifically I can't seem to get Toplink to Bind my parameter(s). I have tried to use both EJBQL and plain SQL with no luck using either

  • Ipod won't turn on and computer won't reconize

    my 80gp replacement ipod that i had for 1-2 days just all of a sudden wouldn't turn on and when i try to connect it to my computer the ipod won't connect to my computer. it is almost like the ipod isn't even connect to the computer. need help on this

  • Debit memo with negative net price value

    Hi experts. Can you help me ? I have a debit memo process and its net price value is negative. Return's flag isn't checked in  customizing (VOV7). Thanks a lot ! Renato