Advice for changing the ESENT logs path

[Jahmai Lay]

We're moving ESENT logs to another drive.

Is there any caveats to doing this to an existing system?

Assuming all databases are shut down cleanly, can we just copy the logs files to a new path?

Or can we just point it to a new path and let it create new log files?

Or is it going to fail catastrophically and we're better to smuggler export/import all data?

Thanks.

[Oren Eini (Ayende Rahien)]

Please test on a scratch server first

We store the full path there, but it is supposed to work, I think

--
You received this message because you are subscribed to the Google Groups "ravendb" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ravendb+u...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Jahmai Lay]

Just a quick note to say that moving the files works OK.

If the files are not present (like you missed copying one of the db's) the db is marked as corrupt and good luck trying to restore it without those files.

On Friday, May 24, 2013 6:42:35 PM UTC+10, Oren Eini wrote:

Please test on a scratch server first

We store the full path there, but it is supposed to work, I think

On Friday, May 24, 2013, Jahmai Lay wrote:

We're moving ESENT logs to another drive.

Is there any caveats to doing this to an existing system?

Assuming all databases are shut down cleanly, can we just copy the logs files to a new path?

Or can we just point it to a new path and let it create new log files?

Or is it going to fail catastrophically and we're better to smuggler export/import all data?

Thanks.

--
You received this message because you are subscribed to the Google Groups "ravendb" group.

To unsubscribe from this group and stop receiving emails from it, send an email to ravendb+unsubscribe@googlegroups.com.