When I got a new laptop last spring, I used my restore process to load everything onto the new box. After those first efforts, I use the backups to get a single file from 3 months ago or a directory from yesterday or to restore a complete system after a do-release-upgrade fails. It took about 5 times to get everything correct to ensure I had enough, but didn't waste too much storage with totally unnecessary files. Restoring each system takes about 30-45 minutes. The local, daily, versioned, backups for each system take between 30 seconds and 25 minutes according to the summary report I get daily. This my my 3-2-1 backup solution.ģ copies, 2 locations, 1 on different media. Daily change data is fairly small, so that usually finishes in less than 2 hrs. With rsync, I can control the bandwidth used, so other WAN users don't notice it. No offsite copies.ĭaily, I rsync the backup areas offsite. I create a list of manually installed package and use that list to feed back during the restore. That means I don't backup /lib/ or /bin/ or /usr/ (except /usr/local/). I do not backup everything on the system, just what is needed to restore everything so it works the same. Each of the details I mention above are important parts of the solution to address risks. It can only run 1 command, limited by the ssh authorized_hosts settings. I use a root-equiv backup userid to make the rdiff-backup connections. Those scripts generate information about each system and place that data into a place that gets included in the daily backups. There are pre-backup and post-backup scripts that get run remotely over ssh. It "pulls" backups using a tool called rdiff-backup. I'm fairly skilled, so some of my methods wouldn't be useful to someone without at least intermediate Unix skills and understanding. Thanks for the help.I'm backing up about 15-20 systems, so what I do might not be good for a 1-computer setup. If you have a particular solution you prefer (cloud service vs local NAS, etc.), I'd be glad to hear it. I'm definitely convinced after this experience. Serial: 86af5768-140d-7a46-ab6c-af126b90db1fĬapabilities: boot precious readonly hidden nomount ntfs initializedĬonfiguration: clustersize=4096 created= 22:23:20 filesystem=ntfs label=WinRE_DRV modified_by_chkdsk=true mounted_on_nt4=true name=Basic data partition resize_log_file=true state=dirty upgrade_on_mount=trueAttempting to mount the drive renders the following: Serial: 6cac19d2-6b53-4a9d-b0e9-ce94f9578585Ĭapabilities: nofs precious readonly hidden nomountĬonfiguration: name=Microsoft reserved partitionĬonfiguration: FATs=0 filesystem=fat name=Basic data partition
Capabilities: gpt-1.00 partitioned partitioned:gptĬonfiguration: ansiversion=6 guid=c8ad4bab-b428-4c5f-bbb3-d096af4a67dc logicalsectorsize=512 sectorsize=512Ĭapabilities: boot precious readonly hidden nomount fat initializedĬonfiguration: FATs=2 filesystem=fat label=SYSTEM name=EFI system partition
0 kommentar(er)
