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.

Similar Messages

  • 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

  • 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

  • Backup Solution For This Specific Setup

    I've been thinking about how I'm going to backup my setup but I'm sort of stuck.
    My setup: 2 Drives
    80GB Intel SSD - boot disk, dual boots Windows 7 and ArchLinux
    500GB HDD  - only for files, not going to be of any concern
    Here's the fdisk -l for the SSD (/dev/sdb)
    Disk /dev/sdb: 80.0 GB, 80026361856 bytes, 156301488 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk identifier: 0x9b9dcc69
    Device Boot Start End Blocks Id System
    /dev/sdb1 * 2048 206847 102400 7 HPFS/NTFS/exFAT
    /dev/sdb2 206848 103811071 51802112 7 HPFS/NTFS/exFAT
    /dev/sdb3 104015872 156301311 26142720 83 Linux
    /dev/sdb4 103811072 104015871 102400 83 Linux
    Here's what I'd like: If the SSD fails, I'd like to be able to have an exact clone bootable USB HDD ready to use (so it must be able to dual boot). Basically, I'd like to minimize down time as much as possible. Then I'd like to be able to transfer everything again to a new SSD.
    I understand that I can use rsync for backups: https://wiki.archlinux.org/index.php/Fu … with_rsync but I'm not sure how to adjust it for dual booting. Should I be cloning with dd instead? From what I've read dd will copy everything including the partition table of the old one so that might not be a good idea if I'm planning to move the whole thing to a new SSD?
    Appreciate any input!
    Last edited by devrepublic (2013-02-22 01:32:15)

    Use rsync as it will then only write what has been changed instead of the whole damn thing like dd.  There is a wiki page about how to back up your entire system with rsync... you should probably have a look at that. 
    This of course will work just fine for your Arch Linux, but I don't know enough about windows to be able to recommend a way to do it with that partition.  I guess you could dd the partition everyday, but that doesn't seem very practical.  I would have to imagine that there is probably some kind of a incremental windows backup solution that you could use, but I don't know.
    You will of course then have to have a bootloader installed on the second drive, set up and ready to boot into either system.  Then just make sure you are booting the right drive all the time and you're good to go. 
    Are you implying that you want to back up to the 500GB drive?  Or are you saying that you want to use an external?

  • Mac OS X Server Backup solutions?

    Hi all, I have built up my network with 3 Leopard servers running on Mac Pro's and 8 mac clients (one mobile)
    Between all of them there is about 12TB's of storage space (about 2TB being used at present)
    it really is time to now invest in a complete backup solution and we won't a format that can be taken offsite (Tape sounds the best)
    I really have hardly any experience in this area and need to get some advice.
    I have an ATTO Ultra320 card in one of the Mac Pro's so need to figure out which tape drive (or drives) which software and the best way to implement it.
    All the clients are on OD so not overly bothered about backing them up, just the 3 main servers really.
    Any help would be really appreciated, thanks.

    Here's some grist for the thought mill...
    The use of "Removable" here likely (probably?) means "remote", which itself (and depending on the bandwidth of the network connection or access to couriers or such) may or may not actually be a removable disk or removable tape storage, or disk or tape libraries.
    What's the volume of the actual data? What's the rate of change of the data? There are two parts to the calculation for the creation and operation of the archive, the initial archive and the occasional (weekly, monthly, before an upgrade) full archive, and then the incremental (hourly, daily, weekly) archives. This assumes the usual two-level archive processing; an occasional full and a more frequent incremental.
    You need to figure out how big these activities are, and what your backup window is. These details then drive the available hardware and media options and then the device selection.
    Then determine (or guesstimate) the growth rate of the data. That tells you what your approach can support now, and how quickly your backup window (if you have one) might be closing. And (if you're using smaller media) when you might need to go to a larger-capacity media or to multi-volume archives. Right now, you can probably get most everything onto a 1 TB or 1.5 TB spindle, for instance.
    You'll also need to sort out the local and continuously-active processing activities, and how to get copies of those. The sqldump tool, for instance, can be the path to get a recoverable installation. And that processing tends to be part of getting a recoverable archive.
    There are cloud services around for storage and (if your change rate is less than the bandwidth "slop" available within your current network pipe) to a remote site that you manage or contract with; to a storage site or to warm site you work with, or out to an Amazon S3 or other competing storage pool. (There are various options for archiving out into Amazon S3, for instance. And Time Capsule and Time Machine is seriously slick.)
    Never assume that RAID is an archival strategy. It's not. RAID is useless against application corruptions, blown software upgrades, user errors, client and server and storage theft, and malicious-user activities. Nor against roof-mounted heat exchanger system that sprout leaks that then pour red-colored coolant into the server racks. RAID protects against disk spindle failures and (for some specific configurations) against certain other "upstream" storage controller failures.
    When you get all done, make sure you can recover and restart using your archives. Periodically test the recoverability of the archives.

  • Definitive Storage and Backup solution

    Hello, I'm looking for a definitive Storage and Backup solution.
    So far I've been looking on to Drobo 5D or N, LaCie 5big Thunderbolt™ 2, or LaCie 2big Thunderbolt™ 2.
    Networking would be a plus but not a must. I'm open for other suggestions and also wonder if these systems can be considered backup since they are ready for single or double disks failures.
    Thanks.

    Methodology to protect your data. Backups vs. Archives. Long-term data protection
    Avoid Lacie, they contain Seagate drives inside.  Bad idea. 
    huge storage, low cost, high quality, very small and portable.
    BEST FOR THE COST, Toshiba "tiny giant" 15mm thick  2TB drive (have several of them, lots of storage in tiny package)    $100
    http://www.amazon.com/Toshiba-Canvio-Connect-Portable-HDTC720XK3C1/dp/B00CGUMS48     /ref=sr_1_3?ie=UTF8&qid=1390020791&sr=8-3&keywords=toshiba+2tb
    best options for the price, and high quality HD:
    Quality 1TB drives are $50 per TB on 3.5" or  $65 per TB on 2.5"
    Perfect 1TB for $68
    http://www.amazon.com/Toshiba-Canvio-Portable-Hard-Drive/dp/B005J7YA3W/ref=sr_1_ 1?ie=UTF8&qid=1379452568&sr=8-1&keywords=1tb+toshiba
    Nice 500gig for $50. ultraslim perfect for use with a notebook
    http://www.amazon.com/Toshiba-Canvio-Portable-External-Drive/dp/B009F1CXI2/ref=s     r_1_1?s=electronics&ie=UTF8&qid=1377642728&sr=1-1&keywords=toshiba+slim+500gb
    *This one is the BEST portable  external HD available that money can buy:
    HGST Touro Mobile 1TB USB 3.0 External Hard Drive $88
    http://www.amazon.com/HGST-Mobile-Portable-External-0S03559/dp/B009GE6JI8/ref=sr     _1_1?ie=UTF8&qid=1383238934&sr=8-1&keywords=HGST+Touro+Mobile+Pro+1TB+USB+3.0+7 2 00+RPM
    Most storage experts agree on the Hitachi 2.5"
    Hitachi is the winner in hard drive reliability survey:
    Hitachi manufacturers the safest and most reliable hard drives, according to the Storelab study. Of the hundreds of Hitachi hard drives received, not a single one had failed due to manufacturing or design errors. Adding the highest average lifespans and the best relationship between failures and market share, Hitachi can be regarded as the winner.
    Data Storage Platforms; their Drawbacks & Advantages
    #1. Time Machine / Time Capsule
    Drawbacks:
    1. Time Machine is not bootable, if your internal drive fails, you cannot access files or boot from TM directly from the dead computer.
    OS X Lion, Mountain Lion, and Mavericks include OS X Recovery. This feature includes all of the tools you need to reinstall OS X, repair your disk, and even restore from a Time Machine
    "you can't boot directly from your Time Machine backups"
    2. Time machine is controlled by complex software, and while you can delve into the TM backup database for specific file(s) extraction, this is not ideal or desirable.
    3. Time machine can and does have the potential for many error codes in which data corruption can occur and your important backup files may not be saved correctly, at all, or even damaged. This extra link of failure in placing software between your data and its recovery is a point of risk and failure. A HD clone is not subject to these errors.
    4. Time machine mirrors your internal HD, in which cases of data corruption, this corruption can immediately spread to the backup as the two are linked. TM is perpetually connected (or often) to your computer, and corruption spread to corruption, without isolation, which TM lacks (usually), migrating errors or corruption is either automatic or extremely easy to unwittingly do.
    5. Time Machine does not keep endless copies of changed or deleted data, and you are often not notified when it deletes them; likewise you may accidently delete files off your computer and this accident is mirrored on TM.
    6. Restoring from TM is quite time intensive.
    7. TM is a backup and not a data archive, and therefore by definition a low-level security of vital/important data.
    8. TM working premise is a “black box” backup of OS, APPS, settings, and vital data that nearly 100% of users never verify until an emergency hits or their computers internal SSD or HD that is corrupt or dead and this is an extremely bad working premise on vital data.
    9. Given that data created and stored is growing exponentially, the fact that TM operates as a “store-it-all” backup nexus makes TM inherently incapable to easily backup massive amounts of data, nor is doing so a good idea.
    10. TM working premise is a backup of a users system and active working data, and NOT massive amounts of static data, yet most users never take this into consideration, making TM a high-risk locus of data “bloat”.
    11. In the case of Time Capsule, wifi data storage is a less than ideal premise given possible wireless data corruption.
    12. TM like all HD-based data is subject to ferromagnetic and mechanical failure.
    13. *Level-1 security of your vital data.
    Advantages:
    1. TM is very easy to use either in automatic mode or in 1-click backups.
    2. TM is a perfect novice level simplex backup single-layer security save against internal HD failure or corruption.
    3. TM can easily provide a seamless no-gap policy of active data that is often not easily capable in HD clones or HD archives (only if the user is lazy is making data saves).
    #2. HD archives
    Drawbacks:
    1. Like all HD-based data is subject to ferromagnetic and mechanical failure.
    2. Unless the user ritually copies working active data to HD external archives, then there is a time-gap of potential missing data; as such users must be proactive in archiving data that is being worked on or recently saved or created.
    Advantages:
    1. Fills the gap left in a week or 2-week-old HD clone, as an example.
    2. Simplex no-software data storage that is isolated and autonomous from the computer (in most cases).
    3. HD archives are the best idealized storage source for storing huge and multi-terabytes of data.
    4. Best-idealized 1st platform redundancy for data protection.
    5. *Perfect primary tier and level-2 security of your vital data.
    #3. HD clones (see below for full advantages / drawbacks)
    Drawbacks:
    1. HD clones can be incrementally updated to hourly or daily, however this is time consuming and HD clones are, often, a week or more old, in which case data between today and the most fresh HD clone can and would be lost (however this gap is filled by use of HD archives listed above or by a TM backup).
    2. Like all HD-based data is subject to ferromagnetic and mechanical failure.
    Advantages:
    1. HD clones are the best, quickest way to get back to 100% full operation in mere seconds.
    2. Once a HD clone is created, the creation software (Carbon Copy Cloner or SuperDuper) is no longer needed whatsoever, and unlike TM, which requires complex software for its operational transference of data, a HD clone is its own bootable entity.
    3. HD clones are unconnected and isolated from recent corruption.
    4. HD clones allow a “portable copy” of your computer that you can likewise connect to another same Mac and have all your APPS and data at hand, which is extremely useful.
    5. Rather than, as many users do, thinking of a HD clone as a “complimentary backup” to the use of TM, a HD clone is superior to TM both in ease of returning to 100% quickly, and its autonomous nature; while each has its place, TM can and does fill the gap in, say, a 2 week old clone. As an analogy, the HD clone itself is the brick wall of protection, whereas TM can be thought of as the mortar, which will fill any cracks in data on a week, 2-week, or 1-month old HD clone.
    6. Best-idealized 2nd platform redundancy for data protection, and 1st level for system restore of your computers internal HD. (Time machine being 2nd level for system restore of the computer’s internal HD).
    7. *Level-2 security of your vital data.
    HD cloning software options:
    1. SuperDuper HD cloning software APP (free)
    2. Carbon Copy Cloner APP (will copy the recovery partition as well)
    3. Disk utility HD bootable clone.
    #4. Online archives
    Drawbacks:
    1. Subject to server failure or due to non-payment of your hosting account, it can be suspended.
    2. Subject, due to lack of security on your part, to being attacked and hacked/erased.
    Advantages:
    1. In case of house fire, etc. your data is safe.
    2. In travels, and propagating files to friends and likewise, a mere link by email is all that is needed and no large media needs to be sent across the net.
    3. Online archives are the perfect and best-idealized 3rd platform redundancy for data protection.
    4. Supremely useful in data isolation from backups and local archives in being online and offsite for long-distance security in isolation.
    5. *Level-1.5 security of your vital data.
    #5. DVD professional archival media
    Drawbacks:
    1. DVD single-layer disks are limited to 4.7Gigabytes of data.
    2. DVD media are, given rough handling, prone to scratches and light-degradation if not stored correctly.
    Advantages:
    1. Archival DVD professional blank media is rated for in excess of 100+ years.
    2. DVD is not subject to mechanical breakdown.
    3. DVD archival media is not subject to ferromagnetic degradation.
    4. DVD archival media correctly sleeved and stored is currently a supreme storage method of archiving vital data.
    5. DVD media is once written and therefore free of data corruption if the write is correct.
    6. DVD media is the perfect ideal for “freezing” and isolating old copies of data for reference in case newer generations of data become corrupted and an older copy is needed to revert to.
    7. Best-idealized 4th platform redundancy for data protection.
    8. *Level-3 (highest) security of your vital data. 
    [*Level-4 data security under development as once-written metallic plates and synthetic sapphire and likewise ultra-long-term data storage]
    #6. Cloud based storage
    Drawbacks:
    1. Cloud storage can only be quasi-possessed.
    2. No genuine true security and privacy of data.
    3. Should never be considered for vital data storage or especially long-term.
    4. *Level-0 security of your vital data. 
    Advantages:
    1. Quick, easy and cheap storage location for simplex files for transfer to keep on hand and yet off the computer.
    2. Easy source for small-file data sharing.
    #7. Network attached storage (NAS) and JBOD storage
    Drawbacks:
    1. Subject to RAID failure and mass data corruption.
    2. Expensive to set up initially.
    3. Can be slower than USB, especially over WiFi.
    4. Mechanically identical to USB HD backup in failure potential, higher failure however due to RAID and proprietary NAS enclosure failure.
    Advantages:
    1. Multiple computer access.
    2. Always on and available.
    3. Often has extensive media and application server functionality.
    4. Massive capacity (also its drawback) with multi-bay NAS, perfect for full system backups on a larger scale.
    5. *Level-2 security of your vital data.
    JBOD (just a bunch of disks / drives) storage
    Identical to NAS in form factor except drives are not networked or in any RAID array, rather best thought of as a single USB feed to multiple independent drives in a single powered large enclosure. Generally meaning a non-RAID architecture.
    Drawbacks:
    1. Subject to HD failure but not RAID failure and mass data corruption.
    Advantages:
    1. Simplex multi-drive independent setup for mass data storage.
    2. Very inexpensive dual purpose HD storage / access point.
    3. *Level-2 security of your vital data.
    Bare hard drives and docks. The most reliable and cheapest method of hard drive data storage, archives, and redundancies
    The best method for your data archives and redundancies, which is also the least expensive, the most reliable, and the most compact option is the purchase of naked hard drives and at least one USB 3.0 HD dock ($40 roughly).
    While regarding Time Machine and your Macbook or desktop, your primary backup is best saved to a conventional USB (or Firewire / thunderbolt) hard drive inside an enclosure, the most important part of your data protection begins after your 1st / primary Time Machine / backup; and these are your secondary (most important) data storage devices, archives and their redundancies.
    However bare hard drives and docks (below) also work perfectly as a Time Machine backup, this is for home use, since the docking station is certainly not very portable as a notebook Time Machine backup device should be; nor should bare HD be packed around with a notebook, rather remain at home or office.
    Six terabytes of 2.5" HD pictured below in a very compact space.
    Bare hard drives and docks have the lowest cost, the highest reliability, and take up the smallest storage space
    Drawbacks:
    1. Care and knowledge in general handling of naked hard drives (how not to shock a bare HD, and how to hold them properly). Not a genuine drawback.
    Advantages:
    1. By far the least expensive method of mass HD storage on a personal basis. Highest quality naked HD can be purchased in bulk very cheap.
    2. Eliminates the horrible failure point of SATA bridges and interfaces between external drives and the computer.
    3. Per square foot you can store more terabytes of data this way than any other.
    4. Fast, easy, no fuss and most simplex method of data storage on hard drives.
    Time Machine is a system  backup, not a data backup
    Important data you “don’t dare lose” should not be considered ultimately safe, or ideally stored (at the very least not as sole copy of same) on your Time Machine backup. Hourly and daily fluctuations of your system OS, applications, and software updates is the perfect focus for the simple user to conduct ‘click it and forget it’ backups of the entire system and files on the Macbook HD.
    Bootable clones are the choice of professionals and others in that Time Machine cannot be booted from and requires a working HD to retrieve data from (meaning another computer). Your vital data needs to be and should be ‘frozen’ on some form of media storage, either in a clone, as an archived HD containing important files, or on DVD blank archival media.
    A file that is backed up to Time Machine is unsafe in that if that file is deleted off the computer by accident or lost otherwise, that file will likewise vanish from Time Machine as it reflects changes on the internal computer HD/SSD.

  • What's the best external backup solution for the 2011 MacBook Air?

    I'm really considering moving to a new 2011 13" MacBook Air for my primary machine and I'm curious to know what ya'll might suggest for the ideal backup solution.
    Currently I use a Firewire 800 drive with my MacBook Pro consisting of a Bootable OS backup, Media volume backup, Time Machine backup + blank volume for files.
    The current external options available —Thunderbolt release date anyone?—are: USB 2.0 and Time Capsule. Lately—and a first up until now—I've started thinking about potentialy moving my backup solution online. I'm curious if anyone has experience with an affordable, simple, online solution?
    Also, don't suppose any kind of storage solutions could utilize the SD card slot in any way?
    I look forward to hearing about your backup solutions!
    All the best,
    —Jordan

    Redundancy is more important than speed when it comes to backup.
    I like a have a clone of my internal drive to an external drive of the same size. If your internal drive fails you can boot from your external clone. I use SuperDuper!
    If your data is important to you, you should keep a backup off-site and have more than one backup set.
    Cloud storage is an option if you have fast broadband and small data volumes.
    I like the simplicity of Time Machine with Time Capsule for incremental and version backups.
    Rather than invest in Thunderbolt (expensive and fast), invest in redundancy (cheap, slow).

  • What is the best free backup solution for Hyper-V R2/2012? CSV support is necessary

    Hi,
    I need so guidance, please.
    I’m planning to deploy a free backup solution for my virtual environment and I need your advice. I have the following configuration:
    Failover Cluster:
    Two Dell Servers
    OS: Windows 2012 STD
    Each server has two AMD Opteron 4180 6C @ 2.6 GHZ
    16 GB – RAM (supports 256GB)
    QNAP NAS (CSV)
    It’s hosting a DC, an Exchange 2010 and soon a SharePoint 2013 VM
    Standalone Hyper-V:
    Dell Server
    OS: Windows 2008 R2 Datacenter
    It has two Intel Xeon E5520 @ 2.2 GHZ
    16 GB - RAM
    It’s hosting 3 VMs
    In my research I found these apps. All of them are limited in some way but they do the job:
    Veeam Backup Free Edition v7
    Altaro Hyper-V Backup
    Unitrends Enterprise Backup
    PHD Virtual Backup for Hyper-V
    HV Backup from CodePlex
    Windows Server Backup (WSB)
    What is your experience with them? What would you recommend?
    When it comes to money, which one is more affordable? (In case I want to buy the full version)
    Thanks in advanced. 

    Hi,
    I need so guidance, please.
    I’m planning to deploy a free backup solution for my virtual environment and I need your advice. I have the following configuration:
    Failover Cluster:
    Two Dell Servers
    OS: Windows 2012 STD
    Each server has two AMD Opteron 4180 6C @ 2.6 GHZ
    16 GB – RAM (supports 256GB)
    QNAP NAS (CSV)
    It’s hosting a DC, an Exchange 2010 and soon a SharePoint 2013 VM
    Standalone Hyper-V:
    Dell Server
    OS: Windows 2008 R2 Datacenter
    It has two Intel Xeon E5520 @ 2.2 GHZ
    16 GB - RAM
    It’s hosting 3 VMs
    In my research I found these apps. All of them are limited in some way but they do the job:
    Veeam Backup Free Edition v7
    Altaro Hyper-V Backup
    Unitrends Enterprise Backup
    PHD Virtual Backup for Hyper-V
    HV Backup from CodePlex
    Windows Server Backup (WSB)
    What is your experience with them? What would you recommend?
    When it comes to money, which one is more affordable? (In case I want to buy the full version)
    Thanks in advanced. 
    Any Altaro Hyper-V Backup User?

  • Backup solutions w/RAID or redundancy (NAS, RAID, DIY File server)

    Hi all, I need a place to bounce my ideas off of. Here goes:
    I have been doing a lot of reading, since I was considering adding an NAS solution for my home network. My data consists mainly of videos (TVs and movies) and pictures (many many years worth).
    Anyways, out of the box solutions seemed a bit too pricy and the RAID not that spectacular unless you're willing to spend, so I began looking at building my own fileserver, with a hardware/software RAID solution. That was a bit better bang for the buck, but I still had one nagging concern.
    I've played around with RAID before, and I realized that with mirroring (the only RAID option I was really considering), was that it relied on the RAID controller. I couldn't just take a hard drive, remove it physically from the array, and have my information accessible when plugging it into another computer.
    What happens in a few years if your RAID controller dies and you can't find the exact same one? Your array will always be dependent on that controller and I really don't like that feeling. I'd rather have the option of taking a drive, plugging it in another computer, rather than needing to move the whole array (RAID, NAS, DIY file server) around. That means quicker access to my information or the ability to take it with me anywhere I go, on a moment's notice.
    The least costly solution I have come up with, for data that doesn't change all that much, is to have two huge drives (1 TB) on a computer, either one or both connected via eSATA. Just remember to ghost/copy the main drive once in a while, and keep the 'backup' drive detached (preferably located in a fire-proof safe) and back it up once in a while, on a regular basis).
    Sorry for the long post, but how does that sound, for a cheap, reliable backup solution, for data that doesn't get updated too frequently and for ease of access and use?

    Hi BGBG;
    For what you are attempting to do, RAID is not the best solution. The reason I say this is because RAID 1 is only capable of protection from disk failure. It is not a valid backup solution.
    I think that your last solution of using eSATA and a copy is the best. My only addition to your proposal would be a third disk. That way when you move the backup disk into storage you could replace it with the third one. In this way you could use SuperDuper to periodically backup between two disks.
    Allan

  • Incrementally updated backup and EMC NMDA

    Hello Everyone,
    I'm kind of a newbie in setting up networker module for oracle, to backup database to tape. We use the oracle's suggested backup strategy to backup DB to Disk first using the incrementally updated backups with recovery set to 3 days (RECOVER COPY OF DATABASE WITH TAG ... UNTIL TIME 'SYSDATE-3') , which helps us to recover DB to any point in time using the backup files in disks vs. going to tape. After backup to disk, we backup recovery area to tape nightly. However, we do want to maintain backup Retention Policy of 1 month. Couple of questions,
    1. If i set RP to recovery window of 31 days in RMAN, then backups don't obsolete at all. this forces me to set RP in networker and they don't recommend setting RP in both RMAN and networker. how is this done generally to obsolete backups from tape as well as rman (catalog in CF) with above strategy. perhaps in this case i should set RP in netwoker and set RP in RMAN to none and rely on crosscheck and delete expired commands to sync with RNAM catalog.
    2. Wondering if nightly backup of recovery area to tape is going to take incremental from previous day and NOT full backup. The reason i ask is, i do not want the tape to do full backup of FRA every day cause full backup datafiles change once in 3 days based on the until time set. is there an option do set in networker to do incremental only or that's the default.
    Thanks in Advance!
    11gR2, 4 Node RAC, Linux, NMDA 1.1, Networker 7.6 sp1

    Loic wrote:
    You do a full backup of the FRA on tape ?No, I do a full backup of the database on tape. Using RMAN together with Veritas NetBackup.
    I mean if you use incremental updated backup it'll not work on tape... Because the level 0 backup that will be updated with the backup of the day after will be on tape and will not be updated.The incrementally updated backup is in the FRA only, on disk (both the image copy and the following backup sets that are used for recovery of the image copy). Never gets written to tape or updated on tape.
    Why don't you use then normal incremental backup ? That will have no problem with the tape backup even if level0, or level1,2 becomes reclaimable... ?I think I do :-)
    Maybe:
    To keep that you can put the redundancy to 2 out of 1 copy. Like this even with one copy on disk and tape it'll say keep the 2 copies.
    CONFIGURE RETENTION POLICY TO REDUNDANCY 2;I'll think about that.

  • INCREMENTAL MERGE BACKUP & RECOVERY

    INCREMENTAL MERGE BACKUP & RECOVERY
    =====================================
    1) 개요
    RMAN을 이용하여 database의 Image copy를 Backup하고 그 Backup에 retention policy만큼의 Incremental Backup을 적용하여서 복구의 시간을 단축한 Backup의 방법입니다.
    즉 retention policy에 설정되어있는 시간 전의 최후의 시간까지 Image Copy를 보장하는 방법이며 Disk Space는 Incremental Backup만 사용하는 방법보다는 Image Copy를 사용하는 것임으로 많이 소요됩니다.
    물론 Backup & Recovery 정책에 따라서 Retention Policy를 Recovery Window나 Redundancy 2이상으로 설정할 수 있으나, Incremental Merge Backup & Recovery의 장점을 극대화 하기 위해서는 Redundancy 1 (Default)로 설정하는 것을 권해드립니다.
    2) 장점
    - Recovery 시에 최근 Incremental Backup의 정보들이 적용이 되어있기 때문에 최소한의 시간으로 Recovery 작업을 진행하실 수 있습니다. 물론 장점을 극대화 하시기 위해서는 Retention Policy를 redundancy 1로 설정해 주시길 권해드립니다.
    - Datafile들의 Destination을 Backup된 Image Copy가 있는 곳으로 Switch 하여 Restore하는 시간을 단축하셔서 Recovery를 진행하실 수도 있으나 Recovery 후의 관리의 용이성을 위해 부득히한 경우를 재외하고는 권장하지 않습니다.
    3) Syntax
    - Backup
    RMAN> BACKUP INCREMENTAL LEVEL 1
    FOR RECOVER OF COPY
    WITH TAG WEEKLY DATABASE;
    위 명령어를 사용하시면 WEEKLY라는 Tag로 생성된 Copy가 없을 시에는 Image Copy를 Weekly라는 Tag로 구분하여 Backup을 받게 됩니다.
    * 여기서 Copy라 함은 FOR RECOVER OF COPY라는 구문을 사용하여서 만든 Image Copy를 뜻합니다.
    RMAN> RECOVER COPY OF DATABASE WITH TAG WEEKLY;
    위 명령어를 사용하시면 현재 받았던 Incremental Backup을 Weekly라는 Tag를 가지고 있는 Database Copy에 적용을 하게 됩니다.
    RMAN> Delete Obsolete;
    위 명령어를 사용하시면 현재의 Image Copy에 적용된 Incremental Backup을 재외한 나머지 Incremental Backup들이 Delete됩니다.
    -Recovery
    RMAN> switch database to copy;
    문제가 발생하셨을 때 위 명령어를 사용하시면 모든 datafile의 pointer들은 image backup copy를 바라보게 됨으로 Restore의 시간을 절약할 수 있습니다.
    4) Retention Policy에 따른 Syntax 변화
    * 기본적으로 INCREMENTAL MERGE BACKUP & RECOVERY의 장점인 Recovery 시간을 극대화 하기 위해서는 Retention Policy를 redundancy 1(Default)로 설정하시는 것을 권장해드립니다.
    하지만 User가 Backup & Recovery 계획을 변경하여 retention policy를 recovery window 또는 redundancy 1 이상으로 설정해 주시면 Obsolete한 Backupset을 Delete하는 부분과 Backupset을 적용시키는 부분을 수정해 주셔야합니다.
    - Recovery Window of 2
    Recovery Window를 2일로 설정해 놓으시면 Backup시에는 똑같은 Syntax를 사용하실 수 있으나 Recover copy of database 명령어는 아래와 같이 바뀌어야 합니다.
    RMAN> BACKUP INCREMENTAL LEVEL 1
    FOR RECOVER OF COPY
    WITH TAG WEEKLY DATABASE;
    RMAN> RECOVER COPY OF DATABASE WITH TAG WEEKLY until time 'sysdate-2';
    왜냐하면 retention policy에 마춰서 image copy도 2일전의 상태로 보관되어야하며 그에 따라서 2일동안의 Backupset들도 보관되어야하기 때문입니다. 만약 until time을 사용하지 않으시면 incremental backup들이 obsolete 상태로 안변하게 됩니다.
    - Redundancy 2 이상
    Redundancy 2이상으로 설정해 주시면 2개 이상의 Tag를 보관하는 효과로서 역시 예상대로 Obsolete로 안 변하는 현상이 발생됩니다.
    DAY 1)
    RMAN> BACKUP INCREMENTAL LEVEL 1 FOR RECOVER OF COPY WITH TAG DAILY DATABASE;
    -위와 같이 실행하시면 한개의 Database Copy (Tag DAILY)가 생성됩니다.
    DAY 2)
    RMAN> BACKUP INCREMENTAL LEVEL 1 FOR RECOVER OF COPY WITH TAG DAILY DATABASE;
    RMAN> BACKUP INCREMENTAL LEVEL 1 FOR RECOVER OF COPY WITH TAG WEEKLY DATABASE;
    -위와 같이 실행하시면 한개의 Database Copy (Tag WEEKLY)와 한개의 Backupset (Tag DAILY)가 생성됩니다.
    DAY 3)
    RMAN> BACKUP INCREMENTAL LEVEL 1 FOR RECOVER OF COPY WITH TAG DAILY DATABASE;
    RMAN> BACKUP INCREMENTAL LEVEL 1 FOR RECOVER OF COPY WITH TAG WEEKLY DATABASE;
    RMAN> BACKUP INCREMENTAL LEVEL 1 FOR RECOVER OF COPY WITH TAG MONTHLY DATABASE;
    -위와 같이 실행하시면 한개의 Database Copy (Tag MONTHLY)와 두개의 Backupset (Tag DAILY, Tag WEEKLY)가 생성됩니다.
    DAY 4)
    RMAN> Delete Obsolete;
    - 위와 같이 실행하시면 DAILY Tag와 관련된 부분이 Delete 됩니다. (최신 2개의 Tag관련 Backup만 보관)
    RMAN> Delete Obsolete redundancy 1
    - 위와 같이 실행하시면 DAYLY Tag와 WEEKLY Tag 관련된 부분이 Delete 됩니다. (Redundancy 1로 설정한 것과 똑같은 효과)
    Reference:
    Article-ID: Note 351455.1
    Title: Oracle Suggested Strategy & Backup Retention
    Article-ID: Note 303861.1
    Title: Incrementally Updated Backup In 10G
    글 수정:
    hunlee

    I would always include an archivelog backup:
    ... with tag 'fullbackup’ database plus archivelog delete all input;
    And at the end:
    delete obsolete noprompt;
    That delete incrmental backups already applied to the basic image copies.
    Your configuration allows only limited point in time recoveries. As soon as an incremental backup is applied to the image copies, you cannot go back in time. To change this you can add a 'until time' clause, for example:
    recover
    copy of database
    with tag 'fullbackup until time 'sysdate-11';
    This creates a recovery window of 10 days, only image copies older than 10 days will be changed.
    Werner

  • Backup Solutions for my MacBook Pro+

    I have a Macbook Pro (2010) w/500gb hard drive. I have one 500gb external hard drive that holds movies and my Aperture library. My current backup solution is a 2nd external hard drive (2TB) that I attach to my laptop while my smaller external hard drive is attached (it is not excluded from the backup).
    I manually attach the laptop and 500gb ehd every week or so to backup to Time Machine
    The problem?  My laptop is approaching it's limit and I'm thinking that I need to move my iPhoto library off to an ehd as well.
    I'm wondering if backing up to my Time Machine drive with a laptop and two ehd (each 500 gb) is smart or if I need to backup those hard drives to other ehd separately.
    Also, I plan to buy an iMac for my family in the next couple of months.  Not sure how that should impact my backup configuration.
    I've also heard that in addition to Time Machine I might consider getting an ehd specifically with the purpose of being a bootable drive (via Super Duper)
    With all of these options my head is swimming a bit.
    Would love recommendations for a backup workflow/solution based on my equipment.
    Thoughts?

    Pretty much any drive will work, but for a laptop, you might like to get a portable drive (doesn't require that you connect it to power) with USB3. Thunderbolt drives are also available, but they're more expensive and no faster than USB3 for a single hard drive.
    I personally like the Lacie rugged series: http://store.apple.com/us/product/H9377ZM/A/lacie-1tb-rugged-hard-drive-triple-u sb-30-5400-rpm?fnode=5f
    If you shop around you should be able to get it a little cheaper than Apple's prices.
    Matt

  • Which backup solution to use?

    I didn't see anything here, but only looked a few screens deep, so sorry if this comes up a lot.
    I just found out from reading here that I was running BOTH the Windows backup AND the Lenovo R&R backup. Nowhere does the computer warn about this (something that should be fixed, IMO).
    I deleted all the R&R backups and recovered almost 60GB of disk space.
    Can someone provide a link or an explaination as to which service is "better", or at least a comparison. From reading, it seems it is recommended to only run one of them. I saw one post which said R&R was better at recovering, etc, but I see other posts which says it just fails (for that person)...
    I have a 142gb drive (reported size for C  Thinkpad T61p purchased in Dec 2007, running Vista Ultimate with SP1
    Thanks.

    977220 wrote:
    Hi ,
    We have Oracle 8i DB running on Windows with Backup using CA client.
    We are planning to migrate all backups from CA to Netbackup but since Oracle 8i is no longer supported by Netbackup so we need to use either RMAN or User managed backup .
    Can somebody guide,which backup solution to use on Oracle 8i (we will migrate DB to MS-SQL) so this will be temporary solution for DB backup.
    1) shutdown IMMEDIATE
    2) OS file copy all the files
    3) STARTUP

  • I want a better backup solution.

    My current network consists of a 1Tb Time Capsule backing up a 500Gb HDD in an iMac and a 500Gb HDD backing up a MacBook Pro via the wireless network.
    I have a 3Tb HDD attached externally to the iMac that I use for large file storage and remote access with my MacBook Pro. It's been a few years since I made the purchase and began using the drive in this way, and I feel like it's time to prepare for the failure of the drive. I've been present for many drive failures of friends and family. I don't take risks of losing my data.
    I was curious of the backup solutions you all must have, drive brands that you trust (I'm a WD fan), and if you use RAID 1 or RAID 1 Mirroring.
    Thank you.

    I use a number of Lacie D2 Quadra drives + OWC Mercury Elite enclosures with WD Caviar Black SATA drives.   They have been 100% reliable for many years.   (I formerly used Seagate Barracuda drives, but gradually migrated to the Caviar Blacks).  In practice, I have 3x backups on separate drives.  The drives are only connected during backup operation, otherwise they are disconnected from my Macs, each other and power.  I keep one set offsite.
    For my more frequent, interim backups, I also use a Lacie D2 Network2 online in my network;  I back up email & documents more frequently than other files since they change daily.  I use a combination of manual copies via the Finder and automated backups via CarbonCopyCloner depending on what I want to backup at any particular time.  I do not use Time Machine or a Time Capsule.
    RAID is interesting and useful, but it is not backup.  Mirroring only protects you against a single hard drive failure in the Mirror set itself.  It does not protect you from software, user or system errors, which are much more frequent than hard drive failures.  And in the event the RAID Mirror enclosure itself fails, both drives are likely to be unusable.

  • Backup solutions for Solaris 10 systems

    I am trying to put together a backup solution for a number of SunFire V240 systems running Solaris 10. We do run our backups using NetWorker, along with a couple of high powered back up systems. But this solution I am trying to create is something that can be performed by our first responders, our help desk folks. The systems in question are already in production but we do have days where we can bring them down for maintenance or whatever we need to do. Therefore, I can implement this new solution during the day(s) of maintenance time.
    I was looking at using Solaris Volume Manager and its metadata configurations. But I am unsure how to start with files sytems already created. I want to be able to have a backup of the boot disk in the event that the hard drive in which it resides goes down. I want our help desk folks be able to immediately bring the system right back up with little down time during the evening to late hours.
    I guess what I am looking for are exact steps to help configure this backup solution with Solaris Volume Manager for our production systems. Can anyone help?

    Hey there,
    Have a look at this excellent guide. I think that you may find what you need here. If not drop an email back. To begin with you need an extra disk(s) since you will mirror your data. This is sort of a pre-requisite.
    Good luck,
    Pierre
    http://www.adminschoice.com/docs/solstice_disksuite.htm

Maybe you are looking for