-
Title
How to run SLSLOGSHIP.EXE from command line -
Description
SLSLOGSHIP.EXE is usualy run from the LiteSpeed for SQL Server Log Shipping GUI Wizard
-
Cause
N/A
-
Resolution
Command Line
Backup
"C:\Program Files\Quest Software\LiteSpeed\SQL Server\engine\SLSLogShip.exe" -Backup GUID -server PUBLISHER
Copy
"C:\Program Files\Quest Software\LiteSpeed\SQL Server\engine\SLSLogShip.exe" -copy GUID -server SUBSCRIBER
Restore
"C:\Program Files\Quest Software\LiteSpeed\SQL Server\engine\SLSLogShip.exe" -restore GUID -server SUBSCRIBER
SQL Server 2000
BACKUP (Publisher)
"C:\Program Files\Quest Software\LiteSpeed\SQL Server\engine\SLSLogShip.exe" -Backup DFF69224-FBD4-4E6E-B729-C63B26C7ECC1 -server SQL2000-600-2
where GUID is "maintenance_plan_id":
select maintenance_plan_id from msdb.dbo.log_shipping_primaries
where primary_database_name = N'plan702'
COPY (Subscriber)
"C:\Program Files\Quest Software\LiteSpeed\SQL Server\engine\SLSLogShip.exe" -copy 5515645A-E40C-419A-9220-10F198416CB4 -server SQL2000-600-2\SQL2000
RESTORE (Subscriber)
"C:\Program Files\Quest Software\LiteSpeed\SQL Server\engine\SLSLogShip.exe" -restore 5515645A-E40C-419A-9220-10F198416CB4 -server SQL2000-600-2\SQL2000
where GUID is "secondary_plan_id":
SQL Server 2005 and higher
BACKUP (Publisher)
where GUID is "primary_id":
select primary_id from msdb.dbo.log_shipping_primary_databases
where primary_database = N'plandb'
COPY (Subscriber) & RESTORE (Subscriber)
where GUID is "secondary_id":
select secondary_id from msdb.dbo.log_shipping_secondary_databases
where secondary_database = N'plandb-2'