Re: G550 Disaster Recovery Software

The hard disk on my three-year old G550 just crashed.
Since the one-button recovery was not an option, I used an MS-Recovery image for the new disk.
It turns out that, using this recovery method, the Windows OS becomes "not genuine".
After spending four hours on the phone with lots of people in MS, and lots of people in Lenovo, I got the following offers: Pay $120 and MS will give me a new OS, or pay Lenovo $150 and they will give me recovery disks.
I am looking for a solution to turn this expensive paperweight into a laptop again - a solution that does not involve a new purchase.
Any help will be highly appreciated

Hi RetireLT,
Welcome and Thanks for posting in the Lenovo Community,
Am sorry to hear about the issue that you’re facing and I’d like to help you but the problem look like that you will have to install an operating system on the machine I believe it will be choice.
Thanks and Best Regards,
Soha
Did someone help you today? Press the star on the left to thank them with a Kudo!
If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"! This will help the rest of the Community with similar issues identify the verified solution and benefit from it.
Follow @LenovoForums on Twitter!

Similar Messages

One Touch Recovery Software for XP for G550 94Q model

Please post the driver link for One touch recovery software link for G550 94Q model. I found drivers for Vista but not for XP...

Thanks, I'll give that a try when I finally get the Windows 7 upgrade disk.
It seems ridiculous that Lenovo doesn't support this product for Windows 7, especially when they mentioned the "FREE" upgrade (with ridiculous "shipping and handling charge") to Windows 7 on the web page where I ordered it. Being a reasonable person, I assumed that when they offered a "Free" upgrade to Windows 7 with the PC, they would also provide the basic software to allow the built-in hardware like webcams to keep on functioning as they did under Vista.
Had I known that they would refuse to offer any software on disks or download, I would have ordered a DELL or some other PC that has a reasonable level of customer service. I am not a typical user; I don't call in for customer support. All I need is the software and drivers, and I will install it myself.

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

Recovering lost data from a very old backup (disaster recovery)

