Who is this article for?

Administrators in charge of file shares or databases.

 No special access or permissions are required.

Ideagen Quality Control Pluri stores every part record, inspection report, and FAI you create in a repository that your organisation owns and manages.

This article explains how to identify your repository type and recommended backup practices.

Understanding what Ideagen Quality Control Pluri manages

Ideagen Quality Control Pluri manages the data inside your repository: it creates, organises, and version-controls parts, reports, and FAI records as you and your team work. It does not back up that repository automatically. There is no built-in process that copies your repository data to a second location, and Ideagen does not hold a separate copy of it on your behalf.

Important: Do not confuse this with Site Configuration's Backup and Restore option. That feature only saves your configuration and report style settings. It does not back up your parts, drawings, attachments, or FAI records. It is not a substitute for backing up the repository itself.

Identifying your repository type

Ideagen Quality Control Pluri repositories are deployed on infrastructure your IT team controls, as one of two types. Confirm which one you are running (Setup → Options, or ask your IT administrator) and make sure it is covered by an existing backup routine:

If your team also relies on the LSRF (Licence and Shared Resources Folder) — the shared location for balloon styles, PFD/FMEA libraries, and shared report style configuration — include that in your backup routine too. It is a separate location from the repository and just as easy to overlook.

Understanding why backups matter

File corruption in a repository is rare, but it happens — a crash or network interruption during a save, a hardware fault, or an interrupted file transfer can leave a part record unreadable. Ideagen Quality Control Pluri does not keep a hidden second copy it can recover from: once a file is corrupted or lost, the only way back is restoring it from a backup your IT team took.

The same is true for deletion. Deleting a part moves it to the repository's Trash, and deleting it from the Trash is permanent — there is no further recovery inside the application. As Ideagen's own field guidance puts it: if there is no backup taken, it is gone.

Following recommended backup practices

• Back up on a schedule that matches your usage. Daily backups are typical for repositories in active production use; adjust the interval to how much data your team can afford to lose
• Back up the whole repository, not just recent changes. For fileshare repositories, that means the entire shared folder tree; for SQL repositories, a full backup plus your regular differential/log backups
• Keep backups on separate storage from the live repository. A backup on the same disk or server will not survive the hardware failure it is meant to protect against
• Test your restores periodically. A backup you have never restored is a guess, not a plan
• Include the LSRF in your backup scope. It holds shared configuration your team would otherwise have to rebuild by hand
• Document your repository and LSRF paths. Your IT team should be able to locate both immediately if a restore is ever needed

Note: Ideagen Quality Control Pluri manages the data in your repository. It does not manage backups of that data. A regular, tested backup and restore plan for your repository — fileshare or SQL — is your organisation's responsibility.

Getting help

If you are not sure which repository type you are running, or where your repository and LSRF are located, contact Ideagen through the Luminate support portal and we can help you confirm your configuration. 

Ideagen Support does not perform backups on your behalf — that remains your IT team's responsibility.