kind.8 3.5 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151
  1. .ds d \-\^\-
  2. .ds o \fR[\fP
  3. .ds c \fR]\fP
  4. .ds | \fR|\fP
  5. .de D
  6. \\.B \*d\\$1
  7. ..
  8. .de DI
  9. \\.BI \*d\\$1 \\$2
  10. ..
  11. .de DR
  12. \\.BR \*d\\$1 \\$2
  13. ..
  14. .de Di
  15. \\.BI \*d\\$1 " \\$2"
  16. ..
  17. .de Db
  18. \\.B \*d\\$1 " \\$2"
  19. ..
  20. .de Df
  21. \\.B \*d\*ono\*c\\$1
  22. ..
  23. .de See
  24. See \fB\\$1\fP for details.
  25. ..
  26. .de SeeIn
  27. See \fB\\$1\fP in \fB\\$2\fP for details.
  28. ..
  29. .de multiple
  30. Multiple \fB\*d\\$1\fP values will accumulate.
  31. ..
  32. .de default
  33. Default value: \fB\\$1\fP
  34. ..
  35. .TH KIND 8
  36. .SH NAME
  37. kind \- kind is no dirvish
  38. .SH SYNOPSIS
  39. .B kind
  40. [
  41. .I OPTIONS
  42. ]
  43. .I vault
  44. .SH DESCRIPTION
  45. .P
  46. Create a backup image of a client directory tree.
  47. .P
  48. Each image is a directory containing transfer
  49. .BR rsync-log,
  50. .B tree
  51. and if errors were detected an
  52. .B error
  53. file.
  54. The
  55. .B rsync-log
  56. retains the the output of rsync listing all files that were changed or added with some statistical information.
  57. Tree is the copy of the client tree.
  58. .P
  59. The client directory tree is compared with an existing image
  60. to create a new image.
  61. Unchanged files are shared between images.
  62. For changed files
  63. only those parts that actually change are transfered over the network.
  64. Unchanged portions of files are copied from the reference image.
  65. .P
  66. The resulting images contain complete copies of the original trees
  67. preserving ownership and file permissions.
  68. In this way even though the backups are made incrementally,
  69. each image can be used independently for restores
  70. or to make removable-media off-site copies or archives.
  71. .P
  72. The removal of an image will have no effect on other images.
  73. .P
  74. After backup all images of the vault are checked and expired images
  75. are removed
  76. .SH OPTIONS
  77. .P
  78. Each option may be unambiguously abbreviated.
  79. .TP
  80. .Di masterconfig config-file
  81. Load general options from the specified file. Default is /etc/d2/master.conf.
  82. Configuration values from this file may be overwritten by the vault config
  83. files. The master config file must contain at least the specification of
  84. the banks
  85. .TP
  86. .D full
  87. Create a full image without using a reference image. This is neccesary
  88. for the first backup.
  89. .TP
  90. .D dryrun
  91. Don't actually do anything.
  92. Process all configuration files, options and tests
  93. then produce a summary on standard output and exit.
  94. .TP
  95. .D backuponly
  96. Only backup, no expire
  97. .TP
  98. .D expireonly
  99. Only expire, no backup
  100. .TP
  101. .D version
  102. Print version string and exit.
  103. .SH EXIT CODES
  104. kind returns 0 in case of no error.
  105. .SH FILES
  106. .TP
  107. .IB /etc/d2/ master.conf
  108. Default master configuration file.
  109. .TP
  110. .IB bank/vault/d2/ vault.conf
  111. Default vault configuration file.
  112. .TP
  113. .IB bank/vault/ last
  114. Symlink to last image
  115. .TP
  116. .IB bank/vault/image/ error
  117. Exists in case of error. May contain an error message.
  118. .TP
  119. .IB bank/vault/image/ rsync-log
  120. Output of rsync command.
  121. .TP
  122. .IB bank/vault/image/ tree
  123. actual image of source directory tree.
  124. .SH SEE ALSO
  125. .nf
  126. ssh(1)
  127. rsync(1)
  128. .SH AUTHOR
  129. kind was created by Wolfgang Ortmann.
  130. .SH BUGS AND ISSUES
  131. In order to preserve permissions
  132. it is necessary for kind to run as root
  133. on the backup server.
  134. For an automated backup process the root user must have
  135. non-interactive ssh access to the client systems.
  136. It is not necessary that this access be as the root user on the client.
  137. File ownership is preserved using numeric values
  138. so it is not necessary to have user accounts on the backup server.
  139. Making the vaults network accessible
  140. using protocols that map UIDs based on names instead of number
  141. could allow access controls on files to be violated.
  142. Making the vaults writable by users will compromise the integrity
  143. of the backups.
  144. Therefore any access to the vaults by users
  145. should be done through a read-only mount.