diff --git a/data/kybackup/en_US/image/1-a.png b/data/kybackup/en_US/image/1-a.png new file mode 100644 index 0000000..7d47dc9 Binary files /dev/null and b/data/kybackup/en_US/image/1-a.png differ diff --git a/data/kybackup/en_US/image/1-b.png b/data/kybackup/en_US/image/1-b.png new file mode 100644 index 0000000..4588ccf Binary files /dev/null and b/data/kybackup/en_US/image/1-b.png differ diff --git a/data/kybackup/en_US/image/10.png b/data/kybackup/en_US/image/10.png new file mode 100644 index 0000000..ec0862e Binary files /dev/null and b/data/kybackup/en_US/image/10.png differ diff --git a/data/kybackup/en_US/image/11.png b/data/kybackup/en_US/image/11.png new file mode 100644 index 0000000..13b1b4b Binary files /dev/null and b/data/kybackup/en_US/image/11.png differ diff --git a/data/kybackup/en_US/image/12.png b/data/kybackup/en_US/image/12.png new file mode 100644 index 0000000..48cd710 Binary files /dev/null and b/data/kybackup/en_US/image/12.png differ diff --git a/data/kybackup/en_US/image/13-1.png b/data/kybackup/en_US/image/13-1.png new file mode 100644 index 0000000..53f9462 Binary files /dev/null and b/data/kybackup/en_US/image/13-1.png differ diff --git a/data/kybackup/en_US/image/13-2.png b/data/kybackup/en_US/image/13-2.png new file mode 100644 index 0000000..5340da8 Binary files /dev/null and b/data/kybackup/en_US/image/13-2.png differ diff --git a/data/kybackup/en_US/image/13.png b/data/kybackup/en_US/image/13.png new file mode 100644 index 0000000..fd997d7 Binary files /dev/null and b/data/kybackup/en_US/image/13.png differ diff --git a/data/kybackup/en_US/image/14.png b/data/kybackup/en_US/image/14.png new file mode 100644 index 0000000..856761c Binary files /dev/null and b/data/kybackup/en_US/image/14.png differ diff --git a/data/kybackup/en_US/image/15.png b/data/kybackup/en_US/image/15.png new file mode 100644 index 0000000..06fdd9c Binary files /dev/null and b/data/kybackup/en_US/image/15.png differ diff --git a/data/kybackup/en_US/image/2.png b/data/kybackup/en_US/image/2.png new file mode 100644 index 0000000..81eaf01 Binary files /dev/null and b/data/kybackup/en_US/image/2.png differ diff --git a/data/kybackup/en_US/image/3-1.png b/data/kybackup/en_US/image/3-1.png new file mode 100644 index 0000000..6807b4a Binary files /dev/null and b/data/kybackup/en_US/image/3-1.png differ diff --git a/data/kybackup/en_US/image/3-2.png b/data/kybackup/en_US/image/3-2.png new file mode 100644 index 0000000..071171d Binary files /dev/null and b/data/kybackup/en_US/image/3-2.png differ diff --git a/data/kybackup/en_US/image/3.png b/data/kybackup/en_US/image/3.png new file mode 100644 index 0000000..ab09fc9 Binary files /dev/null and b/data/kybackup/en_US/image/3.png differ diff --git a/data/kybackup/en_US/image/4.png b/data/kybackup/en_US/image/4.png new file mode 100644 index 0000000..6d2e433 Binary files /dev/null and b/data/kybackup/en_US/image/4.png differ diff --git a/data/kybackup/en_US/image/5.png b/data/kybackup/en_US/image/5.png new file mode 100644 index 0000000..cb2e289 Binary files /dev/null and b/data/kybackup/en_US/image/5.png differ diff --git a/data/kybackup/en_US/image/6-a.png b/data/kybackup/en_US/image/6-a.png new file mode 100644 index 0000000..be02b53 Binary files /dev/null and b/data/kybackup/en_US/image/6-a.png differ diff --git a/data/kybackup/en_US/image/6-b.png b/data/kybackup/en_US/image/6-b.png new file mode 100644 index 0000000..a4b4420 Binary files /dev/null and b/data/kybackup/en_US/image/6-b.png differ diff --git a/data/kybackup/en_US/image/7.png b/data/kybackup/en_US/image/7.png new file mode 100644 index 0000000..78ce049 Binary files /dev/null and b/data/kybackup/en_US/image/7.png differ diff --git a/data/kybackup/en_US/image/8.png b/data/kybackup/en_US/image/8.png new file mode 100644 index 0000000..97dcaf9 Binary files /dev/null and b/data/kybackup/en_US/image/8.png differ diff --git a/data/kybackup/en_US/image/9.png b/data/kybackup/en_US/image/9.png new file mode 100644 index 0000000..c7b75da Binary files /dev/null and b/data/kybackup/en_US/image/9.png differ diff --git a/data/kybackup/en_US/index.md b/data/kybackup/en_US/index.md new file mode 100644 index 0000000..ca29c75 --- /dev/null +++ b/data/kybackup/en_US/index.md @@ -0,0 +1,148 @@ +# Backup and Recovery +## Overview +Kylin Backup and Recovery Tool is used to backup and restore system or user data. + +It supports to create new backup points, and incremental backup based on a backup point; as well as restore the system to the state at the time of a backup, and partial restore retaining user data. + +There are three modes: General, Grub backup and restore, LiveCD restore. + +
+ +## General +### System Backup + +![Fig 1-a system backup-big](image/1-a.png) + + +- **New System Backup** -- Backup the whole system except the backup partition and the data partition. + +After selecting "New System Backup", click "Backup" and there will pop up a box allowing users to specify backup device those need to be ignored during backup, as shown in Fig 2. + +![Fig 2 system backup device choose -big](image/2.png) + +After clicking "Ok" to backup, the system will chech whether the backup partition has enough space for this operation. If no, it will pop up an +error reporting window; Conversely, it will pop up prompt in turn, as shown in Fig 3. + +![Fig 3-1 Backup prompt-big](image/3-1.png) + +![Fig 3-2 Backup prompt-big](image/3-2.png) + +Click "Continue" to create a new backup in the backup partition. During backup, there will show a window as shown in Fig 4. The length of backup time depends on the size of backup contents. + +![Fig 4 Backup now -big](image/4.png) + +The button "Backup Management" near "Backup" is used to view the state of system backups and delete invalid backups. + +![Fig 5 Backup Management-big](image/5.png) + +- **Update System Backup** -- Continue backup based on a existed backup. + +After selecting this function, there will pop up a window to show all backups. Users can choose one from them. + +Incremental backup can be performed on the basis of a failed backup. + +### System Restore +System restore can restore the system to its previous backup state. + +![Fig 6-a system restore-big](image/6-a.png) + +### Data Backup and Data Recovery +- **Data Backup** -- Backup the directories or files specified by user, and the function is similar to system backup. + +![Fig 8 Data backup-big](image/8.png) + +After selecting "New Data Backup", click "Backup" and there will pop up a box allowing users to specify directories or files those need to be backuped. As shown in Fig 9, it will backup the contents in /home/kylin/. + +![Fig 9 Specify directories or files -big](image/9.png) + +The button "Backup Management" near "Backup" is used to view the state of data backups and delete invalid backups. + +- **Update Data Backup** -- Add new data to a existed data backup. + +- **Data Recovery** -- Recovery the data to its previous backup state, and the function is similar to system restore. + +![Fig 10 Data recovery-big](image/10.png) + +The system will restart automatically after recovery is complete. + +### Log Records +Record all operations on backup and recovery tool, and the interface as shown in Fig 11. Turn pages by clicking "Up" and "Next" button. + +![Fig 11 Log records-big](image/11.png) + +### Ghost Image +Install from ghost image means generate an image file from an installed system, and then use this image file to copy the same state system to other computers. To use this function, a backup is needed first. + +#### Create Ghost Image +The interface as shown in Fig 12, including some tips. + +![Fig 12 Ghost image-big](image/12.png) + +Click "Ghost" and there will pop up a window to show all backups. Users select one of them and click "Ok" to start creating, as shown in Fig 13. + +(Tips: The architecture in name depends on hardware platform.) + +![Fig 13-1 Ghost image select and create-big](image/13-1.png) + +![Fig 13-2 Ghost image select and create-big](image/13-2.png) + +Image filename is "computer name + architecture + backup name.kyimg", and only numbers in the backup name are retained. + +#### Install from Ghost Image +1) Copy the ghost image (saved in /ghost) to U-disk or other removable storage device. + +2) Enter livecd system and insert the removable device. + +3) If it doesn't mount automatically, users can manually mount device through terminal: + +sudo mount /dev/sdb1 /mnt + +Removable device is /dev/sdb1 by general, and it can be seen by command "fdisk -l". + +4) Double click the install button to start installation guide. Select "Install from ghost image" in Installation Type, and find the ghost image in the removable device, as shown in Fig 14. The follow-up steps can refer to installation manual. + +(Tips: The architecture in name depends on hardware platform.) + +![Fig 14 Ghost install-big](image/14.png) + +If there exists data partition when creating ghost image file, it needs to check "Create Data Partition" in the next step. + +
+ +## Grub Backup and Recovery + +(Tips: The date and time in the figure is for reference only.) + +1) Select "Backup and Restore" in grub menu when start-up. + +2) Backup or restore are both allowed to select here. If there is an error, restart the system and try again. + +- Backup mode: The system will start to backup immediately and the prompt will display on the screen. + +For backup mode, is smilar to "Whole Disk Backup" in general mode. If there is no enough space, the backup will fail. + +- Restore mode: The system will start to restore to the lastest successful backup state, and the prompt will display on the screen. + +For restore mode, is smilar to "Disk Restore" in general mode. If there is no successful backup, the system will not be restored. + +
+ +## LiveCD Restore +Enter livecd system and click Start Menu to open the application, as shown in Fig 15. + +![Fig 15 Interface in LiveCD-big](image/15.png) + +System restore an log records can refer to the function in general mode. + +
+ +## Q&A +### Can not use backup and recovery tool +In order to use this tool, "Create Backup Partition" must be checked when install system. + +
+ +### Backup data/backup partition is allowed? +The contents in data partition are not important to system and have a large capacity, so it's not necessary to backup /data. + +Backup partition is used to save and recovery other partitions data, so /backup is not allowed to be backuped or restored. diff --git a/data/kybackup/kybackup.png b/data/kybackup/kybackup.png new file mode 100644 index 0000000..317c4c4 Binary files /dev/null and b/data/kybackup/kybackup.png differ diff --git a/data/kybackup/zh_CN/image/1-a.png b/data/kybackup/zh_CN/image/1-a.png new file mode 100644 index 0000000..12feef9 Binary files /dev/null and b/data/kybackup/zh_CN/image/1-a.png differ diff --git a/data/kybackup/zh_CN/image/1-b-1.png b/data/kybackup/zh_CN/image/1-b-1.png new file mode 100644 index 0000000..13d5c16 Binary files /dev/null and b/data/kybackup/zh_CN/image/1-b-1.png differ diff --git a/data/kybackup/zh_CN/image/1-b.png b/data/kybackup/zh_CN/image/1-b.png new file mode 100644 index 0000000..13d5c16 Binary files /dev/null and b/data/kybackup/zh_CN/image/1-b.png differ diff --git a/data/kybackup/zh_CN/image/10.png b/data/kybackup/zh_CN/image/10.png new file mode 100644 index 0000000..84ae4a4 Binary files /dev/null and b/data/kybackup/zh_CN/image/10.png differ diff --git a/data/kybackup/zh_CN/image/11.png b/data/kybackup/zh_CN/image/11.png new file mode 100644 index 0000000..f496e1b Binary files /dev/null and b/data/kybackup/zh_CN/image/11.png differ diff --git a/data/kybackup/zh_CN/image/12.png b/data/kybackup/zh_CN/image/12.png new file mode 100644 index 0000000..b47a7f5 Binary files /dev/null and b/data/kybackup/zh_CN/image/12.png differ diff --git a/data/kybackup/zh_CN/image/13-1.png b/data/kybackup/zh_CN/image/13-1.png new file mode 100644 index 0000000..710883f Binary files /dev/null and b/data/kybackup/zh_CN/image/13-1.png differ diff --git a/data/kybackup/zh_CN/image/13-2.png b/data/kybackup/zh_CN/image/13-2.png new file mode 100644 index 0000000..eb7daf0 Binary files /dev/null and b/data/kybackup/zh_CN/image/13-2.png differ diff --git a/data/kybackup/zh_CN/image/13.png b/data/kybackup/zh_CN/image/13.png new file mode 100644 index 0000000..0ef30b4 Binary files /dev/null and b/data/kybackup/zh_CN/image/13.png differ diff --git a/data/kybackup/zh_CN/image/14.png b/data/kybackup/zh_CN/image/14.png new file mode 100644 index 0000000..a66e4c6 Binary files /dev/null and b/data/kybackup/zh_CN/image/14.png differ diff --git a/data/kybackup/zh_CN/image/15.png b/data/kybackup/zh_CN/image/15.png new file mode 100644 index 0000000..19690f0 Binary files /dev/null and b/data/kybackup/zh_CN/image/15.png differ diff --git a/data/kybackup/zh_CN/image/2.png b/data/kybackup/zh_CN/image/2.png new file mode 100644 index 0000000..37d8289 Binary files /dev/null and b/data/kybackup/zh_CN/image/2.png differ diff --git a/data/kybackup/zh_CN/image/3-1.png b/data/kybackup/zh_CN/image/3-1.png new file mode 100644 index 0000000..96358fc Binary files /dev/null and b/data/kybackup/zh_CN/image/3-1.png differ diff --git a/data/kybackup/zh_CN/image/3-2.png b/data/kybackup/zh_CN/image/3-2.png new file mode 100644 index 0000000..92100c8 Binary files /dev/null and b/data/kybackup/zh_CN/image/3-2.png differ diff --git a/data/kybackup/zh_CN/image/3.png b/data/kybackup/zh_CN/image/3.png new file mode 100644 index 0000000..55e9b0e Binary files /dev/null and b/data/kybackup/zh_CN/image/3.png differ diff --git a/data/kybackup/zh_CN/image/4.png b/data/kybackup/zh_CN/image/4.png new file mode 100644 index 0000000..92148c3 Binary files /dev/null and b/data/kybackup/zh_CN/image/4.png differ diff --git a/data/kybackup/zh_CN/image/5.png b/data/kybackup/zh_CN/image/5.png new file mode 100644 index 0000000..2e99f69 Binary files /dev/null and b/data/kybackup/zh_CN/image/5.png differ diff --git a/data/kybackup/zh_CN/image/6-a.png b/data/kybackup/zh_CN/image/6-a.png new file mode 100644 index 0000000..d8d7846 Binary files /dev/null and b/data/kybackup/zh_CN/image/6-a.png differ diff --git a/data/kybackup/zh_CN/image/6-b.png b/data/kybackup/zh_CN/image/6-b.png new file mode 100644 index 0000000..782f6ea Binary files /dev/null and b/data/kybackup/zh_CN/image/6-b.png differ diff --git a/data/kybackup/zh_CN/image/7.png b/data/kybackup/zh_CN/image/7.png new file mode 100644 index 0000000..43f91b1 Binary files /dev/null and b/data/kybackup/zh_CN/image/7.png differ diff --git a/data/kybackup/zh_CN/image/8.png b/data/kybackup/zh_CN/image/8.png new file mode 100644 index 0000000..8a00e9f Binary files /dev/null and b/data/kybackup/zh_CN/image/8.png differ diff --git a/data/kybackup/zh_CN/image/9.png b/data/kybackup/zh_CN/image/9.png new file mode 100644 index 0000000..e6a9baa Binary files /dev/null and b/data/kybackup/zh_CN/image/9.png differ diff --git a/data/kybackup/zh_CN/index.md b/data/kybackup/zh_CN/index.md new file mode 100644 index 0000000..1a14c81 --- /dev/null +++ b/data/kybackup/zh_CN/index.md @@ -0,0 +1,135 @@ +# 备份还原 +## 概 述 +备份还原用于对系统或用户数据进行备份和还原。该工具支持新建备份点，也支持在某个备份点上进行增量备份；支持将系统还原到某次备份时的状态，或者在保留某些数据的情况下进行部分还原。 + +备份还原有3种模式：常规模式、Grub备份还原、LiveCD还原。 + +
+ +## 常规模式 +### 系统备份 + +![图 1-a 系统备份-big](image/1-a.png) + + +- **新建系统备份** —— 将除备份还原分区、数据分区外的整个系统进行备份。 + +选择新建后，点击 “开始备份” ，会弹出一个对话框，供用户指定设备进行系统备份，如图2所示。 + +![图 2 系统备份设备选择 -big](image/2.png) + +当确定进入备份时，系统查找备份还原分区是否有足够的空间来进行本次备份。若没有足够空间，则会有报错弹窗；若有足够空间，则会依次给出提示。 + +![图 3-1 备份提示-big](image/3-1.png) +![图 3-2 备份提示-big](image/3-2.png) + +按“继续”按钮，则会在备份还原分区上新建一个备份。在备份过程中，会有如下所示的提示框。备份时间长短与备份内容大小有关。 + +![图 4 正在备份 -big](image/4.png) + +系统备份标签页中“开始备份”旁边的“备份管理”，可用来查看系统备份状态，删除无效备份。 + +![图 5 系统备份管理-big](image/5.png) + +- **系统增量备份** —— 在一个已有备份的基础上，继续进行备份。 + +当选择增量备份后，会弹出一个列出了所有备份的对话框，供用户选择。 + +可以在失败的备份基础上进行增量备份。 + +### 系统还原 +“系统还原” 可将系统还原到以前一个备份时的状态。 + +![图 6-a 系统还原-big](image/6-a.png) + + +点击“一键还原”，会弹出一个对话框，供用户指定在还原过程中需要忽略的分区、目录或文件，如图7所示。还原成功后，系统会自动重启。 + +### 数据备份与数据还原 +- **数据备份** —— 对用户指定的目录或文件进行备份，功能与系统备份相似。 + +![图 8 数据备份主界面-big](image/8.png) + +选择“新建数据备份”后，点击“开始备份”，会弹出一个对话框，供用户指定需要备份的目录或文件，如图9所示，会对 /home/kylin/ 目录中的内容进行备份。 + +![图 9 指定数据备份目录 -big](image/9.png) + +“开始备份”旁边的“备份管理”，可用来查看数据备份状态，删除无效备份。 + +- **数据增量备份** —— 在某个数据备份的基础上，增加需要备份的数据。 + +- **数据还原** —— 还原到某个数据备份的状态，功能与系统还原相似。 + +![图 10 数据还原主界面-big](image/10.png) + +完成还原后，系统会自动重启。 + +### 操作日志 +记录了在备份还原上的所有操作，主界面如图所示。可通过“上一页” 、“下一页”按钮进行翻页查看。 + +![图 11 操作日志主界面-big](image/11.png) + +### Ghost镜像 +Ghost镜像安装，是指将一台机器上的系统生成一个镜像文件，然后使用该镜像文件来安装操作系统。要使用该功能，首先需要有一个备份。 + +#### 创建Ghost镜像 +选择菜单“Ghost镜像”，如图12所示。 + +![图 12 Ghost镜像主界面-big](image/12.png) + +点击“一键Ghost”后，会弹出当前所有备份的列表；用户选择一个备份，点击“确定”后，开始制作Ghost镜像。镜像文件名的格式为“主机名+体系架构+备份名称.kyimg”；其中，备份名称只保留了数字。 + +如图13所示。 + +![图 13-1 Ghost镜像选择制作-big](image/13-1.png) +![图 13-2 Ghost镜像选择制作-big](image/13-2.png) + +#### 安装Ghost镜像 +1）把制作好的Ghost镜像（存在于“/ghost”目录下）拷贝到U盘等可移动存储设备。 + +2）进入Live系统后，接入可移动设备。 + +3）若设备没有自动挂载，可通过终端，手动将设备挂载到/mnt目录下： + +“sudo mount /dev/sdb1 /mnt” + +通常情况下，移动设备为/dev/sdb1，可使用命令“fdisk -l”查看。 + +4）双击安装图标，开始安装引导。在“安装方式”中选择“从Ghost镜像安装”，并找到移动设备中的Ghost镜像文件。后续步骤可参考“系统安装”部分。 + +![图 14 Ghost安装-big](image/14.png) + +Tips：如果制作镜像文件时带有数据盘，则在下一步“安装类型”中也要勾选“创建数据盘”。 + +
+ +## Grub备份还原 +1）开机启动系统时，在Grub菜单选择系统备份还原模式。 + +2）备份模式：系统立即开始备份，屏幕上会给出提示。 + +对于备份模式而言，等同于常规模式下的“新建系统备份”。如果备份还原分区没有足够空间，则无法成功备份。 + +3）还原模式：系统立即开始还原到最近一次的成功备份状态，屏幕上会给出提示。 + +对于还原模式而言，等同于常规模式下的“一键还原”。如果备份还原分区上没有一个成功的备份，则系统不能被还原。 + +
+ +## LiveCD还原 +通过系统启动盘进入操作系统后，从开始菜单打开麒麟备份还原，主界面如图15所示。 + +![图 15 LiveCD还原主界面-big](image/15.png) + +系统还原和操作日志可参考常规模式下的对应功能。 + +
+ +## 常见问题 +### 无法使用备份还原 +在安装操作系统时，必须要选中“创建备份还原分区”，备份还原才能使用。 + +### 可以对data分区和backup分区进行备份吗？ +数据分区（/data）保存的内容与系统关系不大，且通常容量很大，因此不建议对数据分区进行备份和还原。 + +备份还原分区（/backup）用于保存和恢复其他分区的数据，故此分区的数据不允许备份或还原。