Recovery Manager: Difference between revisions

From OSNEXUS Online Documentation Site
Jump to navigation Jump to search
VisualWikitext
Create: dedicated Recovery Manager page, moved out of the Storage System page and expanded with the backup rotation, retention settings and cautions
 
m Re-fit screenshot widths to half the captured size (capped at 800px) so 2x captures display at their true on-screen size (wiki-docs rule 5)
 
(9 intermediate revisions by the same user not shown)
Line 1: Line 1:
[[Category:admin_guide]]
[[Category:admin_guide]]


The '''Recovery Manager''' restores the QuantaStor internal configuration
The '''Recovery Manager''' restores the QuantaStor internal configuration database ({{Code|1=osn.db}}) from a backup. Use it when a system has been re-installed and you need the previous configuration back -- Storage Volumes, Network Shares, Users, Hosts, Schedules and the other logical objects.
database from a backup. Use it when a system has been re-installed and you need
the previous configuration back -- Storage Volumes, Network Shares, Users,
Hosts, Schedules, Roles, and the other logical objects.


'''Navigation:''' Storage Management --> Storage Systems --> ''select a Storage System'' --> Recovery Manager ''(toolbar)''
{{Navigation|Storage Management → Storage Systems → ''select a Storage System'' → Recovery Manager ''(toolbar)''}}


It is also on the right-click context menu for a Storage System.
It is also on the right-click context menu for a Storage System.


[[File:ss_recovery_manager.png|thumb|center|800px|Recovery Manager, listing the configuration database backups discovered on the started Storage Pools.]]
[[File:ss_recovery_manager.png|thumb|right|637px|Recovery Manager, listing the configuration database backups discovered on the started Storage Pools.]]


'''Your data does not depend on this database.''' Storage Pools, and the volumes
'''Scope note:''' the Recovery Manager currently recovers the {{Code|1=osn.db}} configuration database only. A full configuration download and recovery workflow covers considerably more than this, and is planned for a future release. Treat this page as covering the database recovery step, not configuration recovery as a whole.
and shares within them, carry their own metadata and are recovered by importing
the pool -- not from this backup. The configuration database holds the logical
objects layered on top. That is why a pool imported into a freshly installed
system comes back with its volumes intact but without the hosts, schedules and
users that referenced them.


'''In a Storage Grid the Recovery Manager matters much less''', because the
'''Your data does not depend on this database.''' Storage Pools, and the volumes and shares within them, carry their own metadata and are recovered by importing the pool. The configuration database holds the logical objects layered on top, which is why a pool imported into a freshly installed system comes back with its volumes intact but without the hosts, schedules and users that referenced them.
configuration database is replicated across all grid nodes. A node rejoining a
 
grid picks the configuration up from its peers.
'''In a Storage Grid this matters much less''', because the configuration database is replicated across all grid nodes; a node rejoining a grid picks the configuration up from its peers.


== Using the Recovery Manager ==
== Using the Recovery Manager ==


# Select the '''Storage System''' to recover.
# Select the '''Storage System''' to recover.
# Choose a backup from the list. Each row shows the backup name, its file size, and when it was created.
# Choose a backup from the list. Each row shows its name, file size and creation time.
# Optionally tick '''Include network configuration recovery''' -- see the warning below before you do.
# Optionally tick '''Include network configuration recovery''' -- see the cautions below.
# Press '''OK'''.
# Press '''OK'''.


The list is built from the backups discovered on the '''started''' Storage
The list is built from backups found on the '''started''' Storage Pools, so if the backup you expect is missing, import and start the pool holding it first.
Pools. A pool that is not imported and started contributes nothing to the list,
so if the backup you expect is missing, import the pool that holds it first.
 
== How the backups are made ==
 
QuantaStor writes a copy of the configuration database to every Storage Pool on
a rotation, so the backups travel with the storage rather than living only on
the boot drive. Backups are named by their rotation slot:


* <code>osn.db.backup.hourly.1</code> through <code>osn.db.backup.hourly.N</code>
Backups are named by rotation slot -- {{Code|1=osn.db.backup.hourly.N}} and {{Code|1=osn.db.backup.daily.N}}. The count of each is set by {{Code|1=max_db_backups}} in {{Code|1=/opt/osnexus/quantastor/conf/quantastor.conf}} (default '''5'''; 0 disables pool backups). A backup failure raises a '''Configuration DB Backup Failure''' alert -- see [[Call-home / Alerting|Alert Manager]].
* <code>osn.db.backup.daily.1</code> through <code>osn.db.backup.daily.N</code>


<code>N</code> is controlled by <code>max_db_backups</code> in
== Cautions ==
<code>/opt/osnexus/quantastor/conf/quantastor.conf</code>, which defaults to
'''5''' of each. Values above 100 are capped at 100, and setting it to 0
disables the pool backups entirely. The local copy on the boot drive is written
to:


<pre>
'''Do not restore a backup taken from a different system.''' The database carries the system's unique ID, so this can leave two systems claiming the same UUID, which causes grid problems.
/var/opt/osnexus/quantastor/osn.db.backup
</pre>


...on a cadence set by <code>hours_per_backup</code> in the same file, which
'''Network configuration recovery can cut off your own session.''' If the restored network settings differ from the current ones, your connection drops when the address changes. Where ports may become unreachable, make the change from the console rather than the web interface.
defaults to '''12''' hours.


A failure to write a backup raises a '''Configuration DB Backup Failure''' alert,
'''The restore replaces the running configuration.''' If you are unsure which backup is correct, contact OSNEXUS support at support@osnexus.com before restoring rather than working through them by trial.
so a system that has quietly stopped producing backups is visible in the Alert
Manager rather than only discovered when a recovery is attempted. See
[[Call-home / Alerting|Alert Manager]].
 
