Restore
3 TopicsDisaster Recovery and with existing replication
Is there any Disaster Recovery plan for SQL Server that can also handle existing replication. In this case: I have an on-premise server with 9 TB in 18 user databases and existing replication with publications from 2 user databases to multiple on-premises subscribers. I have an Azure IaaS server with an identical SQL Server install and local disk allocations. My questions are: For a Basic Backup & Restore DR plan: Can existing replication be handled. The DR server has a new name? Can you restore the distribution database to another server. Can replication continue to the existing subscribers? Or is re-initializing all replication the only option? I never seen existing replication in documented in any DR plan. Does any DR documentation factor in existing replication. I know that when I restored user database in the past to another server that had existing replication, is was impossible to clean up that replication. And a full re-initial from scratch was the only option. For an Availability Group DR plan: Would Availability Groups, and making these two servers part of a WSFC handle existing replication any better? The distribution database is a system database, and I am not sure it can be handled any better with an AG. Would a complete re-initial of any existing replication be required after a failover?Solved39Views0likes2CommentsWhat's wrong with my SQL statement?
I am trying to recover a database for a customer who has been depending on MS Dynamics for a long time. His Server 2003 data drive failed irrevocably, but he had a recent backup of his Server Essentials 2005 database. His C drive held the programs. The object is to get his MS Dynamics working again so that he can add the transactions for the last month and then export all required tables to the company that's putting his company in the cloud (I don't know what the final interface might be but probably not Dynamics.) On another computer, as a test, I recovered the .BAK file to a 2012 Server Essentials - but without reference to his original programs. So, I know that his tables and views exist (I am not a SQL Developer but a generalist, so his 200 tables are not something I know how to deal with). Anyway, after creating a data drive and putting back all folder items backed up, I tried running the RESTORE command and got several errors. I'm going to skip the first try or so, because I've been figuring this out with the help of others. So, I used the following: RESTORE FILELISTONLY FROM DISK='D:\One Stop Backup\OSD_NOv8-2022.bak' Results GPSOSDDat.mdf D:\ONE STOP\MSSQL\GPSOSDDat.mdf GPSOSDLog.ldf D:\ONE STOP\MSSQL\GPSOSDLog.ldf Now I adjusted the script (I also created the folder D:\ONE STOP\MSSQL): RESTORE DATABASE [OSD] FROM DISK = 'D:\One Stop Backup\OSD_Nov8-2022.bak' WITH MOVE 'GPSOSDdat.mdf' TO 'D:\ONE STOP\MSSQL\GPSOSDDat.mdf', MOVE 'GPSOSDLog' TO 'D:\ONE STOP\MSSQL\GPSODLog.ldf', REPLACE, STATS=10 GO Result: Msg 3234, Level 16, State 2, Line 1 Msg 3013, Level 16, State 1, Line 1 The item 'GPSOSDLog' is the only item I made up in order to stay with the formula I found on this forum. It seemed that the formula used the name of the .LDF file without the extension. I don't know if this makes a difference. Also, it seems like the errors are about "Line 1" and OSD is the name of the database according to the dropdown in SQL Server Management Studio. Any ideas as to what the problem might be?568Views0likes0CommentsDo I need to uninstall and reinstall the SQL Server engine?
Sorry this is long, but I need to show some context so people will understand that the object of this is for the user to get back to using Dynamics GP 10.0 with the original database. I have an occasional customer who has been using Microsoft Dynamics GP with SQL Server Express 2005 on a Server 2003 to run his small distribution business. I have been asked to come out and fix this old relic now and then (I recently needed to replace his DIMMs.) His software is installed on his C drive (RAID1) while his data has been kept on his D drive (RAID5.) His RAID5 drive was apparently running on two drives with one marked as missing and now one of those drives failed. Luckily, he had a recent backup of the D drive. I have replaced the RAID drives and put back his files from the backup. I also restored his database on SQL Server Express 2012 on my laptop just to make sure we had his data. He needs this to run on his server so we can access the data through Dynamics GP. By the way, he was in the middle of moving all this to the cloud with some other company, but he needs to export certain tables from Dynamics to them (I'm not a SQL Server developer so this giant jumble of tables aren't very helpful - I exported some "Views" to CSV for him but there's quite a bit else I can't deal with.) So today, on the server, I ran his SQL Server Management Studio and though I could not connect to the non-existent database, I chose Object Explorer and then right clicked Database in the left menu and then chose Restore database. His database was listed in the dropdown and I selected it. I played around in there trying to figure out how to connect to the BAK file I had copied to the new RAID5 drive but then figured I had to use the SCRIPT button. Amazingly, the script filled itself in with the correct path to the external drive that contained the backup! The problem is that it executes with errors. See attached image. Does this mean that I need to reinstall SQL Server Express 2005? Is this going to break anything? Any advice would be appreciated before I press on.1.5KViews0likes2Comments