[bareos-users] New to bareos had limited success

[Waanie Simon]

Hi all

I am working on building a backup solution with bareos. the system will be 
used to replace arkeia which is no longer supported. Arkeia backups were 
quite easy to install and monitor but we are. 

I have install bareos-director and bareos-sd on the same server. They are 
running on the same network interface. 

My initial backups went fine but as time went on the backups would queued. 
Including the catalog backup.
I sometime see that the system is asking for a labeling to happen but it 
doesn't always fix the problem.

mostly linux vms and proxmox physical servers.

Some of the harder ones to backup is our file server with home volume of 90 
TB. This is something that we could never backup and has become a source of 
many problems.

How would you backup such a volume. Should it be split? Since there is a 
lot of static content in there, should it be archived?

I am not sure if config files are is set correctly.

I have incremental backups happening daily and differentials happening 
weekly but I often have full backups happening multiple times during a 
month.

Currently we have no tape library in place so all is running on disk.

Thought I could add some code snippets to give an idea of what I have going 
on here


client


Client {
  Name = dr001-fd
  Address = 10.60.100.12
  Password = 
}

Job

Job {
  Name = dr001-Daily-inc
  JobDefs = linux-daily-inc
  Type = backup
  Messages = Standard
  Client = dr001-fd
}


JobDefs {
  Name = linux-daily-inc
  Type = Backup
  Level = Incremental
  Storage = File
  Pool = Incremental
  FileSet = LinuxAll
}

each job has its own schedule. is this necessary 

Schedule {
  Name = dr001-daily-inc
  Description = Incremental Daily for dr001-fd
  Run = daily at 11:00
}


storage under the bareos-dir.d folder 
File.conf file

Storage {
  Name = File
  Address = ctbackup.cape.saao.ac.za# N.B. Use a fully 
qualified name here (do not use "localhost" here).
  Password = 
  Device = FileStorage
  Media Type = File
  Maximum Concurrent Jobs = 5
}


The Pools are configured as

