[Skip]

When you have multiple libraries does a backup and restore affect ALL libraries or just the active one?

[Zubersoft]

Just the active one at the moment. That may change in the future, as I want to give users the ability to include multiple libraries in a backup if desired, and then choose which libraries to restore when restoring the backup file.

Mike

[itsme]

I use several libraries and backup them individually into the same folder, naming them according to the library name. For me just including the library name into the default backup name as already discussed would be enough. In my use cases .msb files containing several libraries would become too large and individual backup files per library seem less confusing and easier to handle.

[Lester]

For me just including the library name into the default backup name as already discussed would be enough.

That is a great idea, itsme. That would save having to manually add the library name to each backup.

[Swiss1000]

I use several libraries and backup them individually into the same folder, naming them according to the library name. For me just including the library name into the default backup name as already discussed would be enough. In my use cases .msb files containing several libraries would become too large and individual backup files per library seem less confusing and easier to handle.

I Agree

In addition, I suggest having separate sub-folders, one per librairy
Maintenance will be easier.

[Lawrie]

I would love to have the option to backup ALL libraries in a single backup, including all settings and folder structures.  
This would be a major help if you have a catastrophic failure:
install MS to a new tablet; restore everything in one go; complete, new working system that is an exact replica of the old (assuming the backup is current).

Of course, selective restores should also be possible.

[Geoff Bacon]

And warn user if trying to restore up a library which contains a "library name" to a library with a different "name" (they might want to do that but, as it unlikely to be a regular occurrence, havening to confirm what they doing shouldn't be a hardship)

Geoff

[Swiss1000]

I would love to have the option to backup ALL libraries in a single backup, including all settings and folder structures.  
This would be a major help if you have a catastrophic failure:
install MS to a new tablet; restore everything in one go; complete, new working system that is an exact replica of the old (assuming the backup is current).
Of course, selective restores should also be possible.

And warn user if trying to restore up a library which contains a "library name" to a library with a different "name" (they might want to do that but, as it unlikely to be a regular occurrence, havening to confirm what they doing shouldn't be a hardship)
Geoff

Lots of daily problems for a rare crash. I haven't had a tablet crash in 25 years... There's a rule in programming: how many people are bothered often by a rare option? Adding options, selecting, confirming—it's a bit like the Mobile Sheets disease: too many confirmations, not enough simple, immediate things.

And tablet crash is the bad exemple : tablet restore everything

Problems sometime comes from illogical vocabulary : backup everythink has a different name, different menu entry : "Backup DataBase". See Mobile Sheets menus : database is a concept, librairy is another concept, à subdivision of a database.
For me :
1) Backup librairy stay like now, just adding correct name
2) backup database could be an option, if you want, for me, boof, but why not...

By the way: See below for a vocabulary error that could cause confusion: the term "Database" is used, but it refers to different libraries... From the beginning, I've been saying that these concepts must be carefully studied to avoid creating a hellish machine. The concepts need to be clarified: a library is a library, and has nothing to do with any other library. A database is a database that groups libraries together. Then backups become logical.

Belkow : translation : The windows and the menu entry say "Restore DATABASE", in french... and offer to select a "Librairy"

   

[Lawrie]

Lots of daily problems for a rare crash. I haven't had a tablet crash in 25 years... There's a rule in programming: how many people are bothered often by a rare option? Adding options, selecting, confirming—it's a bit like the Mobile Sheets disease: too many confirmations, not enough simple, immediate things.

And tablet crash is the bad exemple : tablet restore everything

<snip>

You may consider a catastrophic crash rare, but before I retired I spent 30 years in IT and I can promise you that I saw way too many catastrophic crashes and they were ALWAYS a disaster, especially when the client had inadequate, or no backup - anything that can make system recovery easier is well worth it.  Total system backups are awesome!

[Swiss1000]

Lots of daily problems for a rare crash. I haven't had a tablet crash in 25 years... There's a rule in programming: how many people are bothered often by a rare option? Adding options, selecting, confirming—it's a bit like the Mobile Sheets disease: too many confirmations, not enough simple, immediate things.

And tablet crash is the bad exemple : tablet restore everything

<snip>

You may consider a catastrophic crash rare, but before I retired I spent 30 years in IT and I can promise you that I saw way too many catastrophic crashes and they were ALWAYS a disaster, especially when the client had inadequate, or no backup - anything that can make system recovery easier is well worth it.  Total system backups are awesome!

Except mine : 45 years (from Cobol, T/Pascal/l4G adding first windowing app, etc...) 

And I do not confuse Database with Librairy

And total crash is the most simple situation, especially for I-tabs or anny orther x-Tabs.