Hello,
I was just trying out Log Shipping with SQL Backup 8 in my testing environment: SQL Server 12 shipping to SQL Server 2016. When I set up log shipping using SQL Backup 8 (latest build) everything seemed fine but the restore job would fail every time. When I checked the job on the destination derver I found out that it had been created without any line breaks - the whole job code was one single line of code and therefore unusable. I manually updated the code and recompiled; now everything seems to be fine.
Here's what the Log Shipping Wizard created on the destination server:
DECLARE @errorcode INTDECLARE @sqlerrorcode INTEXECUTE master..sqlbackup '-SQL "RESTORE LOG [Nummernkreise] FROM DISK = ''\Server01LogShippingLOG_Nummernkreise_*.sqb'' WITH NORECOVERY, MOVETO = ''C:Program FilesMicrosoft SQL ServerMSSQL13.MSSQLSERVERMSSQLBackup''"', @errorcode OUT, @sqlerrorcode OUT;IF (@errorcode >= 500) OR (@sqlerrorcode <> 0)BEGINRAISERROR ('SQL Backup failed with exit code: %d SQL error code: %d', 16, 1, @errorcode, @sqlerrorcode)END
Is this an error in SQL Backup 8 or is something wrong on my system?
Regards, Ralph
I was just trying out Log Shipping with SQL Backup 8 in my testing environment: SQL Server 12 shipping to SQL Server 2016. When I set up log shipping using SQL Backup 8 (latest build) everything seemed fine but the restore job would fail every time. When I checked the job on the destination derver I found out that it had been created without any line breaks - the whole job code was one single line of code and therefore unusable. I manually updated the code and recompiled; now everything seems to be fine.
Here's what the Log Shipping Wizard created on the destination server: Is this an error in SQL Backup 8 or is something wrong on my system?
Regards, Ralph