IT systems · Practical guide

Archiving Empower projects and testing restoration

The Empower project backup succeeds and the archive contains the files. Restore a project and reconstruct an actual result to show that a later investigation remains possible. The data, methods, results and required history must remain usable together.

Table of contents

At a glance

How do you archive Empower projects for a GxP process?

Define the project scope and historical retrieval needs. Use a method supported for the installed Empower version and test backup, integrity, restoration and scientific context. Database and project backups serve different purposes. A success log or PDF result alone does not establish that all necessary data, methods and histories will remain usable.

Archive objective and retrieval requirements to be defined first

Determine which historical inquiry the archive must address. Should a reviewer be required to trace a chromatogram, the employed method, a change in result, or the full project context? These objectives require distinct information sets. A PDF export can document a report but does not automatically capture all dynamic data and interrelationships from a chromatography data system. The required scope is professionally justified.

Capture project, sub-projects, relevant data types, methods, results, user associations, and required history. Also review information outside the project scope, such as system-wide configurations or cross-cutting audit events. A project file must not be unverifiedly designated as a complete copy of all system information. Document the source, Empower version, configuration, and planned recovery environment. This transforms archiving into a controlled lifecycle process rather than a simple file transfer.

Sources: [1] [2]

Database backup and project backup are distinct.

Waters specifies database backups primarily for system restoration to the appropriate version. The referenced knowledge base indicates that for complete restoration, the associated raw data files are also required. Therefore, a database backup alone must not be considered a complete, version-independent archive without verification. The specific supported restoration pathway is confirmed against manufacturer documentation.

Project backups serve primarily for archiving and transferring projects to supported, newer Empower environments. This does not guarantee that any future version, environment, or configuration will automatically represent all required relationships in an identical manner. Verify the specific path and necessary prerequisites. Maintain disaster recovery, project archiving, and data migration as distinct objectives. A procedure may support multiple objectives, but must demonstrably meet the respective requirements of each.

Sources: [3]

Build a comprehensive technical reference package

Select representative project elements prior to backup and ensure the expected relationships are preserved. Include elements such as Sample Set, Injection, Channel, Instrument and Analysis Method, Result Status, and relevant change reference. Use the actual Empower system terminology and objects. The reference scope is determined by the required historical data, not by a generic list of screen views.

Add special considerations: reprocessing, modified method, multiple result states, nested projects, and required signature information. Define what must be visible and interpretable after restoration. An independent reference comparison prevents the acceptance of an empty or incomplete target dataset solely because the restore job completed without error messaging. Automated quantity reconciliations and subject-matter review cases complement each other.

Sources: [1] [2]

Example: re-evaluation of an injection batch

In the example, project P-17 includes injection I-8 with an initial evaluation method M1 and a subsequent controlled re-evaluation using method M2. Both result states and the required change justification must be traceable after restoration. The archiving concept specifies which history is retained within the project and which is additionally preserved externally. The action does not generate a new release solely through restoration.

A reviewer identifies I-8, opens the required chromatogram, and assigns both results to the correct method versions. They then evaluate the existing change reference against the pre-defined reference package. A reprocessed batch, performed after restoration, must not be silently treated as the original historical result. The following matrix serves as an internal audit aid and does not claim identical data coverage across all Empower backup functions.

Own work aid – Example: re-evaluation of an injection batch
Validation elementExpected findingAcceptance activity
Injection I-8 Correct source and affiliation Compare object and project context
Chromatogramme Required data are readable Check that the display conveys the intended result
Method M1/M2 Historically appropriate stands Traceability of results
Result versions Original and re-evaluation separately Verify historical sequence
Change reference Purpose and identity clearly understood Investigate required history
Permission Authorized access Routine reviewer and unauthorized role testing

Sources: [1] [2]

Backup version and protocols to be verified

Capture the scope of the project, storage location, timestamp, performing user, and relevant settings. Waters documents corresponding backup events in the System Audit Trail. This information can serve to document the execution. However, a success event does not replace the full completeness verification of the selected scope nor a restoration validation. Review errors, interruptions, and the handling of partial batches.

When multiple projects or hierarchies are archived, the actual inventory is verified individually. The name of a parent folder does not prove that all required subprojects are included. Review the generated structure and available logs. Integrity checks can detect file modifications, but they do not address all questions regarding functional suitability. Additionally, document how the final archived state is protected against future changes or misinterpretation.

Sources: [4] [1]

Verify restoration under realistic conditions

Plan an appropriate restoration environment with supporting software, required components, permissions, and storage locations. Performing a restore with administrator rights on an arbitrarily available machine cannot adequately support future routine access. Verify the licenses and technical requirements needed for the planned historical access. Availability and agreements will be separately confirmed, rather than assumed permanently.

Following technical restoration, a technical review is conducted. Open selected data and methods, investigate historical records, and compare them against the reference package. Additionally, assess damaged or incomplete archived data as well as unauthorized access incidents. Document the process by which errors were identified and resolved. A successful individual restore represents a validated case; generalization to other projects requires a justified evaluation of their specific differences.

Sources: [3] [1]

Separate migration and new processing of archive access.

