Anyone has a detailed procedure description about how to setup a standby
server? Microsoft makes it sounds very easy which are more complicated.
How to handle system databases, does standby server need to be exact
hardware as the primary one?
Thanks in advance,
Xiaodong
*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!
I've been reading a million and one posts on replication
My scenario is that i have a live SQL 2000 server. In a DR invokation, i'e i've lost my live sever, i want to be able to access the same data at the DR (SQL 2000) site and have it accessable to the users. DR server has a different name to the live box.
Replicate
Master CRMDatabase
Data changes all the time but can have hourly replication of transaction logs for this example. I've currently researched a sp called update logons but this has to be fed each account name to enable them on the new server. There must be a way to activate all CRMDatabase logons with the new server?
Could someone be kind enough to lead me through a step by step guide on the best solution.
Could you suggest me some of the ways to have standby database server?
All of a sudden my company is in a need for standby database server in sync upto the 10 minutes. Main production database is about 8 GB. It serves almost 6 main sites for the company. No body in my group has worked with standby server issue before.
I need to create standy server. My production server has SQL Server 7.0 and standby server has SQL Server 6.5. I've sync the data between two servers and is planning to do log shipping every 15 min. But I'm little confused, Can the version of Sql server be problemetic? Pls. anyone guide me.
Can I implement the Standby SQL Server using the SQL Server Standard Edition? What's actually the difference between Standard and Enterprise Edition? As I know the Enterprise edition can be installed for up to 32 CPU while Standard edition can only be installed for up to 4 CPU.
Can I implement the Standby SQL Server using the SQL Server Standard Edition? What's actually the difference between Standard and Enterprise Edition? As I know the Enterprise edition can be installed for up to 32 CPU while Standard edition can only be installed for up to 4 CPU.
Where can I find a document that describes how to setup and configure a standby server?
I'm new to SQL Server 7 (I like it). We have a NT 4.0 server with SQL Srvr 7. We just bought another Box that will have the same thing on it with the idea if the 1st goes down, the new box is a 'hot' standby...of course a 'cold' standby will be ok too... I'm not fussy at this point. If you have info on both great.
I'm the SQL Srvr 7.0 DBA (my background is Oracle DBA). I've been doing alot of reading!!!
Can some provide the information I need or point me to someone I can contact?
I hope to create a 'Standby' server for a critical web application. I am tempted to set up replication, but realize this task could also be done by a scheduled DTS job, which may be much simpler. I have read up on replication and have some reservations about it. A little about our environment: Data does not change very rapidly. Some days maybe no edits, some days maybe changes to 100 rows. The environment is stable, there are few DDL changes....development is essentially over. This system has 10 databases which it uses. Hence, all would need either replication or DTS Transfers. Intended publishing & subscribing servers are on same domain. Both are production servers. I Believe either Snapshot or Transactional would meet our needs if we replicate. There is no user need for replicated data. This is SOLELY a Disaster Recovery motivated situation. Reservations about replication include the hassles with identity columns, the hassles with Subscriber Databases being left in 'Read Only' mode (thereby slowing & complicating the recovery process), the difficulty in cleaning up a server after replication is halted if we abandon replication. My gut feeling is DTS might be best. There are 10 Databases. Sizes (inaccurately) reported are 5 at less than 5 MB, others at the following sizes: 10 mb, 24 mb, 26 mb, 39 mb and one big one: 3000 mb (3 gb). Latency is not a big issue. If these were DTS'd nightly that would be fine. Transactional Replication would be slightly better, but the amount of data change is not high. I would solicit anybody's input on this. Thanks,
We are maintaining a stand-by database server by doing a daily manual restore of logs. On weekends we do Reindexing of the tables for performance boost. some of these reindexing jobs take upto 10 Hrs We have found that the restore of the logs taken in the source server after the reindexing job takes as much time it took to do the reindexing. Typically 15 transaction log sessions for a day takes 40 minutes to restore. However the restore of the tranlog that was taken after a 10 Hr long reindexing job takes as much time(10 hrs) to do the restore also. The size of the tranlog does not justify this time frame. ( Size of tran logs after reindex is more than other logs but is less than 3 GB) I would like to know what exactly is happening during the restore of the tran log. Is it doing the reindexing in the destination system as well? The destination server (standby) is in non recovered mode all the time. The interesting thing is that I would only take 8 Hrs to do a full restore of the database. We are using ArcServ software for backup and restore.
We are on SQLServer Enterprise 7.0 sp4 on NT 4 Enterprise on source and destination. We run SAP R/3 on a MSCS Clustered env. The source database size is 260 GB
We have a process wherein the production DB is replicated to a server.subscriberA nightly and then a job processes the database for reporting services. Whenever the job fails we have to redo the process all over again. By the time we are finished it is already late in the day and our customers dont like it. Our solution for a standby server is as follows: 1. create another server.subscriberB and start same process from server.subscriberA. So, both servers are replicated from the Production server but SubscriberB is set to run half an hour delayed than subscriberA. The purpose is that should subscriberA process fails, we still have subscriberB. Then we could just change the datasource of the reports to subscriberB 2. replicate subscriberA.ReportServerTempDB to subscriberB.ReportServerTempDB 3. replicate subscriberA.ReportServer to subscriberB.ReportServer
I will explain my environment. I have two servers A and B both with Win2003 SP1 In the server A, i have a database sql server 2005 in compatibility mode -> 8.0.
In server B have SQL server 2005 and one database in standby / read-only mode. This base is getting to the transactional hour of the server A and applying in standby database. This works fine.
The problem I have is: I need to get the standby server B and create another database for test using yours files. I can get the files of server A because i have 512kpbs link and would be impractical.
Putting in the standby offline mode, i copying the files to another directory on the same machine, but when I try to create another database using the duplicate files of standby receive the following message:
Msg 1824, Level 16, State 1, Line 2 Can not attach a database that was being restored.
What is the command that I need to execute to attach the new bank without message Msg 1824. The command that executing is below:
USE master CREATE DATABASE ON homo (FILENAME = N'F:MSSQLDATAhomohomo_prd_homo.mdf '), (FILENAME = N'F:MSSQLloghomohomo_prd_log_homo.ldf ') FOR ATTACH As a newcomer I do not know which command I run before attach to conclude restore.
I execute restore database with homo recovery but the database does not yet exist. If I run the restore standby database with recovery, I lose standby and need to download backup copy the entire database in server A to B using link.
We need to perform some maintainence on our database server which may take quite some time. We have a standby server which we constantly apply logs to. We are planning to recover the standby server and use it while the production server is being maintained.
My question is how to I get back to using the original production machine. The only way I can think of is to do a full backup on the standby machine, do some transaction log backup and then restore these on the original production machine.
Is there any way to use the full backup from the original production machine and well as logs from the standby machine. When I try this I get the message that the database has not been rolled forward far enough.
In summary: 1. Backup full database on Prod Server 2. Restore full database on Standby Server 3. Backup transaction log (1) from Prod Server 4. Restore transaction log (1) on Standby Server 5. Recover database on Standby Server 6. Make modifications on Standby Server 7. Backup transaction log (2) on Standby Server 8. Restore full database on Prod Server 9. Restore transaction log (1) on Prod Server 10. Attempt to restore transaction log (2) fails.
I have one cluster (two machines) of sql server 2005 active/passive called "ClustA" with one Ent. server edition license and another separate server called "STDA" as warm standby server for "ClustA".
We have the following scenario: Server A replicates Database A to Server B. Server C has Database A on it as well, but in standby mode. We are applying the transaction logs generated by Database A on Server A to the database on Server C leaving it in standby mode each time.
Let's say we had planned maintenance for Server Aand dumped the last set of transactions on Server A in standby mode to be applied to to Server C. What happens to the replica on Server B? When I start to use Server C, can I backup its transactions and apply them to Server A, and then have those transactions replicated to Server B? And then what do I do when the maintenance is complete so that I can swithc back to Server A and have the replication continue on as before the maintenance to Server B?
Can anyone direct me to a code that would automatically apply transaction logs to a DB in the standby server? We have a process that dumps the transaction log backup from the primary server into the backup server every hour on the hour, but I need to apply that transaction log as soon as it is in the standby server.
I am sure someone will ask, why not do transactional replication or log shipping? My answer to that is I have yet to learn how to setup replication between servers. I need to get our backup server up and running in the next few days.
SQL Users/DBAs,I'm trying to move data files around for a database that is in standbymode. I can detach/attach the database fine usingSP_DETACH_DB/SP_ATTACH_DB , but when I re-attach the database the logsequence is broken and I can't restore any more logs. Does anyoneknow if there is a way to move around data files and keep the databasein standby mode?Thanks,JB
We are using MSSQL 2005 and Log Shipping. After making our secondary SQL server primary, how can we put the secondary SQL server back into standby mode?
Is there anyway I can implement a standby server in SQL Server 6.5 ? In addition are there any tools in the market which I can use to perform a differential backup ?
I believe SQL Server 7.0 can do this, will I be able to use ARCserverIT or seagates's backup exec to perform these functions ?
I have one standby server that I use for multiple production DB SQL Server 2000 servers. We are upgrading one of the production SQL Servers to 2005. I will install 2005 on my standby and run 2000 and 2005 side by side.
Is this okay? Are there any caveats specific to running 2000 and 2005 on the same standby server?
a different scenario leads to the same problem, the error message: Could not find "Standby" in sysservers. Run "sp_addlinkedserver" to add the server to sysservers"
I browsed the thread for the same error message and the solution doesn't applies to me. Here is my system settings. we have a kind of backup system. a primary server is set up to copy the database files to a standby server. when the primary is off, the standby server will take over primary's name and ip. and our application runs on the standby as if in the primary. in both machine the odbc connection are set to point the primary server.
this setup works well in SQL server 2000 for both primary and standby servers, but it gives the error message on SQL 2005 in the standby server. I noticed that this is because the application opens an empty table. after inserting a record by hand, the error has gone away.
I know it doesn't make too much sense, but it 's what I observed. Could anyone give me some input how could this happens and what' s the solution?
We are planning on setting up a Standby server for our Production SQL Server7.0 for the sake of Redundancy. Does anyone know of a way (script) to automate the trans. log process to the standby server?
We are planning to provide a disaster recovery facility for a production system. Clustering has been ruled out for technical reasons so we are considering either transactional replication or Log shipping.
Microsoft suggested the log shipping option but it seems a bit messy to me and only provides a warm standby in that it only copies log backups to the secondary machine.
Any ideas why log shipping was suggested in preference to transactional replication? Anyone have any experience in this area?
I have inherited a problem that I am hoping someone can help out with. A developer used a perl script to move some backup files from one server to another and then restore the databases on other server (at least we think that is what happened, no one is really sure at this point)
Now I need to take the databases ourt of read only mode and drop them but I get an error 5063 stating that the database is in warm standby and the alter database and sp_dboption statements both fail.
How do I get the databases out of warm standby mode?
Thanks in advance for any help you all can provide.
Consider this scenario: I have a production 2005 database and wanna have another one on the same system that contains just the same everything. What is the best way to do this? Besides, pls give me usefull links to all HA concepts in SQL Server 2005. Thank you!
I'm setting up log shipping and am running into an issue with applying the transactions logs.
This is my 5th server that I'm setting up and I take a backup of the source database, restore it with replace on the standby server. Then I take a log backup, copy it over and try and restore on the standby server, but the LSN#'s are off. It tells me it's too late for the log and try an earlier..
The timestamp on my backup is 11:43 and my translog was at noon...
I ran a checkpoint on the source database, but that didn't seem to do anything.
hi all, I am considering what should be the best way of implementingthe following requirement.I've got a SQL2K production server. Now I've got another machine as thestandby machine for this serverso I'm thinking what method should I be using for this.Should I be using log shipping or Replication? Or if it's replication,what kind of replicationsshould it be?I am thinking maybe snapshot replication can be just fine, right?
I have recently implemented a backup solution that keeps our standby server up-to-date with nightly database backup and restores. Ironed out all the problems with syslogins and orphan users. It's been working very well over the past few weeks.
On the production server we do hourly tran log dumps every hour between 8am and 10pm. I would like to implement some form of "log shipping" to bring the window of vulnerability down to 1 hour. By making some alterations to my current process I been able to incorporate the hourly log dumps in the same process.
However, when I try to restore the log on the standby servre I get the following message, Server: Msg 4305, Level 16, State 1, Line 1 Specified file 'HODB1SQLBACKUPRace_Prd_T_dump.200101231513' is out of sequence. Current time stamp is Jan 23 2001 2:01PM while dump was from Jan 23 2001 3:01PM.
After a bit of investigation I found the dumptrdate field in the sysdatabases table and it was set to Jan 23 2001 14:01. After updating this field to Jan 23 2001 14:01, I ran the load command again but received the same error message.
Is there something else that needs updating on the standby server? Is what I'm trying to do possible in 6.5? Any help or ideas would be greatly appreciated.