Guest User

backup-manager.conf

a guest
Jul 8th, 2014
1,316
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
  1.  
  2. # Backup Manager Configuration File
  3. #
  4. # * This configuration file is divided into sections.
  5. # The 'global' section is mandatory, every keys defined in
  6. # this section are inherited in the other sections.
  7. # * There is one section per "backup method", you have to
  8. # fill the section of the chosen method.
  9. #
  10. ##############################################################
  11.  
  12. ##############################################################
  13. # Repository - everything about where archives are
  14. #############################################################
  15.  
  16. # Where to store the archives
  17. export BM_REPOSITORY_ROOT="/mnt/hubic/default"
  18.  
  19. # Where to place temporary files
  20. export BM_TEMP_DIR="/tmp"
  21.  
  22. # For security reasons, the archive repository and the generated
  23. # archives will be readable/writable by a given user/group.
  24. # This is recommended to set this to true.
  25. export BM_REPOSITORY_SECURE="true"
  26.  
  27. # The repository will be readable/writable only by a specific
  28. # user:group pair if BM_REPOSITORY_SECURE is set to true.
  29. export BM_REPOSITORY_USER="root"
  30. export BM_REPOSITORY_GROUP="root"
  31. # You can also choose the permission to set the repository, default
  32. # is 770, pay attention to what you do there!
  33. export BM_REPOSITORY_CHMOD="770"
  34.  
  35. ##############################################################
  36. # Archives - let's focus on the precious tarballs...
  37. ##############################################################
  38.  
  39. # Each archive generated will be chmoded for security reasons
  40. # (BM_REPOSITORY_SECURE should be enabled for this).
  41. export BM_ARCHIVE_CHMOD="660"
  42.  
  43. # Number of days we have to keep an archive (Time To Live)
  44. export BM_ARCHIVE_TTL="5"
  45.  
  46. # Do you want to purge only the top-level directory or all
  47. # directories under BM_REPOSITORY_ROOT?
  48. export BM_REPOSITORY_RECURSIVEPURGE="false"
  49.  
  50. # Do you want to replace duplicates by symlinks?
  51. # (archive-DAY is a duplicate of archive-(DAY - 1) if they
  52. # are both the same according to MD5 hashes).
  53. export BM_ARCHIVE_PURGEDUPS="true"
  54.  
  55. # Prefix of every archive on that box (default is HOSTNAME)
  56. export BM_ARCHIVE_PREFIX="$HOSTNAME"
  57.  
  58. # Should we purge only archives built with $BM_ARCHIVE_PREFIX
  59. export BM_ARCHIVE_STRICTPURGE="true"
  60.  
  61. # You may want to nice the commands run for archive-creation
  62. # (Recommanded for desktop users.)
  63. # Choose a nice level from -20 (most favorable scheduling) to 19 (least favorable).
  64. export BM_ARCHIVE_NICE_LEVEL="10"
  65.  
  66. # The backup method to use.
  67. # Available methods are:
  68. # - tarball
  69. # - tarball-incremental
  70. # - mysql
  71. # - pgsql
  72. # - svn
  73. # - pipe
  74. # - none
  75. # If you don't want to use any backup method (you don't want to
  76. # build archives) then choose "none"
  77. export BM_ARCHIVE_METHOD="tarball"
  78.  
  79. ##############################################################
  80. # Encryption - because you cannot trust the place your
  81. # archives are
  82. ##############################################################
  83.  
  84. # If you want to encrypt your archives locally, Backup Manager
  85. # can use GPG while building the archive (so the archive is never
  86. # written to the disk without being encrypted.
  87.  
  88. # Note: this feature is only possible with the following archive types:
  89. # tar, tar.gz, tar.bz2
  90.  
  91. # Uncomment the following line if you want to enable encryption
  92. # available method: gpg
  93. export BM_ENCRYPTION_METHOD="false"
  94.  
  95. # The encryption will be made using a GPG ID
  96. # Examples:
  97. # export BM_ENCRYPTION_RECIPIENT=""
  98. # export BM_ENCRYPTION_RECIPIENT=""
  99. export BM_ENCRYPTION_RECIPIENT=""
  100.  
  101.  
  102. ##############################################################
  103. # Section "TARBALL"
  104. # - Backup method: tarball
  105. #############################################################
  106.  
  107. # Archive filename format
  108. # long : host-full-path-to-folder.tar.gz
  109. # short : parentfolder.tar.gz
  110. export BM_TARBALL_NAMEFORMAT="short"
  111.  
  112. # Type of archives
  113. # Available types are:
  114. # tar, tar.gz, tar.bz2, tar.lz, dar, zip.
  115. # Make sure to satisfy the appropriate dependencies
  116. # (bzip2, dar, lzma, ...).
  117. export BM_TARBALL_FILETYPE="tar.gz"
  118.  
  119. # You can choose to build archives remotely over SSH.
  120. # You will then need to fill the BM_UPLOAD_SSH variables
  121. # (BM_UPLOAD_SSH_HOSTS, BM_UPLOAD_SSH_USER, BM_UPLOAD_SSH_KEY).
  122. # If this boolean is set to true, archive will be saved locally (in
  123. # BM_REPOSITORY_ROOT but will be built by the remote host).
  124. # Thus, BM_TARBALL_DIRECTORIES will be used to backup remote directories.
  125. # Those archive will be prefixed with the remote host name.
  126. export BM_TARBALL_OVER_SSH="false"
  127.  
  128. # Do you want to dereference the files pointed by symlinks ?
  129. # enter true or false (true can lead to huge archives, be careful).
  130. export BM_TARBALL_DUMPSYMLINKS="false"
  131.  
  132. # Targets to backup
  133.  
  134. # You can use two different variables for defining the targets of
  135. # your backups, either a simple space-separated list (BM_TARBALL_DIRECTORIES)
  136. # or an array (BM_TARBALL_TARGETS[]).
  137. # Use the first one for simple path that doesn't contain spaces in their name.
  138. # Use the former if you want to specify paths to backups with spaces.
  139.  
  140. # It's recommanded to use BM_TARBALL_TARGETS[] though.
  141. # Warning! You *must not* use both variables at the same time.
  142. # NOTE: The Debian package will only update BM_TARBALL_DIRECTORIES
  143.  
  144. # Paths without spaces in their name:
  145. export BM_TARBALL_DIRECTORIES="/etc /home /var/lib/mysql /var/spool/vmail /var/www /root"
  146.  
  147. # If one or more of the targets contain a space, use the array:
  148. # declare -a BM_TARBALL_TARGETS
  149. # BM_TARBALL_TARGETS[0]="/etc"
  150. # BM_TARBALL_TARGETS[1]="/boot"
  151. # export BM_TARBALL_TARGETS
  152.  
  153. # Files to exclude when generating tarballs, you can put absolute
  154. # or relative paths, Bash wildcards are possible.
  155. export BM_TARBALL_BLACKLIST="/var/bak /var/www/stock/downloads *.mp3 *.avi *.rar *.zip *.mp4 *.ogg *.sql *.tgz *.mpg *.log *.7z *.mkv *.nfo *.MKV *.AVI *.MP4 *.bsp *nav *.kv"
  156.  
  157. # With the "dar" filetype, you can choose a maximum slice limit.
  158. export BM_TARBALL_SLICESIZE="1000M"
  159.  
  160. # Extra options to append to the tarball generation
  161. # (take care to what you do; this will be silently added to the
  162. # command line.)
  163. export BM_TARBALL_EXTRA_OPTIONS=""
  164.  
  165. ##############################################################
  166. # The tarball-incremental method uses the same keys as the
  167. # tarball method, plus two others.
  168. #############################################################
  169.  
  170. # Which frequency to use for the master tarball?
  171. # possible values: weekly, monthly
  172. export BM_TARBALLINC_MASTERDATETYPE="weekly"
  173.  
  174. # Number of the day, in the BM_TARBALLINC_MASTERDATETYPE frequency
  175. # when master tarballs should be made
  176. export BM_TARBALLINC_MASTERDATEVALUE="1"
  177.  
  178. # Examples: you want to make master tarballs every friday:
  179. # BM_TARBALLINC_MASTERDATETYPE="weekly"
  180. # BM_TARBALLINC_MASTERDATEVALUE="5"
  181. #
  182. # Or every first day of the month:
  183. # BM_TARBALLINC_MASTERDATETYPE="monthly"
  184. # BM_TARBALLINC_MASTERDATEVALUE="1"
  185.  
  186. ##############################################################
  187. # Backup method: MYSQL
  188. #############################################################
  189.  
  190. # This method is dedicated to MySQL databases.
  191. # You should not use the tarball method for backing up database
  192. # directories or you may have corrupted archives.
  193. # Enter here the list of databases to backup.
  194. # Wildcard: __ALL__ (will dump all the databases in one archive)
  195. export BM_MYSQL_DATABASES="__ALL__"
  196.  
  197. # The best way to produce MySQL dump is done by using the "--opt" switch
  198. # of mysqldump. This make the dump directly usable with mysql (add the drop table
  199. # statements), lock the tables during the dump and other things.
  200. # This is recommended for full-clean-safe backups, but needs a
  201. # privileged user (for the lock permissions).
  202. export BM_MYSQL_SAFEDUMPS="true"
  203.  
  204. # The user who is allowed to read every databases filled in BM_MYSQL_DATABASES
  205. export BM_MYSQL_ADMINLOGIN="root"
  206.  
  207. # its password
  208. export BM_MYSQL_ADMINPASS=""
  209.  
  210. # the host where the database is
  211. export BM_MYSQL_HOST="localhost"
  212.  
  213. # the port where MySQL listen to on the host
  214. export BM_MYSQL_PORT="3306"
  215.  
  216. # which compression format to use? (gzip or bzip2)
  217. export BM_MYSQL_FILETYPE="bzip2"
  218.  
  219. # Extra options to append to mysqldump
  220. # (take care to what you do; this will be silently added to the
  221. # command line.)
  222. export BM_MYSQL_EXTRA_OPTIONS=""
  223.  
  224. ##############################################################
  225. # Backup method: PostgreSQL
  226. #############################################################
  227.  
  228. # This method is dedicated to PostgreSQL databases.
  229. # You should not use the tarball method for backing up database
  230. # directories or you may have corrupted archives.
  231. # Enter here the list of databases to backup.
  232. # Wildcard: __ALL__ (will dump all the databases in one archive)
  233. export BM_PGSQL_DATABASES="__ALL__"
  234.  
  235. # The user who is allowed to read every databases filled in BM_PGSQL_DATABASES
  236. export BM_PGSQL_ADMINLOGIN="root"
  237.  
  238. # its password
  239. export BM_PGSQL_ADMINPASS=""
  240.  
  241. # the host where the database is
  242. export BM_PGSQL_HOST="localhost"
  243.  
  244. # the port where PostgreSQL listen to on the host
  245. export BM_PGSQL_PORT="5432"
  246.  
  247. # which compression format to use? (gzip or bzip2)
  248. export BM_PGSQL_FILETYPE="bzip2"
  249.  
  250. # Extra options to append to pg_dump
  251. # (take care to what you do; this will be silently added to the
  252. # command line.)
  253. export BM_PGSQL_EXTRA_OPTIONS=""
  254.  
  255. ##############################################################
  256. # Backup method: svn
  257. #############################################################
  258.  
  259. # Absolute paths to the svn repositories to archive
  260. export BM_SVN_REPOSITORIES=""
  261.  
  262. # You can compress the resulting XML files
  263. # Supported compressor are: bzip2 and gzip
  264. export BM_SVN_COMPRESSWITH="bzip2"
  265.  
  266. ##############################################################
  267. # Backup method: pipe
  268. #############################################################
  269.  
  270. # The "pipe" method is a generic way of making archive.
  271. # Its concept is simple, for every kind of archive you want
  272. # to make, you give: a command which will send output on stdout,
  273. # a name, a file type and optionnaly, a compressor.
  274.  
  275. # Be careful, this feature uses arrays!
  276. declare -a BM_PIPE_COMMAND
  277. declare -a BM_PIPE_NAME
  278. declare -a BM_PIPE_FILETYPE
  279. declare -a BM_PIPE_COMPRESS
  280.  
  281. # You can virtually implement whatever backup scenario you like
  282. # with this method.
  283. #
  284. # The resulting archives will be named like this:
  285. # $BM_ARCHIVE_PREFIX-$BM_PIPE_NAME.$DATE.$BM_PIPE_FILETYPE
  286. # If you specified a BM_PIPE_COMPRESS option, the resulting filename
  287. # will change as expected (eg, .gz if "gzip").
  288. #
  289. # Here are a couple of examples for using this method:
  290.  
  291. # Archive a remote MySQL database through SSH:
  292. # BM_PIPE_COMMAND[0]="ssh host -c \"mysqldump -ufoo -pbar base\""
  293. # BM_PIPE_NAME[0]="base"
  294. # BM_PIPE_FILETYPE[0]="sql"
  295. # BM_PIPE_COMPRESS[0]="gzip"
  296. # This will make somthing like: localhost-base.20050421.sql.gz
  297.  
  298. # Archive a specific directory, on a remote server through SSH:
  299. # BM_PIPE_COMMAND[0]="ssh host -c \"tar -c -z /home/user\""
  300. # BM_PIPE_NAME[0]="host.home.user"
  301. # BM_PIPE_FILETYPE[0]="tar.gz"
  302. # BM_PIPE_COMPRESS[0]=""
  303. # This will make somthing like: localhost-host.home.user.20050421.tar.gz
  304.  
  305. export BM_PIPE_COMMAND
  306. export BM_PIPE_NAME
  307. export BM_PIPE_FILETYPE
  308. export BM_PIPE_COMPRESS
  309.  
  310. ##############################################################
  311. # Section "UPLOAD"
  312. # You can upload archives to remote hosts with different
  313. # methods.
  314. #############################################################
  315.  
  316. # Which method to use for uploading archives, you can put
  317. # multiple methods here.
  318. # Available methods:
  319. # - scp
  320. # - ssh-gpg
  321. # - ftp
  322. # - rsync
  323. # - s3
  324. # - none
  325.  
  326. # If you don't want to use any upload method (you don't want to
  327. # upload files to remote hosts) then choose "none"
  328. export BM_UPLOAD_METHOD="none"
  329.  
  330. # where to upload (global to all methods. Not required to be set for S3)
  331. export BM_UPLOAD_HOSTS=""
  332.  
  333. # Where to put archives on the remote hosts (global)
  334. export BM_UPLOAD_DESTINATION="/var/archives/uploads"
  335.  
  336. # Uncomment the 'export ...' line below to activate the uploaded archives
  337. # database.
  338. # Using the database will avoid extraneous uploads to remote hosts in the
  339. # case of running more than one backup-manager jobs per day (such as when
  340. # you are using different configuration files for different parts of your
  341. # filesystem).
  342. # Note that when you upload to multiple hosts, a single succesfull upload
  343. # will mark the archive as uploaded. Thus upload errors to specific hosts
  344. # will have to be resolved manually.
  345. # You can specify any filename, but it is recommended to keep the database
  346. # inside the archive repository. The variable's value has been preset to
  347. # that.
  348. #export BM_UPLOADED_ARCHIVES=${BM_REPOSITORY_ROOT}/${BM_ARCHIVE_PREFIX}-uploaded.list
  349.  
  350. ##############################################################
  351. # The SSH method
  352. #############################################################
  353.  
  354. # the user to use for the SSH connections/transfers
  355. export BM_UPLOAD_SSH_USER="bmngr"
  356.  
  357. # The private key to use for opening the connection
  358. export BM_UPLOAD_SSH_KEY=""
  359.  
  360. # specific ssh hosts
  361. export BM_UPLOAD_SSH_HOSTS=""
  362.  
  363. # port to use for SSH connections (leave blank for default one)
  364. export BM_UPLOAD_SSH_PORT=""
  365.  
  366. # destination for ssh uploads (overrides BM_UPLOAD_DESTINATION)
  367. export BM_UPLOAD_SSH_DESTINATION=""
  368.  
  369. # purge archives on remote hosts before uploading?
  370. export BM_UPLOAD_SSH_PURGE="true"
  371.  
  372. # If you set BM_UPLOAD_SSH_PURGE, you can specify a time to live
  373. # for archives uploaded with SSH.
  374. # This can let you use different ttl's locally and remotely
  375. # By default, BM_ARCHIVE_TTL will be used.
  376. export BM_UPLOAD_SSH_TTL=""
  377.  
  378. ##############################################################
  379. # The SSH-GPG method
  380. # The ssh-gpg method uses the same configuration keys as the
  381. # ssh method, plus one other
  382. #############################################################
  383.  
  384. # The gpg public key used for encryption, this can be a short
  385. # or long key id, or a descriptive name. See gpg man page for
  386. # all possibilities how to specify a key.
  387. export BM_UPLOAD_SSHGPG_RECIPIENT=""
  388.  
  389. ##############################################################
  390. # The FTP method
  391. #############################################################
  392.  
  393. # Use FTP secured transfers (FTP over TLS)
  394. # User, password and data will be uploaded encrypted with SSL.
  395. # Passive mode will be automaticaly activated
  396. export BM_UPLOAD_FTP_SECURE="false"
  397.  
  398. # Do you want to use FTP passive mode?
  399. # This is mandatory for NATed/firewalled environments
  400. export BM_UPLOAD_FTP_PASSIVE="true"
  401.  
  402. # Test the FTP connection before starting archives upload.
  403. # This will enable BM to try sending a 2MB test file before
  404. # sending any archive
  405. export BM_UPLOAD_FTP_TEST="false"
  406.  
  407. # the user to use for the FTP connections/transfers
  408. export BM_UPLOAD_FTP_USER=""
  409.  
  410. # the FTP user's password
  411. export BM_UPLOAD_FTP_PASSWORD=""
  412.  
  413. # FTP specific remote hosts
  414. export BM_UPLOAD_FTP_HOSTS=""
  415.  
  416. # purge archives on remote hosts before uploading?
  417. export BM_UPLOAD_FTP_PURGE="true"
  418.  
  419. # You can specify a time to live for archives uploaded with FTP
  420. # This can let you use different ttl's locally and remotely
  421. # By default, BM_ARCHIVE_TTL will be used.
  422. export BM_UPLOAD_FTP_TTL=""
  423.  
  424. # destination for FTP uploads (overrides BM_UPLOAD_DESTINATION)
  425. export BM_UPLOAD_FTP_DESTINATION=""
  426.  
  427.  
  428. ##############################################################
  429. # The S3 method
  430. #############################################################
  431.  
  432. # The Amazon S3 method requires that you secure an S3
  433. # account. See http://aws.amazon.com
  434.  
  435. # The bucket to upload to. This bucket must be dedicated to backup-manager
  436. export BM_UPLOAD_S3_DESTINATION=""
  437.  
  438. # the S3 access key provided to you
  439. export BM_UPLOAD_S3_ACCESS_KEY=""
  440.  
  441. # the S3 secret key provided to you
  442. export BM_UPLOAD_S3_SECRET_KEY=""
  443.  
  444. # purge archives on remote hosts before uploading?
  445. export BM_UPLOAD_S3_PURGE="false"
  446.  
  447. ##############################################################
  448. # The RSYNC method
  449. #############################################################
  450.  
  451. # Which directories should be backuped with rsync
  452. export BM_UPLOAD_RSYNC_DIRECTORIES=""
  453.  
  454. # Destination for rsync uploads (overrides BM_UPLOAD_DESTINATION)
  455. export BM_UPLOAD_RSYNC_DESTINATION=""
  456.  
  457. # The list of remote hosts, if you want to enable the upload
  458. # system, just put some remote hosts here (fqdn or IPs)
  459. # Leave it empty if you want to use the hosts that are defined in
  460. # BM_UPLOAD_HOSTS
  461. export BM_UPLOAD_RSYNC_HOSTS=""
  462.  
  463. # Do you want to dereference the files pointed by symlinks?
  464. # enter true or false (true can lead to huge archives, be careful).
  465. export BM_UPLOAD_RSYNC_DUMPSYMLINKS="false"
  466.  
  467. ##############################################################
  468. # Section "BURNING"
  469. # - Automatic CDR/CDRW/DVDR burning
  470. #############################################################
  471.  
  472. # the method of burning archives from the list :
  473. # - DVD : burn archives on a DVD medium
  474. # (that doesn't need formatting, like DVD+RW).
  475. #
  476. # - DVD-RW : blank the DVD medium and burn archives
  477. # (recommanded for DVD-RW media).
  478. #
  479. # - CDRW : blank the CDRW and burn the whole
  480. # ARCHIVES_REPOSITORY or only
  481. # the generated archives.
  482. #
  483. # - CDR : burn the whole ARCHIVES_REPOSITORY or
  484. # only the generated archives.
  485. # - none : disable the burning system
  486. #
  487. # Note that if backup-manager is run from interactive prompt you
  488. # will be asked to insert disc(s) when needed
  489.  
  490. export BM_BURNING_METHOD="none"
  491.  
  492. # When the CD is burnt, it is possible to check every file's
  493. # MD5 checksum to see if the CD is not corrupted.
  494. export BM_BURNING_CHKMD5="false"
  495.  
  496. # The device to use for mounting the cdrom
  497. export BM_BURNING_DEVICE="/dev/cdrom"
  498.  
  499. # You can force cdrecord to use a specific device
  500. # Fill in the full path to the device to use or even
  501. # e.g. BM_BURNING_DEVFORCED="/dev/cdrom"
  502. # If none specified, the default cdrecord device will be used.
  503. export BM_BURNING_DEVFORCED=""
  504.  
  505. # By default backup-manager will make Joliet media (using the mkisofs switches
  506. # : "-R -J"). You can change these if you want to use non-Joliet disc images.
  507. # Change this only if you know what you're doing. Refer to mkisofs(8) for
  508. # details.
  509. export BM_BURNING_ISO_FLAGS="-R -J"
  510.  
  511. # enter here the max size of your media
  512. # (usal sizes are 4200 for DVD media and 700 or 800 for CDR media)
  513. export BM_BURNING_MAXSIZE="650"
  514.  
  515.  
  516. ##############################################################
  517. # Advanced settings, use this with care.
  518. #############################################################
  519.  
  520. # Every output made can be sent to syslog
  521. # set this to "true" or "false"
  522. export BM_LOGGER="true"
  523.  
  524. # Which level of messages do you want to log to syslog?
  525. # possible values are : debug,info,warning,error
  526. export BM_LOGGER_LEVEL="warning"
  527.  
  528. # You can choose which facility to use
  529. export BM_LOGGER_FACILITY="user"
  530.  
  531. # Enter here some shell script.
  532. # It will be executed before the first action of backup-manager.
  533. export BM_PRE_BACKUP_COMMAND=""
  534.  
  535. # Enter here some shell script.
  536. # It will be executed after the last action of backup-manager.
  537. export BM_POST_BACKUP_COMMAND=""
RAW Paste Data