Log Shipping To 2 Different Servers
May 2, 2003
Currently we run log shipping to a standby server located at the same site as the production. We currently move the 2 most important databases every 5 minutes. Everything works fine. We are now being asked to also create a standby server at remote site (we should have a high speed connection to this site). Is it possible or has anyone tried to do log shipping to 2 different servers? Can you log ship from a prod server - to a standby server - and then from there to another stand-by server?
View 3 Replies
ADVERTISEMENT
Aug 8, 2003
I have a solution where I have 3 servers to setup in a log shipping environment. The primary and first failover are located at the same location. The 3rd failover is across a slow LAN link. Haven't done it, but inside the wizard can you designate more than 1 server. Also, I have seen back and forth arguments over where the log shipping monitor should reside. With the budget I can't afford a box to just sit there and run the log shipping. Would i be better off putting the log shipping monitor on the standby server that is located at the facility? We have one client where I have the log shipping running on the primary, and the performance impact is non-exsistent.
View 3 Replies
View Related
Sep 15, 2015
I have to set up log shipping from Prod server "A" to 2 different DR servers ("B" and "C")...What do i have to do differently (or additional) using the GUI (ie not using Tsql Scripts) to accomplish this, in addition to the steps that are done to log ship to just one DR server?
View 0 Replies
View Related
Aug 9, 2007
I am having trouble finding any documentation on how linked servers are set-up under SQL 2005 for log-shipping and replication. Under SQL 2000, the only linked servers "visible" were ones that were user-defined. Under SQL 2005, it seems when you set-up log-shipping or replication, you get these new linked servers which are automatically defined. I would like to understand them and in particular, how security is maintained. We recently had a production issue where after some problem with a server which resulted in having to restart SQL Server, and shrink msdb, log-shipping started to fail authentication when trying to run alert jobs. Only after rebooting the server, and also the log-ship target server, and waiting 9 hours, did the authentication correct itself. I would like to know how it resolved itself and what took so long?
View 3 Replies
View Related
May 13, 2007
Hi
I could not able to find Forums in regards to 'Log Shipping' thats why posting this question in here. Appriciate if someone can provide me answers depends on their experience.
Can we switch database recovery model when log shipping is turned on ?
We want to switch from Full Recovery to Bulk Logged Recovery to make sure Bulk Insert operations during the after hours load process will have some performance gain.
Is there any possibility of loosing data ?
Thanks
View 1 Replies
View Related
Jun 8, 2006
Hi,
I 'm sure I am missing something obvious, hopefully someone could point it out. After a failover log shipping, I want to fail back to my inital Primary server database; however, my database is marked as loading. How can I mark it as normal?
I did the failover as follow:
I did a failover log shipping from the 2 server Sv1 (Primary) and Sv2 (Secondary) by doing the following
1) Stop the primary database by using sp_change_primary_role (Sv1)
2) Change the 2nd server to primary server by running sp_change_secondary_role (Sv2)
3) Change the monitor role by running sp-change_monitor_role (Sv2)
4) Resolve the log ins - (Sv2)
5) Now I want to fail back - I copy the TRN files to Sv1 - use SQL Ent to restore the database at point in time. The task is done; however, the database is still mark as loading. I could not use sp_dboption.
I appreciate any suggestion.
Thanks in advance
View 5 Replies
View Related
Nov 21, 2007
I have a report that was designed using SQL Reporting Services that sits on a SQL reporting server. It's nothing too exciting, it is essentially a three page application with legal jumbo on pages 2 and 3 and applicant data in fields on page 1.
We use rectangles to force page breaks to page 2 and to page 3.
When running the report on the report server, it shows and prints fine.
When running the report from the QA website internally, it shows and prints just fine.
When running the report from the production website from a machine internally, it shows and prints just fine.
When running the report from outside of the company network, the report is jacked. It obliterates large chunks of text, crams text together, and creates blank pages.
I need help in determining where I even begin with trouble shooting this!
View 1 Replies
View Related
Aug 21, 2001
can anyone tell me if they know of a way to automate the update process from development servers to live server, with little interference from an administrator
I have a development team that are constantly updating their databases along with their ASP code, and want to publish changes an a weekly basis. They have asked me for a way to take their new structures, tables, procedures etc, and copy them to the live servers, but NOT to interfere with existing customer data.
Funny I know – and I hate the idea btw :(
Any references, contacts, 3rd party tool recommendations welcome,
Thanx,
Darren
View 1 Replies
View Related
Sep 27, 2007
I am in the middle of a major migraton project, moving from x86 SQL 2000 to IA64 SQL 2005. I have a business need to link to several legacy servers. I have a number of problems I am trying to solve.
1) Linking a Kerberos server to a non-Kerberos server.
2) Linking x64 or IA64 servers to x86 servers.
3) Linking SQL 2005 to SQL 2000.
Two of the errors I am encountering are:
------------------------------
TCP Provider: An existing connection was forcibly closed by the remote host.
Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.
OLE DB provider "SQLNCLI" for linked server "SCDC250DB" returned message "Communication link failure".
(Microsoft SQL Server, Error: 10054)
------------------------------
And
------------------------------
The OLE DB provider "SQLNCLI" for the linked server "SCDC250DB" reported an error. Authentication failed.
Cannot initialize the data source object of OLE DB provider "SQLNCLI" for linked server "SCDC250DB".
OLE DB provider "SQLCLI" for linked server "SCDC250DB" returned message "Invalid authorization specification".
(Microsoft SQL Server, Error: 7399)
If someone has worked through these problems before, I would appreciate it if you could direct me to the relevant documentation to resolve these issues.
Thanks!
Brandon Forest
Database Administrator
Data & Web Services Team
Sutter Connect Information Technologyforesb@sutterhealth.org
View 2 Replies
View Related
Jun 21, 2002
Could somebody please guide me on how best to Implement SQL Server Log Shipping. I have gone through BOL without luck. Thanks.
View 2 Replies
View Related
Aug 1, 2000
I need to create a RO copy of a production DB owned by an outside company. We are connectd via a WAN link, but cannot use replication. They are proposing using an initial load via tape, and sending us a text file nightly with the days changes to the DB. We will then need to load that data using BCP, DTS or some other method. Does any one have any ideas on using log shipping instead of the text file. It would only be practical to get a fresh load of the entire DB once a quarter or once a month at most. It is a 40+ GB database and we are expecting 100 to 200 MB of logs per night. For business reasons, we are limited to some type of file transfer mechanism for the data transfer, and cannot really change their backup schedule which is nightly fullbackups and tlogs every 30 minutes.
View 1 Replies
View Related
Nov 28, 2000
Can anyone point out me , What does Log shipping mean ?
Is it backup of Log file ? or moving backup logs to any other destination ?
Thanks
Karthik
View 2 Replies
View Related
Mar 27, 2002
Hi all,
I am using SQL 2k EP Editions with SP2 on Win 2k Advance servers. Since more than week or so I am trying to establish log shipping between two servers. But its not working.
I am using database maintainence plan wizard to set up log shipping. Every thing works fine as far as wizard is concern, it creats plan for log shipping. But my log shipping is not working. The plan to back up log on source database is working fine. I can see the job history and the log files in the backup folder. But I have found that the job on the standby server to copy log file on network folder is failing and so the job to restore log on stand by server. I get the following message
"sqlmaint.exe failed with error state....."
Little reaserch on the standby server found that sql server is using maintainence plan to copy and restore log files, but i do not see any database maintainence plans on standby server as well as I have checked that there is no plan id in sysjobs table on either server.
I have sa rights. The account used by sql service and sql agent have admin rights and they do have rights to access the network folder for both the servers. So there is no rights problem.
I have followed all steps published in white paper for setting up log shipping on microsoft web site.
I have searched microsoft KB but it is of no use for sqlmaint.exe.
Any help is highly appreciated.
thanks in advance.
Minesh.
View 1 Replies
View Related
Sep 6, 2000
This might end up being fairly lengthy...I'm in the midst of implementing log shipping as a "warm stand-by" solution at my company. All the components appear to be in place: I'm using cmd shell to copy the backup device file to a remote server and then execute a RESTORE stored procedure on the remote server.
The copy and restore work just fine. The problem I'm having is with the transaction log dumps and restores.
We normally dump transaction logs (and then truncate) every hour. With the log shipping being implemented, we're going to want to do separate log dumps every ten or fifteen minutes, copy that dump over to the remote server, and then apply that log to the database.
Here's the question: for the log ship portion, I don't truncate the log. But after the "normal" log dump occurs, things get tossed out of whack. When you try to apply a log, I get the message "database has not been rolled forward enough....".
Has anyone encountered this type of issue and if so, how did you work around it? I'm assuming it's a simple of issue of certain options you set on your dumps and scheduling....
I'd appreciate any help....
Thanks!!!
View 3 Replies
View Related
Sep 24, 2002
Does anyone know if Log Shipping in SQL 2000 Ent also ships over database schema changes?
View 2 Replies
View Related
Oct 14, 2002
We are considering implementing log shipping. Do the sql server logs keep track of the logs that are shipped and applied through log shipping? Or is there some other way to make sure that all logs have been shipped and applied?
View 1 Replies
View Related
Jul 25, 2004
I have been successful in getting log shipping working but still have some nagging questions that I cannot find answers to.
1. I had a situation where the copy for one TranLog took much longer than the 15 minute interval I have it setup for. It seemed to get stuck on that copy. Is that how it is supposed to behave.
2. Related to the question above, weekly, I have jobs that reorganize, check integity, recalc statistics. Would these jobs create very large log files? If so, how do others deal with this?
3. Is there any documents available that discuss testing converting your secondary server/database to your primary and back again?
4. Is there a way to setup Email notification to report out-of-sync conditions?
Any other gotcha's that people have run into.
Any help would be greatly appreciated.
Thanks,
Ken Nicholson
View 2 Replies
View Related
Feb 2, 2005
Hi
While configuring log shipping, if i choose the "allow database to assume primary role" then the "ceate and initialise new database " option is selected by default..Does this happen all the time or am i missing something.What if i have already initialised the destination database.
Thanks
Madhukar Gole
View 2 Replies
View Related
Aug 18, 2006
Hi all,
I am testing my log - shipping strategy. I have tried with northwind database and it was successfully created and is operating. However in order to test I have created a new Test Table in the primary database to see whether it is working. From now on database shows that it has been loading and I cannot see any tables it is grayed and it says loading. What would be the problem? When I checked the logs it has been copying to the secondary database and it doesn't show any error in the log-shipping monitor. It seem everything is cool accept this loading part. If some one help me I really appreciate it.
Thanks
LS
:confused:
View 6 Replies
View Related
Mar 27, 2002
Hi all,
I am using SQL 2k EP Editions with SP2 on Win 2k Advance servers. Since more than week or so I am trying to establish log shipping between two servers. But its not working.
I am using database maintainence plan wizard to set up log shipping. Every thing works fine as far as wizard is concern, it creats plan for log shipping. But my log shipping is not working. The plan to back up log on source database is working fine. I can see the job history and the log files in the backup folder. But I have found that the job on the standby server to copy log file on network folder is failing and so the job to restore log on stand by server. I get the following message
"sqlmaint.exe failed with error state....."
Little reaserch on the standby server found that sql server is using maintainence plan to copy and restore log files, but i do not see any database maintainence plans on standby server as well as I have checked that there is no plan id in sysjobs table on either server.
I have sa rights. The account used by sql service and sql agent have admin rights and they do have rights to access the network folder for both the servers. So there is no rights problem.
I have followed all steps published in white paper for setting up log shipping on microsoft web site.
I have searched microsoft KB but it is of no use for sqlmaint.exe.
Any help is highly appreciated.
thanks in advance.
Minesh.
View 2 Replies
View Related
Apr 3, 2002
Hi All,
I failed to configure the Logshipping in
SQLServer2000, through database maintenance plan wizard,
at last step I got the following error.
Microsoft SQL-DMO(ODBC SQLState:42000)
Error 50007:xp_repl_encrypt:Error executing
srv_paramsetoutput
I am running SQLServer2000 Enterprise Edition with
Servicepack2, and Windows2000AdvancedServer with
Servicepack2 on both machines and bothe machines are in
the domain, both SQLServerservices are running under
Domain account.
thanks in advance,
Rob.
View 1 Replies
View Related
Jun 19, 2002
HI,
Is there any effect on taking full backups on Primary Server while log Shipping is in place? If we take a full backup is that applied to the secondary server?
thanks
View 1 Replies
View Related
Jul 18, 2001
We would like to use log shipping for a Near Real Time (5 min delay)reporting server. SQL 2000 requires exclusive use of the database when the logs are applied. This presents a problem since there may be a couple of hundred users on the NRT server. Even if they only make connections when running the reports there could be some contention issues. Has anybody used log shipping in this type of scenario?
View 2 Replies
View Related
Oct 17, 2001
Is it possible to log ship a database from server A (source) to server B (read only) when the database on server A is partly replicated (transactional repl) to several other servers ? All hints and advices are highly appreciated.
View 2 Replies
View Related
Jan 26, 2001
Does anyone know why some databases in SQL 2K Enterprise are not available for log shipping? In other words when you select a database Log Shipping this option is not available (grayed out). Other DB's on the same server log ship without problem.
Any ideas?
I think Microsoft has an answer to this but their site is not working so I can't get to the Q270006 which supposed to discuss that. If you do a search in KB for "Log Shipping is disabled" you will see the WebCast link which references Q270006 but then if you click on the link to go to the Q link does not work and search Q270006 is not found in KB..
View 1 Replies
View Related
Feb 26, 2004
Hello,
to use Log Shipping solution, Entreprise Edition is required for both Primary and Secondry Server (you agree ?).
Do you have an idea about licence regarding the secondry Server (suppose that you have to switch 2 or 3 per year. The second server will be used 2 or three times per year).
In some plateform (xeon CPU), the logical number of CPU is 2 times the physical number (SQL Server See 2 CPUs. You have 1 physical CPU).
Do you have an idea about licence in this case ?
Thanks a lot ...
View 2 Replies
View Related
Apr 8, 2008
Hi,
I have following question ( same was asked to me by my collegue)
I have Log shipping between two servers ( say Server A - Primary & Server B - Secondary).
One user is logged in to B Server and fired a long query on the same database / object. it is taking a very long time to execute.
Q : How this will impact the log shipping process ?
Ans : Log shipping will fail as the secondary db will show as " database is in use" for log shipping process.
Q : How to recover the log shipping process?
And : Notify the user to disconnect the session / or kill the user session. But i don't know how to recover the log shipping.
Thanks in advance.
-- Chetan
View 1 Replies
View Related
Jan 25, 2008
All, I am new to log shipping and I am troubleshooting an issue with it. Basically somebody restored a backup from a day ago on the primary server, now the load is failing on the destination (obviously). I read that I should disable the jobs and backup and restore to the destination server to get it going again. I have some questions on this though, since the destination is a standby I read that I need to use the WITH STANDBY clause and specify a standby file name to use. Where do I find out the standby file name to use here and also is this the only way to get it back in synch?
Thanks in advance.
Future guru in the making.
View 5 Replies
View Related
Jul 23, 2005
I am attempting to set up log shipping from my primary dell clustered 2node sql server to a backup quad xeon server in case of a failure. When Ifollow the information given from Microsoft regarding this and I get tothe point where I am at "Add Destination Database" I am being promptedfor my server name, which shows the primary one ONLY. I dont seem to findany documentation on where I add in the secondary server name...Searching online has yielded no responses for me and MS only says toregister the servers... but where? and do I need to restart? I am onlytrying to be extra cautious as this is a live database.Thank you in advance for your help...
View 5 Replies
View Related
Nov 29, 2005
Hello:I'm using MS SQL Server 2000 developer editionand trying to implement log shipping to the secondary server.I copied a database MDF and LDF files from primary to secondary serverand all data is there, but this database still in recovery mode so I can notapply log shipping to it.My question is:how to put the database on secondary server in standby or non-recovery modeto apply log shipping?Thanks,GB
View 1 Replies
View Related
Jul 20, 2005
Hi all,i was wondering if for the use of logshipping two Enterprise Editionversions of SQL Server are necessay or logshipping can also workbetween a Enterprise Edition and a Standard Edition.Does anyone know an url for me where i can read more about this. I'vefound quite a lot of articles but not one telling me explicit thatlogshipping does not work between an EE and a SE version.Greetings,Sjaak
View 3 Replies
View Related
Jun 28, 2006
I am trying to set up a dual log shipping configuration in SQL 2005 where I have one primary server to two secondary servers.
All of the following is being done from the primary server.
If I fill out the entire log shipping configuration window with both servers and then press OK, and let it all get set up, and then run the log shipping report, I only get status information for one secondary database - the other one is there but has no information available, yet the setups on both secondarys are OK and the jobs are succeeding on them.
If I then go back into the log shipping screen for my database and remove the server that I'm getting no status information for and press OK to actually remove it, then go back in and re-add it and THEN run the log shipping report I now get information for the server I just deleted and re-added, but no status information for the other server. If I look in the secondary database table, I only see a record for whatever secondary server is currently correctly showing status information.
When looking at the scripts generated by the log shippping screen for my setup, I noticed the stored procedure call below gets executed from the proc sp_delete_log_shipping_secondary_database that the script calls. This SP is only getting passed the database name, which is the same on both secondary servers and would therefore be the same for both servers' entries in the secondary database table on the primary server. Therefore, I think it is deleting ALL records in the secondary database table that have that name before re-adding the record for the one server and that's what's causing my issue, i.e. if my database is called "userdb" it is deleting all entries for "userdb" regardless of whether they are on the primary or secondary servers and then only adding one server back. Am I wrong?
exec @retcode = sys.sp_delete_log_shipping_secondary_database_internal
@secondary_database = @secondary_database
,@ignoreremotemonitor = @ignoreremotemonitor
,@overwrite = 0
View 4 Replies
View Related
Sep 15, 2006
Can some one help in understanding Log Shipping. My production database is over 50 GB and we want to implement Log shipping to ensure a standy by server. I know how to implement the Log shippinng and what it does but I am not sure how to perform Log shipping with daily FULL database backup on production server. Consider this scenrio.
1. 1:30 AM Monday Full database backup on production server
2. At 1 hour interval transaction backup on production server and applied on Standby server.
3.1:30 AM Tuesday Full database backup on production server.....
Here I am getting confused. DOo I have to apply this full back up again on standy servers, because if I don't then my LSN for next transaction log will be different.
So how can i take a full database backup of the production server while implementing Log Shipping.
Thanks,
Punu
View 6 Replies
View Related
