Comments
Sort by recent activity
Hi Peter
Unfortunately, I don't have the original seed restore command. We are in the middle of a server migration and already running behind schedule so I can't go through the process again.
The problem (I think) is in the way the shipped backups are moved to the processed folder. I'm assuming this is performed using an OS "copy" command rather than a "move".
This is the log shipping restore command if that helps.
DECLARE @errorCode INT
DECLARE @sqlerrorCode INT
EXECUTE master..sqlbackup N'-SQL "RESTORE LOG [UKREPDIWPRD] FROM DISK = ''\\UKBHSR195\LOG_SHIPPING\UKREPDIWPRD\LOG_UKREPDIWPRD_*.sqb'' WITH ERASEFILES = 48h, NORECOVERY, MOVETO = ''G:\LOG_SHIPPING\UKREPDIWPRD\PROCESSED''"', @errorCode OUT, @sqlerrorCode OUT;
IF (@errorCode >= 500) OR (@sqlerrorCode <> 0)
BEGIN
RAISERROR ('SQL Backup failed with exit code: %d SQL error code: %d', 16, 1, @errorCode, @sqlerrorcode)
END / comments
Hi Peter
Unfortunately, I don't have the original seed restore command. We are in the middle of a server migration and already running behind schedule so I can't go through the process again.
The p...
Thanks Robert. I believe you are right. I'm going to try switching back to full and check the sizes there.
One problem I appear to have run into is that, since trying to ship the large log/pages, the target database has gone into error and will no longer accept restores. I'm getting
SQL error 823: I/O error (bad page ID) detected during read at offset 0x000000f90e000 in file 'E:\MSSQL\Data\UKREPDIWPRD_Data.mdf'
It might be related to a failed log restore, but I can't seem to get round it. I'm going to re-initialise the log shipping and start over.
Thanks
Vince / comments
Thanks Robert. I believe you are right. I'm going to try switching back to full and check the sizes there.
One problem I appear to have run into is that, since trying to ship the large log/pages, t...