This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
admin:features:snapshots:portability [2012/04/03 14:53] doc |
admin:features:snapshots:portability [2016/06/28 22:38] (current) |
||
|---|---|---|---|
| Line 64: | Line 64: | ||
| Copying an Omnidex Snapshot is as simple as copying the files of the snapshot. The only precaution necessary is to make sure the files are not being accessed by any other processes. | Copying an Omnidex Snapshot is as simple as copying the files of the snapshot. The only precaution necessary is to make sure the files are not being accessed by any other processes. | ||
| + | |||
| + | Note that it is generally required that the target server use the same version of Omnidex as the source server. If the Omnidex versions are different, it is usually required to regenerate the Omnidex Environment File and regenerate the Omnidex Indexing. | ||
| + | |||
| + | === Relative Paths vs. Absolute Paths === | ||
| + | |||
| + | Omnidex Environment Files will reference directories and filenames. The CREATE DATABASE statement will declare the Index Directory. The CREATE TABLE statements will declare the physical filename(s) for the the table. These statements can contain either absolute or relative filenames. | ||
| + | |||
| + | An absolute filename is one where the path is fully declared, including drive or volume information, plus any directory or subdirectory information. A relative filename is on that is relative to the "current working directory". With Omnidex, the "current working directory" is the directory containing the Omnidex Environment File. | ||
| + | |||
| + | It is generally easier to move Omnidex Snapshots that use relative filenames. In this situation, you can copy the directory containing the Omnidex Environment File, plus all of its subdirectories. At the same time, performance or space requirements may make relative filenames impractical. Files may need to be moved to other volumes or drives in order to achieve good I/O performance or to obtain enough disk space. In these cases, [[appendix:reference:envvar:variables|environment variables]] can provide a similar flexibility. | ||
| + | |||
| + | |||
| + | |||
| ==== ==== | ==== ==== | ||