Whats wrong with this screenshot? I might be giving it away with backing up the Trans log… T (PS Can I not embed images?, sure I had done before)
Nice, how long has that database been left alone? Why don’t you do a regular full backup and then truncate the transaction log? It’s easier to backup 5GB than 27GB.
I’ve got generic plans for our customers (Full, diff, plus defrag index etc…), but this one had their own Sys Admin, guess hes not a SQL Guy, also found 3 jobs to full backup at 1pm 1.01pm and 1.02pm. Upgrading them from 3.7 to 5.0SP1, logged onto the server and raised my little red flag. 
Not enough space to backup the translog either, might need to do a “backup log Navision with truncate_only” 
That’s another reason why I suggested to do a full backup first, that way you don’t need the transaction log anymore, and truncating is not a problem.
Or just delete the Log file.
I recently met a client that had a 1.8gig DB and a 54gig log file. In that case I just killed to log file. They were told they don’ need to make backups becuase they have RAID 5.
There are two ways that I use. The one I mostly use is this:
http://wiki.dynamicsbook.com/index.php?title=Shrink_SQL_log_file
But if its for a test database or a local DB not live, then I just detach, delete the log and reattach. Then just create a new log the size you want.
Did a full Bkup Bkup Log