Difference between disaster recovery and cloning db

hi,
i have configured cloning of database through rman backup and write now i 'm going to configure disaster recovery database .
please tell me the difference between both .
thanks.

can you provide me any link upon disaster recovery so i could learn much about ithttp://www.oracle.com/us/products/ondemand/collateral/disaster-recovery-exec-brief-069248.pdf
http://www.oracle.com/technetwork/database/features/availability/dataguardoverview-083155.html

Similar Messages

Difference between Database Mirroring and Cloning?

Hi,
Can anybody tell me the exact difference between Database Mirrorring and cloning?
Is database mirroring and multiplexing same?
Thanks
Rajesh

cannot be kept current automatically with the source database It is possible using manually scripted code to automatically update a cloned database to in effect build your own mirrowing process. This is basically a description of home grown Data Guard and is how many sites maintained a ready to use backup prior to Oracle introducing Data Guard.
The best way to create a clone database today is probably to use the rman duplicate command.
The clone could be the base for use with a mirrowing process you are setting up or used for other purposes such as providing a consistent frozen snapshot of production for special reporting. It could become the unit test or system test environment or perhaps be used for diaster recovery purposes.
A clone is a one-time event. Mirrowing is an ongoing process.
HTH -- Mark D Powell --

DIFFERENCE BETWEEN THE FULL AND BULK-LOGGED RECOVERY MODEL

DIFFERENCE BETWEEN THE FULL AND BULK-LOGGED RECOVERY MODEL

In bulk logged recovery mode certain bulk operations are minimally logged. In FULL recovery mode these are fully logged. These bulk operations are as mentioned below
1. SELECT INTO
2. BULK IMport operations including BULK INSERT and BCP
3. INSERT INTO SELECT command using the OPENROWSET(BULK) function
4. Partial updates to columns having large value data type
5. Using WRITE clause in UPDATE statements
6. Index operations e.g CREATE INDEX, ALTER INDEX REBUILD , DROP INDEX
In Bulk Logged Recovery Mode when you execute these operations SQL Server only logs the fact that these operation occured and information about space allocation. The actual change in the data is maintained in the BCM (Bulk
Changed Map)
Since the actual changes are not recorded in the log file, the log file size in the reletively less in size but this tradeoff comes with the price of increased backup time. This is so because during the log backup its not just the log being backup, but also
the extents that are marked by the Bulk Changed Map as changed.
SQLEnthusiast
http://sqlsimplified.com/
Please click the Mark as Answer button if a post solves your problem!

Difference between "Data replication", "Data Cloning", "Data duplication" and "Data Migration"

Hi Gurus,
Can anyone tell me the difference between "Data replication", "Data Cloning", "Data duplication" and "Data Migration". I have gone through Google but doesn't find any appropriate answer for that where I can find the difference.
It would be highly appreciated if you give me a link for all and give me some point out.
Thanks & Regards
Nimai Karmakar

Here is how I see the terms used and understood by most folks
"Data replication"
This is the keeping the same data in sync in 2 different databases. Replication is the process of keeping data in sync between 2 environments/databases and not limited to Oracle to Oracle, it could be Oracle to MySQL to be kept in sync, MySQL to Oracle, Oracle to SQL Server, SQL Server to Oracle. The purpose of keeping data in sync can vary, but that is basic description of what it is.
"Data Cloning"
Make a copy of the data/database from one database environment to another, like for example taking production database and cloning the database to a pre-production database/environment for testing. Coning term is used more when copying a database not just data, but the whole database so typically you hear the reference "Database Cloning", but data cloning is basically the making a copy of the data from one place to another. Sometimes Cloning and Duplicating are used in the same way by folks as the basic end result is the same you are making a copy of the data to someplace else.
"Data duplication"
This is typically term when duplicating the data from one environment to another for a particular purpose, a lot of folks use "Data/Database Cloning" and "Data Duplication" in the same context, meaning they use them to mean the same thing, but I see more difference in the terms so when they are different Data Duplication is done when combining 2 databases to 1 therefore you can not clone the 2 databases into one so this term would be used more in those circumstances.
"Data Migration"
Moving data from one location/database to another location database, for example moving from MySQL to Oracle you would do a data migration from MySQL to Oracle as you are moving the data from MySQL to Oracle and going to leave it in Oracle. You could also be migrating to from Oracle 10g environment to a new Oracle 11g environment, therefore "Migration" is typically used when referring to moving the data from one environment to another and the source and target are different in location, database vendor, database version.
These are very simple ways of looking at the terms from my experience on how they are used.