Because the backup is an ordinary file, it can also be replicated off the
appliance with <code>rsync</code> or <code>sftp</code> from a cron job if you
want a copy outside the storage.
 
== Important cautions ==
 
'''Recovering a database from a different system creates a duplicate identity.'''
The database carries the system's unique ID. Restoring a backup taken from
another server can leave two systems claiming the same UUID, which causes
problems in a grid. Only restore a backup that came from the system you are
restoring onto, unless OSNEXUS support has advised otherwise.
 
'''Network configuration recovery can cut off your own session.''' Ticking
'''Include network configuration recovery''' restores the saved network
settings, and if those differ from the current ones your connection drops when
the address changes. Where all network ports may become unreachable, make the
change from the console instead of the web interface, so you retain access.
 
For context, a newly installed QuantaStor system defaults to DHCP on an
interface. If a DHCP server is present it takes an automatic address, giving you
initial access from which to assign static addresses.
 
'''Restoring is not reversible in place.''' The restored database replaces the
running configuration. If you are uncertain which backup is the right one,
contact support before restoring rather than working through them by trial.


== Restoring by hand ==
== Restoring by hand ==


The database is a SQLite file and can be replaced directly if the dialog is not
The database is a SQLite file and can be replaced directly if the dialog is not available -- for example on a system whose web interface will not start:
available -- for example on a system whose web interface will not start:


<pre>
<pre style="font-size: smaller">
systemctl stop quantastor
systemctl stop quantastor
cp &lt;backup-file&gt; /var/opt/osnexus/quantastor/osn.db
cp &lt;backup-file&gt; /var/opt/osnexus/quantastor/osn.db
systemctl start quantastor
systemctl start quantastor
</pre>
</pre>
== Getting help ==
Database recovery is one of the operations where it is worth asking first. If
you are unsure which backup to use, or a recovery has not produced what you
expected, contact OSNEXUS support at support@osnexus.com.


== Related pages ==
== Related pages ==


* [[Storage System]] -- system-level configuration and the Modify dialog
* [[Storage System]] -- system-level configuration and the Modify dialog
* [[Upgrade Manager]] -- includes a full re-install / boot drive swap procedure that uses the Recovery Manager
* [[Upgrade Manager]] -- includes a re-install / boot drive swap procedure that uses the Recovery Manager
* [[Call-home / Alerting|Alert Manager]] -- the Configuration DB Backup Failure alert
* [[Call-home / Alerting|Alert Manager]] -- the Configuration DB Backup Failure alert
----
<small>''Verified against QuantaStor 6.9.0.''</small>

Latest revision as of 01:24, 3 September 2026


The Recovery Manager restores the QuantaStor internal configuration database (osn.db) from a backup. Use it when a system has been re-installed and you need the previous configuration back -- Storage Volumes, Network Shares, Users, Hosts, Schedules and the other logical objects.

Navigation: Storage Management → Storage Systems → select a Storage System → Recovery Manager (toolbar)

It is also on the right-click context menu for a Storage System.

Recovery Manager, listing the configuration database backups discovered on the started Storage Pools.

Scope note: the Recovery Manager currently recovers the osn.db configuration database only. A full configuration download and recovery workflow covers considerably more than this, and is planned for a future release. Treat this page as covering the database recovery step, not configuration recovery as a whole.

Your data does not depend on this database. Storage Pools, and the volumes and shares within them, carry their own metadata and are recovered by importing the pool. The configuration database holds the logical objects layered on top, which is why a pool imported into a freshly installed system comes back with its volumes intact but without the hosts, schedules and users that referenced them.

In a Storage Grid this matters much less, because the configuration database is replicated across all grid nodes; a node rejoining a grid picks the configuration up from its peers.

Using the Recovery Manager

  1. Select the Storage System to recover.
  2. Choose a backup from the list. Each row shows its name, file size and creation time.
  3. Optionally tick Include network configuration recovery -- see the cautions below.
  4. Press OK.

The list is built from backups found on the started Storage Pools, so if the backup you expect is missing, import and start the pool holding it first.

Backups are named by rotation slot -- osn.db.backup.hourly.N and osn.db.backup.daily.N. The count of each is set by max_db_backups in /opt/osnexus/quantastor/conf/quantastor.conf (default 5; 0 disables pool backups). A backup failure raises a Configuration DB Backup Failure alert -- see Alert Manager.

Cautions

Do not restore a backup taken from a different system. The database carries the system's unique ID, so this can leave two systems claiming the same UUID, which causes grid problems.

Network configuration recovery can cut off your own session. If the restored network settings differ from the current ones, your connection drops when the address changes. Where ports may become unreachable, make the change from the console rather than the web interface.

The restore replaces the running configuration. If you are unsure which backup is correct, contact OSNEXUS support at support@osnexus.com before restoring rather than working through them by trial.

Restoring by hand

The database is a SQLite file and can be replaced directly if the dialog is not available -- for example on a system whose web interface will not start: 

systemctl stop quantastor
cp <backup-file> /var/opt/osnexus/quantastor/osn.db
systemctl start quantastor

Related pages

  • Storage System -- system-level configuration and the Modify dialog
  • Upgrade Manager -- includes a re-install / boot drive swap procedure that uses the Recovery Manager
  • Alert Manager -- the Configuration DB Backup Failure alert

Verified against QuantaStor 6.9.0.

Retrieved from "https://wiki.osnexus.com/index.php?title=Recovery_Manager&oldid=27459"