Inline below how I would handle each


> On Jan 14, 2021, at 8:02 AM, iegan Amadeus <[email protected]> wrote:
> 
> 
> Good day! I want to implement a backup of files from the Microsoft Windows 
> desktop using a client available for this OS. Faced the following 
> difficulties: 
> 
> • How to create a backup task for% USER_PROFILE% \ Desktop? 

This is the fileset that I use for windows,  it will recessively start at 
C:\Users\*   so it will back up every users user space Desktop, My Documents etc
Look at WildDir  to ether exclude everything except Desktop,  or honestly I 
would backup the full user space not just the Desktop, as that is the normal 
location that users can drop data.

FileSet {
  Name = "Windows All Users"
  Enable VSS = yes
  Include { 
    Options {
      compression=LZ4
      Signature = MD5
      IgnoreCase = yes
      WildFile = "[A-Z]:*/MpWppTracing*"
      WildFile = "[A-Z]:*/ntuser.dat*"
      WildFile = "[A-Z]:*/NTUSER.DAT"
      WildDir = "[A-Z]:/RECYCLER"
      WildDir = "[A-Z]:/$RECYCLE.BIN"
      WildDir = "[A-Z]:/System Volume Information"
      WildDir = "[A-Z]:/FileHistory"
      WildDir = "[A-Z]:/bareos-storage"
      WildDir = "[A-Z]:*/Thunderbird*"
      WildDir = "[A-Z]:*/AppData"
      Exclude = yes
    }
    File = C:/Users
  }
}

Do a lot of testing with this using 
estimate job=<jobname> listing
To make sure you are getting the files you want.

> • How to group clients into groups so that you can assign one task for all. 
> After only add new clients to this group. 

There isn’t a way to do this easily that I know of, but you can hack it here is 
how I would do it,
* Create JobDefs 
https://docs.bareos.org/Configuration/Director.html#jobdefs-resource
To create the common propoerties of all these systems and then you define a job 
that contains just the client for each,

eg:
Job {
  Name = "BackupMyth"
  JobDefs = “DefaultJobAI”
}

* To do the ‘groups’  I would make a shell script that takes a list of hosts 
and creates the Client {} and Job {}  entries for each using the @|  syntax 
https://docs.bareos.org/Configuration/CustomizingTheConfiguration.html#including-other-configuration-files

This way when you add a host to that script run  ‘reload’  in bareos to re-read 
it’s config which will call that script and read stdout  to add the new Job{} 
and Client{} entires to the running config.
This all assumes they will use the same backup properties (filelist, retention, 
etc)  but you obviously can add all those to your script to override values in 
the JobDefs{}.


> • And what to do with DHCP? I can add a client only with address = 
> 10.10.10.10 
> configure add client name = test1 address = 10.10.10.10 password = password. 

Assuming your DHCP cannot set static clients or these are road warriors (this 
is my use case for windows and mac)  use a Client Initiated Connection 
https://docs.bareos.org/TasksAndConcepts/NetworkSetup.html#client-initiated-connection

You still put an IP in but it’s basically ignored,  you put the correct 
settings in the client (FD)  and Director and you should see the client when it 
starts connect to the director when you do 'status dir'  in the console.  The 
Director and SD will need static IPs though.

> 
> And if everything is dynamic? Or is it difficult for Bareos? I understand 
> that it was created for someone else, I just don't want to use third-party 
> utilities. Tell me who understands 
> The text was prepared by an auto translator.

Not everything will be dynamic, specifically you need to add a Job and Client 
entry for each host you add,  but again you can make that be a script so it can 
take a list.  Maybe that list could be created dynamically as machines get 
built.   But that’s outside of Bareos.  

I have not looked into but there is a new rest API being worked on,  you may 
also be able to setup everything that way.  I don’t know, and what above is 
what I am comfortable with.

> 
> 
> -- 
> 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 [email protected].
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/bareos-users/23ff2e6f-e6aa-4bc4-9eaf-e546725db7e1n%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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/bareos-users/8CA98203-ED85-4284-9400-AF3D928F2920%40mlds-networks.com.

Reply via email to