Welcome to the SQL Server Disaster Recovery and Availability Forum

(Edited 8/14/2009 to correct links - Paul)
Hello everyone and welcome to the SQL Server Disaster Recovery and Availability forum. The goal of this Forum is to offer a gathering place for SQL Server users to discuss:
Using backup and restore
Using DBCC, including interpreting output from CHECKDB and related commands
Diagnosing and recovering from hardware issues
Planning/executing a disaster recovery and/or high-availability strategy, including choosing technologies to use
The forum will have Microsoft experts in all these areas and so we should be able to answer any question. Hopefully everyone on the forum will contribute not only questions, but opinions and answers as well. I’m looking forward to seeing this becoming a vibrant forum.
This post has information to help you understand what questions to post here, and where to post questions about other technologies as well as some tips to help you find answers to your questions more quickly and how to ask a good question. See you in the group!
Paul Randal
Lead Program Manager, SQL Storage Engine and SQL Express
Be a good citizen of the Forum
When an answer resolves your problem, please mark the thread as Answered. This makes it easier for others to find the solution to this problem when they search for it later. If you find a post particularly helpful, click the link indicating that it was helpful
What to post in this forum
It seems obvious, but this forum is for discussion and questions around disaster recovery and availability using SQL Server. When you want to discuss something that is specific to those areas, this is the place to be. There are several other forums related to specific technologies you may be interested in, so if your question falls into one of these areas where there is a better batch of experts to answer your question, we’ll just move your post to that Forum so those experts can answer. Any alerts you set up will move with the post, so you’ll still get notification. Here are a few of the other forums that you might find interesting:
SQL Server Setup & Upgrade – This is where to ask all your setup and upgrade related questions. (http://social.msdn.microsoft.com/Forums/en-US/sqlsetupandupgrade/threads)
Database Mirroring – This is the best place to ask Database Mirroring how-to questions. (http://social.msdn.microsoft.com/Forums/en-US/sqldatabasemirroring/threads)
SQL Server Replication – If you’ve already decided to use Replication, check out this forum. (http://social.msdn.microsoft.com/Forums/en-US/sqlreplication/threads)
SQL Server Database Engine – Great forum for general information about engine issues such as performance, FTS, etc. (http://social.msdn.microsoft.com/Forums/en-US/sqldatabaseengine/threads)
How to find your answer faster
There is a wealth of information already available to help you answer your questions. Finding an answer via a few quick searches is much quicker than posting a question and waiting for an answer. Here are some great places to start your research:
SQL Server 2005 Books Onlinne
Search it online at http://msdn2.microsoft.com
Download the full version of the BOL from here
Microsoft Support Knowledge Base:
Search it online at http://support.microsoft.com
Search the SQL Storage Engine PM Team Blog:
The blog is located at https://blogs.msdn.com/sqlserverstorageengine/default.aspx
Search other SQL Forums and Web Sites:
MSN Search: http://www.bing.com/
Or use your favorite search engine
How to ask a good question
Make sure to give all the pertinent information that people will need to answer your question. Questions like “I got an IO error, any ideas?” or “What’s the best technology for me to use?” will likely go unanswered, or at best just result in a request for more information. Here are some ideas of what to include:
For the “I got an IO error, any ideas?” scenario:
The exact error message. (The SQL Errorlog and Windows Event Logs can be a rich source of information. See the section on error logs below.)
What were you doing when you got the error message?
When did this start happening?
Any troubleshooting you’ve already done. (e.g. “I’ve already checked all the firmware and it’s up-to-date” or "I've run SQLIOStress and everything looks OK" or "I ran DBCC CHECKDB and the output is <blah>")
Any unusual occurrences before the error occurred (e.g. someone tripped the power switch, a disk in a RAID5 array died)
If relevant, the output from ‘DBCC CHECKDB (yourdbname) WITH ALL_ERRORMSGS, NO_INFOMSGS’
The SQL Server version and service pack level
For the “What’s the best technology for me to use?” scenario:
What exactly are you trying to do? Enable local hardware redundancy? Geo-clustering? Instance-level failover? Minimize downtime during recovery from IO errors with a single-system?
What are the SLAs (Service Level Agreements) you must meet? (e.g. an uptime percentage requirement, a minimum data-loss in the event of a disaster requirement, a maximum downtime in the event of a disaster requirement)
What hardware restrictions do you have? (e.g. “I’m limited to a single system” or “I have several worldwide mirror sites but the size of the pipe between them is limited to X Mbps”)
What kind of workload does you application have? (or is it a mixture of applications consolidated on a single server, each with different SLAs) How much transaction log volume is generated?
What kind of regular maintenance does your workload demand that you perform (e.g. “the update pattern of my main table is such that fragmentation increases in the clustered index, slowing down the most common queries so there’s a need to perform some fragmentation removal regularly”)
Finding the Logs
You will often find more information about an error by looking in the Error and Event logs. There are two sets of logs that are interesting:
SQL Error Log: default location: C:\Program Files\Microsoft SQL Server\MSSQL.#\MSSQL\LOG (Note: The # changes depending on the ID number for the installed Instance. This is 1 for the first installation of SQL Server, but if you have mulitple instances, you will need to determine the ID number you’re working with. See the BOL for more information about Instance ID numbers.)
Windows Event Log: Go to the Event Viewer in the Administrative Tools section of the Start Menu. The System event log will show details of IO subsystem problems. The Application event log will show details of SQL Server problems.

hi,I have a question on sql database high availability. I have tried using database mirroring, where I am using sql standard edition, in this database mirroring of synchronous mode is the only option available, and it is giving problem, like sql time out errors on my applicatons since i had put in the database mirroring, as asynchronous is only available on enterprise version, is there any suggestions on this. thanks ---vijay

What is the difference between undo tablespace and online redo log files.

what is the difference between undo tablespace and online redo log files. I am confused
as per my knowledge undo tablespace is used to store the undo information when a table is being updated so that, just incase we need to rollback a transaction we know what was present in the table earlier.
when a transaction fails the SMON performs the rollback of the data.
This undo data is stored in the undo tablespace and read consistency if any is enforced.
is my understanding till here correct?
Now, can this undo data/before image not be stored in the redo log buffer and online redolog files?
can redo-log files not store this information?
in fact, is it that when undo tablespaces exist in a database, the undo data/before image is stored in both the undo tablespace and also the redo log files?
kindly clarify my doubt.
thank you.

This question has been asked many times before. The answer is always the same.
Yes, redo contains the before image of data (and the after-image). Therefore, it **COULD** be used to roll back a transaction.
BUT... Redo is written sequentially. Using it to rollback your transaction would involve reading through all the redo written by maybe thousands of other people. It would be painfully slow.
Your transaction is, however, directly linked to just the UNDO that it generates (which is JUST the before image of the data). So, your undo is your undo and doesn't share space with anyone else's undo. Therefore, using it to roll back YOUR transaction is fast.
The fact that undo is only the before image of the data also makes it faster than wading through a sea of before and AFTER images as you'd find in redo. About twice as fast, in fact, since there's half the data. Roughly.
Redo also gets written and flushed to disk whenever there's a commit, 3 seconds are up or too much (1MB, actually) redo gets generated between flushes caused by other factors. Your redo gets flushed when those things happen, even if you haven't actually committed your transaction. And redo logs recycle themselves, meaning that your redo -even if your transaction hasn't been committed yet- can be over-written by later transactions. Try rolling back when that's happened, if redo was the source of your rollback data!
Undo, however, cannot be over-written if the transaction has not been committed. Ever. If you don't commit for three years, there will be three years' undo stored in your database (assuming you had the space, of course!).
I could go on, but that will do. Redo is there fore RECOVERY, after catastrophe. Undo is there for read-consistency (and the occasional change of mind). Two different functions. Two different mechanisms. Each one highly tuned to doing what it does, why it does it, most efficiently and effectively.

What is the difference between FND_CONC_CLONE.setup_clean and target_clean

What is the difference between fnd_conc_clone.setup_clean and fnd_conc_clone.target_clean?
I always run setup_clean to wipe out all the information carried from source, and then run adautocfg.sh on dbTier followed by appsTeir. This will give me the clean newly cloned ebs system. But what is target_clean for? What is the difference between setup_clean and target_clean;
James

I finally go through the code and actually run the target_clean in our test system. Here is general rule, if you clone the ebs system, you only need to run setup_clean, it will clean out topology information or ebs connection information from the system. Then you run adautocfg.sh on db tier first following by adautocfg.sh on apps tier. All the topology or connection information will be populated again inside the database.
Once you have cloned the system, you do not want any printer setup info, log/out info or profile info carried from source, then you can run target_clean. For me, I do need preserve printer and profile info, so I need to export following 4 tables before running target_clean.
FND_PROFILE_OPTION_VALUES,
FND_PRINTER,
FND_PRINTER_TL,
FND_CONCURRENT_PROGRAMS
Hope this will help.
James

Difference between Synchronization Wrappers and Unmodifiable Wrappers

Hi,
I am not clear abt. the "Difference between Synchronization Wrappers and Unmodifiable Wrappers" in Collection implementation.
How Unmodifiable Wrappers make read-only access to your data structures?
Is it thru deep cloning of objects? If that is the case where this is mostly being used?

You might find it useful to look at the Collections class source code in src.zip.
It will answer both questions.
The Unmodiferable wrapper just a wrapper, no cloning occurs. Only the collection wrapped is protected. If you have collections inside collections they will not be protected.
The unmodifiable wrapper would be used to ensure a collection is not modified by third party code. It could be used if you return a Collection to ensure the caller does not 'accidently' modify it.

What is the difference between full checkpoint and incremental checkpoint?

What is the difference between full checkpoint and incremental checkpoint?
And what is checkpoint queue?
Can someone clarify these concepts?
Thanks!

Hi,
there are different types of checkpoints:
- Full checkpoint:
=> DBWR writes all dirty buffers from the Buffer cache to the datafiles and CKPT retrieves a new Checkpoint Change Number from a sys owned sequence and writes this number to all file headers and the controlfile.
-- can be triggered by different events, like a logswitch, a manual checkpoint (alter system ..), a shutdown and so on
This is the setup point for SMON for a crash recovery.
- Partial checkpoint:
=> DBWR writes all dirty buffers of a singel tablespace from the Buffer cache to the datafiles and CKPT retrieves a new Checkpoint Change Number from a sys owned sequence and writes this number to all file headers and the controlfile.
-- can e triggered by an ALTER TABLESPACE OFFLINE, ALTER TABLESPACE READ ONLY, ALTER TABLESPACE BEGIN BACKUP statement.
Incremental checkpoint:
number to all file headers and the controlfile.
-- can be triggered by different events, like a logswitch, a manual checkpoint (alter system ..), a shutdown and so on
- Partial checkpoint:
=> DBWR writes all dirty buffers of a single tablespace from the Buffer cache to the datafiles and CKPT retrieves a new Checkpoint Change Number from a sys owned sequence and writes this number to all file headers and the controlfile.
-- frequency is determined by FAST_START_MTTR_TARGET parameter (new feature to Oracle 9i), with wich you can specify a time in seconds which SMON is allowed to take maximal for a Crash Recovery until the database must be open again.
Dapending on the system you have SMON must calculate the maximum number of Redolog-blocks which it can manage to recover in the specified number of seconds. It will then create so called incremental checkpoints which will be tracked in the so called checkpoint queue in memory.
FAST_START_MTTR_TARGET is auto-tuned in Oracle 10g and Oracle tries to manage (incremental) checkpoint in a fashion that a minimum of I/Os are caused and a minimum time for crash recovery is needed.
If you set LOG_CHECKPOINTS_TO_ALERT to TRUE you will find checkpoint information in the alertSID.log file. You will see FULL and INCREMENTAL checkpoints then.
Hope this clarifies your question,
Lutz Hartmann

Difference between Full backup and lncremental level 0 backup

Hi,
What is the difference between Full backup and lncremental level 0 backup?
what I understand is:
Actually incremental backup backups all the block containing data and skips the blocks that are unused.
Similarly full backup backups all the blocks containing data.(does it skip unused blocks ?????).
The only difference that I feel is that the level 0 backup is recorded as an incremental backup in the RMAN repository, so it can be used as the parent for a level 1 backup where Full database backup is not recorded in the Rman respository and cannot be used as parent for level 1 backup.
(if you still feel you have some more points to share regarding the difference between backups, I request to share with me)
so my question here is
Can we use Incremental level 0 backup for full database recovery. Else is there any compulsion like we must only use full database backup for full database recovery?
can anyone throw light on this
with regards;
Boo

nowhere in this thread we talked about the image copies as we are only talking about the incremental backup.
The word "always" has a meaning. If you now wish to say, "well, RMAN will mostly use a level 0 or full backup, except when there are image copies around" then the word "always" doesn't fit your newly-revised description. That would make it an inappropriate word to use. And indeed, it's a factually wrong word to use.
If you want to get really picky about it, incidentally, the words 'datafile copy' appear in a post from me at Aug 4, 2007 6:03 PM whereas your post (in which the "always" word was used) only appears Aug 4, 2007 8:32 PM -a full 2 and a half hours (and and two posts) AFTER the concept of image copies had been mentioned.
But regardless of times: you can't just pretend image copies don't exist just because they haven't been mentioned so far in a thread. If you post "this is the way something ALWAYS works", you'd better be completely right about it, because "ALWAYS" is a big word. And there's no grey about this: either "always" is right, or it's wrong. And in this case, it's wrong: there are many times when RMAN will not do what you baldly asserted it would do. Image copies aren't some rare, exotic beast, either... so the occasions when your 'rule' breaks down are many and common.
until now I was simply beliving in what Oracle docs and metalink notes says
Try not to do that. Because you will fall into error after error if you do. Metalink is not the Holy Gospel of Oracle. Testing is, and it's because I've been testing this stuff since 1999 I will, on this occasion, decline your kind invitation to do "a small test". Been there, done that.
All of which leaves us discussing things that are of no relevance to the original poster, and I have no desire to take the thread off into silly areas of dispute. So I will leave it there, and I have nothing further to say on the matter. RMAN does what it does, and what it does is not what you said it would do. End of story.

What is the difference between "to sbt" and "to sbt_tape"?

In channel allocating, what is the difference between "to sbt" and "to sbt_tape"?----No.184

Syntax looks wierd, but if you are looking for differences between sbt and sbt_tape, you can find it in the Backup and Recovery books.
http://www.oracle.com/pls/db102/portal.portal_db?selected=4

Difference between v$option and dba_registry views ??

Hello all,
Whats the difference between v$option and dba_registry views.
SQL> select * from v$option ;
PARAMETER VALUE
Partitioning TRUE
Objects TRUE
Real Application Clusters FALSE
Advanced replication TRUE
Bit-mapped indexes TRUE
Parallel backup and recovery TRUE
Parallel execution TRUE
Parallel load TRUE
Point-in-time tablespace recovery TRUE
Fine-grained access control TRUE
Proxy authentication/authorization TRUE
...etc
47 rows selected
and
SQL> select comp_name from dba_registry;
Oracle9i Catalog Views
Oracle9i Packages and Types
2 rows selected.
Why the difference ??
TIA,
Jj
Message was edited by:
user566698
the DB is 9.2.0.7

DBA_REGISTRY displays information about the components loaded into the database
V$OPTION lists options that are installed with the Oracle server.
http://download-uk.oracle.com/docs/cd/B10501_01/server.920/a96536/toc.htm
Regards
Acr

Difference between snow leapord and lion

Hi .. I am trying to analyse the wifi driver code for mac os x and I am not getting what is the exact difference between snow leapord and lion in driver side.. I could only find the differnce in framework of ioctl .. could anyone tell me what is the exact difference other than features.. i mean in driver code..
Thanks in advance...

You can greatly reduce your level of concern, if you use an external drive to make a cloned duplicate of your current internal drive. You can use Carbon Copy Cloner
http://www.bombich.com
It seems to no longer be free (it was voluntary "donationware" before), but you can use it for free during a 30-day trial period. A "clone" is an exact duplicate of a hard drive volume, such as your usual internal startup disk. You can also use Disk Utility to make the duplicate, but using Carbon Copy Cloner is more straight forward.
Once you have the clone on an external drive volume, you can go to System Preferences Startup Disk pane and set the clone as the startup disk. Restart from the clone to confirm it is working properly. Once you are satisfied, start up from your usual internal startup disk and perform the system upgrade.
If there is a problem with the upgraded system, you can start up from the clone (on the external drive volume) like you did before, and "clone the clone" back to the internal drive. Since the clone is a duplicate of your startup disk immediately before you upgraded, you will be "back to square one."
NOTE: You should also use Time Machine for ongoing backups. You can also use your Time Machine backup to restore your system back to a previous state (in this case immediately before the upgrade). However, you cannot start up from a Time Machine backup, so having a bootable cloned backup feels safer. But, if you use Time Machine, it's good to know that you have a secondary way to restore the state of the previous system, if needed.

What is difference between sy-tabix and sy-index.

SAP Seniors,
Can you please let me know what is difference between sy-index and sy-tabix.
I read the SAP help, it is confusing for me. it looks like both are same from help. please help me.
Thank you
Anitha.

HI,
Here is a brief description of difference between SY_TABIX and SY_INDEX and using them with several conditions.
SY-TABIX
Current line of an internal table. SY-TABIX is set by the statements below, but only for index tables. The field is either not set or is set to 0 for hashed tables.
APPEND sets SY-TABIX to the index of the last line of the table, that is, it contains the overall number of entries in the table.
COLLECT sets SY-TABIX to the index of the existing or inserted line in the table. If the table has the type HASHED TABLE, SY-TABIX is set to 0.
LOOP AT sets SY-TABIX to the index of the current line at the beginning of each loop lass. At the end of the loop, SY-TABIX is reset to the value that it had before entering the loop. It is set to 0 if the table has the type HASHED TABLE.
READ TABLE sets SY-TABIX to the index of the table line read. If you use a binary search, and the system does not find a line, SY-TABIX contains the total number of lines, or one more than the total number of lines. SY-INDEX is undefined if a linear search fails to return an entry.
SEARCH <itab> FOR sets SY-TABIX to the index of the table line in which the search string is found.
SY-INDEX
In a DO or WHILE loop, SY-INDEX contains the number of loop passes including the current pass.
Hope this helps.
Thank you,
Pavan.

Difference between sy-tabix and sy-index?

tell me about sy-tabix and sy-index?what is the difference between sy-tabix and sy-index?
Moderator Message: Please search before posting. Read the [Forum Rules Of Engagement |https://wiki.sdn.sap.com/wiki/display/HOME/RulesofEngagement] for further details.
Edited by: Suhas Saha on Jun 18, 2011 5:33 PM

HI,
Here is a brief description of difference between SY_TABIX and SY_INDEX and using them with several conditions.
SY-TABIX
Current line of an internal table. SY-TABIX is set by the statements below, but only for index tables. The field is either not set or is set to 0 for hashed tables.
APPEND sets SY-TABIX to the index of the last line of the table, that is, it contains the overall number of entries in the table.
COLLECT sets SY-TABIX to the index of the existing or inserted line in the table. If the table has the type HASHED TABLE, SY-TABIX is set to 0.
LOOP AT sets SY-TABIX to the index of the current line at the beginning of each loop lass. At the end of the loop, SY-TABIX is reset to the value that it had before entering the loop. It is set to 0 if the table has the type HASHED TABLE.
READ TABLE sets SY-TABIX to the index of the table line read. If you use a binary search, and the system does not find a line, SY-TABIX contains the total number of lines, or one more than the total number of lines. SY-INDEX is undefined if a linear search fails to return an entry.
SEARCH <itab> FOR sets SY-TABIX to the index of the table line in which the search string is found.
SY-INDEX
In a DO or WHILE loop, SY-INDEX contains the number of loop passes including the current pass.
Hope this helps.
Thank you,
Pavan.

Difference between disaster recovery and cloning db

Similar Messages

Maybe you are looking for