Create Backup Is Unavailable
Symptom: Create Backup on the Backup and Restore card in Dermi Atlas Manager cannot be selected.
- "Docker Unavailable": Docker is not running. Start it as described in Troubleshooting Docker and System Requirements.
- "Busy": Another operation is running, and a chip names it. Wait until it finishes.
Backup Fails
Symptom: The Backup and Restore card reads "Could not back up Atlas", with a message below it. Atlas runs as it did before the backup unless the message states otherwise.
- "Not enough free space for the backup: X needed, Y available." Free at least the difference on the drive that holds the Atlas Manager data, then create the backup again.
- "Atlas services could not be paused for the backup:" followed by a reason. Check the Container Status card on the Atlas Status page, select Restart in the Atlas Control card if a row reports an error, and create the backup again.
- "The backup has been created, but Atlas services could not be resumed:" followed by a reason. The backup is complete. Select Start in the Atlas Control card.
- "The backup could not be verified:" followed by a reason. Create the backup again. If the message returns, send diagnostics to Dermi support.
- "The backup could not be completed: the image storage holds images that cannot be copied." This occurs on Windows computers where long file paths are turned off. Send diagnostics to Dermi support.
- "The last update did not finish. Run the update again before creating a backup." See Troubleshooting System Update Issues.
- "The last restore did not finish, so Atlas holds incomplete data. Restore a backup before creating a new one." See An Unfinished Restore below.
Restore Is Unavailable or Refused
Symptom: Restore cannot be selected on a backup row, or a restore stops before it changes anything.
- Restore cannot be selected: Backups made with another Atlas version are restored during installation, and the list notes "Restore is available for backups made with Atlas" followed by the installed version. Rows labeled Full Archive have no Restore button and are also restored during installation. Backing Up and Restoring Dermi Atlas Professional describes that path.
- "Not enough free space for the restore: X needed, Y available." Shown when a Full Archive backup is restored during installation. Free at least the difference, then restore again. Nothing was changed.
- "The Docker disk has" or "The drive that holds the Docker data has" followed by the space needed and a remedy. Apply the remedy, then restore again. Nothing was changed.
- "The last update did not finish. Run the update again." See Troubleshooting System Update Issues.
Restore Fails or Is Cancelled
Symptom: The Backup and Restore card reads "Could not restore Atlas" or "Restore cancelled".
- "The restore was cancelled." Atlas keeps its data and runs as before. Cancel is available only until the restore starts replacing data.
- A message ending with "Atlas services were left stopped." The restore had started replacing data, and Atlas holds incomplete data. Follow An Unfinished Restore below.
- Any other message. Atlas runs with its data as before. Address the reason the message names and restore again, or send diagnostics to Dermi support.
An Unfinished Restore
Symptom: The Atlas Status page shows "The last restore did not finish, so Atlas holds incomplete data." Start is refused with "The last restore did not finish, so Atlas holds incomplete data. Restore a backup first.", and creating a backup and updating are refused with messages that begin the same way.
Solution: Select Restore Backup on that notice, which opens Backup Management, and restore the backup whose restore did not finish, or another backup from the list. Atlas starts once the restore completes. If no backup made with the installed Atlas version is listed, contact Dermi support before uninstalling.
Service Recovery at Launch
Symptom: After Atlas Manager was closed, or the computer restarted, during a backup or restore, a Service Recovery chip appears at the next launch, and other operations wait.
Solution: Atlas Manager is resuming the Atlas services the interrupted operation left paused. It first waits for Docker, so start Docker if it is not running. When the chip disappears, Atlas runs as before. If the interrupted operation was a restore that had started replacing data, the Atlas Status page shows the unfinished restore notice instead; follow An Unfinished Restore above.
Related Articles
- Backing Up and Restoring Dermi Atlas Professional for creating, exporting, and restoring backups
- Troubleshooting Dermi Atlas for sending diagnostics to Dermi support