Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
backup [2017/05/15 11:59] 127.0.0.1 external edit |
backup [2021/06/03 19:48] (current) |
||
|---|---|---|---|
| Line 101: | Line 101: | ||
| **3.** Perform an initial backup. | **3.** Perform an initial backup. | ||
| + | <WRAP indent> | ||
| The first backup is the largest and slowest backup because it is copying everything over to your backup drive. Subsequent backups will be much much smaller, because it will only copy changes to that base layer. | The first backup is the largest and slowest backup because it is copying everything over to your backup drive. Subsequent backups will be much much smaller, because it will only copy changes to that base layer. | ||
| Line 114: | Line 115: | ||
| <code> | <code> | ||
| - | $ rdiff-backup --terminal-verbosity 8 --print-statistics --exclude-globbing-filelist /home/klaatu/.excludes /home/klaatu/ /safehouse/klaatuWork/ | + | $ rdiff-backup --terminal-verbosity 8 --print-statistics \ |
| + | --exclude-globbing-filelist /home/klaatu/.excludes /home/klaatu/ \ | ||
| + | /safehouse/klaatuWork/ | ||
| </code> | </code> | ||
| Line 124: | Line 127: | ||
| <code> | <code> | ||
| - | $ rdiff-backup --terminal-verbosity 8 --print-statistics --exclude-globbing-filelist /home/klaatu/.excludes /home/klaatu/ klaatu@10.1.1.11::/safehouse/klaatuWork/ | + | $ rdiff-backup --terminal-verbosity 8 --print-statistics \ |
| + | --exclude-globbing-filelist /home/klaatu/.excludes /home/klaatu/ \ | ||
| + | klaatu@10.1.1.11::/safehouse/klaatuWork/ | ||
| </code> | </code> | ||
| Line 213: | Line 218: | ||
| <code> | <code> | ||
| - | #!/usr/bin/bash | + | #!/bin/sh |
| - | echo $date > /tmp/udev.log | + | date > /tmp/udev.log |
| </code> | </code> | ||
| Line 240: | Line 245: | ||
| With ''udevadm'' monitor running, plug in your backup drive and watch as all kinds of information is spewed out onto your screen. Notice, particularly, that the type of event is an ''ADD'' event. That's a good way of identifying what type of event we want. | With ''udevadm'' monitor running, plug in your backup drive and watch as all kinds of information is spewed out onto your screen. Notice, particularly, that the type of event is an ''ADD'' event. That's a good way of identifying what type of event we want. | ||
| - | The ''udevadm'' monitor provides a lot of good info, but we can see it with prettier formatting with the command ''udevadm info'', assuming you know where your drive is currently located in your ''dev'' tree. If not, unplug and then plug your thumbdrive back in and then immediately issue this command: | + | The ''udevadm'' monitor provides a lot of good info, but we can see it with prettier formatting with the command ''udevadm info -a -n'', assuming you know where your drive is currently located in your ''dev'' tree. If not, unplug and then plug your thumbdrive back in and then immediately issue this command: |
| <code> | <code> | ||
| Line 254: | Line 259: | ||
| This will return a wealth of information. Focus on the first block of info, first. | This will return a wealth of information. Focus on the first block of info, first. | ||
| - | The feedback from ''udevadm info'' starts with the device specified by the ''devpath'', and then walks up the chain of parent devices. It prints for every device found, all possible attributes in the ''udev'' rules key format. | + | The feedback from ''udevadm info -a -n'' starts with the device specified by the ''devpath'', and then walks up the chain of parent devices. It prints for every device found, all possible attributes in the ''udev'' rules key format. |
| A ''udev'' rule must contain one attribute from one single "parent" device; parent attributes are things that describe a device from the most basic level, such as "it's something that has been plugged into a physical port" or "it is something with a size of XX" or "this is a removable device". | A ''udev'' rule must contain one attribute from one single "parent" device; parent attributes are things that describe a device from the most basic level, such as "it's something that has been plugged into a physical port" or "it is something with a size of XX" or "this is a removable device". | ||
| - | That info, just under the ''udevadm info'' introductory paragraph, looks a little something like this: | + | That info, just under the ''udevadm info -a -n'' introductory paragraph, looks a little something like this: |
| <code> | <code> | ||