Hi all,
I am trying to restore and recover data from an old DAT-72 cassette. All I know is the date when the backup was taken, that is back in November 2006. I do not know the DBID or anything else except for the date.
To recover this, I bought an internal SCSI HP c7438a DAT-72 tape drive on eBay and installed it on a machine running Windows 2003 Server SP2. I made a fresh Oracle 11g Enterprise Edition installation. HP tape drivers have been installed and Windows sees the tape drive without problem. To act as a Media Manager, I have installed Oracle Secure Backup. Oracle Secure Backup sees the HP tape drive without problems as well.
I have to admit my information about Oracle is not very in-depth. I read quite a lot of documents, but the more I read the more confused I become. The closest thing I can find to my situation is the following guide about disaster recovery:
http://download.oracle.com/docs/cd/B10500_01/server.920/a96566/rcmrecov.htm#1007948
I tried the suggestions in this document without success (details below).
My questions are:
1. Is it possible to retrieve data without knowing the DBID?
2. If not, is it possible to figure out the DBID from the tape? I tried to use dd in cygwin, also booted with Knoppix/Debian and Ubuntu CDs to dump the contents of the tape with dd but all of them failed to see the tape device. If there is any way to dump the raw contents of the tape on Windows, I would also welcome input.
3. Is there any way at all to recover this data from the tape given all the unknowns?
Thanks very much in advance,
C:\Program Files>rman target orcl
Recovery Manager: Release 11.2.0.1.0 - Production on Sat Mar 19 15:01:28 2011
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
target database Password:
connected to target database: ORCL (not mounted)
RMAN> SET DBID 676549873;
executing command: SET DBID
RMAN> STARTUP FORCE NOMOUNT; # rman starts instance with dummy parameter file
Oracle instance started
Total System Global Area 778387456 bytes
Fixed Size 1374808 bytes
Variable Size 268436904 bytes
Database Buffers 503316480 bytes
Redo Buffers 5259264 bytes
RMAN> RUN
2> {
3> ALLOCATE CHANNEL t1 DEVICE TYPE sbt;
4> RESTORE SPFILE TO 'C:\SPFILE.TMP' FROM AUTOBACKUP MAXDAYS 7 UNTIL TIME 'SYS
DATE-1575';
5> }
using target database control file instead of recovery catalog
allocated channel: t1
channel t1: SID=63 device type=SBT_TAPE
channel t1: Oracle Secure Backup
Starting restore at 19-MAR-11
channel t1: looking for AUTOBACKUP on day: 20061125
channel t1: looking for AUTOBACKUP on day: 20061124
channel t1: looking for AUTOBACKUP on day: 20061123
channel t1: looking for AUTOBACKUP on day: 20061122
channel t1: looking for AUTOBACKUP on day: 20061121
channel t1: looking for AUTOBACKUP on day: 20061120
channel t1: looking for AUTOBACKUP on day: 20061119
channel t1: no AUTOBACKUP in 7 days found
released channel: t1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 03/19/2011 15:03:26
RMAN-06172: no AUTOBACKUP found or specified handle is not a valid copy or piece
RMAN>
RMAN> RUN
2> {
3> ALLOCATE CHANNEL t1 DEVICE TYPE sbt
4> PARMS 'SBT_LIBRARY=C:\WINDOWS\SYSTEM32\ORASBT.DLL';
5> RESTORE SPFILE TO 'C:\SPFILE.TMP' FROM AUTOBACKUP MAXDAYS 7 UNTIL TIME 'SYS
DATE-1575';
6> }
allocated channel: t1
channel t1: SID=63 device type=SBT_TAPE
channel t1: Oracle Secure Backup
Starting restore at 19-MAR-11
channel t1: looking for AUTOBACKUP on day: 20061125
channel t1: looking for AUTOBACKUP on day: 20061124
channel t1: looking for AUTOBACKUP on day: 20061123
channel t1: looking for AUTOBACKUP on day: 20061122
channel t1: looking for AUTOBACKUP on day: 20061121
channel t1: looking for AUTOBACKUP on day: 20061120
channel t1: looking for AUTOBACKUP on day: 20061119
channel t1: no AUTOBACKUP in 7 days found
released channel: t1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 03/19/2011 15:04:56
RMAN-06172: no AUTOBACKUP found or specified handle is not a valid copy or piece
RMAN>
-----------------------------------

Hi 845725,
If the backups were created with OSB might be you can query the tape with obtool.
http://www.stanford.edu/dept/itss/docs/oracle/10gR2/backup.102/b14236/obref_oba.htmTo list pieces you could use <lspiece> within obtool.
http://www.stanford.edu/dept/itss/docs/oracle/10gR2/backup.102/b14236/obref_oba.htm#BHBBIFFEIf this works you should be able to identify the controlfile autobackup if it has the standard naming < c-dbid-date-xx > and you than know the DBID or you are able to restore a controlfile from a backup piece in the output list.
Might be you have to install 9i or 10g rdbms software as 11g was released a year later in 2007.
Anyway goodluck.
Regards,
Tycho

What is the quickest to upgrade disaster recovery system to NW04s in MSCS?

Hi,
I have an issue which I need assistance from SAP/Windows 2003 experts.
Hope you can share your opinion on an SAP upgrade issue we're grappling with.
Objective : Upgrade our SAP Bank Analyzer disaster recovery environment from NW04 to NW04s SR2, to be same as production. Both production and disaster recovery (DR) run under two node WIN2003 Enterprise MSCS. The SAP CI usually runs on node A and Oracle 10g runs on node B.
The Oracle software, parameters, database files and the SAP folder \usr\sap are already matching. These files and folders are on EMC mirrored disks, so this will be automatically synchronized from production status.
Therefore I believe it is only the SAP software components on the local hard disks - binaries, DLLs, registry, DCOM, environment variable etc, that need to be upgraded on the two DR machines.
For your information, the current SAP 6.40 instance, Oracle 10g instance, MSCS failover capability are all working in the DR environment as we just did an exercise a month ago to prove this.
 Disaster Recovery Environment :
