Skip to content
Nuca Systems

Archive Server managed service

Archive Server managed service for production archives

Five diamond glass plates stacked on a vertical axis in blue and purple

An OpenText archive is easy to ignore until the day a restore, a legal hold or an SAP document retrieval proves it was never as healthy as the green lights suggested. Archive Server and Archive Center sit under retention, storage cost and audit pressure at the same time.

Nuca supports OpenText estates across the UK, Ireland, DACH and the wider EU. We run production Archive Server and Archive Center estates as part of a specialist OpenText managed service. Monitoring, patching, incident response, capacity and performance under real archive workloads, and careful attention to the joins into Content Server and SAP ArchiveLink where those exist. The database and the content store are treated as one recovery story, not two teams' separate assumptions. Platform, business and database administration sit under one coordinated support model alongside the rest of the OpenText stack, for a fixed monthly fee scoped to your estate.

We do not sell new archiving programmes or large decommissioning projects. We keep the archive you already depend on stable, documented and restorable.

If a second pair of eyes would help, book a free 45-minute continuity check call.

Why archive estates fail quietly until a restore or audit

Archive estates often look calm. Jobs report success. Dashboards stay green. The first hard proof that something was wrong can be a restore, a legal hold or an audit retrieval that fails when it matters. Quiet failure is the pattern: capacity pressure that nobody trends, documentation that drifted, or a content store and database that no longer tell the same story.

Day to day run for a production archive means treating restore readiness as a standing concern, not a project you schedule after an incident. For practical depth on quiet job failure, see OpenText archiving stopped: finding the fault.

What we run day to day on Archive Server and Archive Center

We run live Archive Server and Archive Center estates already in production. Day to day that means monitoring around the clock, patching on a controlled cadence, incident ownership, and attention to capacity and performance under real archive workloads. Where the estate joins Content Server or SAP ArchiveLink, those joins sit in the same operational picture.

We administer the archive you have, whichever name your team uses for it, and keep the day to day run coherent with the rest of the OpenText stack you already depend on.

Consistency between database, content store and linked applications

An archive is only healthy when the database, the content store and the linked applications agree. A backup job that reported success is not the same as a restore you have proven. A content object that exists in one place but not the other is a recovery problem waiting for an audit or a legal hold.

We treat the database and the content store as one recovery story. Linked applications, including Content Server and SAP paths where they exist, stay in the same diagnostic surface. See OpenText ECM database administration for how we think about the data layer under OpenText workloads.

Stacked circular database layers in brushed metal and glowing glass

Backups you have restored, not only jobs that reported success

Backup verification means restores you have actually run, on a cadence you can defend, with documentation that matches the live estate. A green job status is useful. It is not proof. Restore tests, recovery readiness and clear ownership of the database and content store together are what turn a quiet archive into a restorable one.

We keep restore readiness inside the managed service, alongside monitoring, patching and incident ownership. Use the 15 estate self-checks if you want a structured self-review of recovery risk before you talk to anyone.

A glass estate tile with connected squares inside

Boundaries: we run live archives; we do not rebuild archiving programmes

On this page, we mean running production archives that already exist. We do not sell new archiving programmes, large decommissioning projects or greenfield archive design. Those stay with the people built for them, including OpenText Professional Services and systems integrators where that is the right fit. On-premise and private cloud only.

If the archive is already live and short of senior OpenText capacity, that is the work we take: monitoring, patching, incident ownership, restore readiness, and the joins into Content Server and SAP ArchiveLink where they exist. The managed service is a fixed monthly fee scoped to your estate. We keep the archive you already depend on stable, documented and restorable.

How this combines with Content Server and xECM cover

Archive Server and Archive Center estates rarely sit alone. Many production pictures also include Content Server and Extended ECM or xECM connectors. Nuca can cover those under the same coordinated support model, so an incident that crosses archive, content platform and database is diagnosed once rather than bounced between separate queues.

That matters when ArchiveLink retrieval, Content Server access and connector behaviour all touch the same records. One accountable team keeps the operational run coherent across the stack you already have. See Content Server managed services and Extended ECM and xECM support. For the full tier model, see OpenText managed services.

Use the self-check list, then book a free 45-minute continuity check call if restore readiness is unclear

If restore readiness is unclear, start with the 15 estate self-checks. They are a free self-check resource, not a Nuca review, and you can run them without sending logs to anyone. Use them to pressure-test whether backups have been restored, whether documentation matches the live estate, and whether one person still holds all the archive knowledge.

If you want a conversation next, book a free 45-minute continuity check call. No system access and no log upload. We help you see options for a production Archive Server and Archive Center estate: standing managed service, interim cover, or a clearer restore-readiness plan with the specialists you already have. For quiet job failures while you prepare, OpenText archiving stopped: finding the fault is a practical companion read.

Printed first page of the 15 estate self-checks workbook, shown as a physical booklet with checklist pages and tick boxes visible behind

How we support Archive Server and Archive Center

TierWhat it covers on a production archive estateResponse
Tier 1 PlatformArchive platform and database kept production-stable. Monitoring and alerting around the clock.Critical-incident response in core hours.
Tier 2 Platform + BusinessEverything in Tier 1, plus the business-administration layer.Critical-incident response 24×7×365. Monitoring around the clock.
Tier 3 Full LifecycleEverything in Tier 2, plus full lifecycle: upgrades, migrations and a named Technical Account Manager.Critical-incident response 24×7×365. Monitoring around the clock.

Monitoring runs around the clock whichever tier you choose. Tier 1 Platform is enough when business administration is already covered. Interim Cover covers a temporary administrator gap: three-month minimum, then rolling monthly. The managed service uses a fixed monthly fee scoped to your estate. See OpenText managed services.

How this sits next to OpenText vendor support and Current Maintenance

OpenText stays the product vendor. Vendor support and Current Maintenance stay on that path. Nuca's work is the live archive: monitoring, incidents, capacity under real archive workloads, and the database and content store treated as one recovery story, including ArchiveLink joins where they exist.

While an archive release approaches the end of its Current Maintenance period, restore readiness and day to day run still need an owner. Use OpenText's published lifecycle materials for the dates that apply to your release; they are not restated here. OpenText support for legacy versions is a useful companion read.

If you want the findings in writing after the call, the Estate Continuity Review is the paid next step: two weeks on your live Archive Server estate, five senior days, review only, fixed price agreed in advance and credited against the work that follows. Start with the free 45-minute continuity check call (no system access, no log upload) via book a free 45-minute continuity check call.

Further reading: OpenText archiving stopped: finding the fault, OpenText ECM database administration, OpenText support for legacy versions.

FAQ

If a second pair of eyes would help, book a free 45-minute continuity check call.

No system access and no log upload. For a self-review first, use the 15 estate self-checks. No other meeting ask.

End of section