Disaster Recovery with different ASM diskgroups

Hi@all,
actually I'm trying to test a Disaster Recovery Scenario. At a Oracle Linux 6 server with installed Grid Infra 12c and Ora Database 11.2.0.4 (there is also a 12.1.0.2 database instance) I'm trying to do a disaster recovery. But I'm getting wild by restoring and recovering the database. The problem here is, that the ASM diskgroup name has changed. As you read out I also switched the physical server, but I think that shouldn't be any problem.
At the old server I've two ASM diskgroups "+DATA" and "+FRA_1", at the new they're called "+DATA_SRVNAME" and "+FRA_SRVNAME". I've already changed the startup parameter in spfile, but now after restoring the controlfile RMAN has the directions to the old diksgroup:
RMAN> report schema;
using target database control file instead of recovery catalog
RMAN-06139: WARNING: control file is not current for REPORT SCHEMA
Report of database schema for database with db_unique_name SID
List of Permanent Datafiles
===========================
File Size(MB) Tablespace           RB segs Datafile Name
1    0        SYSTEM               ***     +DATA/SID/datafile/system.438.816606399
So I've tried three ways. First was to rename the datafile name:
ALTER DATABASE RENAME FILE '+DATA/SID/datafile/system.438.816606399' TO '+DATA_SRVNAME/SID/datafile/system.438.816606399';
Second was to set the newname in RMAN:
set newname for datafile 16 to '+DATA_SRVNAME/SID/datafile/mms_basic_tab.455.816617697/';
And second was to recreate the controlfile with
CREATE CONTROLFILE REUSE DATABASE "SID" RESETLOGS ARCHIVELOG
    MAXLOGFILES 16
    MAXLOGMEMBERS 3
    MAXDATAFILES 254
    MAXINSTANCES 1
    MAXLOGHISTORY 1815
LOGFILE
GROUP 1 ('+DATA__SRVNAME', '+FRA_SRVNAME') SIZE 1024M,
DATAFILE
'+DATASRVNAME/SID/datafile/system.438.816606399',
CHARACTER SET AL32UTF8;
But all three methods gave me the error, that the datafile at the new location isn't available (example):
ORA-15012: ASM file '+DATA_QUM169/cogn11/datafile/system.438.816606399' does not exist
So now my question to you: How am I able to tell the controlfile or database to use the other ASM diskgroup?
I know, easiest way would be to create a diskgroup +DATA and do the restore / recover, but at the new server I've no more storage to assign to a new diskgroup and because of there are running other instances I would'nt change the ASM diskgroups.
Did you have anny solution?
Thanks a lot and Regards,
Dave

Please try this
RMAN> run
set newname for datafile 1 to '+DATA_SRVNAME';
restore datafile 1;
switch datafile 1;
recover datafile 1;
Did you created +DATA_SRVNAME diskgroup?
and

Similar Messages

Apps 11i disaster recovery with hot standby db

Hello,
We are trying to formulate a disaster recovery plan for Apps 11i (single node install) utilizing a hot standby database for the db layer and file synchronization
(rsync, rcp, whatever) of the application stack. We're comfortable with the hot standby db technology, but uncertain that simply keeping the application stack
sync'd on the standby host is sufficient to have a complete failover solution. Is anyone successfully using this type of configuration and , if so, is there a
cookbook methodology for promoting the standby system to a primary? Can you simply rename the host on the standby and turn the key on?
Thanks for any/all suggestions.
Terry Riddle

Hi,
we are planning a similar recovery strategy. Where can I find documentation about your strategy? A consultant has suggested has to install Legato with two products for DBs synchronization.
Thanks Gigi
My email: [email protected]

"Disaster Recovery with Messaging server"

Suggest a better solution for load balancing on Netscape Messaging Server. Also for disaster recovery - in case one server goes down.

Better solution than what? Nothing? Use a cluster for the mail store. Use more than a single server for the other components and use a load balancer as the front end for those services.

Question on OAS Disaster Recovery with Disk Replication

Dear all,
We are reviewing OAS - DR approach with Disk Replication. From the docs I read that that we need to use external storage for this purpose.
Besides that, do we need other 3rd party software/hardware to implement DR with Disk Replication ?
Thank you very much,
xtanto

No double posting.
Close the open thread before opening a new one with the same info.
Read the "Rules of Enagagement"
Regards
Juan

Is there a way to rename an ASM DiskGroup from the Disks in 11g ?

Hello,
I've been looking for that and I didn't find anything except that it may not have been possible with 10g.
I'd like to rename a diskgroup to reuse it in the same ASM instance from a netapp snapclone. Of course I would prefer to do it without any ASM instance accessing it but afterall, if there is a way... (even not supported; it's to enable a set of testing database all together) !
Thank you for your help.
Gregory

Hi Gregory,
since all information about ASM Disk, Diskgroup, etc. are stored directly on the disks there is no way to rename the diskgroup at the moment (hopefully in the future, like a way to change diskgroup redundance).
Only option you have is to create a new diskgroup and copy the datafiles over with either RMAN or DBMS_FILE_TRANSFER. Then rename the file to point to new location. (alter datafile).
But since you want to duplicate it into a different ASM Diskgroup, that will not help you. The option left is to change the Disk Header information directly. Unfortunately I do not have any information about the disk header itself...
Hopefully someone can give you a hint what all to change there if you would DD this to a file change it and store it back...
Regards
Sebastian

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

Refresh to New Server with different file system

Dear Gurus,
We are having our Production DB,Test and RMAN in 10.2.0.3. We are trying to refresh TEST database with production db with last months backups and I've few queries.
Below is the filesystems:
Prod: /u99 for backup
Test: /ttu/t99 for backup
Datafiles locations are different and I can use either "SET NEWNAME" or "DB_FILENAME_CONVERT".
My production uses catalog database RMAN.
How can we duplicate test db with production (having catalog) with different backup locations on both systems. We don't have permissions to create similar directory structure on test machine.
With this I only left with restoring the production db on test server and then renaming the database. But, I want to know, if there's any possibility with RMAN directly to refresh TEST db.
Please help me.
Regards,
Kumar

If you want copy database to different OS, the n you must use transportable tablespaces
see more : http://docs.oracle.com/cd/B19306_01/backup.102/b14191/ontbltrn.htm
if you want copy database to same OS, then you can use backup based - DUPLICATE command or disaster recovery with is you shall use RESTORE database with SET NEWNAME option.
Regards
Mahir M. Quluzade
http://www.mahir-quluzade.com

Synchronizing Disaster Recovery site with the production server

Hi All,
One of the customer is asking the following query:
"How Disaster recovery site can be synchronized with the production server and how do they switch? Will the web logic server do this for them?"
This customer is having two sites one live and one a DR (Disaster Recovery) site on different location.
Can somebody answer my query?
Thanks in advance.,
Regards.,
Naveen

Firstly
Is your Datagaurd Physical( Redo Apply) or Logical( SQL apply)?
Does it have Datagaurd Broker?
When Datagaurd is setup in your environment - on the primary database( live database) the Datagaurd users LGWR or/and ARCH process to collect redo data and ship this data to standby ( DR site) and the FAL process to provide client-server mechanism for shipping archived logs to standby.
On standby database, The Datagaurd users RFS process to receive redo records from primary database, the MRP process applies redo information to standby database.
If the Data Gaurd Broker is enabled, Datagaurd also used DMON process to manage and monitor both primary and standby databases as a unified configuration.
When there is any connectivity issue to the standby and when connection is re-established, the accumulated archive logs are automatically shipped and apploed to stanby, until stanby is resynchronized with the primary. This process does not require any administrative intervention.
If there is a very large Archive Gap between the primary and secondary due to some major issue. Then the unshipped archive logs need to be shipped manually from primary to standby and needs to be applied in standby to sync up with primary. For some reason there will also arise rare issues like problem with not applying of archive logs though log shipping is success. So some work arround will solve it.
Comming to planned /unplanned outages of production site.
Datagaurd has Failover and Switchover( planned ) methods, These are not automatic, but have to be explicitly initiated by the administrator( So there will be downtime but minimal). Once initiated, Datagaurd automates the processes involved.
- S K A
Edited by: user12297346 on Jan 27, 2010 7:13 AM

