Which is the best approach with regards to the mirror of data from one server to another.
My first option is to use the replication service available in SQL.
what I need to know here is what are thr pro's and the con's of using this method.
My second option is to use a third party software such as Double Take. Again what would be the pro's and con's
I will not be using cluster service or any hardware high availability.
answers on a postcard.
I have taken three dtsx files and re written them into one each in its own container. I use the XML Task task alot which the File connection is set by a variable and the variable value is evaluated by expression (the expression makes up the path/filename from other variable values). All the variables that make up the connection are at the container scope. The package will not run now because it is saying that the source (created by variables) for the file connection do not exist.
It seems the answer is that file connections exist at the package level therefore the variable has to be at the package level. This seems to be alot of variables i now have to move to package level to generate the XML source connection. Which in essence makes it confusing as to which variables operate in which container.
My question is can we easily move variable scope (Not ideal as we have alot of variables at package level) Or Can we do the same for connection managers as we do for variables and have them only used in a scope? (this will be ideal as some connections only need to be at a container scope)
Hello,
I have a problem. I am trying to set up a disaster recovery plan and have ran into some problems. Just so you are aware, we have tried setting up replication but it failed since the database does not have primary keys(don't ask--I have no control) and we have tried to set up log shipping but we do not have the Enterprise version of SQL server so that won't work. The database is over 200GB so shipping by tape or transferring full backups across the wire is impractical. So basically my question is - "What other options can we explore for setting up disaster recovery that do not involve 'substantial' expenditures?"
There is a direct connection set up between the off site data store.
Thanks
I have the Master, Msdb and User Database dumps. I want to build another server with the avilable dumps.
Please help me....
Clark
I thought I had a good backup of my database, but it turns out my Backup Executive jobs were misconfigured and
my backup backup via MS Backup only grabbed the files that weren't in use. (.bak file)
I re-installed my Server 2000 to fix some other problems and now I've lost all my database. My wife (the MD) is
very upset over losing her schedule, billing info, and all her medical records. Whoops.
Anyway, I have two BAK files from one (and two) days ago, but when I replace them into the database, no data shows up.
The BAK files were created on an NTFS system, which is now running FAT32 - I don't think that should matter?.
Is there any hope or do I start typing?
Hi,
A test server I was developing on has died and all of my good work was on it.
However I have a copy of the Data folder containing the folloing files:
Test_Data.MDF
Test_Log.LDF
Is it possible to restore my database from these files?
If so how would I go about it?
Many thanks in advance!
We are having major hardware replaced on our W2000 Adv Server and we
need to be prepared to restore the entire system.
If the hardware fix goes badly, worst case, the plan is to
rebuild the server and then REINSTALL SS7 and
then restore all the databases from tape backups.
My question is, which database(s) should we restore first?
Should we restore master and then proceed to restore the user
databases or restore the user databases first and restore master last?
Thank you in advance.
I'm looking for something beyond trying to recover databases and/or SQLServer. My group has been tasked with documenting the recovery for 30+ servers that make up our applications infrastructure including SQL, Web, etc. I posted this here as opposed to another forum because I couldn't even find disaster recovery related topics in the other forums.
Our Systems group (Lan, Wan, etc.) isn't really much help at all. Their focus is more on the mainframe and Novell network recovery. Their perspective is that they will get any replacement server back on line in the event of failure but we are on our own from there.
There are three disaster scenarios for which we must plan: 1) A 737 does a nose dive into the Data Center. 2) A hurricane floods the Data Center. 3) A server gets smoked for whatever reason and is no longer useable.
Assume...
- that there were enough survivors to rebuild the network infrastructure at a remote site.
- we have to recover the operating system, additional software, IIS, SQL, applications, etc.
Questions:
What's the best way to capture the server's configuration on an automated basis?
What's the best way to recover the configuration mentioned above?
How do you maintain a current snapshot of any particular server and how do you ensure there's a documented history of the changes?
Does anybody use a centralized backup system? OmniBack, BackupExec?
What's the best/fastest way to get the replacement equipment?
Where else can I look to find this information?
Have I asked all the questions that I should or can you think of one I've missed?
Confused? Ask any questions you wish.
Sidney Ives
Database Administrator.
Yikes! I lost my autoloader bakcup device along with my SQL2K Server. I reinstalled Win2k and now can see my RAID partitions where I had SQL server installed, along with all of the files. Since my tape backup is dead, I cannot simply restore from media. I'd like to reinstall SQL Server and then somehow grab the files on the partition and restore all of the data back to where things were. Is this even possible? If so, could someone help me out? I am worried by reading this list that my primary application (Sharepoint) will not be able to be restored because of security issues. Any ideas on that?
I appreciate any help you can provide.
-Den
Hi Experts,
I am planning to create a disaster recovery site for my production database server. But I am not able to identify which option to choose. Not sure if I should go with database mirroring or transactional replication.
What are the pros and cons of each option?
Production and disaster recovery site location will be geographically very far.
please help
Regards,
S
Don't sit back because of failure. It will come back to check if you still available. -- Binu
I'm looking for a proven method and documenation on recovering a publisher that is also the distributor. I have had problems with subscribers failing and database corruption on subscribtion databases. I do not have any documentation or experience in recovering a publisher that also is it's own distributor. Please point me in the right direction for this and any in house documentation that may not be published to the public would be great.
View 2 Replies View Related
I am using SQL 2000 and have a major issue! I am new to SQL and not sure what to do about the license key being lost due to an update.
Background:
The server was originally loaded with a temp verison of SQL 2000 by the installer of the hardware until the Enterprise Edition arrived on site to insure that all the hardware worked fine. The Enterprise software was loaded onto the system and the license keys were installed. Everything has been working fine for several months. The server has been rebooted a few times after installing the license keys.
Trouble:
I loaded SP2 for Server 2003 and rebooted the server and now SQL thinks it is running the temp version and states that the license key has expired. I tried the suggested solution listed on the site of "upgrading with no changes" and the installation completes but never asks for my license keys. I rebooted the server and it states the samething thing that the temp has expired. It appears that one section can see the keys and another section does not. I have an active database that I do not want to loose but I am stumped on what to do to in order to re-install the license keys.
Any suggestions? Can copy the databases that I have created, uninstall SQL, re-install SQL from CD and then paste back my database? Will the databases restore correctly or is this to simple of a solution?
I have run out of ideas and options in order not to loose the database.
I used to have WSS 3.0 Beta version, to update that to B2TR i got a problem and for which i require to reinstall the WSS again. Now I have the old WSS_Content.mdf and WSS_Content.ldf. I want this old site content tranfer to the current one.
How can I restore the data of this Site Content Database to the new one which I have newly created.
The mdf size is 3 gb and the ldf is nearly 8 gb.
Immediate response is highly appretiated.
Regards,
Raj
Recently I watched Microsoft Support WebCast: Microsoft SQL Server 7.0 Common Problems and Resolutions dated August 29, 2000. I am trying to find information for a total disaster recovery for my server. In the webcast the presenter made a reference to a Microsoft article Q240872, "How to Resolve Permission Issues When a Database is Moved Between SQL Servers?". I can't find this article. Since we are working with the scenerio of total diaster, we are starting with a new server. I know that when we tried to recover a database to a new server, the server recognized that the database did not originate on that server. Does anyone have any ideas? Or does anyone know how to contact Microsoft so I can find out how to get a copy of this article?
Thanks!
What is the best recovery plan consist of??
Backup : Full and Transaction log.
Hardware : Clustering, RAID
I am not sure about what all need to be Scripted for having a good disaster recovery plan??
Scripting:: tables, views, defaults, rules, users, roles, permissions
Backup : Triggers, Stored Procedures
Your inputs are appreciated.
Sneha
Hi friends,
My company is planning to do exercise for disaster(complete server screwed up). They don't want to add the users or jobs. They are asking me to restore Master,Msdb and User Databases. I Planned like this if there is any mistake please reply me ( It is urgent)
1.Installing NT, IE and MS sql server 7.0. with all appropriate service packs.
2.Creating User databases which were present on the previous screwed up server with same name.
3.Restoring Master Database and Rebooting the server.
4.Restoring Msdb Database and Rebooting the server.
5.Restoring the User Database along with the transaction logs.
6.Running 'DBCC checkdb' command on all the databases.
Please reply me soon.
Thanks
dindu.
Hi, Im going to set up a disaster recovery plan for SQL-servers at my company. Does anyone know where to find a template for this ? Something to help me that describes what you must write down and so on ?
Please email me besides answering at discussion board.
regards
We have the following situation. Box A is publisher & Box B is a DR box that is a subscriber to Box A keeping it in line with Box A. If Box A goes down Box B then becomes the 'live' box. I assume I have to do nothing to Box B to allow this to happen but if I'm wrong please let me know. My question is :- Once Box A is back online how do I get the data from Box B onto Box A so that Box A can be made the 'live' box again?
View 1 Replies View RelatedHi All
This is a Pearler !!. SQL 7 and NT 4
Site A and B are 30 miles apart
"Site A" SQL 7.0 Cluster with Drives on Shared Storage.
"Site B" SQL Server Cluster with Drives on Shared Storage
Both Configured as Active/Active (8+ databases <100GB total)
How can I get the DB's (all) from Site A and allow a DIFFERNET cluster to control them.
Basically, I want to move all DB's from "Site A" and bring them into "Site B" with all relevant data ..ie master DB etc . I have a time window of 90 Mins and I cannot lose one single piece of data.........( I need to lie down now)
Help would be apprecitated)
I am part of a team developing a Disaster Recovery plan for our company, most of the data is in SQL Server 2000, and Visual Foxpro, what are the best options of backing up this data to one remote site, and being able to failover to those servers in case of a disaster.
[
We've all data and log files located in SAN mount point. In case ofprimary server crash, is it possible to unmount the volumes andremount at secondary server? Do we have any problems with master DBmoving this way. Detach,attach or backup/restore are not our options.Thanks
View 1 Replies View RelatedI am trying to get our database back to a "clean" state after a disaster at the weekend. The primary server died - completely - and so the secondary server was promoted to primary. Now, I'd like to remove all traces of log shipping on the server so I can start fresh when our new server arrives imminently.
However, when I try to remove log shipping, SQL tries to connect to the old primary server which of course no longer exists. I can't find anyway to remove the log shipping. What can I do?
Hi,
Can any one please share the sample disaster recovery plan. I dont know what I have to include in it and how to prepare it. Your help will be highly appreciated. Thanks in advance...
Would appreciate if anyone can advice me about disaster recovery plan for SSRS.
I am going to build one report server with Windows 2003 Enterprise x64 + SQL 2005 Enterprise x64 with Reporting Service, all in one box. The remote report data source is on another SQL 2000 server.
If the report server has failed, what option do I have to continue reporting services? I am not worry about the remote report data source as it is backup regularly.
Thanks in advance!
I need to know if anybody has any suggestions on websites to visits, documents or templates that will give examples on how to set up a Disaster Recovery Plan for SQL Server 7.0 Databases. I am mostly interested in the Documentation portion to acquire knowledge on the various methodologies used out there. I am a Jr DBA and would appreciate any feedback.
Thanks.
I am a newbie to SQL admin. I have been given a responsibility to document
a) Backup, recovery and disaster plan
Can some one give me poninters where I would start???. Please let me know if you can suggest any sites for new DBA's and also where I would find out about what to document, etc??. Thanx for your time
Barry(hiremeasap@hotmail.com)
Hi,
I want to setup disaster recovery site for small databases from disffrent data centre.Which method would be good and from where I will get some good stuffs to read except online documents?
we are trying to simulate a disater recovery of our SQL2000 and SQL2005 development servers. Which is the order in which we should restore the DBs. I am talking specifically of MSDB, master and user DBs; should we restore user DBs before master and MSDB?
Thanks,
Carlos
We have 10 SSIS packages which are deployed on 2 servers. (at different geographical locations)
On both the servers we will install all the 10 packages, but on server1 we will enable 1 - 5 and server2 we will enable 6 to 10.
the idea is that if server1 goes down we enable all the 10 on server2 (and vise-versa).
Is this the best way to implement disaster recovery of SSIS packages? We want that in all cases of failure the SSIS packages are ready to process the ETL: tasks.
regards,
Abhishek.
Hi All,
Does somebody know where can I find a guide or white paper regarding to the subject?
It should contain the procedures needed to recover Analisys, Reporting and Integration services as well.
Thanks,
Miska
We have implemented replication on SQL Server 2005 with 1 publisher and 1 snapshot (non-update) subscriber.
The purpose is for emergency disaster fail-over.
If the publisher (Primary) fails, then we switch the DNS so the subscriber (Secondary) becomes ‘live’ and we need it to be able to accept new records.
The problem is that the identity seeds start at 0 on the Secondary server - so no records can be input, as there are primary key violations.
We can set the increment value to -1 for all the seeds, and this works.
However there are config & replication issues with bringing up the database on the failed (Primary) server once it is restored and back online.
Does it really need to be this complicated?
Where are the ‘next identity seeds’ for all the tables in the database stored? Can they be restored on the database when fail-over occurs?
Or is there some setting in the Microsoft SQL Dba?
Folks:
Is it possible to setup a Disaster Recovery server for Reporting services (Databases: ReportServer and ReportServerTempDB)? If so, will loading these 2 databases (Log shipping) allow to me access the same reports as in Production server. Is there anything which I have to do on DR Server when the Production site is down?
Thanks!
I'm trying to figure out what solution (replication, mirroring, clustering) would work best for me.
I have been reading many articles in BOL and in this forum. Most talk about getting data TO a backup/standby/subscriber, but I can't find a lot of info regarding getting the data BACK after a disaster is over.
We have a main office and a disaster recovery facility. Most of the time there are no data updates at the disaster location. So, I need to get data to the disaster facility via WAN (latency is not a huge issue - end of day syncing is fine) for backup purposes. In the event of a disaster, the main office will be offline and data changes will happen at the disaster site. When the disaster is "over" and we return to the main office, what's the best scheme to reverse the data back to the main office to start business again? We are a financial company, and have gigabytes of relatively static data. Most changes are current day. So, to snapshot a 100GB database when I know only a few hundred MB changes a day doesn't seem feasible to me.
Most replication scenarios (at least from what I see) can't easily "reverse" the replication after a disaster situation. I'm looking at merge replication on a schedule which seems to look good, but was wondering if anyone else has any ideas or suggestions?