If above two T-SQL statements return different results, please update the log_shipping_monitor_secondary table manually. There are also some similar blogs for you troubleshooting this issue.
There is only a Primary server running Win Server 2003 withe Service pack 2 and SQL Server 2005 with service pack 2 and one secondary server runnung Win Server 2003 R2 with service pack 2 and SQL Server 2005 with service pack 2.
I support a company that is using Log Shipping setup by the previous DBA. The log shipping is setup to do the default transaction log backup/ship each 15 min’s, 24 hours a day. Each night I do a Full backup of the Primary database which takes about 30-50 min’s. So during this backup the log backup/ship has occurred several times.
Do you want to build log shipping between on-prem SQL Server 2014 and AWS RDS? If you can make sure the on-prem server and AWS RDS service can communicate with each other, maybe it is possible.
Estou enfrentando vários problemas com a etapa de restore do Log shipping, se você olhar nos logs do SQL Server Agent ele apresenta com sucesso, mas na verdade ele não restaurou nada, ele simplesmente pulou todos os arquivos.
The adm_BackupHistory table is the central history point for the log shipping process for the source system. All backup work performed is recorded to this table. Connect to SQL Server management studio Disable three Log shipping related jobs i.e. “BTS Log Shipping – Get Backup History”, “BTS Server Log Shipping Restore Databases”
You CAN definitely use log shipping and mirroring at the same time. You can make use of log shipping to ship the log to a remote site for DR and have a database-mirroring, high-availability configuration locally. However, Sometimes it is a slight bit tiresome to set up log shipping going the other way once a failover has occurred, whereas mirroring is easy in that portion.
From error log above, it shows that there is an operating system error and SQL Server is not able to access the transaction log file. To detect the system error, please view the system event in the event viewer.
The smallest size for a virtual log file is 256 kilobytes (KB). The minimum size for a transaction log is 512 KB, which provides two 256-KB virtual log files. The number and size of the virtual log files in a transaction log increase as the size of the log file increases.
