Replication Manager and SQL Log Truncation

Hi there

While Replication Manager is an excellent application to create quick, painless copies of your application data, and at scale.....it deliberately as such does not perform log truncation of SQL or Oracle Databases.

The main reason behind this is that it is fully understood that RM can co-exist with existing backup products a customer may use with their database, and so not affect the back-up chain of Full, Diff + Transactional backups, which in turn would affect the recovery process.

Yes, RM can truncate Exchange logs, but the backup and recovery models perscribed by Microsoft and how customers protect Exchange in that sense differ from databases.

A Database maintenance job in the context of the RM documentation relates to setting up a scheduled database maintenance job to perform Full, incremental/diff and transaction log backups (with truncation).

A note, SQL Server 2008 onwards will require a full and t-log backups in order to truncate the t-logs.  Previous versions of SQL Server 2000/2005 allowed for unadviseable actions like "backup log with truncation only".

Does this help?

James.

James,  This is what I guessed by looking around today so you have confirmed my thinking. As I'm using a third party product to backup the remote copy of the database then I don't really want to do a sql backup. Is there anyway you can send the backup to a nulll file like in Unix but still truncate the logs? Also on your 2008 point do you mean you have to backup both the database and logs wheras before you could just backup the logs? Sorry for the no line break but for some reason it won't let me type a return on here today.