Hello everyone,
To perform a mass configuration on a group of PCs,
how do I reset the local database?
How do I reset an existing client-side backup configuration?
How do I disable database or backup encryption?
Which duplication utility should I use?
Thank you for your feedback.
Hey ludoobernard, for mass deployments like this, the easiest way is usually to manage the Duplicati-server.sqlite file directly. That file holds all the global settings and backup job definitions. If you’re looking to clear the local database for a specific job, you can usually just delete the .sqlite file associated with that job (found in the ‘Database’ settings) and Duplicati will prompt to recreate it. For disabling encryption, you’ll need to update the job’s command line or export/import the JSON without the --passphrase argument.
Thanks for the feedback.
I would like to use the command-line tool duplicate.commandLine.exe
Deleting a backup job configuration with CLI ?
When I delete the SQLite file from the backup, I have to go into the graphical interface to delete the backup job.
$ duplicati-server-util --list-backups
Connecting to http://localhost:8200/...
1: test5
delete job backup “1: test5” , with CLI command ?
Could you say something about how similar or different the configs are?
Who is going to maintain configs, run the backups, and do file restores?
There was a mention later of CLI? Which parts are CLI, and which GUI?
I don’t see that option for duplicati-server-util. Maybe you could ask for it.
The old duplicati-client that no longer ran after Duplicati 2.0 could delete.
You delete it, but delete the destination files at the same time for a fresh start.
The local database describes what the database contains. It’s not job configs.
I suppose I can ask for all the reset questions: Reset to what, some constant?
Reset of local database doesn’t make much sense, but delete is even in GUI.
Before first backup, local database doesn’t exist, so delete isn’t needed either.
Securing the database or unsecuring, but why is that preferable to securing?
Backup encryption has a similar question, but that setting is in the job config.
import <file> <passphrase> Import a backup configuration
export <backups> Export a backup configuration
from the ServerUtil help may be another way to do minor changes to settings.
You could even start by setting the main part in GUI then tweaking job export.
Import command creates duplicate job instead of updating existing job with same name is a forum question that the dev hasn’t replied to. And delete is missing.
Wiping out all job configurations can be done by deleting the server database.
You could then import whatever the standard (or custom) config is, for a reset.
There is also a mechanism to add or override parts of configs. This might help:
If you decide to backup using CommandLine, there’s no server database used.
It’s just CLI options (or a parameters-file full of them) so it’s only text to edit.
The Duplicati devs are also adding remote management of agents in enterprise
which is part of the new optional paid services. I’m also seeing a claim on page:
Get the flexibility and security of Duplicati’s Open Source backup, with the tools you need to deploy at scale.
I’m not sure if this is a fit for your mass configuration scenario, but I’ll mention it.
Thank you for your feedback and time.
Configuration maintenance is handled by administrators, while file restoration can be performed by the user or administrator.
The goal is to update the job configuration on client machines, for example, adding a video exclusion.
I read the post about updating the task, but haven’t received a response yet.
If I delete the local *.sqlite database and import the new configuration via the JSON file using the serverutil.exe command, what happens? This adds a new backup job.
Where is the server database located?
The GUI would probably be easier for the users, however once they’re in GUI, configuration view and change is also there. There’s no separate admin login.
Users should be somewhat trusted. One can also separate backup encryption (although you didn’t want encryption) or destination access to keep them apart.
If users are even less trusted, more severe and complicated steps can be used.
If administrators maintain config, the question is how. Duplicati’s web UI can be accessed over a network, but admin might need to coordinate with user’s login, which might raise user privacy issue if they set the same password everywhere.
If admin can run a script remotely to change config, that may be another option, depending on whether admin can also get files, e.g. if a config export gets done then it’s still on the user machine until moved somewhere else to edit change in.
Which post? In this topic, I can find only one sort of like that, which I answered.
Too ambiguous. Please see my links and text. The local database usually means database for job which summarizes the destination files and has no configuration.
The server database is also a local *.sqlite database, but has a specific name of Duplicati-server.sqlite. Job databases are the ones with random letters dot sqlite.
If you were asking about server database that has the configurations for all jobs, your own answer is my understanding, but see the complaint it doesn’t overwrite previous job of the same name. You still get a new job, and likely a new number.
That forum request seemed to want an overwrite, and you’ve asked for a delete.
Feel free to try some of this stuff, then you’ll know, but things might change later.