Fusion Middleware, Disaster Recovery Sites with Oracle Applications

I have oracle applications EBS R12.x.x deployed with one disaster recovery site. I have some composite applications built on SOA 11g suite deployed at OFM which is taking care of my EBS R12.x.x (not disaster recovery site) instance. When my EBS R12.x.x down, is it possible that services deployed at OFM starts taking care of my disaster recovery site.
Regards

There really aren't any stupid questions, just dumb answers :-)
Have taken a look at B/R section in Admin Guide?
For 10.1.3.x refer this:
http://download.oracle.com/docs/cd/B32110_01/core.1013/b32196/part5.htm#i436649
For 10.1.2.x refer this:
http://download.oracle.com/docs/cd/B14099_19/core.1012/b13995/part5.htm#i436649
Hope this will help.
Thanks
Shail

DBFS ASM diskgroup

Re: our new X3 machines (in the data centers, yet to be installed).
I know that some of this was sort of covered in the earlier thread about DBFS. However, I do have slightly different questions...
I understand that the DBFS ASM diskgroup is mandatory and, because of the nature of how its size is calculated, the ACS consultants configure it at its minimum size. However, is it possible to (preferably at configuration time) increase the ASM diskgroup? Or is it meant to have a set size, no matter what?
Oracle have told me that I could put Flashback Logs into the DBFS ASM diskgroup (as long as I don’t configure DBFS to use it, obviously). I’m sure I read that Flashback Logs HAVE to be put into the db_recovery_file_dest (Fast Recovery Area or RECO diskgroup). Has anyone used DBFS (the ASM diskgroup) for such storage? I know it's not IDEAL given the fact it won't be spread across all storage cells, but I'm trying to figure out a way of separating the Flashback Logs from the Archive Logs because we monitor the Archive Log location for space usage (we get an alert if it gets too full and automatically kick off an archivelog backup/purge at a certain level of usage).
Mark

The first two Spinning Drives on each cell contain a 29 GB sized partition with the OS. The other 10 contain instead a 29 GB sized GridDisk from which the DBFS_DG diskgroup is built. In other words: The DBFS_DG diskgroup is also spread across all the cells but only on 10 drives (not 12 as DATA and RECO) on each cell.
This way, the GridDisks that make up DATA and RECO can have the same size on all spinning drives. And the DBFS_DG diskgroup will consume about 300GB on each cell for that reason, which can't be changed reasonably, I suppose.
You could set DB_RECOVERY_FILE_DEST='+DBFS_DG' and turn on Flashback Database, so that Flashback Logs are being generated there, while you set LOG_ARCHIVE_DEST_1 to the RECO diskgroup, so that Archivelogs get stored there. And with RMAN backups, you specify FORMAT '+RECO' to get the backups not into the Recovery Area (DBFS_DG in that example).
Kind regards
Uwe Hesse

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

SharePoint 2010 backup and restore to test SharePoint environment - testing Disaster recovery

