Date: Thu, 28 Mar 2024 16:07:13 -0700 (PDT) Message-ID: <1165509800.35.1711667233632@DESKTOP-IQF616V> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_34_542610715.1711667233631" ------=_Part_34_542610715.1711667233631 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
This page is for self-hosted users only and you should also reference&nb= sp;Self Hosted.
When this page is migrated and updated it should be merged into the Self Hosted page instead of being its= own page.
An archive is a complete copy of your Alexandria database, which can be = used as a restore point in the event that your data is lost or damaged. It'= s a quick and automatic way of saving your database before making any large= changes, such as performing an import, utility, update, or upgrading= your machine.
The major difference between a backup and an archive is that a bac= kup is made from the archive data and placed on removable media that can be= physically stored away from the library.
There are two types of archives:
See also: Database Archive<= /a> utility and My dat= a!=E2=80=94All about archives
An archive is not= em> a backup, but it can be used as= a backup once you've copied it to a secure, offsite location. This = way, if the computer running Alexandria is damaged or otherwise inaccessibl= e, the data you saved offsite will still be available to you. Read Back Up Your Data for more informa= tion.
Archives are configured in your Administration > Database Settings or = Controller Database Settings.
If you're Cloud-Hosted, you won't have access to these settings because = your hosting subscription includes automatic nightly archives and regular d= atabase maintenance.
By default, archives are stored in folder within the Al= exandria Support folder. However, we highly recommend that you change t= he location to a one outside of the Alexandria Support folder, preferably o= n a separate drive. You can set a custom location for your Archive Director= y in Administration > Database. If you enter an in= valid folder, or if it becomes invalid for any reason (such as disconnectin= g the drive it's on), it will automatically be replaced with the default fo= lder.
We control the folder structure within your Archive Directory. Within th= e Archive folder is a subfolder for each of your database serial numbers, i= n which individual archives are stored. Archives are titled by the date and= time in the YYYYMMDD HHMMSS format. Daily archives include "DAILY" in the = title; Snapshot archives do not.
Archives > Serial Number > Archive YYYYMMDD HHMMSS
Archives > 8888001 > Archive 20180720 110704 DAILY
Here, you can choose how many Daily Archives and Snapshot Archives to st= ore at a time, up to 14 of each. Just make sure you have enough free space = for them all! If you begin to run out of space, or if you're already storin= g more than the number you specified, the oldest archive of the type being = run will be removed.
We strongly advise you to review your Database Setting= s to ensure that your archive directory is up to date and the number of= archives stored is properly configured based on your needs and available d= isk space.
Before archiving your data, here are a few things you should know:
If you run into an error, check the log in Operations Management to see = what happened.
If there is a problem during a Daily Archive, the server will quit. = You can restart Alexandria as long as you have more than 40GB of free space= available. However, make sure you solve the underlying problem as soon as = possible; continuing to use Alexandria without doing so may make things wor= se and result in lost data.
A Restore will replace your current data folder with data from an archiv= e. It basically takes you back in time to the point when the archive you're= restoring was created. You will lose all of your current reports, utilitie= s, etc., so make sure this is what you want to do. A Snapshot Archive will = be performed prior to initiating the restore, just in case anything goes wr= ong. But if there isn't enough free space to perform the archive, neither t= he archive nor the restore will be performed.
Remember, your database will be inaccessible while the restore is being = processed.
To restore an archive: