Sponsored Content
Top Forums UNIX for Dummies Questions & Answers Check that backup MX actually does its job Post 302248443 by Lazydog on Friday 17th of October 2008 04:30:21 PM
Old 10-17-2008
That would be a good way to do it.
You are then testing a real world scenario.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

backup job help

I have a backup program on my unix box. I run it manualy and normaly start it from the terminal. But i would like to be able to start it up threw a telnet session. I was told that i had to leave teh telnet setion open untel the backup was complete, cuase if i closed the telnet the process would... (1 Reply)
Discussion started by: Thump
1 Replies

2. Shell Programming and Scripting

Backup with shell program and cron job.

Hi, The object of my program is to take automatic backup on daily basis to different folders. I have created the respective folders. when I execute below given shell program manually it is working perfectly and taking the backup to respective folder. #!/bin/sh #script to take backup on... (1 Reply)
Discussion started by: jarkvarma
1 Replies

3. UNIX for Dummies Questions & Answers

Check backup file size on backup tape

Hi, I performed backup on tape and I want to append more files to my previous backup on the same backup tape. But before I do that I need to know the backup file size of the first backup I performed so that I know the available size on the backup tape. Can someone help me what command I will use... (0 Replies)
Discussion started by: ayhanne
0 Replies

4. UNIX for Dummies Questions & Answers

Showing a daily backup job from a unique log file.

Hi guys, I´m a newbie in Linux, but I´m trying to solve some problems studying on my own, but I´ve had some problems with AWK. Look, I have one single backup log file per server and I want to make a daily delection from the last backup job to show in a intranet of my work. The log files are from... (0 Replies)
Discussion started by: metalfreakbr
0 Replies

5. UNIX for Dummies Questions & Answers

To check, a table is used in a job

Hi, I have a list of jobs scheduled in unix. I want to check whether a particular view or table is used in a job. If they are not used, I can make changes to them. Thanks, Raaga (2 Replies)
Discussion started by: Raaga
2 Replies

6. Shell Programming and Scripting

check mail backup cron job

i have just installed a cron job to run at 3 in the morning once a week. It's difficult for me to test if it works because the email backup program takes the email service down before running the backup. I wondered if i could ask you gurus if this would work? 0 3 * * 0 ... (1 Reply)
Discussion started by: timgolding
1 Replies

7. UNIX for Advanced & Expert Users

Check the status of job

Hi, I have master job which will run based on the sub jobs status. In the master job I am giving the condition like, condition: s(sub_job) f(sub_job) This scenario will work if the sub job status is success or failed. but I want to run my master job even if the sub_job was... (1 Reply)
Discussion started by: Kattoor
1 Replies

8. Programming

Refire a backup job.

how to code script using shell scripting to refire a backup job if it fails with an error code of 196? (1 Reply)
Discussion started by: Pawan Ramnani
1 Replies

9. Shell Programming and Scripting

To refire a backup job using shell scripting..........

how to write a code using shell scripting to refire a back up job if it fails with an error code of 196? (7 Replies)
Discussion started by: Pawan Ramnani
7 Replies

10. Shell Programming and Scripting

CRON JOB not running - for tape backup from root user

I am trying a cron on root user to backup to tape using TAR command here is the cron entry 11 08 * * 6 /erdhot1cron 2>&1 >> /test3/scripts/dba/erdhot1cron.log here is script inside - edhot1cron #!/bin/bash vsysdt=`date +%d%m%y` date tar -cvf /dev/st0... (4 Replies)
Discussion started by: vijaymec50
4 Replies
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)
All times are GMT -4. The time now is 06:57 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy