If your drive is full and you need to get rid of transaction logs, and for some reason you can't run a full backup... the next best choice is to turn on circular logging so that it would safely eat the unnecessary logs. Then turn off circular logging and do a full backup ASAP. Moving transaction logs somewhere else is NUTS!
Sincerely, Andrey Fyodorov Systems Engineer Messaging and Collaboration Spherion -----Original Message----- From: Chris Megginson [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 16, 2003 9:27 AM To: Exchange Discussions Subject: RE: Manually relocate transaction log files I may have not been clear enough. If your server does not have room to hold all of its transaction log files (on any partition) and if you can not back it up, and you want to avoid filling up the partition containing the log files, you can stop the services, move the (no longer needed) log files elsewhere and restart the services. (I've done it without any problem many times in the lab and a few times in a production environment.) You later run the backup when it's available. Keep all the log files, though, as you may need them if you have a crash. No one said do this carelessly. Do this if you have no alternative. _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&text_mode=&; lang=english To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&text_mode=&lang=english To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED]