On shared drives that are synchronized between prod and DR : SAP folder \usr\sap including the kernel binaries, Oracle parameter files, database datafiles, redologs, sapbackup etc.
Issue : What is the quickest and reliable method to achieve the objective? Other than the SAP kernel binaries and profiles, I'm not certain what other related components are updated/replaced that are stored locally on each of the clustered machine.
There are three different approaches we can think of :
1) Repeat the whole NW04s upgrade process in the DR environment. This takes several days. The exposure of not having a disaster recovery environment for several days is a minus.
 or
2) Un-install the SAP CI and MSCS definitions. Synchronise the DR shared disks from production to have the upgraded production NW04s database contents and SAP folder \usr\sap.
Use SAPINST to re-install either traditional CI or ASCS option 'System Copy". And then re-create the MSCS definitions for SAP CI using SAPINST again.
The disadvantage is I can't trial this in any other of our environments. Also, we want to run with the traditional CI instead of ASCS until early next year for other reasons. So we would have to reverse the ASCS back to traditional CI with this method, by reversing the steps in OSS NOTE 101190 "Splitting CI after upgrade to 700".
 or
3) Somehow identify all the SAP components that are stored locally on each machine (eg. environment variables, registry settings, DCOM definitions, DLL in various folders). Then just copy them from Production to DR machines or recreate them. I'm not confident of identifying the local SAP components. And I have not been able to find any good OSS NOTEs or forum threads on this topic. The most helpful OSS NOTE I can find is 112266 point 13 and 19.
Thanks for any input.
Benny Kwan

See:
* https://support.mozilla.com/kb/Form+autocomplete
* Firefox > Preferences > Privacy > History: "Remember search and form history"
* Autofill Forms: https://addons.mozilla.org/firefox/addon/autofill-forms/

Disk Utility in Lion 10.7.4 for Bare Metal Disaster Recovery??

We just got our 15" Macbook Pro back from repair of a catastrophic hard disc failure. Wow. An older Seagate Momentus XT 500 toasted its little self. It seems most of our data are intact. If any software on the *new* hard disc get corrupted, we need a fairly straightforward disaster recovery process.
I need to ask if anyone has successfully used Disk Utility to create a (bare metal) disaster recovery image of everything on their hard drive, including all their software *and* the perfectly functioning OS. We'd like to be able to restore a complete disc image of the new Seagate Momentus 750 XT - taken from a 1 TB Seagate FreeAgent GoFlex USB drive - to the Macbook.
Has anyone done this successfully? Thanks very much for your help!

Time Machine, SuperDuper and Carbon Copy Cloner are some of the utilities that will allow you to backup your disk and do a complete restore.

Disaster Recovery For SAP ECC 6.0 On Oracle