We have a production SharePoint 2010 environment with one Web/App server and one SQL server.
We have a test SharePoint 2010 environment with one server (Sharepoint server and SQL server) and one AD (domain is different from prod environment).
Servers are Windows 2008 R2 and SQL 2008 R2.
Versions are the same on prod and test servers.
We need to setup a test environment with the exact setup as production - we want to try Disaster recovery.
We have performed backup of farm from PROD and we wanted to restore it on our new server in test environment.Backup completed successfully with no errors.
We have tried to restore the whole farm from that backup on test environment using Central administration, but we got message - restore failed with errors.
We choosed NEW CONFIGURATION option during restore, and we set new database names...
Some of the errors are:
FatalError: Object User Profile Service Application failed in event OnPreRestore. For more information, see the spbackup.log or sprestore.log file located in the backup directory.
SPException: The specified user or domain group was not found.
Warning: Cannot restore object User Profile Service Application because it failed on backup.
FatalError: Object User Profile Service Application failed in event OnPreRestore. For more information, see the spbackup.log or sprestore.log file located in the backup directory.
Verbose: Starting object: WSS_Content_IT_Portal.
Warning: [WSS_Content_IT_Portal] A content database with the same ID already exists on the farm. The site collections may not be accessible.
FatalError: Object WSS_Content_IT_Portal failed in event OnRestore. For more information, see the spbackup.log or sprestore.log file located in the backup directory.
SPException: The specified component exists. You must specify a name that does not exist.
Warning: [WSS_Content_Portal] The operation did not proceed far enough to allow RESTART. Reissue the statement without the RESTART qualifier.
RESTORE DATABASE is terminating abnormally.
FatalError: Object Portal - 80 failed in event OnRestore. For more information, see the spbackup.log or sprestore.log file located in the backup directory.
ArgumentException: The IIS Web Site you have selected is in use by SharePoint. You must select another port or hostname.
FatalError: Object Access Services failed in event OnRestore. For more information, see the spbackup.log or sprestore.log file located in the backup directory.
SPException: Object parent could not be found. The restore operation cannot continue.
FatalError: Object Secure Store Service failed in event OnRestore. For more information, see the spbackup.log or sprestore.log file located in the backup directory.
SPException: The specified component exists. You must specify a name that does not exist.
FatalError: Object PerformancePoint Service Application failed in event OnRestore. For more information, see the spbackup.log or sprestore.log file located in the backup directory.
SPException: Object parent could not be found. The restore operation cannot continue.
FatalError: Object Search_Service_Application_DB_88e1980b96084de984de48fad8fa12c5 failed in event OnRestore. For more information, see the spbackup.log or sprestore.log file located in the backup directory.
Aborted due to error in another component.
Could you please help us to resolve these issues?

I'd totally agree with this. Full fledged functionality isn't the aim of DR, getting the functional parts of your platform back-up before too much time and money is lost.
Anything I can add would be a repeat of what Jesper has wisely said but I would very much encourage you to look at these two resources: -
DR & back-up book by John Ferringer for SharePoint 2010
John's back-up PowerShell Script in the TechNet Gallery
Steven Andrews
SharePoint Business Analyst: LiveNation Entertainment
Blog: baron72.wordpress.com
Twitter: Follow @backpackerd00d
My Wiki Articles:
CodePlex Corner Series
Please remember to mark your question as "answered" if this solves (or helps) your problem.

SharePoint 2013 Search - Disaster Recovery Restore

