Northern Commander

Backups

A backup is one zip file holding everything the application keeps that you would miss: your settings, favorites, commands and keys, histories, saved searches and where you left off. Take one before trying something, keep them in iCloud Drive or on another disk, and put one back when you need to.

A backup you took yourself is listed by its note; the others, by what they hold.

Backups… is in the Options menu, and is a button on the settings screen.

The list

The backups in the backups folder, newest first, each with:

  • when it was made;
  • why — manual, scheduled, or before restore for the copy a restore takes first;
  • its note, or where it has none, what it holds.

The folder is under the list. It is read each time the screen opens, so a backup copied in from another Mac is listed, and one deleted in Finder is gone.

Back up now…
Takes one, asking what it should hold — below.
Restore…
Puts the chosen one back, once it has said what that would change. Enter on a backup does the same.
Delete
Deletes the chosen one, asking first: what it holds is not anywhere else.

What was done — Backed up to …, Deleted … — is said in a notice over the panes.

Taking one

What you leave unticked is left out of the next backup too, until you tick it again.
What to back up
The parts there are to copy, ticked as they were for the last backup. Space ticks and unticks; Back up waits until one is ticked. A part with nothing to copy yet is not offered.
File name
Starts on the name it would get anyway — the application, then when — so a folder of them sorts in the order they were taken. What you type is used in small letters, with - for anything but letters and digits; a name already there gets -2.
Note
Why you took it. The list shows it in place of what the backup holds, and so does the restore screen — it is what you will be looking for later.

The parts:

Part What it is
Settings Everything in the settings file
Favorites Your favorite folders, in their order
User menu The commands you wrote, in the user menu
Key bindings The keys you changed
Recent entries What you typed into fields that remember, and how the last archive was made
Histories Where each pane has been, and the commands the command line ran
Saved searches The searches you kept
Pinned in menus What you pinned to the top of a menu, and the places you gave a key
Where you left off Each pane’s place, order and view, and the window’s size and place
  • What you leave unticked is remembered, and left out of later backups — the scheduled ones too — until you tick it again. A part a later version adds is taken.
  • Before anything has been written — a first start with nothing changed — it says there is nothing to back up yet.
  • Your answers about reports, updates and the license are never in a backup, since restoring them would be answering for you. Nor are the logs.
  • It is a plain zip: backup.json saying what it is, and the files as they are on disk under files/. Anything that opens a zip opens it, with or without the application — see the files the application keeps.

Putting one back

Every setting that differs, as it is now and as the backup has it, and a line for each part it would replace.
The backup
Its file, when it was made and by which version, and its note.
What to restore
The parts it holds, all ticked. Untick one to leave it as it is now. Restore and restart waits until one is ticked.
Back up before restore
Ticked, the parts about to be replaced are backed up first, so there is a way back. That backup is listed as before restore.
What would change
Each setting that differs — as it is now, then as the backup has it — or No setting would change; then a line for every other part it replaces, counted where it can be: Favorites: 3 places → 2 places. A restore replaces whole files, which is why every part is listed and not only the settings.

Restore and restart quits the application — asking first, as a quit does, if something is running — and opens it again. The backup is put back before anything reads what it replaces, and a notice says what was restored and which backup holds what was there before. If you choose Stay when it asks, the restore waits: the next time the application quits, it opens again and puts the backup back.

  • A part the backup does not hold is left as it is.
  • A backup that cannot be read changes nothing, and the notice says so.
  • A part whose copy in the backup cannot be read is left as it is. The others are put back, and the notice names both.
  • If what is there now cannot be backed up first, nothing is restored.
  • If the application is stopped partway, the next start finishes the restore. No file is left missing or half-written.
  • If the restore cannot be asked for — a full disk, say — the application does not quit, and the reason is said over the panes.

Backups taken by themselves

As the application starts, if no backup in the folder is newer than Back up every — a day, a week, the default, or a month — it takes one, of the parts you chose for your last backup. Any backup counts, so one you took this morning means none this afternoon. It never delays the start, and set to never, none is taken.

Backups kept, ten unless you change it, is how many of the backups nobody asked for are kept: the scheduled ones and those taken before a restore. The oldest beyond it are deleted as the application starts and after you take one. Backups you take yourself are never deleted.

Where they go

Backups folder is ~/.northern-commander/backups unless you change it, and ~ is your home folder. A folder in iCloud Drive or on another disk is better, since backups kept beside what they copy are lost with them.

  • The folder is made when the first backup is written.
  • Changing it lists the new folder; backups in the old one stay where they are.
  • A backup is written beside itself and moved into place when it is whole, so one interrupted halfway never appears.

Also on the Backups page of the settings: Write settings, when what you set reaches the settings file — see Settings › Backups.