Bacula Software backup function of the actual combat demo

One, example demo Bacula full backup function

1. Create a volume group

Perform the following command to connect to the Bacula control and perform a backup restore operation:

[root@baculaserver opt]#/opt/bacula/sbin/bconsole  
connecting to Director 192.168.12.188:9101  
1000 OK: F10-64-build-dir version:3.0.2 (July 2009)  
Enter a period to cancel a command  
*label automatically  
selecte D Storage:dbsd  
     
Enter new Volume Name:cicro4   #卷组名称, can be specified at will, after the completion  
of the #bacula-dir.conf file at the specified location to generate a Cicro4 file  
Defined Pools:  
     1:dbpool  
     2:scratch  
Select the Pool (1-2): 1  #指定卷组的放置位置, which is the SD name.  
#Dbpool在bacula defined  
in-dir.conf Connecting to Storage daemon Dbsd at 192.168.12.188:9103 ...  #由于指定SD在  
#192.168.12.188 host, the volume Cicro4 was created on this host  
sending label command for Volume "Cicro4" Slot 0 ...  
3000 OK label. volbytes=191 dvd=0 volume= "Cicro4" device= "Dbdev" (/cicro/backup2)  
Catalog record for Volume "Cicro4", Slot 0  Successfully created.  
Requesting to mount Dbdev  
... 3906 File Device "Dbdev" (/cicro/backup2) is always mounted.

2. Performing a backup operation with the Run command

Next, continue to perform backup operations on the Bacula control side:

*run  
A Job name must be specified.  
The defined job are:   
     1:client1  #这里的Client1 is a job execution task defined in bacula-dir.conf  
     2:client   # The client here is also a job execution task defined in bacula-dir.conf  
     3:backupcatalog  
     4:restorefiles  
Select Job Resource (1-2): 1  
Run Backup Job  
JobName:  Client1 level  
:    incremental  
Client:   dbfd  
fileset:  dbfs  
Pool:     Dbpool (from Job Resource)  
Storage:  Dbsd (from Job Resource) when  
:     2009-08-21 13:40:13  
priority:10  
OK to run? (yes/mod/no): Yes  
Job queued. jobid=67

So far, you can start the backup, and the Client1 defined in the bacula-dir.conf file is an incremental backup, so this backup is only an incremental operation. Because this is the first backup, the default Client1 makes a full standby, and the second backup does not perform an incremental backup.