How to implement Disaster Recovery in TimesTen?

hello, chris:
we have a requirement to implement disaster recovery from remote when the master and standby nodes are failover in local. how to implement it in timesten? Can master standby pairs with subscribers mode caryy out it? when the master and standby nodes are fail, can subscriber node take over the application?? thank you.

The best, and recommended, solution for this is to have an active/standby pair located locally as the primary mechanism for high-availability and to configure a remote readonly subscriber datastore. In the event that the primary site completely fails, the remote subscriber can be easily (few seconds) promoted to an active to form the basis of a new active/standby pair at the remote site.
It is not supported to split an active/standby pair across a network connection that is anything less than LAN grade but a remote subscriber can be located across any reasonable network connection (WAN, VPN etc.) as long as there is sufficient bandwidth and the latency is not too high.
Chris

Similar Messages

Is anyone doing disaster recovery for a J2EE application?

We generally use database log shipping to maintain a standby database for our ABAP instances. We can successfully fail over our production application to our disaster recovery site with no real issues. With the J2EE instances (EP, ESS/MSS, BI, etc), we have a few concerns:
hostname cannot change, without going through a system copy procedure, so we would have to keep the hostnames in DR the same. (for example, ref: oss note 757692 - changing hostname is not supported)
fully qualified domain name - from what I understand, there are potentially issues with changing the fqdn, for example SSO certificates, BSPs, XI has issues, etc.
we can't keep both hostname and fqdn the same between DR and production, or we could never do a DR test.
Has anyone implemented disaster recovery for any SAP J2EE application that has run into these concerns and addressed them? Input would be greatly appreciated regarding how you addressed these issues, or how you architected your disaster recovery implementation.
Regards,
David Hull
The Walt Disney Company

I haven't done this personally, but I do have some experience with these issues in different HA environments.
To your first point: You can change the hostname, note 757692 tells you exactly how to do it. However like the note says, "Changing the name of a host server in a production system is not automatically supported by SAP." When it says "supported by SAP" I think it means SAP the company, not SAP's software. So I would contact SAP to see if this configuration would be covered under your service agreement. Then you have to think about whether you want to do something that isn't "officially supported" by SAP. Also I'm sure you'll need some kind of additional licensing for the DR systems as their hardware keys will de different.
To your second point: As for SSO certs (SAP Login Tickets), I think they should still work as long as the SID and client number of the issuing system remain the same. I don't think they are hostname or fqdn dependant. For BSPs I would think they would still work as long as they use relative paths rather than absolute paths. And for XI... I have no idea what kind of issues may arise, I'm not an XI guy.
Again, I haven't done what you're describing myself. This is just based on my HA experiences.
Hope this helps a little,
Glenn

RAC at Disaster Recovery site?

HI
I am having two node RAC production database right now. Now i want to implement disaster recovery using oracle data guard and for that also i am planning to go for 2 node RAC. Is it possible to implement two node RAC at disaster recover site. If yes then please send me link for the document that is related to this implementation.
DB Version:10.2.0.1
OS:LINUX
Thank You....

hi,
yes its similar to normal stanby crearttion
http://www.oracle.com/technology/deploy/availability/pdf/MAA_WP_10g_RACPrimaryRACPhysicalStandby.pdf
http://www.dba-oracle.com/real_application_clusters_rac_grid/single_instance.htm
regards,
Deepak

How to configure high availability and disaster recovery? And user authenticate

We are in the process of rolling out our online help which was created using Robohelp. In our initial rollout we will provide access to the files via our Client Portal which requires authentication. We are also planning for our next version where we intend to implement Robohelp server functionality.
Our IT team is looking at options on how to configure for High Availability and Disaster Recovery. It seems that Robohelp doesn't have any built-in functionality in this area. In addition we require that our users authenticate. The options for the server version seem to be more internally focused and we would need to solution the authentication using a third party.
Would anyone be willing to share their approach in these areas? Would you be willing to participate in a conference call with our IT Professionals?

Hello again
I see my good friend Peter replied to your LInkedIn post where you cross-posted the same question. For those here that have no clue what Peter stated, here it is:
What are you seeking to recover? Your projects? Your outputs? This sounds like a question more appropriate to Disaster Recovery consultants and far wider reaching than RoboHelp. To me it seems like a question your IT people should be asking direct to such consultants who would expect a fee for their advice.
I would agree with Peter's reply.
I'll also go further and ask what exactly is being done in this realm for the application? Help files generally are there to support an application on the server. So whatever you are doing for the applciation should also be able to be used for the WebHelp, FlashHelp or web based AIR Help files, no?
Cheers... Rick
Helpful and Handy Links
RoboHelp Wish Form/Bug Reporting Form
Begin learning RoboHelp HTML 7, 8 or 9 within the day!
Adobe Certified RoboHelp HTML Training
SorcerStone Blog
RoboHelp eBooks

How to migrate Planning from Production to Disaster-Recovery server?

We are using Planning 11.1.1.3 Oracle repository. Presently our DR Planning Application name is different than production's name, and the DR's Windows server names are different from Production's. Otherwise, all other configuration the same.
How do we migrate Planning from Production to Disaster-Recovery server? We stopped Planning on DR server. Then we exported production planning Oracle repository and imported it to DR Planning. We restarted DR's Planning. DR planning seems to be running fine, but I am afraid to click "Refresh Planning" on DR Planning - it might update Production server. So how can I be sure DR and Production planning are disconnected ?
Is there anything we need to do? This method seems to be faster than migrating with LCM.
Edited by: Essbase Fan on Oct 18, 2010 10:11 AM

You are definitely go about it the correct way, if you are migrating the whole planning application I have to agree it is a safer and quicker route.
The connection information to essbase is stored in the planning system database/schema so as long as you have not migrated that then you should be good to refresh.
To put your mind at rest, log into the planning application and edit the datasource associated with the application then you will see where the essbase server is it is going to refresh.
Cheers
John
http://john-goodwin.blogspot.com/

How to install and configure Exchange Server 2010 DR (disaster recovery) on Windows server 2012.

We need to install and configure Exchange Server 2010 with DR(disaster recovery on Server 2012.
Pls suggest step by step.
Pankaj Kumar

Hi,
Here is an article which may help you for your reference.
Deploying High Availability and Site Resilience
https://technet.microsoft.com/en-us/library/dd638129(v=exchg.141).aspx
Besides, there is a related thread here.
https://social.technet.microsoft.com/Forums/exchange/en-US/577c9433-a20b-442e-8ce7-be59aea35855/preparation-for-deploying-exchange-2010-servers-at-remote-site-dr-site?forum=exchangesvrdeploylegacy
Hope this is helpful to you.
Best regards,
Belinda Ma
TechNet Community Support

How to replicate CDC on Disaster Recovery Database.

I have a scenario here.
In Case you have CDC installed on your main database. The changes are getting captured and you get the changes in the subscriber views.
In case your main database goes down due to some reasons. You cannot access even a single table of the database now you are to take an export dump to be taken to a different database.
In this case there is a disaster recovery database, wherein the tables and the number of records is same as the main database, since it is refreshed every now and then.
Is it possible to replicate the change tables with the archived log files present??
The mode of operation of CDC is Asynchronous Hotlog mode.
Please suggest the alternative for replicating CDC on a separate database, if one database is gone, without any miss in the changes.
Regards,
Uravesh Vora

moz44 wrote:
Hi guys, happy thanksgiving day to you all.
Some people say that it is possible to replicate a derby database running on one host to mysql running on another host. Has any of you have experience with that?That wouldn't be quite the same as for example replication on Oracle to Oracle.
But the following claims that it does what you want. No reason to suppose it doesn't. Look at the license carefully (I didn't look at it at all.) It basically supports any jdbc driver (two one for each source.)
[http://enterprise.replicator.daffodilsw.com/]
I would expect more problems with more complicated databases. But that is true with databases that have built in replication as well.

Setting up a Disaster Recovery

Hi,
We are planning to setup Disaster Recovery for our entire land scape.
We have implemented EP also.
I just want to all the paths at OS level where all the data including customizations is store apart from Database, so that we can take the file system backup of those directories.
Thanks and Regards,
Naresh Sadu

Hi Naresh,
http://help.sap.com/saphelp_nw04s/helpdata/en/72/96d34c435c3c4ca5894749ef1435ac/frameset.htm
SAP on Oracle
if you're talking about how you do a backup that you can roll back in emergency cases:
1. make a copy from your SBO installation directory (the whole C:Program FilesSAP directory)
2. make a copy from SBO-Common
the Database backup you can do after installing the new Patch. because you anyway have to do a backup
before upsizing them (because SAP will block the update without a backup)
http://help.sap.com/saphelp_nw04s/helpdata/en/72/96d34c435c3c4ca5894749ef1435ac/frameset.htm
Thanks
Suresh

UCM setup DR (Disaster Recovery) environment

Hi all,
We did implementation part in production. Now we are planning setup DR (Disaster Recovery) environment.When ever Production will goes down automatically RD will take place to provide continue services to user, But in installation part of RD little bit challenging,let me know below problems how we can override.
1) While installing UCM in DR environment I need to give Production DB schema details, Is it workout (if I give production DB Schema details , is there any effect in production )
2) All ways production and DR both file systems will sync up every time. How we can achieve these thing?
Thanks.

Vijay,
read this document: http://download.oracle.com/docs/cd/E17904_01/doc.1111/e15250/recommendations.htm#CHDGAEEA
In a nutshell:
- as for installation, configuration, etc. I'd suggest you to use images (OracleVM will do you the service and it's almost free)
- you will need to synchronize database AND file system
- if Oracle DB Enterprise Edition is your database, you may use DataGuard to synchronize primary and secondary locations (DG is free in EE, in SE or other databases you may use Oracle Golden Gate or a third party product)
- for file system you will need a 3rd party system (I was recommended TrueCopy - this very much depends who is your HW provider)
Note that you can use file system synchronization even for database - I'd suggest to use Partitioning option, because the size of files that need to be synchronize will be smaller - but you might transfer also errors in the database, whilst DataGuard will transfer only correct transactions, so your secondary db will always be in a consistent state.

Advice on SAP B1 Disaster Recovery

Dear All,
We are a SAP B1 Customer and are in the process to apply a Disaster Recovery Plan. For that we need advice how to take Application Back Up, how will that backup be restored on the back up server and what is the good configuration for the Back Up Machine.
Your advice shall be appreciated.
Regards,
Faisal Baloch

Hi,
It is very difficult to summarize the answer for your questions. SO, I suggest to read the book disaster recovery. Here is the book title:
Pro SQL Server Disaster Recovery (DR)
Author : Janes Luetkehoelter
Publisher: Apress
You can use the book to implement DR. The book also answers your questions.
JimM

SQL Server 2005 High Availability and Disaster Recovery options

Hi, We are are working on a High Availability & Disaster Recovery Planning solution for an application database which is on SQL Server 2005. What different options have we got to implement this for SQL Server 2005 and after we have everything setup how
do we test the failover is working?
Thanks in advance.........
Ione

DR : Disaster recovery is the best option for the business to minimize their data loss and downtime. The SQL server has a number of native options. But, everything is depends upon your recovery time objective RTO and recovery point objective RPO.
1. Data center disaster
Geo Clustering
2. Server(Host)/Drive (Except shared drive) disaster
Clustering
3. Database/Drive disaster
Database mirroring
Log shipping
Replication
Log shipping
Log shipping is the process of automating the full database backup and transaction log on a production server and then automatically restores them on to the secondary (standby) server.
Log shipping will work either Full or Bulk logged recovery model.
You can also configure log shipping in the single SQL instance.
The Stand by database can be either restoring or read only (standby).
The manual fail over is required to bring the database online.
Some data can be lost (15 minutes).
Peer-to-Peer Transactional Replication
Peer-to-peer transactional replication is designed for applications that might read or might modify the data in any database that participates in replication. Additionally, if any servers that host the databases are unavailable, you can modify the application
to route traffic to the remaining servers. The remaining servers contain same copies of the data.
Clustering
Clustering is a combination of one or more servers it will automatically allow one physical server to take over the tasks of another physical server that has failed. Its not a real disaster recovery solution because if the shared drive unavailable we cannot
bring the database to online.
Clustering is best option it provides a minimum downtime (like 5 minutes) and data loss in case any data center (Geo) or server failure.
Clustering needs extra hardware/server and it’s more expensive.
Database mirroring
Database mirroring introduced in 2005 onwards. Database Mirroring maintain an exact copy of a database on a different server. It has automatic fail over option and mainly helps to increase the database availability too.
Database mirroring only works FULL recovery model.
This needs two instances.
Mirror database always in restoring state.
http://msdn.microsoft.com/en-us/library/ms151196%28v=sql.90%29.aspx
http://blogs.technet.com/b/wbaer/archive/2008/04/19/high-availability-and-disaster-recovery-with-microsoft-sql-server-2005-database-mirroring-and-microsoft-sql-server-2005-log-shipping-for-microsoft-sharepoint-products-and-technologies.aspx
http://www.slideshare.net/rajib_kundu/disaster-recovery-in-sql-server
HADR Considerations
Need to Understand the business motivations and regulatory requirements that are driving the customer's HA/DR requirements. Understand how your customer categorizes the workload from an HA/DR perspective. There is likely to be an alignment between the needs
and categorization.
Check for both the recovery time objective (RTO) and the recovery point objective (RPO) for different workload categories, for both a failure within a data center (local high availability) and a total data center failure (disaster recovery). While RPO and
RTO vary for different workloads because of business, cost, or technological considerations, customers may prefer a single technical solution for ease in operations. However, a single technical solution may require trade-offs that need to be discussed with
customers so that their expectations are set appropriately.
Check and understand if there is an organizational preference for a particular HA/DR technology. Customers may have a preference because of previous experiences, established operational procedures, or simply the desire for uniformity across databases from
different vendors. Understand the motives behind a preference: A customers' preference for HA/DR may not be because of the functions and features of the HA/DR technology. For example, a customer may decide to adopt a third-party solution for DR to maintain
a single operational procedure. For this reason, using HA/DR technology provided by a SAN vendor (such as EMC SRDF) is a popular approach.
To design and adopt an HA/DR solution it is also important to understand the implications of applying maintenance to both hardware and software (including Windows security patching). Database mirroring is often adopted to minimize the service disruption
to achieve this objective.
HADR Options :
Failover clustering for HA and database mirroring for DR.
Synchronous database mirroring for HA/DR and log shipping for additional DR.
Geo-cluster for HA/DR and log shipping for additional DR.
Failover clustering for HA and storage area network (SAN)-based replication for DR.
Peer-to-peer replication for HA and DR (and reporting).
Backup & Restore ( DR)
keep your server DB backups in network location ( DR)
Always keep your sql server 2005 upto date, in case if you are not getting any official support from MS then you have to take care of any critical issues and more..
Raju Rasagounder Sr MSSQL DBA

