|
(Appended info on import/export)
|
(→Fidelity/Integrity)
|
| Line 162: | |||
| A lot of customers mistakenly use the import/export option of anthillpro to make "full backups" of their projects, library jobs, etc. While this may seem like a good idea, the fidelity & integrity of projects most likely will become compromised. Therefore it is recommended to do a database backup/clone if trying to copy projects to a new server. Exporting and importing projects is not meant for moving projects around from one server to another. It was included in AnthillPro primarily for debugging off of the production server, mainly for our needs in checking out customer project configurations etc. | A lot of customers mistakenly use the import/export option of anthillpro to make "full backups" of their projects, library jobs, etc. While this may seem like a good idea, the fidelity & integrity of projects most likely will become compromised. Therefore it is recommended to do a database backup/clone if trying to copy projects to a new server. Exporting and importing projects is not meant for moving projects around from one server to another. It was included in AnthillPro primarily for debugging off of the production server, mainly for our needs in checking out customer project configurations etc. | ||
| - | = Fidelity/Integrity = | + | == Fidelity/Integrity == |
| Examples of losses in fidelity and corruption in integrity include ('''''but are not limited to'''''): | Examples of losses in fidelity and corruption in integrity include ('''''but are not limited to'''''): | ||