Hi All,
This is our infrastructure
Windows 2003 Server
SAP ECC 6.0
Oracle 10
Legato Networker Client / Library
Actually our Backup Strategy is to do an Online Backup Every Night from monday to saturday. We want to test our backup by doing a Restore. We are assuming a complete loss of the system including hardware.
What we do:
1. Install the SAP System on a new host with the same hardware characteristic of the source system.
2. Install & Configure the legato utility.
3. Copy the E:\oracle\MIS\sapbackup\ directory from the source system to the test system.
4. Them we put the database in mount mode.
5. Execute the command: brrestore -b bdyxwoqv.fnf -m full (bdyxwoqv.fnf-> Full Online Backup that was executed without problems).
It gives the following errors:
BR0386E File 'F:\ORACLE\MIS\SAPDATA2\SR3_10\SR3.DATA10' reported as not found by
backup utility
BR0386E File 'F:\ORACLE\MIS\SAPDATA3\SR3700_9\SR3700.DATA9' reported as not foun
d by backup utility
BR0280I BRRESTORE time stamp: 2008-10-01 17.45.19
BR0279E Return code from 'backint -u MIS -f restore -i E:\oracle\MIS\sapbackup\.
rdyybrzp.lst -t file -p E:\oracle\MIS\102\database\initMIS.utl': 2
BR0374E 0 of 63 files restored by backup utility
BR0280I BRRESTORE time stamp: 2008-10-01 17.45.19
BR0231E Backup utility call failed
BR0406I End of file restore: rdyybrzp.rsb 2008-10-01 17.45.19
BR0280I BRRESTORE time stamp: 2008-10-01 17.45.19
BR0404I BRRESTORE terminated with errors
Since this is a new SAP system it never will find the SAPDATA files because they where on the source system and this is a new test system.
We found the following note:
96848 Disaster recovery for SAP R/3 on Oracle
But this note is for SAP R/3 no for SAP ECC!
It explain that you have to install your SAP system with the System Copy Method (is this the only way??).
2.) Installation of the R/3 System
The installation of SAP software contains the software installation of the database. The initial SAP database should be created again but the SAP data should not be loaded.
Install the SAP system with the Oracle-specific system copy method, which is based on backup/restore. This method is described in the system copy guide for your Product/Release. Refer to Note 659509 for products that are based on Web AS.
3.) Modification of the installation
Above all, you must take into account the mounted file systems at the time of the loss. If necessary create new SAPDATA directories (mount points). These generally identify a disk or a logical storage area (logical volume).
Are we working in the right way? maybe there is a formal procedure to do a Restore from an Online backup when you complete loss your system.
Please some tips.
Best Regards,
Erick Ilarraza

Hi Eric,
Thanks a lot for your reply, I will follow the Note 96848 Disaster recovery for SAP R/3 on ORACLE point 5.
5.) Restore profile and log files, as you sayed in case of disaster we will lost our "source" system.
On the other hand to configure the legato client we take care of the name of the server, we configured the .sap, .cfg and .utl files so in theory the restore will be done on the new test system since we run the brrestore command from that system.
Officially there is not a documentation from SAP to do a Restore from a Online Backup with SAP ECC, SAP Netweaver (ABAP / ABAP + Java). You only have the 96848 note??? I found the following information:
http://help.sap.com/saphelp_nw70/helpdata/en/65/cade3bd0c8545ee10000000a114084/frameset.htm
But there is not a official procedure like a System Copy Guide or Installation Guide.
Best Regards,
Erick Ilarraza

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

Looking for comment on disaster recovery plan

Looking for some comment on where we are and where we’re planning on going with our Continuity of Operations / Disaster Recovery plan.
Current setup is Oracle 10.2.0.2.0 on HP-UX Itanium 64-bit. OAS / Forms 9i on a separate HP-UX Itanium box. We do not have control over the version of Oracle or the hardware. I am pushing the powers that be on upgrading to 10.2.0.4, but am not holding my breath.
Basic backup is threefold. DB is in archivelog mode. RMAN full backup is taken weekly. Incremental backup taken daily. These backups are to disk. In addition, a daily full-system backup (to tape) is done with the db shut down, providing a daily cold backup as well as backup of the online backups. Also daily exports – full and schema specific.
All db files are on an HP SAN unit. SAN replication software is used to mirror all i/o to a similar unit located at a sister site. Likewise, they replicate their SAN to ours. Each site has a pair of backup servers to be used by the other site if needed. Sister site has already tested loading our backup servers, mounting the mirror of their SAN, and starting the db.
Since sister site is a couple of hours away and crosses major network boundaries, management would like to also put up a DataGuard standby at a facility only 30 minutes away and within our own network. Plan is to host that on duplicate HP servers, but disk would be on a NAS instead of a SAN.
I have managed a DataGuard setup, but did not create/configure it, so am now digging into the docs, starting with the DataGuard Concepts. I’ve never worked with NAS and am not clear on how it differs from SAN, and what the implications are.
I'm looking for any comment, especially any red flags, on what I’ve described.

Satish Kandi wrote:
Not an expert comment on your setup but just the thoughts that came to my mind while reading this...
1. What is the setup for backup preservation? Is it in one of the servers only? Is the backup also replicated?Belt and suspenders. The backup location on disk is part of what gets mirrored to the sister SAN. Plus, the nightly system backup to tape picks it up as well.
2. What about OAS/Forms 9i backup? You have not mentioned anything about that.That is also mirrored to the sister SAN.
3. What is the archive log generation frequency? Or how much data loss can you afford?A typical day will see one or two dozen archivelog files.
>
In addition, a daily full-system backup (to tape) is done with the db shut down, providing a daily cold backup as well as backup of the online backupsLucky you :-) but I don't see a need for this with the levels of backup that you have (especially with RMAN weekly backup and daily archive log backup). No, no need, but it does give us another layer at no real cost. This cold backup is really just a byproduct of a daily full system shutdown and backup. We have a high tolerance for system down time, but low tolerance for data loss.

Disaster Recovery on another Sun Server

I have a question in regards to disaster recovery of Sun servers. We have a client that hosting applications within Sun T platform which utilizes LDOM configuration. These boxes host around five guests.
Currently we use a software called EMC HomeBase(http://www.emc.com/backup-and-recovery/homebase/homebase.htm) to enhance our DR recovery by profiling the Sun box and transmitting that profile to our DR vendor. DR vendor in turn with help from EMC will install the OS, patch level and apply that profile to setup the system with NIC information, file systems and other components so we would only
need to restore our data from NETBACKUP and don't do any system recovery.
Unfortunately, EMC does not support LDOMs nor containers. Now my question is if Sun has a way around this? Please note that the servers will be different models at DR. for example T5220 to a T5440 or V890 to V490.

It'd be rather easy to manually install same LDOM configuration on DR site... all EMC seems to be doing is getting the profile & then someone is creating setup manually...
Anyways... here you go:
Backup & Recovery of guest domain
Archive and backup the guest domain configuration:
ldm list-constraints -x <ldom> > <ldom>.xml
Backup the guest domains over the network with backup software as regular server
Restore the guest domain configuration, assuming that your VSW and VDS resources are available:
ldm add-domain -i <ldom>.xml
Make sure that you have enough VCPU, MAU, and Memory to boot your guest domain.
Jumpstart guest domain and install backup client. Restore data from backup.
Backup LDOM configuration
You can take the backup of the configuration using "ldm add-spconfig saveconfigurtion" command which will store in SP of the server.
For taking the backup of the individual domain use "ldm ls-constrants >> filename.xml" it will give the xml output just redirect it to a file.
While creating the domain again use "ldm create ldomname -f filename.xml"
You can not create control domain by the above procedure we hve to configure manualy or even if your control domain crashed install new OS and install LDOM Manager in the Base OS create /etc/hostname.vsw0 & vsw1 files poweroff the server from SP. set bootmode config=saveconfiguration
How to backup the primary domain
Backup the LDM db files in: /var/opt/SUNWldm
Archive and backup the primary domain configuration:
ldm list-constraints -x primary > primary.xml
Backup the primary domains over the network with backup software as regular server.
How to recover primary domain
Update firmware
Install backup client & LDM software
Restore /var/opt/SUNWldm
Start up LDM services
If all goes well, the LDM config will be read and you will be in initial configuration mode. Save the config to the hypervisor and
reboot. If not, parse the primary.xml file to recreate the primary domain configuration, save config, and reboot.
Restore guest domain configs and data. Then bring up guest domains.

Disaster Recovery scenario for MSCS Production system.

Hi
Our production system is on win2008/sql2008 MSCS. We decided to install a disaster recovery system. We will use a database replication software. If we have a standalone production system, not a MSCS system, i know that i can install Disaster Recory system with same SID and hostname and i don't need any homogeneous system copy procedure to switch to DR system. But in our scenario, we have many hostname (sap cluster group, sql cluster group, hostnames of nodes... etc.).
How can i install my DR system (which hostname.. etc.) to make our DR scenario easy?
Best Regards...

You May have trouble with RFC connections:
So, one possible solution is, your new server name(Host name) should be your message server name to minimise the trouble and you have to maintain this for all RFC connections (to Prod ECC system) to virtual host which could be message server.
If I could think if any other possible issues, I will update.
Krishna

Disaster Recovery on XI server

Hi experts,
Sorry this question might be a bit like BASIS question. But i just try my luck here to see hv anyone of you have the experience on Disaster Recover (DR) on XI server?
We know there is lot of product on ECC server DR, but I never heard of anything abt DR for PI/XI server. Normally in business, do they DR the XI? or they just backup it. Any build in tool by SAP can enable us to backup the XI object?
As we know, rebuilding up the SLD, IR, ID can be 1-2 years job. So, any alternative for us to make sure the XI/PI will be operational if the existing hardware failure?
Thanks.
Cheers,
Isaac.

Yeah I know the Import/Export strategy. However, what I am actually looking at is any disaster recovery or some other approach we can use which is close to the DR concept.
For example, if our XI server having serious hardware failure or damaged due to natural disaster. We need to re-install and set all the SLD, RFC, and proxy all over again, right? That's y I m thinking of any Backup tool or DR tool we can use within SAP/ or maybe third party software which is compliance with SAP.. just name some example will do...
It will be good if any of you can share your experience on how your company / client handle this....
Thanks.

Disaster recovery in Oracle BPEL

Hi,
For a disaster recovery scenario, how does Oracle BPEL support lost transactions? Is there any mechanisum which takes care of re-sending the lost transactions and checking for duplicates?
As Oracle BPEL maintains state information, does Oracle BPEL take's care of lost transactions on server startup.
Can anyone please, through some light on Disaster recovery in Oracle BPEL.
Thanks and Regards
Raj

> I am confused. Option 3 will be restoring backup
Yes - but what will you restore? Everything? If you're running on a cluster it's unlikely that both nodes will fail at the same time so there is still one node that can and will run the software, no?
> and 4 will be sapinst. Isn't it? Are both options supported by SAP?
Yes.
> Is there a SAP standard documentation for building cluster from scratch and build SAP system from backup or sapinst for DR?
The standard installation documentation cover a cluster installation.
> I am sure there will be installation document if it is a fresh installation. But not sure if there is one for DR.
If you have a cluster then you have a high availability already. If a node fails, you will "just" reinstall that node and put it back into the cluster.
What kind of DR scenario are you thinking about?
Markus

Disaster Recovery in Windows 2003/Cluster, SQL 2000 and R3

Hi,
Can someone share experience/knowledge of disaster recovery scenarios in MSCS/SQL Server/SAP. One of our customer has R3/SQL Server2000/Win 2003 (Cluster).
We would like to evaluate best possible options for the Disaster Recovery which are supported by SAP.
We have thought about
1. Log shipping
2. Standby Database
3. Restore backup on new cluster
4. Homogeneous System copy.
We do not want to go for first two and would like to explore on 3rd and 4th option.
Any links to documents/blogs will be helpful.
Thanks,
Manoj

> I am confused. Option 3 will be restoring backup
Yes - but what will you restore? Everything? If you're running on a cluster it's unlikely that both nodes will fail at the same time so there is still one node that can and will run the software, no?
> and 4 will be sapinst. Isn't it? Are both options supported by SAP?
Yes.
> Is there a SAP standard documentation for building cluster from scratch and build SAP system from backup or sapinst for DR?
The standard installation documentation cover a cluster installation.
> I am sure there will be installation document if it is a fresh installation. But not sure if there is one for DR.
If you have a cluster then you have a high availability already. If a node fails, you will "just" reinstall that node and put it back into the cluster.
What kind of DR scenario are you thinking about?
Markus

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

Re: G550 Disaster Recovery Software

Similar Messages

Maybe you are looking for