Progressive migration to the next generation backup platform
As part of the ongoing evolution of RG System Suite, we are upgrading the technology used by the Backup Files & Data module.
This evolution concerns the technological component responsible for file backups. Historically, this service relied on Dell Avamar technology. It will now be based on a new architecture built around the Restic backup engine, integrated and orchestrated by RG System Suite.
This transition has been designed to be progressive, secure and transparent, ensuring uninterrupted protection of your customers' data.
Why this change?
The backup market has evolved significantly over the past few years. To continue improving our offering, we are strengthening our technological independence and innovation capabilities by relying on a more modern and flexible architecture.
This evolution will enable us to:
- Strengthen our technological autonomy.
- Accelerate product innovation.
- Improve backup and restore performance.
- Benefit from greater data resilience.
- Prepare new backup scenarios for the years ahead.
- Gradually extend functional coverage to new environments.
As with all RG System Suite components, our added value goes beyond the underlying technology. We handle its integration, orchestration, hosting, monitoring and continuous improvement to deliver a reliable solution tailored to MSP needs.
Which environments are affected?
In this first phase, the transition applies to:
- Windows file backups managed through the Backup Files & Data module.
The following backup types continue to use the existing technology:
- Linux
- SQL
- Bare Metal
Specific communications will be issued if these environments are included in future migration phases.
How will the transition take place?
To guarantee complete data preservation and compliance with existing retention policies, the migration will be carried out in several stages.
Step 1: Deployment of the new backup engine
Starting on June 15, 2026, a second backup engine will be activated for eligible backups.
This new engine will operate alongside the current infrastructure.
At this stage:
- Dell Avamar backups continue to operate normally.
- New backups are also performed using the new technology.
- Restores remain available.
- No existing backup history is removed.
Step 2: Coexistence period
During this phase, two backup histories coexist:
- The Dell Avamar backup history.
- The new backup history built by Restic.
This period is essential to allow the new platform to gradually rebuild its own backup history while preserving all previously protected data.
Step 3: Migration completion
The historical Dell Avamar backups will only be removed once:
- The new backup platform has accumulated sufficient history.
- The configured retention period has been fully rebuilt.
- Consistency checks have been successfully validated.
No historical data will be removed until all these conditions are met.
Compatibility with EDR and antivirus solutions
The new backup generation is deployed through a proprietary component called RGStick.
To facilitate integration within secure environments:
- The component is digitally signed by Septeo IT Solutions.
- It is distributed directly through the RG System Suite ecosystem.
- Its identity is distinct from the underlying open-source engine.
In most environments, no specific action is required.
Should any specific recommendations be identified for a particular EDR or antivirus vendor, dedicated documentation will be provided.
Backup policy synchronization during the transition
To ensure a smooth migration without loss of history, the transition between Dell Avamar and the new Backup Files & Data 2.0 platform relies on a controlled synchronization mechanism.
When the new technology is activated, an initial migration is performed to create an equivalent configuration in Backup Files & Data 2.0 based on the existing Dell Avamar setup. This establishes a consistent baseline for all affected backups.
Throughout the coexistence period, Dell Avamar remains the authoritative source for backup policies.
In practical terms, any changes made in Dell Avamar are automatically replicated to their equivalent Backup Files & Data 2.0 policies, including:
- Protected items.
- Configured exclusions.
- Backup schedules.
- Retention settings.
- Policy modifications or deletions.
This one-way synchronization ensures that the new technology gradually builds a backup history fully aligned with the production configuration.
Conversely, modifications made directly within Backup Files & Data 2.0 on migrated backup policies are not replicated back to Dell Avamar.
The new Backup Files & Data generation will become the reference platform once all backups for a customer have been migrated and all retention requirements have been fully satisfied.
At that point:
- Dell Avamar will be permanently retired for that customer.
- Backup policies will be managed directly in Backup Files & Data 2.0.
- The new platform will become the sole source for backup configuration and execution.
FAQ
1. Impact on existing backups
No existing backups are removed when the transition begins.
Historical backups remain accessible throughout the coexistence period.
The objective is to ensure that data remains recoverable at all times.
2. Impact on retention policies
Existing retention policies remain unchanged.
The coexistence period depends directly on the retention period configured for each backup.
3. Do I need to take any action?
No. The transition is entirely managed by the RG System teams.
No reinstallation, reconfiguration or manual migration is required.
Your backup policies continue to operate normally.
4. Will I be billed twice?
No. The coexistence period between the two technologies is fully covered by RG System.
No double billing will be applied during the transition.
5. Impact on restores
Restores remain available throughout the migration period.
Depending on the timeframe involved, data may be restored from either the Dell Avamar history or the new backup history.
The objective remains unchanged: ensuring data availability and recoverability.
6. Does this change affect the way Backup Files & Data operates?
No. The backup, monitoring and restore principles remain unchanged.
7. Do I need to update my internal procedures?
No. Existing procedures remain valid.
8. Why choose an open-source technology?
Using a recognized open-source technology strengthens our technological independence, innovation capacity and long-term control while relying on a proven and sustainable foundation.
9. When will Dell Avamar be permanently retired?
Retirement will occur progressively, only once retention and service continuity requirements have been fully met for each affected backup.