Hi, all!
Please, help me :)
My schedule:
Schedule {
Name = "Weekly"
run = Full Sun at 03:00
run = Incremental Mon-Sat at 03:00
}
For every day i want to use one tape.
Total - 7 tapes.
What Volume Use Duration and Volume Retention Perion should i use?
--
You received this message
> Alternatively you can use 7 pool, one for each day, adapt you schedule
> to you the matching pool per day and assign the tapes to them.
In this case i need to define 7 x number_of_clients jobs?
I can't define Pool in Schedule resource :(
--
You received this message because you are
> How many tapes have you got?
7
> Volume Retention Period is only for reusing the volume again, so
> throwing away the data you backuped.
I just want to save backups of ~7 days data. One tape per one day.
> Do you want to overwrite the tapes in the next week? I'm not sure, if
> this makes
> certainly you can overwrite the pool in a schedule, see
> http://doc.bareos.org/master/html/bareos-manual-main-reference.html#directiveDirScheduleRun
>
> run = Level=Incremental pool=Monday Mon at 03:00
> run = Level=Incremental pool=Tuesday Tue at 03:00
Thank you for reply!
I just trying to
Director ver: Bareos 17.2.4, Debian.
Client ver: 17.2.4, SLES.
I have configured my FD with "Client Initiated Connection", because FD is
behind nat.
After starting the backup job, this job never ends.
FD started in debug mode. Some last messages:
ADSERV (100): bfile.c:1101-0 bopen: fname
Yes.
Client config on the director:
Client {
Name = "ADSERV"
Address = "..."
Connection From Client To Director = yes
Connection From Director To Client = no
Heartbeat Interval = 60
Password = "..."
}
Director config on the director:
Director {
Name = "bareos-dir"
Messages =
> Did "status client=" worked before? And during the backup job? It should
> work at all times.
"status client=" works file right after restarting bareos-fd. And some time
(2-3 minutes) after that. Even with no running jobs...
After that, the client stops responding.
With tcpdump i found that
No :)
I didn't know about this option in FD.
There is no information about the "Heartbeat interval" in reference part
"Client Initiated Connection":
http://doc.bareos.org/master/html/bareos-manual-main-reference.html#x1-38200028.1
...
To only allow Connection From the Client to the Director use:
One more question.
Is it possible not to log the "Using Client Initiated Connection (xxx)."
messages? :)
--
You received this message because you are subscribed to the Google Groups
"bareos-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
One more question about the jobs migration.
It is possible to automatically truncate the volume from which i have migrated
all jobs previously? After migration, the volume has no jobs, but volume file
size is not reduced. I can truncate that volume manually, but, maybe, it is
possible to do
I've upgraded bareos 18.2.5 -> 19.2.5
PostgreSQL.
/usr/lib/bareos/scripts/update_bareos_tables
DB migrated to version 2192
*.bvfs_clear_cache yes* done without errors.
After .bvfs_update, some error messages appears in the logfile:
09-Feb 13:08 bareos-dir JobId 0: Fatal error:
It looks like the job list has been sorted in reverse order :) Can this be
fixed somehow?
воскресенье, 9 февраля 2020 г., 13:26:53 UTC+2 пользователь Vladislav
Solovei написал:
>
> I've upgraded bareos 18.2.5 -> 19.2.5
> PostgreSQL.
>
> /usr/lib/bareos/scripts/update_ba
Is it possible to automatically delete job records (that seen in files
restore dialog) when volume is purged by "Recucle Oldest Volume"?
Now, in the jobs list, I have some tasks that no longer have files
associated with them.
I would like them to be deleted automatically.
--
You received
13 matches
Mail list logo