Pool {
  Name = Incremental
  Pool Type = Backup
  Recycle = yes   # Bareos can automatically recycle 
Volumes
  AutoPrune = yes # Prune expired volumes
  Volume Retention = 30 days  # How long should the Incremental 
Backups be kept?  (#12)
  Maximum Volume Bytes = 150G   # Limit Volume size to something 
reasonable
  Maximum Volumes = 30   # Limit number of Volumes in Pool
  Label Format = "Incremental-"   # Volumes will be labeled 
"Incremental-"
}

Pool {
  Name = Differential
  Pool Type = Backup
  Recycle = yes   # Bareos can automatically recycle 
Volumes
  AutoPrune = yes # Prune expired volumes
  Volume Retention = 90 days  # How long should the Differential 
Backups be kept? (#09)
  Maximum Volume Bytes = 100G  # Limit Volume size to something 
reasonable
  Maximum Volumes = 60   # Limit number of Volumes in Pool
  Label Format = "Differential-"  # Volumes will be labeled 
"Differential-"
}

Pool {
  Name = Full
  Pool Type = Backup
  Recycle = yes   # Bareos can automatically recycle 
Volumes
  AutoPrune = yes # Prune expired volumes
  Volume Retention = 365 days # How long should the Full Backups be 
kept? (#06)
  Maximum Volume Bytes = 350G  # Limit Volume size to something 
reasonable
  Maximum Volumes = 100   # Limit number of Volumes in Pool
  Label Format = "Full-"  # Volumes will be labeled 
"Full-"
}


unfortunately there has been a bit of a thumb suck regarding the numbers 
here.

The storage config looks like this


Devices

Device {
  Name = FileStorage
  Media Type = File
  Archive Device = /data1/bareos/FileStorage
  LabelMedia = yes;   # lets Bareos label unlabeled media
  Random Access = yes;
  AutomaticMount = yes;   # when device opened, read it
  RemovableMedia = no;
  Collect Statistics = yes
  AlwaysOpen = no;
  Description = "File device. A connecting Director must have the same Name 
and MediaType."
}


bareos-sd.conf

Storage {
  Name = bareos-sd
  Maximum Concurrent Jobs = 20

  # 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/lib/bareos/plugins"
  # Plugin Names = ""
  Collect Device Statistics = yes
  Collect Job Statistics = yes
  #Statistics Collect Intevals = 60
}
~ 



I know that my largest backups will probably not work since my capacity I 
can write to is only about 70 Tb

I have the web gui working but there is no easy way to see progress on a 
job.

Any improvements would be appreciated

Regards
Waanie
~   

-- 
You received this message because you are subscribed to the G

[bareos-users] Always incremental / Consolidation

[sim....@gmail.com]

Hello

I'm trying to set up always incremental jobs.
The storage target is ceph, so one big storage target.
I have read many guides and believe I did the right configuration, just 
some timing problems.
When a consolidation Job runs, it starts a new one with the level 
"VirtualFull", that's correct, isn't it?

The other question is, how to efficiently eliminate physically used volume 
storage, not used in bareos?
A "du -skh" in the cephfs tells me, there is 3.2TB storage used, but in the 
job list, the full Consolidated job is 1.06 TB and the other incrementlas 
are like 700GB, so where are those 1.5TB from?

[root@testnode1 ~]# ls -lah /cephfs/
total 3.2T
drwxrwxrwx   4 root   root 21 Jun 24 01:00 .
dr-xr-xr-x. 18 root   root258 Jun 17 10:04 ..
-rw-r-   1 bareos bareos 200G Jun 11 16:04 AI-Consolidated-0001
-rw-r-   1 bareos bareos 200G Jun 11 17:50 AI-Consolidated-0002
-rw-r-   1 bareos bareos 200G Jun 11 19:20 AI-Consolidated-0003
-rw-r-   1 bareos bareos 200G Jun 11 20:35 AI-Consolidated-0004
-rw-r-   1 bareos bareos 176G Jun 11 21:44 AI-Consolidated-0005
-rw-r-   1 bareos bareos 200G Jun 23 16:18 AI-Consolidated-0013
-rw-r-   1 bareos bareos 200G Jun 23 18:00 AI-Consolidated-0014
-rw-r-   1 bareos bareos 200G Jun 23 19:16 AI-Consolidated-0015
-rw-r-   1 bareos bareos 200G Jun 23 20:34 AI-Consolidated-0016
-rw-r-   1 bareos bareos 200G Jun 23 21:52 AI-Consolidated-0017
-rw-r-   1 bareos bareos  49G Jun 23 22:12 AI-Consolidated-0018
-rw-r-   1 bareos bareos 200G Jun 15 11:25 AI-Incremental-0007
-rw-r-   1 bareos bareos 200G Jun 15 13:04 AI-Incremental-0008
-rw-r-   1 bareos bareos 200G Jun 19 00:27 AI-Incremental-0009
-rw-r-   1 bareos bareos 200G Jun 20 01:22 AI-Incremental-0010
-rw-r-   1 bareos bareos 200G Jun 21 00:33 AI-Incremental-0011
-rw-r-   1 bareos bareos 200G Jun 24 01:00 AI-Incremental-0012
-rw-r-   1 bareos bareos  27G Jun 24 01:25 AI-Incremental-0019

Is there a way to view this efficiently, or do I have to search my way from 
job to job?

Thanks in advance
Simon

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/bareos-users/50bfad73-bf8d-4506-93e7-afa0afa91939n%40googlegroups.com.

Re: [bareos-users] Long Path UNC

[Sylvain Donnet]

Hi,

Thanks. I knew about that. Bareos-fd service run under an account having 
the maximum rights, and having also "net share" declared.
I am looking to the special writing of "Files=..." with UNC...
My job failed, but I don't know if it is due to the writing, or a missing 
prerequisite, or both...

Le mercredi 24 juin 2020 12:31:10 UTC+2, Spadajspadaj a écrit :
>
> Apart from all the possible other prerequisites, you have to remember that 
> the paths have to be accessible from the context of the user from which the 
> bareos-fd is running. So if you - for example - mount the NAS share as a g: 
> drive from your normal user, it won't be visible to the bareos-fd process 
> since it's running from another user session. If you want to call UNC-paths 
> you might have to do some windows-voodoo with credentials.
>
>
> On 24.06.2020 10:17, Sylvain Donnet wrote:
>
> Hi,
>
> I need to backup network shares on a Windows guest, and the shares are 
> coming from a branded NAS. No capability to install Bareos client on this 
> NAS.
>
> So, I discovered on this forum an old post, telling that UNC, in long path 
> format (\\?\UNC\server\share) works for Bareos.
>
> My tests didn't work. But I discovered that at least one prerequisite is 
> required : a regedit key (HKLM\SYSTEM\CurrentControlSet\Control\FileSystem 
> LongPathsEnabled) to declare.
>
> So, my questions are :
> - are there other prerequisites ?
> - is the Bareos windows client compatible with such call ? (or above a 
> specific version ?)
> - how do I have to write the files instruction in the Fileset (native 
> \\?\UNC\..., ?\\UNC\\, //?/UNC/, ...)
>
> Any help will be greatly greatly appreciated... I am going to be 
> completely mad with, for me, a simple+old problem...
>
> Sylvain
> -- 
> 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...@googlegroups.com .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/bareos-users/bc51bde5-9073-4346-a3ef-ec8d0ba2518bo%40googlegroups.com
>  
> 
> .
>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/bareos-users/98e61a1b-5f94-40c0-a68e-98aed7866f39o%40googlegroups.com.

Re: [bareos-users] Long Path UNC

[Spadajspadaj]

Apart from all the possible other prerequisites, you have to remember 
that the paths have to be accessible from the context of the user from 
which the bareos-fd is running. So if you - for example - mount the NAS 
share as a g: drive from your normal user, it won't be visible to the 
bareos-fd process since it's running from another user session. If you 
want to call UNC-paths you might have to do some windows-voodoo with 
credentials.



On 24.06.2020 10:17, Sylvain Donnet wrote:

Hi,

I need to backup network shares on a Windows guest, and the shares are 
coming from a branded NAS. No capability to install Bareos client on 
this NAS.


So, I discovered on this forum an old post, telling that UNC, in long 
path format (\\?\UNC\server\share) works for Bareos.


My tests didn't work. But I discovered that at least one prerequisite 
is required : a regedit key 
(|HKLM\SYSTEM\CurrentControlSet\Control\FileSystem LongPathsEnabled) 
to declare.|

|
|
|So, my questions are :|
|- are there other prerequisites ?|
|- is the Bareos windows client compatible with such call ? (or above 
a specific version ?)|
|- how do I have to write the files instruction in the Fileset (native 
\\?\UNC\..., ?\\UNC\\, //?/UNC/, ...)

|
|
|
|Any help will be greatly greatly appreciated... I am going to be 
completely mad with, for me, a simple+old problem...|

|
|
|Sylvain
|
--
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/bareos-users/bc51bde5-9073-4346-a3ef-ec8d0ba2518bo%40googlegroups.com 
.


--
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/bareos-users/9cede40f-1883-1c0b-d3c7-28f928da0ce2%40gmail.com.

[bareos-users] Long Path UNC

[Sylvain Donnet]

Hi,

I need to backup network shares on a Windows guest, and the shares are 
coming from a branded NAS. No capability to install Bareos client on this 
NAS.

So, I discovered on this forum an old post, telling that UNC, in long path 
format (\\?\UNC\server\share) works for Bareos.

My tests didn't work. But I discovered that at least one prerequisite is 
required : a regedit key (HKLM\SYSTEM\CurrentControlSet\Control\FileSystem 
LongPathsEnabled) to declare.

So, my questions are :
- are there other prerequisites ?
- is the Bareos windows client compatible with such call ? (or above a 
specific version ?)
- how do I have to write the files instruction in the Fileset (native 
\\?\UNC\..., ?\\UNC\\, //?/UNC/, ...)

Any help will be greatly greatly appreciated... I am going to be completely 
mad with, for me, a simple+old problem...

Sylvain

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/bareos-users/bc51bde5-9073-4346-a3ef-ec8d0ba2518bo%40googlegroups.com.