[bareos-users] Re: Huge data backup schedule
On Tuesday, March 19, 2019 at 1:13:50 AM UTC-5, HyunChul Lee wrote: > Hello, > Our company uses file server and data size is about 55TB Because data is > very huge, I know some people who have more than that on their home server. -- 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 bareos-users+unsubscr...@googlegroups.com. To post to this group, send email to bareos-users@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[bareos-users] Huge data backup schedule
Hello, Our company uses file server and data size is about 55TB now and it keeps on increasing. Because data is very huge, we want to Full backup every 5 years. Can bareos set to every 5 years full backup schedule and could you tell me any best guideline or practice to huge data backup? Warm Regards, -- 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 bareos-users+unsubscr...@googlegroups.com. To post to this group, send email to bareos-users@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [bareos-users] 3999 Device "vchanger-1" not found or could not be opened.
Thanks for the config but if I'm not mistaken it won't let me do what I
mainly wanted to achieve with vchanger - it won't let me plug in and out
external drives. That's the whole point of using vchanger for me so I
can take one external disk and move it somewhere offline or even
off-site, Your storage seems to depend on a directory permanently
mounted on the SD.
Best regards,
Mariusz
On 18.03.2019 17:10, Bartek R wrote:
Hi,
I have tried to start vchanger long time ago but i found it a bit too
complex. Since then i am running following configuration:
Autochanger {
Name = local-sd
Changer Device = /dev/null
Changer Command = ""
Device = drive-0, drive-1, drive-2, drive-3
}
Device {
Name = drive-0
Device Type = File
Media Type = File
Archive Device = /var/lib/bareos/storage
Automatic Mount = yes
Always Open = yes
RemovableMedia = no
RequiresMount = no
Autochanger = yes
Drive Index = 0
Maximum Concurrent Jobs = 1
RandomAccess = yes
Label Media = yes
}
Device {
Name = drive-1
Device Type = File
Media Type = File
Archive Device = /var/lib/bareos/storage
Automatic Mount = yes
Always Open = yes
RemovableMedia = no
RequiresMount = no
Autochanger = yes
Drive Index = 1
Maximum Concurrent Jobs = 1
RandomAccess = yes
Label Media = yes
}
Device {
Name = drive-2
Device Type = File
Media Type = File
Archive Device = /var/lib/bareos/storage
Automatic Mount = yes
Always Open = yes
RemovableMedia = no
RequiresMount = no
Autochanger = yes
Drive Index = 2
Maximum Concurrent Jobs = 1
RandomAccess = yes
Label Media = yes
}
Device {
Name = drive-3
Device Type = File
Media Type = File
Archive Device = /var/lib/bareos/storage
Automatic Mount = yes
Always Open = yes
RemovableMedia = no
RequiresMount = no
Autochanger = yes
Drive Index = 3
Maximum Concurrent Jobs = 1
RandomAccess = yes
Label Media = yes
}
Storage {
Name = bareos-sd
Maximum Concurrent Jobs = 4
# remove comment from "Plugin Directory" to load plugins from
specified directory.
# if "Plugin Names" is defined, only the specified plugins will be
loaded,
# otherwise all storage plugins (*-sd.so) from the "Plugin Directory".
#
# Plugin Directory = "/usr/lib64/bareos/plugins"
# Plugin Names = ""
}
Pool {
Name = default
Pool Type = Backup
Recycle = no # No recycling, volumes used once
and then truncated
AutoPrune = yes # Prune expired volumes
Action On Purge = Truncate
File Retention = 70 days
Job Retention = 70 days
Volume Retention = 70 days
# Use Volume Once = yes
Maximum Volume Jobs = 1
Label Format = "default-${JobId}"
Storage = local-sd
}
I belive this setup is a bit tricky but it works perfectly for me. The
trick is to have only one job per volume and having number of jobs
limited on SD level to the total sum of devices. I am not sure but i
think it was set that way in order to avoid having the same volume
opened by multiple jobs simultanously.
Hope this can be helpful but feel free to correct me if you find this
configuration to be a total mess.
PS. It is possible that this setup require a helper script in order to
have expired volume files (and jobs) correctly removed.
Kind Regards,
Bartłomiej
pon., 18 mar 2019 o 14:33 Go Away > napisał(a):
Hello.
I'm trying to set up an environment with removable disks managed
by vchanger.
I managed to install vchanger, I created the media files but I
cannot seem to be able to make bareos see my virtual autochanger.
And I'm a bit stuck.
Whenever I try to do "update slots" I'm getting the 3999 error.
Relevant parts of my config:
# cat /etc/vchanger/vchanger.conf
Storage Resource = vchanger-1
User = bareos
Group = bareos
Logfile = /var/log/vchanger/vchanger-1.log
Work Dir = /var/spool/vchanger/vchanger-1
Log Level = 7
Magazine = /srv/backupstor/252f8c87-02bd-4509-aa63-fa2fe8ee105d
bconsole config = /etc/bareos/bconsole.conf
# cat bareos-sd.d/autochanger/vchanger1
Autochanger {
Name = vchanger-1
Device = vchanger-1-0
# Changer Command = "/usr/local/bin/vchanger -u bareos -g
bareos %c %o %S %a %d"
Changer Command = "/usr/local/bin/vchanger %c %o %S %a %d"
Changer Device = /etc/vchanger/vchanger.conf
}
# cat bareos-sd.d/device/vchanger1.conf
Device {
Name = vchanger-1-0
DriveIndex = 0
Autochanger = yes
Device Type = File
Media Type = Offsite-File
Label Media = no
Random Access = yes
Removable Media = yes
Automatic Mount = yes
Archive Device = /var/spool/vchanger/vchanger-1/0
}
# cat bareos-dir.d/storage/vchanger-1.conf
S
Re: [bareos-users] 3999 Device "vchanger-1" not found or could not be opened.
Hi,
I have tried to start vchanger long time ago but i found it a bit too
complex. Since then i am running following configuration:
Autochanger {
Name = local-sd
Changer Device = /dev/null
Changer Command = ""
Device = drive-0, drive-1, drive-2, drive-3
}
Device {
Name = drive-0
Device Type = File
Media Type = File
Archive Device = /var/lib/bareos/storage
Automatic Mount = yes
Always Open = yes
RemovableMedia = no
RequiresMount = no
Autochanger = yes
Drive Index = 0
Maximum Concurrent Jobs = 1
RandomAccess = yes
Label Media = yes
}
Device {
Name = drive-1
Device Type = File
Media Type = File
Archive Device = /var/lib/bareos/storage
Automatic Mount = yes
Always Open = yes
RemovableMedia = no
RequiresMount = no
Autochanger = yes
Drive Index = 1
Maximum Concurrent Jobs = 1
RandomAccess = yes
Label Media = yes
}
Device {
Name = drive-2
Device Type = File
Media Type = File
Archive Device = /var/lib/bareos/storage
Automatic Mount = yes
Always Open = yes
RemovableMedia = no
RequiresMount = no
Autochanger = yes
Drive Index = 2
Maximum Concurrent Jobs = 1
RandomAccess = yes
Label Media = yes
}
Device {
Name = drive-3
Device Type = File
Media Type = File
Archive Device = /var/lib/bareos/storage
Automatic Mount = yes
Always Open = yes
RemovableMedia = no
RequiresMount = no
Autochanger = yes
Drive Index = 3
Maximum Concurrent Jobs = 1
RandomAccess = yes
Label Media = yes
}
Storage {
Name = bareos-sd
Maximum Concurrent Jobs = 4
# remove comment from "Plugin Directory" to load plugins from specified
directory.
# if "Plugin Names" is defined, only the specified plugins will be loaded,
# otherwise all storage plugins (*-sd.so) from the "Plugin Directory".
#
# Plugin Directory = "/usr/lib64/bareos/plugins"
# Plugin Names = ""
}
Pool {
Name = default
Pool Type = Backup
Recycle = no # No recycling, volumes used once and
then truncated
AutoPrune = yes # Prune expired volumes
Action On Purge = Truncate
File Retention = 70 days
Job Retention = 70 days
Volume Retention = 70 days
# Use Volume Once = yes
Maximum Volume Jobs = 1
Label Format = "default-${JobId}"
Storage = local-sd
}
I belive this setup is a bit tricky but it works perfectly for me. The
trick is to have only one job per volume and having number of jobs limited
on SD level to the total sum of devices. I am not sure but i think it was
set that way in order to avoid having the same volume opened by multiple
jobs simultanously.
Hope this can be helpful but feel free to correct me if you find this
configuration to be a total mess.
PS. It is possible that this setup require a helper script in order to have
expired volume files (and jobs) correctly removed.
Kind Regards,
Bartłomiej
pon., 18 mar 2019 o 14:33 Go Away napisał(a):
> Hello.
>
> I'm trying to set up an environment with removable disks managed by
> vchanger.
> I managed to install vchanger, I created the media files but I cannot seem
> to be able to make bareos see my virtual autochanger. And I'm a bit stuck.
> Whenever I try to do "update slots" I'm getting the 3999 error.
>
> Relevant parts of my config:
>
> # cat /etc/vchanger/vchanger.conf
> Storage Resource = vchanger-1
> User = bareos
> Group = bareos
> Logfile = /var/log/vchanger/vchanger-1.log
> Work Dir = /var/spool/vchanger/vchanger-1
> Log Level = 7
> Magazine = /srv/backupstor/252f8c87-02bd-4509-aa63-fa2fe8ee105d
> bconsole config = /etc/bareos/bconsole.conf
>
>
> # cat bareos-sd.d/autochanger/vchanger1
> Autochanger {
> Name = vchanger-1
> Device = vchanger-1-0
> #Changer Command = "/usr/local/bin/vchanger -u bareos -g bareos %c %o
> %S %a %d"
> Changer Command = "/usr/local/bin/vchanger %c %o %S %a %d"
> Changer Device = /etc/vchanger/vchanger.conf
> }
>
> # cat bareos-sd.d/device/vchanger1.conf
>
> Device {
> Name = vchanger-1-0
> DriveIndex = 0
> Autochanger = yes
> Device Type = File
> Media Type = Offsite-File
> Label Media = no
> Random Access = yes
> Removable Media = yes
> Automatic Mount = yes
> Archive Device = /var/spool/vchanger/vchanger-1/0
> }
>
> # cat bareos-dir.d/storage/vchanger-1.conf
> Storage {
> Name = vchanger-1-changer
> Address = backup1
> Password = "edited"
> Device = vchanger-1
> Media Type = Offsite-File
> Autochanger = yes
> }
>
> # cat bareos-dir.d/pool/Offsite-eSATA.conf
> Pool {
> Name = Offsite-eSATA
> Storage = vchanger-1-changer
> Pool Type = Backup
> Recycle = yes
> AutoPrune = yes
> Volume Retention = 4 weeks
> Recycle Oldest Volume = yes
> Volume Use Duration = 2 hours
> Maximum Volume Bytes = 42949672960
> }
>
> Oh, and btw, if I try to run bareos-sd with high debug level (somewhere
> a
[bareos-users] 3999 Device "vchanger-1" not found or could not be opened.
Hello.
I'm trying to set up an environment with removable disks managed by vchanger.
I managed to install vchanger, I created the media files but I cannot seem to
be able to make bareos see my virtual autochanger. And I'm a bit stuck.
Whenever I try to do "update slots" I'm getting the 3999 error.
Relevant parts of my config:
# cat /etc/vchanger/vchanger.conf
Storage Resource = vchanger-1
User = bareos
Group = bareos
Logfile = /var/log/vchanger/vchanger-1.log
Work Dir = /var/spool/vchanger/vchanger-1
Log Level = 7
Magazine = /srv/backupstor/252f8c87-02bd-4509-aa63-fa2fe8ee105d
bconsole config = /etc/bareos/bconsole.conf
# cat bareos-sd.d/autochanger/vchanger1
Autochanger {
Name = vchanger-1
Device = vchanger-1-0
#Changer Command = "/usr/local/bin/vchanger -u bareos -g bareos %c %o %S %a
%d"
Changer Command = "/usr/local/bin/vchanger %c %o %S %a %d"
Changer Device = /etc/vchanger/vchanger.conf
}
# cat bareos-sd.d/device/vchanger1.conf
Device {
Name = vchanger-1-0
DriveIndex = 0
Autochanger = yes
Device Type = File
Media Type = Offsite-File
Label Media = no
Random Access = yes
Removable Media = yes
Automatic Mount = yes
Archive Device = /var/spool/vchanger/vchanger-1/0
}
# cat bareos-dir.d/storage/vchanger-1.conf
Storage {
Name = vchanger-1-changer
Address = backup1
Password = "edited"
Device = vchanger-1
Media Type = Offsite-File
Autochanger = yes
}
# cat bareos-dir.d/pool/Offsite-eSATA.conf
Pool {
Name = Offsite-eSATA
Storage = vchanger-1-changer
Pool Type = Backup
Recycle = yes
AutoPrune = yes
Volume Retention = 4 weeks
Recycle Oldest Volume = yes
Volume Use Duration = 2 hours
Maximum Volume Bytes = 42949672960
}
Oh, and btw, if I try to run bareos-sd with high debug level (somewhere above
500), it segfaults on any command.
I'm using bareos on Raspberry Pi on Raspbian.
--
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 bareos-users+unsubscr...@googlegroups.com.
To post to this group, send email to bareos-users@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: [bareos-users] Cephfs and Bareos
Am 17.03.19 um 22:38 schrieb Dakota Pilot: > Can I use the RH7 package or should I compile that package from source? EPEL > does not seem to have the package. You should be able to use the RHEL 7 packages on CentOS 7. Best Regards, Andreas -- Andreas Rogge andreas.ro...@bareos.com Bareos GmbH & Co. KG Phone: +49 221-630693-86 http://www.bareos.com Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646 Komplementär: Bareos Verwaltungs-GmbH Geschäftsführer: S. Dühr, M. Außendorf, J. Steffens, Philipp Storz -- 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 bareos-users+unsubscr...@googlegroups.com. To post to this group, send email to bareos-users@googlegroups.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: OpenPGP digital signature
