Restoring a Database Using OS Commands when the Log File Is Not in the Default Location

If You Used the Built-In Backup Command:

When you back up a database whose log file is not in the default location, Derby puts the log file in the default location. When you restore the database from this backup copy, you must move the log file if you want to put it in a non-default location. Follow the instructions in "Logging on a Separate Device" for moving a log file.

If You Used Operating System Commands:

After you restore the database, you must move the log file to the original location. If the database log is not in the default location, or if a logDevice entry is specified in the service.properties file that specifies the location to which the database is being restored, ensure that the logDevice entry and the new log location correspond. Copy the database to the new location and connect to the database.

To correspond the logDevice entry to the log file location, use one of the following methods:

• Move the log to the location that is indicated by the logDevice entry.
• Change the logDevice entry in the service.properties file to correspond to the log location.
• Change both the new log location and the logDevice entry to represent the same location.
• Move the log to the default location and delete the logDevice entry in the service.properties file.