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:49] doc |
admin:features:snapshots:portability [2016/06/28 22:38] (current) |
||
|---|---|---|---|
| Line 16: | Line 16: | ||
| Omnidex Snapshots are extremely easy to move around as they are simply a collection of files. They can be backed up, moved to other servers, or if allowed, transferred to an analyst's laptop. | Omnidex Snapshots are extremely easy to move around as they are simply a collection of files. They can be backed up, moved to other servers, or if allowed, transferred to an analyst's laptop. | ||
| + | |||
| + | === The Files in an Omnidex Snapshot === | ||
| There are three groups of files associated with an Omnidex Snapshot: | There are three groups of files associated with an Omnidex Snapshot: | ||
| - | * **Metadata Files** - The Omnidex Environment File contains all the metadata describing the Omnidex Snapshot. | + | == Metadata Files == |
| + | |||
| + | The Omnidex Environment File contains all the metadata describing the Omnidex Snapshot. | ||
| + | <code> | ||
| ./simple.xml | ./simple.xml | ||
| + | </code> | ||
| - | * **Data Files** - The data files often reside in a single directory, but can be spread to different locations as determined by the Omnidex Administrator. | + | == Data Files == |
| + | The data files often reside in a single directory, but can be spread to different locations as determined by the Omnidex Administrator. | ||
| + | |||
| + | <code> | ||
| ./dat/cnt.dat | ./dat/cnt.dat | ||
| ./dat/gdr.dat | ./dat/gdr.dat | ||
| Line 30: | Line 39: | ||
| ./dat/individuals.dat | ./dat/individuals.dat | ||
| ./dat/sta.dat | ./dat/sta.dat | ||
| + | </code> | ||
| + | == Index Files == | ||
| - | * **Index Files** - The index files are located in a single directory as declared in the Omnidex Environment File | + | The index files are located in a single directory as declared in the Omnidex Environment File |
| + | <code> | ||
| ./idx/SIMPLE0000 | ./idx/SIMPLE0000 | ||
| ./idx/SIMPLE0001 | ./idx/SIMPLE0001 | ||
| Line 47: | Line 59: | ||
| ./idx/SIMPLE0011 | ./idx/SIMPLE0011 | ||
| ./idx/SIMPLESTATS | ./idx/SIMPLESTATS | ||
| + | </code> | ||
| - | The example below shows the files for a small Omnidex Snapshot: | + | === Copying an Omnidex Snapshot === |
| - | ./simple.xml | + | 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. | ||
| - | ./dat/cnt.dat | ||
| - | ./dat/gdr.dat | ||
| - | ./dat/households.dat | ||
| - | ./dat/individuals.dat | ||
| - | ./dat/sta.dat | ||
| - | ./idx/SIMPLE0000 | ||
| - | ./idx/SIMPLE0001 | ||
| - | ./idx/SIMPLE0002 | ||
| - | ./idx/SIMPLE0003 | ||
| - | ./idx/SIMPLE0004 | ||
| - | ./idx/SIMPLE0005 | ||
| - | ./idx/SIMPLE0006 | ||
| - | ./idx/SIMPLE0007 | ||
| - | ./idx/SIMPLE0008 | ||
| - | ./idx/SIMPLE0009 | ||
| - | ./idx/SIMPLE0010 | ||
| - | ./idx/SIMPLE0011 | ||
| - | ./idx/SIMPLESTATS | ||