I've seen and read a lot of questions about the transaction log and I know that backing it up to nul is usually frowned upon, however my understanding is that this is from a data recovery perspective. As there is a lot of transient data passing through this system the logs are changed quite rapidly and can grow quite large. In order to save disk space I do not want to keep data that has no intrinsic value.
The Setup We have two SQL servers running SQL Server Mirroring, these are important from a usage (up-time) perspective but the data is transient and for the most part unimportant.
What I Do In order to manage the transaction log size I run a log backup every 15 minutes to backup the log file to NUL as below.
BACKUP LOG [DatabaseName] TO DISK = 'NUL:';
So my question is thus: Other than not being able to recover data are there any other potential issues that could occur by backing up to NUL in a mirrored environment?