Man page or keyword search:   man All Sections 1 - General Commands 2 - System Calls 3 - Subroutines, Functions 4 - Special Files 5 - File Formats 6 - Games and Screensavers 7 - Macros and Conventions 8 - Maintenence Commands 9 - Kernel Interface New Commands Server 4.4BSD AIX Alpinelinux Archlinux Aros BSDOS BSDi Bifrost CentOS Cygwin Darwin Debian DigitalUNIX DragonFly ElementaryOS Fedora FreeBSD Gentoo GhostBSD HP-UX Haiku Hurd IRIX Inferno JazzOS Kali Knoppix LinuxMint MacOSX Mageia Mandriva Manjaro Minix MirBSD NeXTSTEP NetBSD OPENSTEP OSF1 OpenBSD OpenDarwin OpenIndiana OpenMandriva OpenServer OpenSuSE OpenVMS Oracle PC-BSD Peanut Pidora Plan9 QNX Raspbian RedHat Scientific Slackware SmartOS Solaris SuSE SunOS Syllable Tru64 UNIXv7 Ubuntu Ultrix UnixWare Xenix YellowDog aLinux   44335 pages apropos Keyword Search (all sections) Output format html ascii pdf view pdf save postscript

SNAP(8)			  BSD System Manager's Manual		       SNAP(8)

NAME
     snap — FreeBSD UFS2 Snapshot Management Tool

SYNOPSIS
     snap [-p] [-m] [-h] [-c config_file] [filesystem ...]

DESCRIPTION
     You can use the snap utility to periodically create new snapshots while
     rotating the olds.	 It can also be used to manually create snapshots.

     The options are as follows:

     -p	     Perform periodic task. It can only be used on the hour, otherwise
	     nothing will happen.  If “atHour” is given in the configuration
	     file, then snap will only run on the specified hour.  When this
	     flag is not given, it is considered as a manual snapshot cre‐
	     ation.

     -m	     List manually created snapshots and then exit.

     -h	     Show the help message.

     -c config_file
	     Specify the pathname of an alternative configuration file; The
	     default is /usr/local/etc/snap.conf.

     The snap utility reads its configuration file when it starts up.  If
     filesystems are given and corresponding entries in the configuration file
     can be found, snap will only handle these filesystems and ignore their
     “enable” flag in the configuration file.

     All snapshot files are created with the local creation time as their
     filename.	In periodic maintaining task, three types of periodic snap‐
     shots, namely, hourly, daily, and weekly, are created and rotated accord‐
     ing to the settings in the configuration file.  They are also hard-linked
     to “nicknames”, for example, the last hourly snapshot is hard-linked to
     hour.0.

EXAMPLES
     The following command creates snapshots manually according to the config‐
     uration file.

	   snap

     To perform periodic maintaining, invoke snap in /etc/crontab as

	   0 * * * * root /path/to/snap -p

     since periodic maintaining requires to be performed on the hour.

     To manually create snapshots on filesystem / and /home and /var only:

	   snap / /home /var

     This command will ignore the “enable” flag in the configuration file.
     If, say, /var is not found in the configuration file, nothing would hap‐
     pen.

     We can list manual created snapshots on filesystems / and /home:

	   snap -m / /home

     or also specify an alternative path for the configuration file:

	   snap -m -c /tmp/gg/snap.conf / /home

FILES
     /usr/local/etc/snap.conf  configuration file
     hour.0		       last hourly snapshot
     daily.0		       last daily snapshot
     week.0		       last weekly snapshot

SEE ALSO
     mount(8), crontab(5), mdconfig(8), snapshot(8)

AUTHORS
     This manual page was written by Wu Chin-Hao wchunhao@cs.nctu.edu.tw.

BSD				  May 6, 2007				   BSD

Vote for polarhome