FIRST TIMER: Backups and recovery. [W530]

First time ever attempting to create recovery media, so the questions may be numerous.
For the first time creating backup media for Factory Recovery image, how much space is required on the medium?
I would prefer to have it stored onto a USB stick because they are much easier to store and keep track of...
Also, If i wanted to switch from the 500gb HDD that I ordered with the thinkpad to a SSD in the future would running the Factory Recovery media onto that drive create an exact image compared to the one on the HDD (included with preloaded partition "Q: Lenovo_Recovery")  If not, how would I go about transfering the data?
W530 i7-3840Qm. Quad K1000M. 16GB RAM. 16GB mSSD(expresscache). 500gb HDD

The Backup program copies the data in your Windows partition to another drive, so you need as much free space in your backup drive as you have used space in your Windows partition. It also takes a correspondingly long time to complete, so keep that in mind.
In order to make an exact copy of the whole drive, you need imaging software like Acronis True Image, Norton Ghost, or something similar.
Thinkpad W530, i7-3720QM, 1920x1080 screen, 32GB RAM, dual SSDs (Samsung 830, Crucial M4 mSATA), Quadro K2000M, 9-cell battery, DVD burner, backlit keyboard, Bluetooth, Intel 6300 wireless card

Similar Messages

  • Dell Backup and Recovery - Factory Recovery fails, need advice.

    Back story:
    I have tried this three times on three separate laptops, with poor results. Windows 7 on two of them and 8.1 one one, on all three the recovery partition is corrupt.I first boot it off of a live disk and backup any desired files. Then I boot, press F8, choose "Repair your computer" and discover that "Dell Factory Image Restore" is not one of the available options... so I boot the pc off of a different live disk and remove a bunch of "viruses", then I boot it off of the internal harddrive.In Windows I find that "Dell Backup and Recovery" may or may not be on the pc. It may or may not have ever been run before. If it is absent I download it and install it. When I run DBaR it tells me it needs to update, don't power off or disconnect the machine from the internet, etc. I then wait HOURS for this part to complete. When done it...
    This topic first appeared in the Spiceworks Community

    Country: Greece
    Ship date: March 04, 2013
    XPS 14 (L421X, Mid 2012)
    EMEA (Europe, Middle East and Africa) Support is not provided on the USA User Forum. You have to contact support in your country.
     Dell Backup and Recovery SOFTWARE support is also not provided here.
            Download Dell Backup and Recovery

  • Error in Oracle Database Backup and Recovery User's Guide 12c Release 1 (12.1) E17630-13

    on page 88 of the "Backup and Recovery User's Guide 12c Release 1 (12.1) E17630-13", the example 5-1 SHOW ALL Command is the same of the "Backup and Recovery User's Guide 11g Release 2 (11.2) E10642-06" on page 82 and that output is related to a Oracle Database 11g version (the 10g doesn't print the first line "RMAN configuration parameters for database with db_unique_name PROD1 are:").

    My test cases here:
    Database administrator workshop: Differences in default RMAN configuration settings between 12c and 11g
    {code}[oracle@vsi08devpom ~]$ export ORACLE_SID=CDB001
    [oracle@vsi08devpom admin]$ sqlplus system/oracle@CDB001
    SQL*Plus: Release 12.1.0.1.0 Production on Thu Sep 26 09:10:50 2013
    Copyright (c) 1982, 2013, Oracle.  All rights reserved.
    Last Successful login time: Tue Jul 16 2013 13:43:48 +02:00
    Connected to:
    Oracle Database 12c Enterprise Edition Release 12.1.0.1.0 - 64bit Production
    With the Partitioning, OLAP, Advanced Analytics and Real Application Testing options
    SQL> show con_name
    CON_NAME
    CDB$ROOT
    [oracle@vsi08devpom ~]$ rman target /
    Recovery Manager: Release 12.1.0.1.0 - Production on Thu Sep 26 09:12:42 2013
    Copyright (c) 1982, 2013, Oracle and/or its affiliates.  All rights reserved.
    connected to target database: CDB001 (DBID=4134963396)
    RMAN> show all;
    using target database control file instead of recovery catalog
    RMAN configuration parameters for database with db_unique_name CDB001 are:
    CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
    CONFIGURE BACKUP OPTIMIZATION OFF; # default
    CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
    CONFIGURE CONTROLFILE AUTOBACKUP ON; # 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 COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default
    CONFIGURE RMAN OUTPUT TO KEEP FOR 7 DAYS; # default
    CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/opt/app/oracle/product/12.1.0/db_1/dbs/snapcf_CDB001.f'; # default{code}
    {code}
    [oracle@localhost orcl]$ rman target /
    Recovery Manager: Release 11.2.0.2.0 - Production on Wed Sep 25 08:12:17 2013
    Copyright (c) 1982, 2009, Oracle and/or its affiliates.  All rights reserved.
    connected to target database: ORCL (DBID=1229390655)
    RMAN> show all;
    using target database control file instead of recovery catalog
    RMAN configuration parameters for database with db_unique_name ORCL are:
    CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
    CONFIGURE BACKUP OPTIMIZATION OFF; # default
    CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
    CONFIGURE CONTROLFILE AUTOBACKUP OFF; # default
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE SBT_TAPE 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 DATAFILE BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
    CONFIGURE MAXSETSIZE TO UNLIMITED; # default
    CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
    CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
    CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default
    CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/home/oracle/app/oracle/product/11.2.0/dbhome_2/dbs/snapcf_orcl.f'; # default
    {code}

  • Backup and recovery questions

    Hi,
    I am a newbie in Oracle database 11g Release 11.2.0.1.0 and Oracle Linux and I have questions regarding backup and recovery.
    I used the “Schedule Oracle-Suggested Backup” and have it run nightly to back up to local disk. In the Backup Setting, on the Retention Policy, I selected “Retain backup that are necessary for a recovery to any time within the specified number of days (point-in-time recovery) day = 7”
    With the setting above, I checked the “Manage Current Backups” and I have many back sets for SPfiles, controlfiles, datafiles, and archivelogs for the last several days. However, for image copies, I have only one set and it get over write nightly. With the configuration above, is that true that I can only recover to any point in last 24 hours?
    My goal is to be able to recover any “point-in-time” in the past 5 days, should I change my Retention Policy to “Retain at least the specified number of full backups for each datafile” to 5 backups (each full daily backup)?  Please provide some advices. Thanks

    By looking the following, it looks like by default its 24 hours but it depends upon the recovery window you choose.
    Enterprise Manager makes it easy to set up an Oracle-suggested backup strategy for backups to disk that protects your data and provides efficient recoverability to any point in the a recovery window of your choosing. (In the simplest case, examined in this section, this window is 24 hours.) The Oracle-suggested strategy leverages Oracle's incremental backup and incrementally-updated backup features to provide faster backups than whole database backups, and faster recoverability than is possible through applying database changes from the archived log to your datafiles.
    The Oracle-suggested backup strategy is based on creating an image copy of your database. This copy is rolled forward by means of incrementally updated backups. Oracle Enterprise Manager schedules RMAN backups jobs for you to run during the overnight hours.
    For each datafile, the strategy calls for backups as follows:
    At the beginning of day 1 of the strategy (the time the first scheduled job actually runs), an incremental level 0 datafile copy backup. It contains the datafile's contents at the beginning of day 1. In a restore-and-recovery scenario, the redo logs from day 1 can be used to recover to any point during day 1.
    At the beginning of day 2, an incremental level 1 backup is created, containing the blocks changed during day 1. In a restore-and-recovery scenario, this incremental level 1 can be applied to quickly roll forward the level 0 backup to the beginning of day 2, and redo logs can be used to recover to any point during day 2.
    At the beginning of each day n for days 3 and onwards, the level 1 backup from the beginning of day n-1 is applied to the level 0 backup. This brings the datafile copy to its state at the beginning of day n-1. Then, a new level 1 is created, containing the blocks changed during day n-1. In a restore-and-recovery scenario, this incremental level 1 can be applied to the datafile rolled forward on day n-1 to the beginning of day n, and redo logs can be used to recover the database to any point during day n.
    The datafile copies used in the Oracle-suggested backup strategy are tagged with the tag ORA$OEM_LEVEL_0. The level 1 incremental backups for use in this strategy are created for use with datafile copies that are so labelled. You can safely implement other backup strategies without concern for interference from the backups for the Oracle suggested strategy.
    There are also Oracle-suggested strategies that use tape backups along with disk backups, but those are beyond the scope of this chapter.

  • Backup And Recovery on 7.2.3

    i need information on backup and recovery, please help me.(from begin)
    i don't speak english, but don't worry, i read the english.
    Thanks you.
    Oscar Rojano. [email protected]

    i suggest you read the oracle backup and recovery manual sections, or take the course, as this is an extremely important topic.
    a cold backup is done when the database is down. to do a cold backup, first shutdown the database. then backup all datafiles. then restart the database. you can use this type of backup if your business can tolerate the database being down for the time it takes to do the backup.
    a hot backup is done when the database is up and running. the database must be running in archive log mode. then, a hot backup can be performed by putting tablespaces into backup mode, and then backing up the affected datafiles. whenever you do a hot backup, you must be sure to also back up all archive log files from the start of the backup through the end of the backup. if you must restore the backup, and you don't have the archive logs, your database will not start and you will not be able to get it back.
    an export is a backup of selected tables. it is not a complete backup and should not be used if a fast, complete recovery of the entire database is required. it is good if a fast restore of a single table is something you need to do often. be aware of database consistency problems if you are restoring a single table that is updated frequently.
    depending on your requirements, you will use one or more of the three backup solutions above.
    i would recommend that you use the oracle RMAN (recovery manager) tool, in conjunction with an enterprise backup tool from HP, Veritas, or IBM, to be sure your backups are as complete and reliable as possible.

  • Backup and Recovery of Enterprise

    I've inherited an instance of Enterprise XI R2, and have discovered that it is a critical system, but is not being backed up.  I'm new to this, please bear with me.
    I found the backup and recovery guide (https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c09a069c-6a3f-2b10-3399-e0ed04d866f8), and it gives a good high level overview, but I need a little more info.
    Questions: 
    1.  The guide states that "The Central Management Server (CMS) and all job-processing and Performance Management servers should be stopped by an automated script."  Is there a specific order that the servers need to be stopped and started in?  Would anyone be willing to share their script?
    2.  I assume that when the servers are down, anything scheduled to run during that time will be lost.  i.e., the server won't check for missed jobs caused by the stopped state once the it resumes, correct?
    3.  The only thing that I need to back up on the file system is the contents of FileStore (C:Program FilesBusiness ObjectsBusinessObjects Enterprise 11.5FileStore*.*), correct?
    4.  This looks like a vanilla install using MySql.  Would anyone be willing to share their MySql backup scripts?  Is there a default password for MySql?  How can I determine this password?  How many databases are there? 
    5.  I plan to create a backup script that stops the servers, copies the FileStore path to a backup folder (using xcopy to preserve the archive attribute), have MySql generate a backup file to the same folder, and then start the servers.  This folder will be written to tape nightly (fulls on weekends, incrementals during the week).  Is there anything else that I might need to backup?  Config files?  Ini's?
    Thanks!!!

    1. There is no specific order, but last to go down should be CMS and first to come up should be CMS.
    @echo off
    Stop Business Objects Services
    echo
    net stop "BOBJCrystalReportApplicationServer"
    net stop "BOBJEventServer"
    net stop "BOBJProgramServer"
    net stop "BOBJOutputFileServer"
    net stop "BOBJProcessServer"
    net stop "BOBJInputFileServer"
    net stop "BOBJDestinationServer"
    net stop "BOBJCrystalReportspageserver"
    net stop "BOBJJobServer_Report"
    net stop "BOBJCentralMS"
    exit
    Similarly to Start services, instead of stop use start and put CentralMS at the top and save it as a batch file.
    2. Jobs running when the server goes down will fail, other recurring jobs will wait till the server comes up.
    3. Yes, backup File Store & Database.
    4. Not sure about the default password for My SQL, you should be able to backup the MySQL database, I have done that once.
    5. Backup FileStore & Database.

  • Backup and Recovery procedures for production system

    I am trying to decide and test a best backup/recovery approach for our DBXML database in the production environment. Right now I am trying to go through the documentation.
    http://www.oracle.com/technology/documentation/berkeley-db/db/gsg_txn/CXX/filemanagement.html
    What is the best option among offline, hot and incremental backups?
    I am thinking of implementing incremental backups.
    What are the constraints in implementing incremental backups? Is there a detailed step by step example to do this?
    Can I test the backup and recovery procedures by copying the db files and log files from Linux (production) environment to my local machine (Windows XP)? I see only one log.00000000xx file in production and staging environments. It is of same size 52428800 in all our environments (both production and staging) at this point of time.
    What is __db.001 file? What is the significance of this file in backup and recovery procedures?
    A detailed input with example is greatly appreciated.
    Thanks in advancs

    Raghu,
    A couple of points, up front:
    1. the __db* files are the environment (cache, locks, various shared memory regions), and are not part of backup, other than the fact that you need to checkpoint or otherwise flush your cache to your database(s) for a full backup.
    2. log files are not architecture-neutral. That is you can't use a log file created on linux and just use it safely on another hardware platform. It's OK to copy them around, but they can only be used on the same architecture that created them. Database files (containers) are entirely portable among hardware and operating system platforms.
    I don't know of a step-by-step cookbook for backups. This is because of the variations among application needs. However, the procedures described on this page are pretty straightforward:
    http://www.oracle.com/technology/documentation/berkeley-db/db/gsg_txn/CXX/backuprestore.html
    I'm not sure what you mean by "constraints" on incremental backups. The only constraint is that you need to have a full backup first, or you won't be able to recover properly. Based on what I said above, the other constraint is that you'll only be able to recover on a machine of the same architecture as the one that created the log files.
    As for testing, you can certainly copy your database and log files to your Windows machine, treating Windows as an offline backup. If you want to test recovery, you need to copy the files back to Linux. You'll start seeing additional log files when your log data starts to exceed the configured log file size.
    Let me know if you need more clarification,
    Regards,
    George

  • LIVE Video Tutorial! How to Prepare for Backup and Recovery - HP Expert Day "How-To" Video Series – Today at 2:00pm PST

    Join us at 2:00pm Pacific time for a LIVE video tutorial of how to prepare for system backup and recovery! The video features HP experts who work with the products every day!
    I am an HP employee.

    #test

  • Issue with backup and recovery of WLS

    I have installed WLS 10.3.6 in my 64-bit Linux box, now I am trying to take backup my server. I have a web-application deployed to my WLS, the path to my war file was something like:
    <home_dir>/install_files/myapp.war
    Now to take backup I ran tar command on my current Linux box, now I copied the .tar files to my new Linux box and extracted it. When I am starting my weblogic server it is looking for the war file from the path <home_dir>/install/myapp.war which does not exist on my new machine. So I logged into Admin console of WLS on my new machine and trying to change the path for myapp.war by clikcing update button. But I am getting this error when I change the path:
    weblogic.management.ManagementException: [Deployer:149007]New source location, '/u01/Oracle/install_files/myapp.war', cannot be deployed to configured application, 'myapp'. The application source is at '<home_dir>/myapp.war'. Changing the source location is not allowed for a previously attempted deployment. Try deploying without specifying the source.
    Update operation failed - no deployments changed.
    Please help me how to deploy my files. I'm expecting backup and recovery option should also take care of deployed files but it is not happening in my case, is that wrong?

    1. There is no specific order, but last to go down should be CMS and first to come up should be CMS.
    @echo off
    Stop Business Objects Services
    echo
    net stop "BOBJCrystalReportApplicationServer"
    net stop "BOBJEventServer"
    net stop "BOBJProgramServer"
    net stop "BOBJOutputFileServer"
    net stop "BOBJProcessServer"
    net stop "BOBJInputFileServer"
    net stop "BOBJDestinationServer"
    net stop "BOBJCrystalReportspageserver"
    net stop "BOBJJobServer_Report"
    net stop "BOBJCentralMS"
    exit
    Similarly to Start services, instead of stop use start and put CentralMS at the top and save it as a batch file.
    2. Jobs running when the server goes down will fail, other recurring jobs will wait till the server comes up.
    3. Yes, backup File Store & Database.
    4. Not sure about the default password for My SQL, you should be able to backup the MySQL database, I have done that once.
    5. Backup FileStore & Database.

  • BACKUP AND RECOVERY USING RMAN

    제품 : ORACLE SERVER
    작성날짜 : 2003-08-04
    BACKUP AND RECOVERY USING RMAN
    ==============================
    1. Backup Method
    1.1 backing up in noarchivelog mode
    SVRMGR> shutdown;
    SVRMGR> startup mount
    rman을 가동시킨 후 다음을 수행
    run {
    # backup the database to disk
    allocate channel dev1 type disk;
    backup (database format '/oracle/backups/bp_%s_%p'); }
    1.2 Backing up databases and tablespaces in archivelog mode >
    - database 단위 backup script
    run {
    allocate channel dev1 type 'sbt_tape';
    backup skip offline (database format '/oracle/backups/%d_%u');
    release channel dev1;
    - tablespace 단위 backup script
    run {
    allocate channel dev1 type disk;
    backup
    (tablespace system,tbs_1,tbs_2,tbs_3,tbs_4,tbs_5
    format '/oracle/backups/bp_%s_%p');
    - datafile 단위 backup script
    run { 
    allocate channel dev1 type disk;
    backup
    (datafile '?/dbs/t_dbs1.f'
    format '/oracle/backups/%d_%u');
    - control file backup script
    control file은 system datafile의 첫번째 화일을 백업받을 때 백업되며 다음과
    같은 방법으로도 백업받을 수 있다.
    run {
    allocate channel dev1 type 'sbt_tape';
    backup
    (tablespace tbs_5 include current controlfile
    format '%d_%u');
    - archived logs backup script
    NLS_LANG=american
    NLS_DATE_FORMAT='Mon DD YYYY HH24:MI:SS'
    run {
    allocate channel dev1 type 'sbt_tape';
    backup
    (archivelog from time 'Nov 13 1996 20:57:13'
    until time 'Nov 13 1996 21:06:05'
    all
    format '%d_%u');
    run {
    allocate channel dev1 type 'sbt_tape';
    backup
    (archivelog low logseq 288 high logseq 301 thread 1
    all delete input
    format '%d_%u');
    - copying datafiles
    run {
    allocate channel dev1 type disk;
    copy datafile '?/dbs/tbs_01.f/dbs/tbs_01.f' to '?/copy/temp3.f';
    - incremental backups
    새로운 데이타화일이 추가되거나 테이블스페이스가 추가된다면 level 0의 backup을
    반드시 수행한다.
    run {
    allocate channel dev1 type 'sbt_tape';
    backup incremental level 0
    (database
    format '%d_%u');
    run {
    allocate channel dev1 type 'sbt_tape';
    backup incremental level 1
    (database
    format '&d_%u');
    2. Recovery Method
    - tablespace recovery
    run { 
    allocate channel dev1 type disk;
    allocate channel dev2 type 'sbt_tape';
    sql "alter tablespace tbs_1 offline immediate" ;
    set newname for datafile 'disk7/oracle/tbs11.f'
    to 'disk9/oracle/tbs11.f' ;
    restore (tablespace tbs_1) ;
    switch datafile all ;
    recover tablespace tbs_1 ;
    sql "alter tablespace tbs_1 online" ;
    release channel dev1;
    release channel dev2;
    - point-in-time recovery
    TBS_1 테이블스페이스는 두 개의 데이타 화일 소유. TEMP1은 백업이 없으나 user
    data는 없는 temporary segemnt만 가지고 있음.
    NLS_LANG=american
    NLS_DATE_FORMAT='Mon DD YYYY HH24:MI:SS'
    SVRMGR> shutdown abort;
    SVRMGR> startup nomount;
    run { 
    # recover database until 3pm after restoring tbs_1 to a new location
    allocate channel dev1 type disk;
    allocate channel dev2 type 'sbt_tape';
    set until time 'Nov 15 1996 15:00:00'
    set newname for datafile '/vobs/oracle/dbs/tbs_11.f'
    to '?/dbs/temp1.f' ;
    set newname for datafile '?/dbs/tbs_12.f'
    to '?/dbs/temp2.f' ;
    restore controlfile to '/vobs/oracle/dbs/cf1.f' ;
    replicate controlfile from '/vobs/oracle/dbs/cf1.f';
    sql "alter database mount" ;
    restore database skip tablespace temp1;
    switch datafile all;
    recover database skip tablespace temp1;
    sql "alter database open resetlogs";
    sql "drop tablespace temp1";
    sql "create tablespace temp1 datafile '/vobs/oracle/dbs/temp1.f' size 10M";
    release channel dev1;
    release channel dev2;
    - 전체 데이타베이스를 복구하려 할때
    current redologfile이 존재할때 다음과 같은 작업으로 전체 데이타베이스를 복구할
    수 있다.
    replace script restore_recover_db_cf {
    execute script restore_cf;
    sql 'alter database mount';
    execute script restore_db;
    execute script recover_db;
    sql 'alter database open resetlogs';
    replace script alloc_1_disk {
    allocate channel d1 type disk;
    setlimit channel d1 kbytes 2097150 maxopenfiles 32 readrate 200;
    replace script rel_1_disk {
    release channel d1;
    replace script restore_cf {
    execute script alloc_1_disk;
    restore
    controlfile to '/private/db_files/twih/dbf/ctrl_twih_1.ctl';
    replicate
    controlfile from '/private/db_files/twih/dbf/ctrl_twih_1.ctl';
    execute script rel_1_disk;
    replace script restore_db {
    execute script alloc_1_disk;
    restore
    (database);
    execute script rel_1_disk;
    replace script recover_db {
    execute script alloc_1_disk;
    recover
    database;
    execute script rel_1_disk;
    Reference Documents
    <Note:104796.1>

    Hi Alok,
    why there is a need for standby here? you mean to say standby db?
    what i exactly need is , whether i will be making use of archivelogs which are all archived during that backup period (in mount stage) after some days, if i face any problem with the PRODUCTION Database..

  • About Backup and Recovery in a distribuited enviroment

    Hi.
    I've read that if you more that one DB (say 2) connected in a distribuited enviroment, all DBs must be recovered in case one of your DBs fails.
    I'd like to clarify the folloiwng issues:
    - It that 100% true, i mean isn't an exception to that rule?.
    - What happens if one DB is in archive mode and the other is not?
    - Why do i have to restore both DBs if there's one one in trouble?.
    - Isn't there a way to tell recovery process that you don't want restore or apply the distributed data, since you know that data is already there (at least in the case of complete recovery)?
    Thanks in advance ...!

    I couldn't find much info on the topic for 9i (you don't mention your version), but found this in the Backup and Recovery Concepts manuls:
    "If the database is a member of a distributed database system, then all databases in the system should operate in the same archiving mode. Note the consequences and constraints contained in the following table.
    Mode Constraint Consequence
    ARCHIVELOG
    Closed cleanly
    Backups at each node can be performed autonomously, that is, individually and without time coordination.
    NOARCHIVELOG
    Closed cleanly
    Consistent whole database backups must be performed at the same global time to plan for global distributed database recovery. For example, if a database in New York is backed up at midnight EST, the database in San Francisco should be backed up at 9 PM PST."
    Therefore, I wouldn't recommend having one database in archivelog mode and the other not. As far as your last question is concerned, I'd say that Oracle won't try any recovery if there isn't a need for it (if the data is already there), but that could be tested to confirm. I think that you need to read carefully the RAC concepts manual, and try some backup/recovery scenarios hopefully on a test box.
    Daniel

  • Dell Inprision 2330 Backup and Recovery error message 0x4001100200001005

    A week ago, there were problems with the computer Dell Inprision 2330, and I'm using a Dell Backup and Recovery to restore the disk C to the image stored on the dvd disks. 3 days ago the computer began to hang when windows starts. I decided again to restore the system with dvd, but this time got the error message 0x4001100200001005.
    Tried to restore the image to another drive, but the error appears again.
    Other recovery media then dvd-disks "dell backup and recovery" I don't have.
    Please help.

    I was very disappointed with this buggy system recovery. After I got tired of trying to restore the system, I found a post "Download Windows 8.1 Retail and OEM.iso". Did everything according to instructions. Now the computer is running. Activation performed automatically.
    Recovery Media disks thrown in the trash.

  • Backup and recovery oracle XE

    Hi, oracle guru.
    I have searched in google how to backup and recover to and from removable disk or hard disk (in separated folder) in oracle XE 10g, but I didn't found any.
    I tried to use backup and recovery database given from oracle itself, and I analyze which file is added and modified. I do somekind of trial and error action. First, I backup my database and then I copy 2 files (I forgot the names, 1 is about 853 kb, and one is the backup file (about 500 mb)). And then I do some user deletion (I have several users) and then I backup and copy again to different folder from the previous one. Note that I am not using archive log: on.
    Unfortunately, when I copy the previous backup (the one with complete users) to oracle folder, the restore database does work until, I guess starting database, it throws error saying that something error in SYSTEM.DBF, thus making my oracle doesn't work, even I canot go to database home page.
    My question is that how to backup and recover database to and from removable disk or harddisk with different folder? Which files do I need to copy or should I add backup and recover script?
    Thanks for the reply.

    Yes, as I already mentioned, previously (assumes) that I have database with several users (say 5 users). And I use backup database and restore database from oracle folder in start menu, and it works perfectly (assuming that I delete one user and then restore database).
    However, I tried to copy the backup file (which I mentioned before, but I am not sure the files I am copying is backup file since I only analyzed it). So, I test it. First I backup, and I copy to separate folder. Next, I do some user deletion, and I do backup. Say, for example I want to use that backup file in another computer. I copy the files to oracle installation folder. One in product/database/ folder, and one in flash-recovery area. When I try to use restore database (in start menu), it works, until, I guess, starting database, and it throws error saying that error in SYSTEM.DBF.
    So, my point is that, how do I backup my database so that the backup file can be in separated folder (for example in removable disk), thus I can also select backup file to be restored.

  • Backup and Recovery Procedures for S&OP

    Hi Team,
    My customer is trying to evaluate S&OP and has the following quesitons around backup and recovery.  If you have any info on this, can you pl. share with me?
    What is the SLA on Cloud based system availability?
    How often does the backup happen for Cloud based system?
    When a system goes down and there is a recovery, how much data would be lost – i.e., what is the lapse time between backups?
    Thank you
    Kamala

    Hi Kamala Rao,
    Please follow this link. Hope it will help your question.
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/805fbf53-8295-3110-1d89-f4cfc211687f?QuickLink=index&…

  • Backup and recovery a tablespace

    Hi all,
    I recently started reading about oracle backup and recovery concepts, and  I needed to understand what is happening where we put a tablespace to a backup mode (alter tablespace tablespace_name begin backup) ?
    thanks for help

    Three things happen when you put a tablespace in hot backup mode:
    1. A checkpoint is issued, so that dirty blocks belonging to that tablespace are flushed to disk
    2. The header of the datafiles associated with the tablespace are locked from further update by CKPT.
    3. The first insert/update/delete that affects a data block that is part of the tablespace being backed up, after the 'begin backup' command is issued, causes the entire block to be written to the online redo logs. Second and subsequent changes generate the same amount as redo as normal, though.
    That's it. As Hemant mentions, the really important bit is number 2 in that list: whilst the header of the datafile(s) is locked, the datafiles themselves are not, and are written to as much as they always are. The idea that somehow the datafiles are not written to and that the redo logs are the only place that stuff is written to during the backup is completely and utterly wrong. CKPT is not allowed to write to the header, because that way, we know the earliest "age" of the datafile copy when it went into backup mode, and thus know the point from which redo needs to be applied during a recovery. But DBWR writes to the rest of the datafile perfectly normally.
    Number 3 is also important, because it's why we don't leave tablespaces in hot backup mode more than we can help: the amount of redo generated increases because we need a 'starter image' for any block that's modified during the backup.

Maybe you are looking for