Hello,
We are setting up a new SharePoint 2013 with a separate Disaster Recovery farm as a hot-standby. In a DR scenario, we want to restore all content and service app databases to the new farm, then fix any configuration issues that might arise due to changes
in server names, etc...
The issue we're running into is the search service components are still pointing to the production servers even though they're in the new farm with completely different server names. This is expected, so we're preparing a PowerShell script to remove
then re-create the search components as needed. The problem is that all the commands used to apply the new search topology won't function because they can't access the administration component (very frustrating). It appears we're in a chicken &
egg scenario - we can't change the search topology because we don't have a working admin component, but we can't fix the admin component because we can't change the search topology.
The scripts below are just some of the things we've tried to fix the issue:
$sa = Get-SPEnterpriseSearchServiceApplication "Search Service Application";
$local = Get-SPEnterpriseSearchServiceInstance -Local;
$topology = New-SPEnterpriseSearchTopology -SearchApplication $sa;
New-SPEnterpriseSearchAdminComponent -SearchTopology $topology -SearchServiceInstance $local;
New-SPEnterpriseSearchQueryProcessingComponent -SearchTopology $topology -SearchServiceInstance $local;
New-SPEnterpriseSearchCrawlComponent -SearchTopology $topology -SearchServiceInstance $local;
New-SPEnterpriseSearchContentProcessingComponent -SearchTopology $topology -SearchServiceInstance $local;
New-SPEnterpriseSearchAnalyticsProcessingComponent -SearchTopology $topology -SearchServiceInstance $local;
New-SPEnterpriseSearchIndexComponent -SearchTopology $topology -SearchServiceInstance $local -IndexPartition 0 -RootDirectory "D:\SP_Index\Index";
$topology.Activate();
We get this message:
Exception calling "Activate" with "0" argument(s): "The search service is not able to connect to the machine that
hosts the administration component. Verify that the administration component '764c17a1-4c29-4393-aacc-de01119aba0a'
in search application 'Search Service Application' is in a good state and try again."
At line:11 char:1
+ $topology.Activate();
+ ~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [], MethodInvocationException
+ FullyQualifiedErrorId : InvalidOperationException
Also, same as above with
$topology.BeginActivate()
We get no errors but the new topology is never activated. Attempting to call $topology.Activate() within the next few minutes will result in an error saying that "No modifications to the search topology can be made because previous changes are
being rolled back due to an error during a previous activation".
Next I found a few methods in the object model that looked like they might do some good:
$sa = Get-SPEnterpriseSearchServiceApplication "Search Service Application";
$topology = Get-SPEnterpriseSearchTopology -SearchApplication $sa -Active;
$admin = $topology.GetComponents() | ? { $_.Name -like "admin*" }
$topology.RecoverAdminComponent($admin,"server1");
This one really looked like it worked. It took a few seconds to run and came back with no errors. I can even get the active list of components and it shows that the Admin component is running on the right server:
Name ServerName
AdminComponent1 server1
ContentProcessingComponent1
QueryProcessingComponent1
IndexComponent1
QueryProcessingComponent3
CrawlComponent0
QueryProcessingComponent2
IndexComponent2
AnalyticsProcessingComponent1
IndexComponent3
However, I'm still unable to make further changes to the topology (getting the same error as above when calling $topology.Activate()), and the service application in central administration shows an error saying it can't connect to the admin component:
The search service is not able to connect to the machine that hosts the administration component. Verify that the administration component '764c17a1-4c29-4393-aacc-de01119aba0a' in search application 'Search Service Application' is in a good state and try again.
Lastly, I tried to move the admin component directly:
$sa.AdminComponent.Move($instance, "d:\sp_index")
But again I get an error:
Exception calling "Move" with "2" argument(s): "Admin component was moved to another server."
At line:1 char:1
+ $sa.AdminComponent.Move($instance, "d:\sp_index")
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [], MethodInvocationException
+ FullyQualifiedErrorId : OperationCanceledException
I've checked all the most common issues - the service instance is online, the search host controller service is running on the machine, etc... but I can't seem to get this database restored to a different farm.
Any help would be appreciated!

Thanks for the response Bhavik,
I did ensure the instance was started:
Get-SPEnterpriseSearchServiceInstance -Local
TypeName : SharePoint Server Search
Description : Index content and serve search queries
Id : e9fd15e5-839a-40bf-9607-6e1779e4d22c
Server : SPServer Name=ROYALS
Service : SearchService Name=OSearch15
Role : None
Status : Online
But after attempting to set the admin component I got the results below.
Before setting the admin component:
Get-SPEnterpriseSearchAdministrationComponent -SearchApplication $sa
IndexLocation : E:\sp_index\Office Server\Applications
Initialized : True
ServerName : prodServer1
Standalone :
After setting the admin component:
Get-SPEnterpriseSearchAdministrationComponent -SearchApplication $sa
IndexLocation :
Initialized : False
ServerName :
Standalone :
It's shown this status for a few hours now so I don't believe it's still provisioning. Also, the search service administration is still showing the same error:
The search service is not able to connect to the machine that hosts the administration component. Verify that the administration
component '764c17a1-4c29-4393-aacc-de01119aba0a' in search application 'Search Service Application' is in a good state and try again.

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

Disaster Recovery with different ASM diskgroups

Similar Messages

Maybe you are looking for