Disaster Recovery set-up for SharePoint 2013

Hi,
We are migrating our SP2010 application to SP2013. It would be on-premise setup using virtual environment.
To handle disaster recovery situation, it has been planned to have two identical farms (active, passive) hosted in two different datacenters.
I have prior knowledge of disaster recovery only at the content DB level.
My Question is how do we make two farm identical and how do we keep Database of both the farm always in sync.
Also if a custom solution is pushed into one of the farm, how does it replicate to the other farm.
Can someone please help me in understanding this D/R situation.
Thanks,
Rahul

Metalogix Replicator will replicate content, but nothing below the Web Application level (you'd still have to configure the SAs, Central Admin settings, deploy solutions, etc.).
While AlwaysOn is a good choice, do remember that ASync AO is not supported across all of SharePoint's databases (see
http://technet.microsoft.com/en-us/library/jj841106.aspx). LogShipping is a good choice, especially with content databases as they can be placed in a read only mode on the DR farm for an
active crawl to be completed against them.
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

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

Best Way to setup a disaster Recovery site for a logical standby database

I have a logical standby DB (L1DB) as a reporting db on the same machine as the primary (P1DB). We are planning on building a disaster recovery site with similar hardware and potentially have disk mirroring of atleast the redo log files.
The DR site can hold an additional physical standby (S1DB) for the primary (P1DB). I am trying to understand what would be the best way to setup the Disaster Recovery site for the L1DB logical stdby. Ideally, when the disaster happens, and I no longer have P1DB and L1DB, I should be able to switch to S1DB as the new primary. But how do I setup to have a L2DB that takes the place of L1DB and has its contents and can be setup as a logical standby of S1DB?

If you already setup one logical standby, then you know how it works, so not sure what question you are asking ?
Personally I would setup L2DB as a standby of the original primary P1DB. Having downstream standby databases complicates things, and adds additional lag between primary transaction time and L2DB apply.

Disaster Recovery from tape library!

Hi,
I am using oracle 10g and Backup Exec 12 as the media management software. How do i perform the disaster recovery. My entire scenario is like this:
Server A has the DB (Database).
Configured Backup Exec with RMAN and took full DB backup along with autobackup of controlfile to the tape.
Server A crashes and is unusable.
Installs Oracle on server B and needs to restore the DB on this new server.
I know the DBID of the DB but how to configure RMAN to work with Backup Exec, so that I can restore the db from the tape library?
When you configure the RMAN integration with Backup Exec, it finds the database running on the server and will perform the integration. But in my case, since the database does not exist, how will the Backup Exec agent configure the integration?
How do we go about the restoration to Server B in this case?
Thanks!

Hi!
I am still not able to restore the db. The scenario is like:
Took a full database backup to tape from server A with controlfile autoconfig
Trying to restore the db on server B. The following is the script used to restore.
connect target /
set dbid=152417844;
startup nomount;
run
+{+
allocate channel sbt1 type 'sbt_tape';
SEND 'BSA_SERVICE_HOST=ipaddress,NBBSA_TOTAL_STREAMS=1';
set controlfile autobackup format for device type 'sbt_tape' to 'cf_%F';
restore spfile from autobackup;
restore controlfile from autobackup;
alter database mount;
restore database;
recover database;
release channel sbt1;
+}+
alter database open resetlogs;
When i try to restore, the output is:
channel sbt1: looking for autobackup on day: 20090624
channel sbt1: looking for autobackup on day: 20090623
channel sbt1: looking for autobackup on day: 20090622
channel sbt1: looking for autobackup on day: 20090621
channel sbt1: looking for autobackup on day: 20090620
channel sbt1: looking for autobackup on day: 20090619
channel sbt1: looking for autobackup on day: 20090618
channel sbt1: no autobackup in 7 days found
released channel: sbt1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 06/24/2009 11:19:28
RMAN-06172: no autobackup found or specified handle is not a valid copy or piece
Please advice!
Edited by: Libra DBA on Jun 24, 2009 1:39 PM

How to implement Disaster Recovery in TimesTen?

Similar Messages

Maybe you are looking for