-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
.conf specifies 2 different repos, npbackup only backs up the "default" via TaskScheduler [Windows] #96
Comments
Indeed, currently NPBackup task creation GUI only cretes a task for the current repository. This is linked to #61. |
Thank you. Would these options also apply with the --housekeeping flag? |
All operations that NPBackup does can be batched via |
Currently implementing task scheduler GUI for all tasks types and all repos in operation center. |
So this is getting way harder than I thought. Anyway, I won't improve that GUI part until next release, since it involves getting rid of task scheduler completely, and running npbackup with it's own task scheduler, which implies running as service. So for now, I added a remark that any other than default task must be configured manually. |
Finally a part of this has been put into latest 3.0.0rc8, which allows task creation for various repos / repo groups. |
This may be a restic question, or a misunderstanding of how things are supposed to work with restic/npbackup. Please just let me know if that is the case as I am not a restic power-user.
Goal: I want 1 instance of npbackup to manage 2 different repos (each backs up a different file set to a different repo location).
Windows
npbackup-3.0.0-rc6-pub-3.11-x86
Taskscheduler > Start a program:
C:\...\npbackup-gui\npbackup-gui.exe -c "C:\...\npbackup-gui\npbackup.conf --backup --run-as-cli
Shortened .conf file. Notice "default" and "DrivePool" repos, each backs up a different fileset to different repo locations:
At this point, I would expect whenever
--backup
is executed via the TaskScheduler it would generate snapshots according to the retention policy (in this case, the default_group's policy).However, the repo "DrivePool" is now going on several days of not being snapshotted (but the "default" repo is working just fine).
cli.log example output:
I am reading the log as npbackup is seeing both repos (ie. "no extra information..." entries), but then it lists snapshots and sees that a recent snapshot exists (I imagine only for "Default" repo?) and then doesn't go and check the next repo and it's snapshot status. The second repo "DrivePool" never gets analyzed as needing to also be snapshotted.
Any ideas why this would be or how to adjust for it?
The text was updated successfully, but these errors were encountered: