I'm attempting to configure log shipping on 2 servers with SQL Server 2000 sp4 Enterprise Edition. I keep getting the following error when the job attemtps to execute.
Error 14261: The specified primary_server_name.primary_database_name('C')
already exists.
I have tried this KB http://support.microsoft.com/kb/298743 and i got the same error again!
Please HELP!
I am in the process of migrating from Sql Server 2000 to 2005. Part of my plan is to move some database's to 2005, but use the 2000 compatibility mode for the short term. My issue is this, our DR boxes are still on SQL Server 2000, would I still be able to use our log shipping processes? Or would I be better off in starting with migrating the DR boxes to 2005 first?
Thanks in advance.
I am implementing log shipping in sql server 2000.The logs are been backed up on the source server but they are not been restored on the destination server.What could be the possible reason for this?
Thanks
Madhukar
------------
Robbie at 3/7/2002 10:13:00 AM
Great news but how??
------------
mmwops at 3/7/2002 9:09:32 AM
can be done
------------
Robbie at 3/7/2002 7:03:16 AM
Does anyone know if Log Shipping be done using SQL Server 2000 standard edition or does this have to be Enterprise??
Many Thanks
Robbie
I am currently running a Standard Edition of SQL 2000 on a WIndows NT4.0 Platform with service pack 6a installed. I want to implement Simple Log Shipping on my Standby Server as a means of improving my ability to recover from a contingency.
The Setup is as follows:
1. Both the SQL Server Service and SQLAGENT Service on the Primary Server Start with a Domain Admin Account
2. Both the Primary and Standby Server have mixed authentication
3. The current security context of the User (Which happens to be a Domain Admin) is used for the Link Server Relationship.
4. The Directory on the Standby Server where the Transaction Log gets backed up to has permissions of "Everyone" - Full Control" as does the log file itself.
The error I am receiving is as follows:
Executed as user: xxxinvbsg. Backing up Northwind to
DISK=S5ad$yyyNorthwind_20020130_1540_LOG.BAK [SQLSTATE 01000] (Message 0)Processed 1 pages for database 'Northwind', file 'Northwind_log' on file 1. [SQLSTATE 01000] (Message 4035) BACKUP LOG successfully processed 1 pages in 0.264 seconds (0.007 MB/sec). [SQLSTATE 01000] (Message 3014) Execute [s5a].master.dbo.sp_ApplyStandByLog 'Northwind',N'S5ad$yyyNorthwind_20020130_1540_LOG .BAK',N'd:yyyUNDO_Northwind.DAT'
[SQLSTATE 01000] (Message 0) Executing RESTORE LOG Northwind FROM
DISK='S5ad$yyyNorthwind_20020130_1540_LOG.BAK' WITH STANDBY='d:yyyUNDO_Northwind.DAT [SQLSTATE 01000] (Message 0) RESTORE LOG is terminating abnormally. [SQLSTATE 42000] (Error 3013) Cannot open backup device 'S5ad$yyyNorthwind_20020130_1540_LOG.BAK'. Device error or device off-line. See the SQL Server error log for more details. [SQLSTATE 42000]
(Error 3201). The step failed.
Any help on this will be appreciated.
Thanks
Brad
Hi,
I am now trying to configure Log Shipping in my compeny but I have encountered some difficulties. The destination site and the source site are far from each other and the transaction logs are too big, this situation causes an huge overload on our private network (we use WAN which is complitly disconnected from the internet). Is there any way to compress the transacion logs with zip or rar and combine it in the log shipping mechanizem?
Is there another way for making this files smaller?
I would be greatful for any ideas in this matter.
Thanks in advance,
Zvi Gilinsky
Hi,In the MS SQL 2000 Server, if the log shipping is set up right, does thatmean data in primary server changed will mapped to secondary server lateron?Thanks.Jason
View 4 Replies View Related
Hi,
I have maintanance plan for log shipping.it was working fine for last 2 months.But due to some reason I have to restart the server and after that my log shipping job was failed.When I start the job it is showing error "Executed as user: OKS-MARAdministrator. Invalid drive specification 0 File(s) copied. Process Exit Code 4. The step failed".This error is coming when I copy the bakup database file to another server.I have checked all the mapping and sharing option.Also I have nt changed anything in the two servers.But still then the error is coming.
Can you please help me out to shot out the problem?
Thanks in advance.
Sunanda
hi,
i have log shipping between 2 servers on sql server 2000. the log shipping failed because of some problem with transaction log backup files. somehow the files are missing and it is not able to apply transaction log. can someone please tell me how can i restore the log shipping between 2 servers. please help asap..need to fix it in couple hours
We have an environment where 3 SQL 2000 servers exist; one production servers and two standby servers that receive logs via log shipping. Everything works fine and it is stable. My client wants to get a new 64 bit server and run SQL 2005 64 bit version for the production box. Can we still do log shipping with the two remaining SQL 2000 boxes or do they all have to be on the same version and bit version?
Thanks
Bill
Hey all-
I am working to establish a backup plan for SQL Server 2000. We are currently doing log shipping between servers.
A full backup once a week
transaction log backup every hour
We run a bulk deletion (delete * from table where date < ninetydays) which deletes 22,000 rows approximately. We are running in Full Recovery mode.
I wonder if there was anyway to improve my backup plan, preferably minimizing logging when the deletion takes place but still backup the data with log shipping.
Let me know if any of you have ideas. Thanks
Nate
Dear all,
I have setup log shipping for one of my production server.The purpose of setting log shipping is having a standby server in case the primary fails.
Now i am getting the error saying:
The log shipping destination server is out of sync by 640 minutes. [SQLSTATE 42000] (Error 14421) Associated statement is not prepared [SQLSTATE HY007] (Error 0). The step failed.
I appreciate any ideas.
Hi All
Can someone tell me what to do with this Error:
SQL Server Management Studio could not save the configuration of 'B1' as a Secondary.
------------------------------
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)
------------------------------
The specified @server_name (A1) does not exist.
The specified @server_name (A1) does not exist.
The specified @server_name (A1) does not exist. (Microsoft SQL Server, Error: 14262)
I have two sql 2005 servers A1 and B1 but the databases are setup with sql 2000 compatibility.
A1 service accounts use local system account.
B1 service accounts use domain system account.
I can easily restore a database from a shared folder on A1.
I followed this article to setup log shipping.
http://deepakinsql.blogspot.com/2007/06/how-to-configure-log-shipping-in-sql.html
did anyone come across this problem?
Log Shipping is not replication in the immediate sense, but it is as close as I could find in this set of forums. If there is a better place for this question, please direct me to it.
View 6 Replies View RelatedHi all,
Scenario : MS Windows 2003 SP1 - MS SQL Server 2000 EE SP4
Log Shipping
My secondary server was restoring backup logs successfully, but suddenly i got the following error:
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 4323: [Microsoft][ODBC SQL Server Driver][SQL Server]The database is marked suspect. Transaction logs cannot be restored. Use RESTORE DATABASE to recover the database.
[Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE LOG is terminating abnormally.
How can I fix this situation without re create the maintenance plan ??
I have SQL Server 2005 log shipping setup with primary/secondary configuration. I can confirm from the logs that log shipping is working without issue, however, reports generated from the monitor server show this message:
Violation of PRIMARY KEY constraint 'PK__#log_shipping_mo__3ABBDC91'. Cannot insert duplicate key in object 'dbo.#log_shipping_monitor'. The statement has been terminated.
There is nothing special about the configuration. Any ideas?
I am receiving errors from a job that no longer exists. The databases created for this no longer exist also.
DATE/TIME: 4/6/2007 3:32:00 PM
DESCRIPTION: The log shipping secondary database LOG1.log_ship_test has restore threshold of 45 minutes and is out of sync. No restore was performed for 6004 minutes. Restored latency is 0 minutes. Check agent log and logshipping monitor information.
COMMENT: (None)
JOB RUN: (None)
I have gone into agent jobs and deleted those associated with it. I have also gone into the msdb database and deleted any lines associated with it in the log_shipping tables. But the errors keep coming. What do I need to do to clean this up?
Thanks
Hey all!
I have log shipping set up between two servers (s1 and s2). Data is flowing from s1 to s2 and the log shipping monitor is on s1.
I get the following error sporadically
"Transaction Log Backup Job for DB Maintenance Plan 'LogShip DatabaseName" failed..
Error: 60000, Severity: 10, State: 1
So i usually go and start the job manually and it runs fine. But why does this happen and what does the error mean? The above job is scheduled to run every 5mins daily.
Thanks in advance!
THE LADDERS (The Most $100k+ Jobs.)
www.TheLadders.com
I am getting the following error " The specified servername does not exist" when I run the Log Shipping procedure. There is only a Primary server running Win Server 2003 withe Service pack 2 and SQL Server 2005 with service pack 2 and one secondary server runnung Win Server 2003 R2 with service pack 2 and SQL Server 2005 with service pack 2. All permission setting look ok . Can anyone help
View 4 Replies View RelatedHi
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
my database is already deleted and there is no job are running for that database .previously we configure a log shipping for that database and deleted.log shipping backup job also deleted.the log shipping alert job is throwing bellow error.
The log shipping primary database tes1 has backup threshold of 60 minutes and has not performed a backup log operation for 132722 minutes. Check agent log and logshipping monitor information.
We tried to configure log shipping using script generated by GUI and when executed specific script which is meant for secondary server the database is not created and threw below error.
Msg 15010, Level 16, State 1, Procedure sp_add_log_shipping_secondary_database, Line 50
The database 'BUBALLO' does not exist. Supply a valid database name. To see available databases, use sys.databases.
Note: Only Copy, restore and alerts jobs have been created.
The account I'm trying to configure log shipping is the service account by which SQL and agent services are running and folder in where data and log files are intended and to be created is open to all (everybody has read/write permissioins) believe the issue is not with permissions.
I set up Log Shipping with just 2 servers primary and secondary. When I run from the Wizard for the very first time keeps failing at the stage of saving Secondary Server Configuration info. When i instead run the generated script this problem disappears but then restoring of transactions fails - the process can backup transactions from the Primary server , copy them accross to the secondary and fails on the restore. Any ideas why.
View 6 Replies View RelatedHi,
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
I received an alert from one of my two secondary servers (all servers are running 2012 SP1):
File 'E:SQLMS SQL ServerMSSQL11.MSSQLSERVERMSSQLDATAMyDatabaseName_DateTime.tuf' is not a valid undo file for database 'MyDatabaseName (database ID 8). Verify the file path, and specify the correct file.
The detail in the job step shows this additional information:
*** Error: Could not apply log backup file 'MyDatabaseName_DateTime.trn' to secondary database 'MyDatabaseName'.(Microsoft.SqlServer.Management.LogShipping) ***
*** Error: Table error: Page (0:0). Test (m_headerVersion == HEADER_7_0) failed. Values are 0 and 1.
Table error: Page (0:0). Test ((m_type >= DATA_PAGE && m_type <= UNDOFILE_HEADER_PAGE) || (m_type == UNKNOWN_PAGE && level == BASIC_HEADER)) failed. Values are 0 and 0.
Table error: Page (0:0). Test (m_freeData >= PageHeaderOverhead () && m_freeData <= (UINT)PAGESIZE - m_slotCnt * sizeof (Slot)) failed. Values are 0 and 8192.
Starting a few minutes later, the Agent Job named LSRestore_MyServerName_MyDatabaseName fails every time it runs. The generated log backup, copy, and restore jobs run every 15 minutes.
I fixed the immediate problem by running a copy-only full backup on the primary, deleting the database on the secondary and restoring the new backup on the secondary with NORECOVERY. The restore job now succeeds and all seems fine. The secondaries only exists for DR purposes - no one runs reports against them or uses them at all. I had a similar problem last weekend on a different database that is also replicated between the same servers. I've been here for over a year, and these are the first instances of this problem that I've seen. However, I've now seen it twice in a week on the same server.
I work for a small state government department. We are about to install SQL Server 2005.
A national government department that runs on SQL Server 2000 are willing to give us a backup of their database (20 gig I think) and then log ship to us regulary. Our aim is to have a copy of the database that we can query from and that is only a day or so out-of-date.
I'm having no luck.
1. I can backup the SQL Server 2000 database.
2. I can restore the SQL Server 2000 database onto the SQL Server 2005 box no worries.
2. BUT, if I attempt to restore the 2000 database with the option 'Leave the database in read-only mode ...' selected (so that I can then restore transaction logs and it's read-only), then I get an error message. ""This backup cannot be restored using WITH STANDBY because a database upgrade is needed. Reissue the RESTORE without WITH STANDBY.". I'm doing all this using SQL Server Management Studio.
It appears we will have to use SQL Server 2000 rather than 2005 to get this working.
Q: Has anyone successfully done this from SQL 2000 to SQL 2005 please? If so, how was it achieved please?
Thanks.
I have log shipping set up between 2 SQL 2000 SP1 Servers on Win 2000. The db is small 10 meg, and when the restore job on the backup server fails I am getting "sqlmaint.exe failed. [SQLSTATE 42000] (Error 22029). The step failed." as the message, the maint paln on the primary server show no error. Anyone seen this before? The restore has worked 3 out of 5 times
View 2 Replies View RelatedHello
I want make log shipping between a Sql Server 2000 64 bits itanium (primary server) and a SQL Server 2005 32 bits.
Is it possible or I'll have got any problem?
Thanks you
I have a web application developed in VS.NET 2005 [using C# as code behind]; and it uses SQL Server 2000 Enterprise edition as backend.
The application runs fine, though it gives an error on IRREGULAR intervals on SQL data requests.
Error Details:
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
My problem is this:
1) Why does it show an error of SQL 2005, while I use SQL 2000. SQL 2005 is not even installed on the server, though VS.NET 2005 is installed.
2) The error comes only at irregular intervals. Users are able to login properly otherwise.
3) Application starts working again if we do either of the following: (a) Restart IIS (b) Restart application pool (c) Restart server.
4) Named pipes and TCP/IP are added to the "Network Configuration" of the SQL server 2000.
5) Error does not come on any specific page; or any specific code; or at any specific time.
6) We do not have any background service or any other activity happening on the server; and the server hosts only this application, within a single virtual root.
Any thoughts on why is this happening, and how to resolve this?
Hello,
I am applying hourly differential backup to the backup server from production with the following command. This command makes the database on standby server into read only mode.
RESTORE DATABASE ARSYSTEM FROM DISK = 'E:SQL backup from productionsql_full_backup'
WITH MOVE 'arsystem' TO
'd:ardataarsystem.mdf' ,
MOVE 'arsystem_log' TO 'D:ARLOGARsystem' ,
STANDBY = 'E:SQL backup from productionSQL daily diff back up'
Now I want to run a command which will put the database in write mode. I have created a job which would make the datbase Write mode. This job runs successfully sometimes and fails sometimes. I need to ensure that the job always succeeds. When it fails, how do I troubleshoot and what is the possible fix?
Thanks in advance.
The error message is
Cannot apply the backup on device 'E:SQL backup from productionSQL daily diff back up' to database 'ARSYSTEM'. [SQLSTATE 42000] (Error 3136) RESTORE DATABASE is terminating abnormally. [SQLSTATE 42000] (Error 3013). The step failed.
The steps for the job are as follows with the failing step highlighted in bold.
copy /y "\172.31.9.12Remedy BackupackupSQL backupsql_full_backup" "E:SQL backup from productionsql_full_backup"
copy /y "\172.31.9.12Remedy BackupackupSQL backupSQL daily diff back up" "E:SQL backup from productionSQL daily diff back up"
xp_cmdshell 'net stop "bmc remedy action request system server"'
exec rp_kill_db_processes 'ARSYSTEM'
RESTORE DATABASE ARSYSTEM
FROM DISK = 'E:SQL backup from productionsql_full_backup'
WITH
MOVE 'arsystem' TO 'd:ardataarsystem.mdf' ,
MOVE 'arsystem_log' TO 'D:ARLOGARsystem' ,
NORECOVERY
Failing step
RESTORE DATABASE ARSYSTEM
FROM DISK = 'E:SQL backup from productionSQL daily diff back up'
WITH
MOVE 'arsystem' TO 'd:ardataarsystem.mdf' ,
MOVE 'arsystem_log' TO 'D:ARLOGARsystem' ,
RECOVERY
xp_cmdshell 'del /f "E:SQL backup from productionsql_full_backup"'
xp_cmdshell 'del /f "E:SQL backup from productionsql daily diff back up"'
xp_cmdshell 'net start "bmc remedy action request system server"'
I have scheduled the following hourly diffential restore job too which never fails.
RESTORE DATABASE ARSYSTEM FROM DISK = 'E:SQL backup from productionsql_full_backup'
WITH MOVE 'arsystem' TO
'd:ardataarsystem.mdf' ,
MOVE 'arsystem_log' TO 'D:ARLOGARsystem' ,
STANDBY = 'E:SQL backup from productionSQL daily diff back up'
EXEC MASTER..XP_CMDSHELL 'del /f "E:SQL backup from productionSQL daily diff back up"'
Our SQL Server 200 box is getting perflib errors when we get a decentamount of people using an application that I wrote, call queue system,web based. To accomplish a queue type system on a button push I wrotea query like this...BEGIN TRANSACTION;Select top 1...fields here...FROM table with (xlock,readpast)(2 joins)WHERE numerous where clausesORDER BY 2 order bys.Now our sql server starts timing out..then in the app log this showsup....Error: 1203, Severity: 20, State: 1Process ID 62 attempting to unlock unowned resource PAG: 6:1:126407.For more information, see Help and Support Center athttp://go.microsoft.com/fwlink/events.asp.The reason I am doing xlock is to make a record not viewable to 2people if they click the button on the web form that runs the abovequery within the same minute, they would get different records....So to avoid this error which I assume is due to my xlock should Irethink my query?
View 3 Replies View RelatedWe have a stored procedure that calculates the floor nr for users at our company campus using their office location. The calculation is done by a function that returns an integer. Unfortunately, not all users enter their information correctly so the function sometimes raises an error. Below is the code of that stored procedure.
UPDATE PERSONS
SET FLOORNR = dbo.FloorNR(OFFICELOCATION)
WHERE OFFICELOCATION IS NOT NULL
IF(@@ERROR <> 0 OR @@ROWCOUNT = 0)
BEGIN
RAISERROR ('Failed to calculate the floor number', 16, 1 ) with nowait
END
However, when the function dbo.FloorNR fails, it doesn't raise our error, but it seems to raise the error that comes from dbo.FloorNR.
How can we catch errors that come from dbo.FloorNr so that we can raise our own error? Our company still uses SQL 2000, so we cannot use the SQL 2005 try/catch option.
Hi
I'm trying to finish a DTS Package by controlling the error flow with @@ERROR.
Yet, there's one error which I can't seem to capture
'Syntax error converting the varchar value to a column of data type int'
If you try the code below, I can't seem to pull an @@ERROR ID from it.
IF
OBJECT_ID('tempdb..##LogTemp') IS NOT NULL
BEGIN
DROP TABLE
##LogTemp
END
CREATE TABLE
##LogTemp
(
Error_ID INT
)
INSERT INTO ##LogTemp
(
Error_ID
)
VALUES
(
'Test'
)
PRINT @@ERROR
Query Analyzer prints this out:
Server: Msg 241, Level 16, State 1, Line 83
Syntax error converting datetime from character string.