MSSQL 2005: Log Shipping Alert Error Message

Salam & hi,

Sebelum ni, log shipping setting tidak ada masalah. Sehinggalah, pada suatu hari, server pada secondary server shut-down secara tiba-tiba.

La ni, bila view pada history job, ada 2 error bagi Alert job pada log shipping secondary database.

Semalam, saya telah cuba reset configuration log shipping, dan ia nya kembali berfungsi. Tapi pagi ni error ini berlaku lagi.

Apa yang perlu saya check untuk setting ni ya?

Ni saya dapat dari job history...
----------------------------------------------------------------------------------

Untuk Alert Job:

Alert Error: 1
Message
The job failed. The Job was invoked by Schedule 105 (Log shipping alert job schedule.). The last step to run was step 1 (Log shipping alert job step.).

Alert Error: 2
Message
Executed as user: SERVERPRIMARY\Administrator. The log shipping secondary database SERVERSECOND.DB has restore threshold of 45 minutes and is out of sync. No restore was performed for 1111 minutes. Restored latency is 0 minutes. Check agent log and logshipping monitor information. [SQLSTATE 42000] (Error 14421). The step failed

----------------------------------------------------------------------------------

Copy Job:
Message : 1
2009-07-08 11:00:08.01 *** Error: The process cannot access the file '\\SERVERPRIMARY\backup\DB_20090708030000.trn' because it is being used by another process.(mscorlib)

Message : 2
*** Error: Could not copy log backup file '\\SERVERPRIMARY\backup\DB_20090708030000.trn'. The copy operation will be re-attempted on the next run of the Copy job.(Microsoft.SqlServer.Management.LogShipping) ***


----------------------------------------------------------------------------------

Restore Job:
Message
2009-07-08 11:36:22.98 Skipped log backup file. Secondary DB: 'DB', File: '\\SERVERSECOND\Backup\DB_20090706150000.trn'
----------------------------------------------------------------------------------


Terima kasih in advanced

dari secondry try masuk primary ikut network.. dia akan tanya password.. masukkan password.. done.. tu kalau guna windows 2003 ke atas

jadual ( job service ) biasa takde masalah jika permission di allow

kalau tak dapat .. cuba buat jadual baru utk backup file tu. then delete jadual backup yang lama.

atau cuba check jadual backup mana tau ada yang sama. delete yang conflict tu..


kalau server tu buat macam HA like win2008 or guna HA software.. mmm tu tak tau.. base your setting takleh nak tolong.

* High Availability

From Primary to Secondary leh access to sharing folder and vise versa.

Backup schedule yang kita set masa set-up log shipping kan?
em, untuk yang lain, ada 15 lagi schedule yang enable dalam job list.
Apa yang perlu dicheck-kan ya? Em..

Guna Windows Server 2003 R2 and tanpa menggunakan sebarang software bagi High Availability.

http://sql-articles.com/articles/lship/index.php?page=articles/lship/pre-lship.htm

6. Shared folder should be created in Primary server to hold the tran log backups.

* Read/Write permission required --->For SQL service account of Primary for the tran log backup to be successful

* Read/Write permission required --->For SQL Agent account of Secondary for the copy job to be successful

* Read/Write permission required --->For SQL Service Account of Secondary for the restore job to be successful

apa saya perlu buat:
1. Saya check dekat services Secondary Server , userSQL Server dan SQL Server Agent, untuk Log On, adalah berbeza. Adakah ini puncanya?

bila ada kat site, jadi kabur-kabur.. panik..
if baca betul2.. insyaAllah, ada jawapannya..
akan try ni esuk..

http://www.sqlservercentral.com/Forums/Topic438664-146-1.aspx

tq ayoi..

hi,

tak berjaya.

lain pula errornya..

LSAlert function: Executed as user xxx. User must be in the master database. [SQLState 4200] (Error 5001)


saya try nak reconfigure balik log shipping.
tapi tak boleh remove pula secondary database.

Errornya kerana ada replication. Tai bila check on replication folder, tidak ada setting apa-apa. Em, terlepas pandang mana-mana ke?

harap dapat membantu
terima kasih

buat jadual baru dgn user create baru utk kedua server tersebut