Hi Rob (and all),
Am 02.01.2025 um 18:14 schrieb Rob Gerber:
Arno,
Thank you very much for your reply and advice. I will investigate "
Allow Duplicate Jobs" and look at adding a runscript with 'whoami /all'
to my windows clients.
I can suggest something like
JobDefs {
Name = "DefaultJob"
Type = "Backup"
Accurate = yes
AllowDuplicateJobs = no
CancelLowerLevelDuplicates = yes
CancelQueuedDuplicates = yes
Client = "gnom-fd"
Fileset = "Full"
Level = "Incremental"
MaximumConcurrentJobs = 1
Messages = "Standard"
Pool = "long"
Priority = 10
ReRunFailedLevels = yes
RescheduleOnError = no
Schedule = "Daily"
SpoolAttributes = yes
Storage = "gnom-file1"
WriteBootstrap = "/opt/bacula/bsr/%n.bsr"
}
Schedule {
Name = "Daily"
# beware line breaks below!
Run = DifferentialPool="medium" FullPool="long"
IncrementalPool="short" Level="Full" Pool="long" Sun 1st at 23:05
Run = DifferentialPool="medium" FullPool="long"
IncrementalPool="short" Level="Differential" Pool="medium" Sun
2nd-5th at 23:05
Run = DifferentialPool="medium" FullPool="long"
IncrementalPool="short" Level="Incremental" Pool="short" Mon-Sat
at 23:05
}
And while my schedules need attention (days and timne become
inconvenient...) the scheme should be straightforward.
My goals for my clients are primarily to back up their files, not be
able to restore their systems to a certain state. This is a very
(allegedly) simple small business workstation environment. I am also
currently planning to copy my windows backups to cloud storage devices,
and the manual advises me that the windows vss backups don't copy
correctly because there is some xml data associated with each vss backup
that isn't currently copied by a copy job. Do you know if this is still
the case?
Should be no problem with recent Bacula versions (I am not sure about
since when exactly), but there are some critical pieces of information
that are relevant for some VSS writers in the catalog and that means,
you may not experience the best workflow when doing restores without a
catalog.
I think this is less problematic, as IMO, when you restore without a
catalog, you are already in deep trouble and any file restored at all
will be worth any inconvenience.
I had considered having the FD simply do two backups, one to
local storage and one to the cloud, but I'd rather avoid such a practice.
Copy jobs are indeed a better choice. In many instances.
For this reason, I am currently planning to set vss backups to no, and
portable backups to yes. If you can share any wisdom on this subject
(good practices, pitfalls), I would appreciate it. I think
implementation should be fairly straightforward.
You will get kind of the worst experience then... lots of files not
being backed up and the logs cluttered with predictable error messages.
Also, the files not being backed up will be the ones most interesting,
as they will be the ones you actually use...
Man, windows can be such a pain in the butt.
Quite so, but we're not going to see it vanishing any time soon, I
think. We may live to see a situation where actual windows is just a
crappy terminal and all data will be in MS 365, but even though Bacula
Enterprise subscribers pay my rent, I hope that a sufficient number of
people remain clever enough to keep their information under their own
control...
Ugh. Thank you so much for
your help!
You're welcome!
Cheers,
Arno
--
Arno Lehmann
IT-Service Lehmann
Sandstr. 6, 49080 Osnabrück
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