When a project is opened in a different Empower status, assess the supported transition and potential impacts on display, calculation, and context. Historical access and reprocessing are not the same activity. A new evaluation may employ different settings or software logic. It must remain clearly traceable as a distinct action and shall not silently replace the original result state.

Upon decommissioning or cessation of a system, the long-term retrieval pathway becomes particularly critical. Determine whether native usage, an appropriate alternative procedure, or a combination is required. A PDF may suffice for certain assertions, while for others, dynamic data and relationships are necessary. Assess the required functionality, not the format in a general sense. A data storage medium in existence for years provides little value if no one can currently access and review the stored projects.

Sources: [1] [2]

Archive operation and closure responsibility to be transferred

The final report integrates scope, backup status, integrity checks, restore results, technical acceptance, and remaining limitations. Identify which information is stored separately and describe how the user can access it. If a required historical reference is missing, assess the impact and define an appropriate corrective action. Successful file backup alone does not constitute adequate evidence of such findings.

For operations, responsibilities, access, retention, recovery, and re-evaluation are defined. Changes to software, infrastructure, identities, or display programs may affect usability. Assess archival capability through a risk-based approach; no universal frequency is asserted. The key question remains practical: Can an authorized employee reliably trace the required historical data under the specified conditions?

Sources: [1]

Project experience and collaboration

Retrieve and read a known Empower project from the archive

With the laboratory, QA and IT, we define which historical question the Empower archive must answer. A project with known data, methods and analyses provides a reference. We plan the supported backup and restore procedure and compare the relationships after retrieval. Limited archival access may justify a narrow scope. Migration to a different version or reprocessing are separate purposes that need separate assessment. A successful backup log does not complete the test.

Frequent Questions on Empower Archiving and Recovery

Does an Empower database backup suffice as a project archive?

Not automatically. Database and project backups serve different purposes and have distinct requirements. Assess the required scope, including raw data files, supported versioning, and future retrieval needs. A database backup may be part of a broader strategy, but it alone does not guarantee long-term, version-independent usability of individual projects.

Sources: [3]

Does a project backup contain all system-wide audit information?

This must not be assumed generically. Define the specific and cross-project information required, and verify its actual coverage. External evidence required outside the project will be separately controlled stored and linked to historical investigations.

Must every archived project be restored on a test basis?

The scope is justified based on risk, project differences, and appropriate completeness controls. Representative restore cases may form part of a viable strategy. A general percentage without reference to underlying structure is largely inconclusive. Critical special cases and known defects must be specifically addressed.

Can a PDF replace the native Empower project?

For dynamic chromatographic data, a static PDF report alone is insufficient as the sole original data evidence. It does not support re-evaluation nor retain all method relationships and processing capabilities. The FDA explicitly outlines this limitation for CGMP laboratory records; PIC/S requires dynamic retention, where this is essential for data integrity or future audits. PDFs may complement results presentation. Review the archived format based on specific historical investigation and data analysis cases.

Sources: [2] [5]

Can one simply re-integrate after a restore?

A new processing step is a new action and must be appropriately controlled. It shall not appear as an unchanged historical result. Retain required original results, method versions, and change references. Assess separately the impact of the software version and the permissible use of new results.

When is archiving considered complete?

When the scope of the released batch has been verified for security, integrity, and required recoverability, and future operations have been transferred, any remaining limitations and separately stored information must be clearly documented. A green backup status is a technical evidentiary indicator only and does not constitute a complete professional conclusion.

Sources: [1]

Sources and review date

As of October 14, 2026. Regulatory classification and manufacturer responsibilities are separately documented. Examples, test matrices, and templates are standalone reference tools; they are customized for actual usage purposes.

  1. European Commission: EU GMP Annex 11, Computerised Systems (2011)Current version as per EudraLex inventory as of 14.10.2026. Application, risks, operation, and data lifecycle; specific testing proposals are derived independently.
  2. PIC/S: PI 041-1, Good Practices for Data Management and Integrity (2021)Inspection Guidance on Data Integrity; in particular electronic data, transmission, access, and review.
  3. Waters: Database backups versus project backups, WKB117704Version-bound database restoration; project backup serves primarily for archiving and transfer to newer versions. Verify the specific supported path. Checked on 14.10.2026.
  4. Waters: Backup information in the system audit trail, WKB7500Backup action, time, project, comment, and user. Success log does not replace a technical restoration review. Reviewed on 14.10.2026.
  5. FDA: Data Integrity and Compliance With Drug CGMP – Questions and Answers, December 2018Question 10 on the retention of dynamic chromatographic data on 18.10.2026. Scope: Pharmaceuticals under CGMP; no general objection to PDF as supplemental report.

Sources checked: .

Daniel Herrmann, Daniel Herrmann Consulting

Daniel Herrmann Consulting

How we can support you

Daniel Herrmann Consulting combines professional assessment with hands-on work on the specific system. During the first meeting, we clarify your intended use, existing documentation, and the next most appropriate action step.

  • GxP system decommissioning →

    Retire legacy systems while preserving data, context and auditability. We plan and manage the decommissioning so that data, metadata and audit trails remain readable and retrievable after shutdown.

Send a project enquiry Customer testimonials →