sql 2000 log shipping problems
-
hello,
I am trying to test log shipping between a server 2k3 box with a instance of sql2k5 ent and a named instance of sql 2k ent from a windows 2k sql 2k ent box. The first problem i had was registering the named instance of sql 2k on the 2003 box so what i did was use an alias via named pipes. after i got that sorted out i got rid of the error of sql server does not exist. well now im running into a whole new error and i dont know what to do. here is the error from the log files.-----------
Microsoft (R) SQLMaint Utility (Unicode), Version Logged on to SQL Server 'SERVERNAME' as 'NT AUTHORITY\SYSTEM' (trusted)
Starting maintenance plan 'lgshippingtest' on 6/14/2007 9:30:05 AM
[1] Database LOGTEST: Transaction Log Backup...
Destination: [E:\transactlogs_replicate\LOGTEST_200706140930.TRN]
** Execution Time: 0 hrs, 0 mins, 1 secs **
[Microsoft SQL-DMO (ODBC SQLState: 28000)] Error 18456: [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'DOMAIN\SERVERNAME$'.
[2] Database LOGTEST: Delete Old Backup Files...
0 file(s) deleted.
Deleting old text reports... 0 file(s) deleted.
End of maintenance plan 'LGSHIPPINGTEST' on 6/14/2007 9:30:06 AM
SQLMAINT.EXE Process Exit Code: 0 (Success)
---------------------------------------------------------------------------------------
what i dont understand why in the beginnig it shows loging in as nt authorit\system (trusted) then it fails as domian\servername$... dont get it.
Thank YOU
-
What account are the SQL services running under?
--------------------
Colt 45 - the original point and click interface
-
agent runs as domain account and server runs under system.
-
So change the server account to a domain account and it should be right.
Personally I don't use the maintenance plans for log shipping. Too many points were things like this can trip you up. Basically the log shipping proces is a 3 point process, backup, copy and restore. Each of these steps should be run independently so there is reduced risk of a failure in one step bringing down the whole process.
eg: using the maintenance plan approach, how would you upgrade/service pack the standby server without disrupting the backup and file copy for the production server? When they're seperate steps you can "turn off" the restore, but the backup and copy continue to function.
--------------------
Colt 45 - the original point and click interface
Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply