DB Maint.: Copying the Production Database to Test

DANGER! You can corrupt your live database if you do not stop the InterBase Server before copying. Please follow this procedure closely.

(Related article: Moving, Copying, or Renaming a Database)

The safest way to test the effect of changes on current data is to copy current data into the test environment. Here's how:

Process
The following procedure applies to Bundle-Track versions 3.6 and above. Perform the following steps:

1. Instruct all Bundle-Track users to exit Bundle-Track and inform all users that the database will be down momentarily.
2. Stop the InterBase Server.
3. Copy the Production database file and paste it into the same directory.
4. Note the name of the Test database file, and then delete the Test database file.
5. Rename the newly pasted file to replace the deleted Test Database file.
6. Start the InterBase Server.
7. Tell the Bundle-Track users that they can come back in.

Now, when you log into Bundle-Track, if you select Test database at the login panel, you'll be working with a very recent copy of live data, but your changes will have no effect on the actual live data.

We welcome your comments at support@bundle-track.com.

If you would like our live assistance, you may hire us at our professional services rate.