bacula 소프트웨어 백업 기능 실전 프레젠테이션
1. 볼륨 그룹을 생성하여 다음 명령을 실행하고 bacula 제어단에 연결하여 백업 복구 작업을 수행합니다.
- [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 (18 July 2009)
- Enter a period to cancel a command
- *label
- Automatically selected Storage: dbsd
-
- Enter new Volume name: cicro4 # ， ，
- #bacula-dir.conf cicro4
- Defined Pools:
- 1: dbpool
- 2: Scratch
- Select the Pool (1-2): 1 # ， SD 。
- #Dbpool bacula-dir.conf
- Connecting to Storage daemon dbsd at 192.168.12.188:9103 ... # SD
- #192.168.12.188 ， cicro4
- 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. 런 명령을 이용하여 백업 작업을 수행합니다. 다음에 bacula 제어단에서 백업 작업을 계속 수행합니다.
- *run
- A job name must be specified.
- The defined Job resources are:
- 1: Client1 # Client1 bacula-dir.conf Job
- 2: Client # Client bacula-dir.conf Job
- 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
지금까지 백업을 시작할 수 있습니다. 백업-dir.conf 파일에 정의된 Client1은 증가분 백업이므로 이 백업은 증가분 작업일 뿐입니다.첫 번째 백업이므로 기본 Client1은 전체 백업을 수행한 다음 두 번째 백업을 수행해야 증가분 백업을 수행합니다.
3. 백업 상태 보기bacula 제어단에서'status'를 이용하여 백업의 각종 상태를 볼 수 있습니다. 여기서 백업할 때 Director단의 상태 정보를 볼 수 있습니다.
- *status
- Status available for:
- 1: Director
- 2: Storage
- 3: Client
- 4: All
- Select daemon type for status (1-4): 1
- f10-64-build-dir Version: 3.0.2 (18 July 2009) x86_64-unknown-linux-gnu redhat
- Daemon started 21-Aug-09 13:22, 0 Jobs run since started.
- Heap: heap=241,664 smbytes=82,242 max_bytes=82,498 bufs=245 max_bufs=250
-
- Scheduled Jobs:
- Level Type Pri Scheduled Name Volume
- ===============================================================================
- Incremental Backup 10 21-Aug-09 23:05 Client1 cicro4
- Running Jobs:
- Console connected at 21-Aug-09 13:37
- JobId Level Name Status
- ======================================================================
- 67 Full Client1.2009-08-21_13.40.16_07 is running
- ， ， ， ：
- *status
- Status available for:
- 1: Director
- 2: Storage
- 3: Client
- 4: All
- Select daemon type for status (1-4): 1
- bacula (SD) （DIR） ， 1“Director” SD ， SD DIR ， 2， “Storage”。 1r ：
- f10-64-build-dir Version: 3.0.2 (18 July 2009) x86_64-unknown-linux-gnu redhat
- Daemon started 21-Aug-09 13:22, 1 Job run since started.
- Heap: heap=241,664 smbytes=73,891 max_bytes=84,825 bufs=212 max_bufs=250
-
- Scheduled Jobs:
- Level Type Pri Scheduled Name Volume
- ===============================================================================
- Incremental Backup 10 21-Aug-09 23:05 Client1 cicro4
-
- Running Jobs:
- Console connected at 21-Aug-09 13:42
- No Jobs running.
- Terminated Jobs:
- JobId Level Files Bytes Status Finished Name
- ====================================================================
- 58 Incr 2 46.85 M OK 19-Aug-09 16:51 Client1
- 59 Incr 2 3.908 M OK 19-Aug-09 16:51 Client1
- 60 Incr 2 8.377 K OK 19-Aug-09 16:52 Client1
- 61 Incr 1 0 OK 19-Aug-09 16:53 Client1
- 62 Incr 2 8.344 K OK 19-Aug-09 16:53 Client1
- 63 Incr 2 8.377 K OK 19-Aug-09 16:54 Client1
- 64 3 77.44 K OK 19-Aug-09 16:57 RestoreFiles
- 65 1 0 OK 19-Aug-09 16:58 RestoreFiles
- 66 2 38.77 K OK 19-Aug-09 16:59 RestoreFiles
- 67 Full 25 145.5 M OK 21-Aug-09 13:41 Client1
-
여기서 볼 수 있듯이 JobId가 67인 백업은 완전 백업이고 백업 데이터의 파일 수는 25개이며 백업이 압축된 크기는 145.5MB이다. 백업이 완료된 것은'21-Aug-09 13:41'이고 마지막 Client1은 백업 자원의 이름이다.
2. bacula의 증량 백업 기능을 실례적으로 보여 준다.
위의 작업에서 설정된 백업 자원 Job 자체는 증량 백업이다. 아래에서 실행된 백업 작업은 위와 완전히 같다. 다른 것은 이것은 두 번째 백업이다. bacula는 설정에 따라 증량 백업을 실행한다. 다음과 같은 코드 목록은 다음과 같다.변동분 백업 수행
- * run
- Automatically selected Catalog: MyCatalog
- Using Catalog "MyCatalog"
- A job name must be specified.
- The defined Job resources are:
- 1: Client1
- 2: Client
- 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 14:20:24
- Priority: 10
- OK to run? (yes/mod/no): yes
- Job queued. JobId=68
- *status
- Status available for:
- 1: Director
- 2: Storage
- 3: Client
- 4: All
- Select daemon type for status (1-4): 1
- f10-64-build-dir Version: 3.0.2 (18 July 2009) x86_64-unknown-linux-gnu redhat
- Daemon started 21-Aug-09 13:22, 2 Jobs run since started.
- Heap: heap=241,664 smbytes=84,576 max_bytes=97,749 bufs=218 max_bufs=252
-
- Scheduled Jobs:
- Level Type Pri Scheduled Name Volume
- ===============================================================================
- Incremental Backup 10 21-Aug-09 23:05 Client1 cicro4
-
- Running Jobs:
- Console connected at 21-Aug-09 14:19
- No Jobs running.
-
- Terminated Jobs:
- JobId Level Files Bytes Status Finished Name
- ====================================================================
- 59 Incr 2 3.908 M OK 19-Aug-09 16:51 Client1
- 60 Incr 2 8.377 K OK 19-Aug-09 16:52 Client1
- 61 Incr 1 0 OK 19-Aug-09 16:53 Client1
- 62 Incr 2 8.344 K OK 19-Aug-09 16:53 Client1
- 63 Incr 2 8.377 K OK 19-Aug-09 16:54 Client1
- 64 3 77.44 K OK 19-Aug-09 16:57 RestoreFiles
- 65 1 0 OK 19-Aug-09 16:58 RestoreFiles
- 66 2 38.77 K OK 19-Aug-09 16:59 RestoreFiles
- 67 Full 25 145.5 M OK 21-Aug-09 13:41 Client1
- 68 Incr 2 3.908 M OK 21-Aug-09 14:20 Client1
-
마지막 백업 목록에서 알 수 있듯이 시스템은 증분 백업을 했고'3.908M'은 지난번 백업과 이번 백업 사이의 데이터 증가량이다.JobId=68 이 백업의 Level 레벨이 Incr인 것도 이번 백업이 증량 백업이라는 것을 설명한다.
3. bacula의 차이 백업 기능을 실례적으로 보여 준다.
차이 백업과 증량 백업의 원리는 앞에서 이미 소개했고 여기에는 구체적인 조작 절차만 제시한다.
1. 백업 시작
- *run
- Automatically selected Catalog: MyCatalog
- Using Catalog "MyCatalog"
- A job name must be specified.
- The defined Job resources are:
- 1: Client1
- 2: Client
- 3: BackupCatalog
- 4: RestoreFiles
- Select Job resource (1-4): 2 # Job ， Client1
- # ， Client
- Run Backup job
- JobName: Client
- Level: Differential
- Client: dbfd
- FileSet: dbfs
- Pool: dbpool (From Job resource)
- Storage: dbsd (From Job resource)
- When: 2009-08-21 14:31:04
- Priority: 10
- OK to run? (yes/mod/no): yes
- Job queued. JobId=69
- You have messages.
- ， ， ， 。 “status” 。
- 2．
- *status
- Status available for:
- 1: Director
- 2: Storage
- 3: Client
- 4: All
- Select daemon type for status (1-4): 1
- f10-64-build-dir Version: 3.0.2 (18 July 2009) x86_64-unknown-linux-gnu redhat
- Daemon started 21-Aug-09 14:30, 0 Jobs run since started.
- Heap: heap=253,952 smbytes=67,810 max_bytes=68,066 bufs=267 max_bufs=272
-
- Scheduled Jobs:
- Level Type Pri Scheduled Name Volume
- ===========================================================================
- Incremental Backup 10 21-Aug-09 23:05 Client1 cicro4
- Incremental Backup 10 21-Aug-09 23:05 Client cicro4
- Incremental Backup 10 21-Aug-09 23:05 BackupCatalog cicro4
-
- Running Jobs:
- Console connected at 21-Aug-09 14:30
- JobId Level Name Status
- ======================================================================
- 69 Full Client.2009-08-21_14.31.10_03 is running
- Terminated Jobs:
- JobId Level Files Bytes Status Finished Name
- ====================================================================
- 59 Incr 2 3.908 M OK 19-Aug-09 16:51 Client1
- 60 Incr 2 8.377 K OK 19-Aug-09 16:52 Client1
- 61 Incr 1 0 OK 19-Aug-09 16:53 Client1
- 62 Incr 2 8.344 K OK 19-Aug-09 16:53 Client1
- 63 Incr 2 8.377 K OK 19-Aug-09 16:54 Client1
- 64 3 77.44 K OK 19-Aug-09 16:57 RestoreFiles
- 65 1 0 OK 19-Aug-09 16:58 RestoreFiles
- 66 2 38.77 K OK 19-Aug-09 16:59 RestoreFiles
- 67 Full 25 145.5 M OK 21-Aug-09 13:41 Client1
- 68 Incr 2 3.908 M OK 21-Aug-09 14:20 Client1
- ， ， running。
- ， ：
- * status
- Status available for:
- 1: Director
- 2: Storage
- 3: Client
- 4: All
- Select daemon type for status (1-4): 1
- f10-64-build-dir Version: 3.0.2 (18 July 2009) x86_64-unknown-linux-gnu redhat
- Daemon started 21-Aug-09 14:30, 1 Job run since started.
- Heap: heap=253,952 smbytes=65,680 max_bytes=78,853 bufs=240 max_bufs=274
-
- Scheduled Jobs:
- Level Type Pri Scheduled Name Volume
- ==========================================================================
- Incremental Backup 10 21-Aug-09 23:05 Client1 cicro4
- Incremental Backup 10 21-Aug-09 23:05 Client cicro4
- Incremental Backup 10 21-Aug-09 23:05 BackupCatalog cicro4
-
- Running Jobs:
- Console connected at 21-Aug-09 14:30
- No Jobs running.
-
- Terminated Jobs:
- JobId Level Files Bytes Status Finished Name
- ====================================================================
- 60 Incr 2 8.377 K OK 19-Aug-09 16:52 Client1
- 61 Incr 1 0 OK 19-Aug-09 16:53 Client1
- 62 Incr 2 8.344 K OK 19-Aug-09 16:53 Client1
- 63 Incr 2 8.377 K OK 19-Aug-09 16:54 Client1
- 64 3 77.44 K OK 19-Aug-09 16:57 RestoreFiles
- 65 1 0 OK 19-Aug-09 16:58 RestoreFiles
- 66 2 38.77 K OK 19-Aug-09 16:59 RestoreFiles
- 67 Full 25 145.5 M OK 21-Aug-09 13:41 Client1
- 68 Incr 2 3.908 M OK 21-Aug-09 14:20 Client1
- 69 Full 26 149.4 M OK 21-Aug-09 14:32 Client
- ，JobId 69 ， ， 149.4MB， Job Client。
- 3．
- ， FD （ ， /cws3） 3.8MB 。
- * run
- A job name must be specified.
- The defined Job resources are:
- 1: Client1
- 2: Client
- 3: BackupCatalog
- 4: RestoreFiles
- Select Job resource (1-4): 2
- Run Backup job
- JobName: Client
- Level: Differential
- Client: dbfd
- FileSet: dbfs
- Pool: dbpool (From Job resource)
- Storage: dbsd (From Job resource)
- When: 2009-08-21 14:34:25
- Priority: 10
- OK to run? (yes/mod/no): yes
- Job queued. JobId=70
- *status
- Status available for:
- 1: Director
- 2: Storage
- 3: Client
- 4: All
- Select daemon type for status (1-4): 1
- f10-64-build-dir Version: 3.0.2 (18 July 2009) x86_64-unknown-linux-gnu redhat
- Daemon started 21-Aug-09 14:30, 2 Jobs run since started.
- Heap: heap=253,952 smbytes=67,989 max_bytes=81,162 bufs=240 max_bufs=274
-
- Scheduled Jobs:
- Level Type Pri Scheduled Name Volume
- ===========================================================================
- Incremental Backup 10 21-Aug-09 23:05 Client1 cicro4
- Incremental Backup 10 21-Aug-09 23:05 Client cicro4
- Incremental Backup 10 21-Aug-09 23:05 BackupCatalog cicro4
-
- Running Jobs:
- Console connected at 21-Aug-09 14:30
- No Jobs running.
-
- Terminated Jobs:
- JobId Level Files Bytes Status Finished Name
- ====================================================================
- 61 Incr 1 0 OK 19-Aug-09 16:53 Client1
- 62 Incr 2 8.344 K OK 19-Aug-09 16:53 Client1
- 63 Incr 2 8.377 K OK 19-Aug-09 16:54 Client1
- 64 3 77.44 K OK 19-Aug-09 16:57 RestoreFiles
- 65 1 0 OK 19-Aug-09 16:58 RestoreFiles
- 66 2 38.77 K OK 19-Aug-09 16:59 RestoreFiles
- 67 Full 25 145.5 M OK 21-Aug-09 13:41 Client1
- 68 Incr 2 3.908 M OK 21-Aug-09 14:20 Client1
- 69 Full 26 149.4 M OK 21-Aug-09 14:32 Client
- 70 Diff 2 3.908 M OK 21-Aug-09 14:34 Client
-
JobId가 70인 백업 정보를 통해 알 수 있듯이 이 백업은 차등 백업으로 이번에 차등 백업된 데이터의 양은 3.908MB로 앞에 추가된 파일의 크기와 거의 같다.이전에 수행한 차등 증량 백업을 증명하기 위해 FD에서 백업해야 하는 폴더 아래에 3.8MB 정도의 파일을 다시 추가하여 다음 백업 작업을 계속합니다.
- *run
- A job name must be specified.
- The defined Job resources are:
- 1: Client1
- 2: Client
- 3: BackupCatalog
- 4: RestoreFiles
- Select Job resource (1-4): 2
- Run Backup job
- JobName: Client
- Level: Differential
- Client: dbfd
- FileSet: dbfs
- Pool: dbpool (From Job resource)
- Storage: dbsd (From Job resource)
- When: 2009-08-21 14:34:59
- Priority: 10
- OK to run? (yes/mod/no): yes
- Job queued. JobId=71
- *status
- Status available for:
- 1: Director
- 2: Storage
- 3: Client
- 4: All
- Select daemon type for status (1-4): 1
- f10-64-build-dir Version: 3.0.2 (18 July 2009) x86_64-unknown-linux-gnu redhat
- Daemon started 21-Aug-09 14:30, 3 Jobs run since started.
- Heap: heap=253,952 smbytes=69,087 max_bytes=82,260 bufs=240 max_bufs=274
-
- Scheduled Jobs:
- Level Type Pri Scheduled Name Volume
- ===========================================================================
- Incremental Backup 10 21-Aug-09 23:05 Client1 cicro4
- Incremental Backup 10 21-Aug-09 23:05 Client cicro4
- Incremental Backup 10 21-Aug-09 23:05 BackupCatalog cicro4
-
- Running Jobs:
- Console connected at 21-Aug-09 14:30
- No Jobs running.
-
- Terminated Jobs:
- JobId Level Files Bytes Status Finished Name
- ====================================================================
- 62 Incr 2 8.344 K OK 19-Aug-09 16:53 Client1
- 63 Incr 2 8.377 K OK 19-Aug-09 16:54 Client1
- 64 3 77.44 K OK 19-Aug-09 16:57 RestoreFiles
- 65 1 0 OK 19-Aug-09 16:58 RestoreFiles
- 66 2 38.77 K OK 19-Aug-09 16:59 RestoreFiles
- 67 Full 25 145.5 M OK 21-Aug-09 13:41 Client1
- 68 Incr 2 3.908 M OK 21-Aug-09 14:20 Client1
- 69 Full 26 149.4 M OK 21-Aug-09 14:32 Client
- 70 Diff 2 3.908 M OK 21-Aug-09 14:34 Client
- 71 Diff 3 7.817 M OK 21-Aug-09 14:35 Client
-
JobId가 71인 백업을 통해 알 수 있듯이 이번 백업의 크기는 7.817M으로 지난번 추가 백업의 크기와 이번에 추가된 파일의 크기를 합한 것으로 차이 백업임을 증명한다.세 번째는 FD에서 백업해야 하는 폴더 아래에 3.8M 정도의 파일을 추가하여 백업 작업을 계속합니다.
- *run
- A job name must be specified.
- The defined Job resources are:
- 1: Client1
- 2: Client
- 3: BackupCatalog
- 4: RestoreFiles
- Select Job resource (1-4): 2
- Run Backup job
- JobName: Client
- Level: Differential
- Client: dbfd
- FileSet: dbfs
- Pool: dbpool (From Job resource)
- Storage: dbsd (From Job resource)
- When: 2009-08-21 14:35:32
- Priority: 10
- OK to run? (yes/mod/no): yes
- Job queued. JobId=72
- *status
- Status available for:
- 1: Director
- 2: Storage
- 3: Client
- 4: All
- Select daemon type for status (1-4): 1
- f10-64-build-dir Version: 3.0.2 (18 July 2009) x86_64-unknown-linux-gnu redhat
- Daemon started 21-Aug-09 14:30, 4 Jobs run since started.
- Heap: heap=253,952 smbytes=69,087 max_bytes=82,260 bufs=240 max_bufs=274
-
- Scheduled Jobs:
- Level Type Pri Scheduled Name Volume
- ===========================================================================
- Incremental Backup 10 21-Aug-09 23:05 Client1 cicro4
- Incremental Backup 10 21-Aug-09 23:05 Client cicro4
- Incremental Backup 10 21-Aug-09 23:05 BackupCatalog cicro4
-
- Running Jobs:
- Console connected at 21-Aug-09 14:30
- No Jobs running.
-
- Terminated Jobs:
- JobId Level Files Bytes Status Finished Name
- ====================================================================
- 63 Incr 2 8.377 K OK 19-Aug-09 16:54 Client1
- 64 3 77.44 K OK 19-Aug-09 16:57 RestoreFiles
- 65 1 0 OK 19-Aug-09 16:58 RestoreFiles
- 66 2 38.77 K OK 19-Aug-09 16:59 RestoreFiles
- 67 Full 25 145.5 M OK 21-Aug-09 13:41 Client1
- 68 Incr 2 3.908 M OK 21-Aug-09 14:20 Client1
- 69 Full 26 149.4 M OK 21-Aug-09 14:32 Client
- 70 Diff 2 3.908 M OK 21-Aug-09 14:34 Client
- 71 Diff 3 7.817 M OK 21-Aug-09 14:35 Client
- 72 Diff 4 11.72 M OK 21-Aug-09 14:35 Client
-
세 번째 백업은 JobId가 72인 백업에서 차이 백업과 증량 백업의 차이를 분명히 볼 수 있다.
본 논문 은 '기술 성취 꿈' 블로그 에서 나온 것 이니, 반드시 이 출처 를 보존해 주십시오http://ixdba.blog.51cto.com/2895551/832080
이 내용에 흥미가 있습니까?
현재 기사가 여러분의 문제를 해결하지 못하는 경우 AI 엔진은 머신러닝 분석(스마트 모델이 방금 만들어져 부정확한 경우가 있을 수 있음)을 통해 가장 유사한 기사를 추천합니다:
nginx 실전 설정: 접근 제어 및 DDOS 예방ngx_http_access_module 설정 이 허용 하 는 주소 에 접근 할 수 있 습 니 다. 금 지 된 주소 가 거부 되 었 습 니 다.이것 은 간단 한 접근 제어 일 뿐 규칙 이 많은 상황 에서 ngx 를 ...
텍스트를 자유롭게 공유하거나 복사할 수 있습니다.하지만 이 문서의 URL은 참조 URL로 남겨 두십시오.
CC BY-SA 2.5, CC BY-SA 3.0 및 CC BY-SA 4.0에 따라 라이센스가 부여됩니다.
좋은 웹페이지 즐겨찾기
