Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

When setting up log shipping for an active/passive environment, I always try to keep the files neat, by dumping the log backups into their own folders:


etc. However a database server I came to manage today has five database log shipping files all dumped into C:\TransLogs\.

Not all databases are shipping to the same secondary instances

Apart from being a mess, is there any advantage into splitting them into their own folders? Should I spend my time cleaning it up, or is it safe to leave it be?

share|improve this question
up vote 1 down vote accepted

I've been doing log shipping for years now, and I haven't bothered to break them up into their own folders. On one server I have 35 databases, all log shipping and all going to a single logship location. No problems.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.