This blog describes Time Slider, a new feature in OpenSolaris 2008.11. Time slider provides an automatic way to backup your data on the same disc using one of Sun's ZFS file system's unique features, snapshots. With Time Slider, you can browse and recover files from snapshot backups using the GNOME file manager.
I created a zpool and in it there is a zfs volume. I used that to backup data on another server using ISCSI. Now I have the data and want to take a snapshot so that I can view it on another machine that is not in production.
Here is what I have done
# zfs snapshot mat/vol_1@snap1
# zfs list -t... (6 Replies)
I have installed Solaris 11 Express on my server and want to set up automatic backuping using zfs snapshots. In the backup script I need to find out the name of the last snapshot of the given filesystem (in order to refer to it as the startpoint of an incremental backup). What is the best way to do... (4 Replies)
Hi, I deleted a zfs snapshot because it was as big as the original zfs. After the snapshot was removed, all the data in the original zfs is gone. How this happened? Can I restore the snapshot? Please help. Thanks a lot! (5 Replies)
I saved one of my zfs snapshot on the remote machine with following command. And now i want to restore the same snapshot to original server how can i receive it on the original server from backup server.
#zfs send rpool/ROOT/sol10_patched@preConfig | ssh x.x.x.x zfs receive... (1 Reply)
I 've a weired situation .. my system has zfs root as its file system and now root file system is full at 100%
# zfs list
NAME USED AVAIL REFER MOUNTPOINT
rpool 134G 65.2M 94K /rpool
rpool/ROOT ... (1 Reply)
Hi,
I am working on Network Management Software product. This is supported both windows and solaris platform. I need to take the snapshot of the solaris server ( which installed our product), like vmware in windows.
I think using ZFS files system, we can take the snapshot in solaris 10 but... (2 Replies)
Hi,
I am working on Network Management Software product. This is supported both windows and solaris platform. I need to take the snapshot of the solaris server ( which installed our product), like vmware in windows.
I think using ZFS files system, we can take the snapshot in solaris... (1 Reply)
backintime(1) USER COMMANDS backintime(1)NAME
backintime - a simple backup tool for Linux.
This is command line tool. The graphical tools are: backintime-gnome and backintime-kde4.
SYNOPSIS
backintime [ --backup | --backup-job | --snapshots-path | --snapshots-list | --snapshots-list-path | --last-snapshot | --last-snapshot-path
| --help | --version | --license ]
DESCRIPTION
Back In Time is a simple backup tool for Linux. The backup is done by taking snapshots of a specified set of folders.
All you have to do is configure: where to save snapshots, what folders to backup. You can also specify a backup schedule: disabled, every
5 minutes, every 10 minutes, every hour, every day, every week, every month. To configure it use one of the graphical interfaces available
(backintime-gnome or backintime-kde4).
It acts as a 'user mode' backup tool. This means that you can backup/restore only folders you have write access to (actually you can backup
read-only folders, but you can't restore them).
If you want to run it as root you need to use 'su'.
A new snapshot is created only if something changed since the last snapshot (if any).
A snapshot contains all the files from the selected folders (except for exclude patterns). In order to reduce disk space it use hard-links
(if possible) between snapshots for unchanged files. This way a file of 10Mb, unchanged for 10 snapshots, will use only 10Mb on the disk.
When you restore a file 'A', if it already exists on the file system it will be renamed to 'A.backup.currentdate'.
For automatic backup it use 'cron' so there is no need for a daemon, but 'cron' must be running.
user-callback
During backup process the application can call a user callback at different steps. This callback is "$XDG_CONFIG_HOME/backintime/user-
callback" (by default $XDG_CONFIG_HOME is ~/.config).
The first argument is the progile id (1=Main Profile, ...).
The second argument is the progile name.
The third argument is the reason:
1 Backup process begins.
2 Backup process ends.
3 A new snapshot was taken. The extra arguments are snapshot ID and snapshot path.
4 There was an error. The second argument is the error code.
Error codes:
1 The application is not configured.
2 A "take snapshot" process is already running.
3 Can't find snapshots folder (is it on a removable drive ?).
4 A snapshot for "now" already exist.
OPTIONS -b, --backup
take a snapshot now (if needed)
--backup-job
take a snapshot (if needed) depending on schedule rules (used for cron jobs)
--snapshots-path
display path where is saves the snapshots (if configured)
--snapshots-list
display the list of snapshot IDs (if any)
--snapshots-list-path
display the paths to snapshots (if any)
--last-snapshot
display last snapshot ID (if any)
--last-snapshot-path
display the path to the last snapshot (if any)
-h, --help
display a short help
-v, --version
show version
--license
show license
SEE ALSO
backintime-gnome, backintime-kde4.
Back In Time also has a website: http://backintime.le-web.org
AUTHOR
This manual page was written by BIT Team (<bit-team@lists.launchpad.net>).
version 1.0.10 Mars 2009 backintime(1)