Sponsored Content
Full Discussion: Crontab backup
Top Forums UNIX for Dummies Questions & Answers Crontab backup Post 81529 by blowtorch on Monday 22nd of August 2005 03:54:15 AM
Old 08-22-2005
I think that the OP wants to backup the crontab files for every user every day. This would be as simple as doing a 'cp -p' of the crontab files. Use the following script:

Code:
today=$(date +%Y%m%d)
mkdir /some_backup_dir/$today
cp -p /var/spool/cron/crontabs/* /some_backup_dir/$today

Maintain the following cron entry in root's crontab:

00 01 * * * /full_path_of_script/whatever_you_call_this_script
 

9 More Discussions You Might Find Interesting

1. 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

2. SCO

copy crontab file from backup server

Hi, I did a terrible mistake of issuing crontab -r command which deleted my table on a new installation. Is there any way i can transfer the table from an existing unix box. Regards, Joseph:confused: (4 Replies)
Discussion started by: njoroge
4 Replies

3. AIX

about backup with crontab

dear all! i'm a newbie to this forum as well as aix. i'm using aix version 6.1 by ssh remote with no GUI. i'm using crontab for scheduling backup with "backup" command too. i've created an entry in crontab file to backup some files daily. everything works well. but i've got a question: how can... (8 Replies)
Discussion started by: unknown_man
8 Replies

4. Solaris

Automatic backup through DD and crontab

Hi, I have not been working with Solaris for more than 10 years ago. Many things and details have ben forgotten. Hopes that some could help me with the problem. We used this scripts (below) for daily backup. The problems is following: I want to backup all partions/slice on a specific... (4 Replies)
Discussion started by: gjh
4 Replies

5. Shell Programming and Scripting

rsync backup mode(--backup) Are there any options to remove backup folders on successful deployment?

Hi Everyone, we are running rsync with --backup mode, Are there any rsync options to remove backup folders on successful deployment? Thanks in adv. (0 Replies)
Discussion started by: MVEERA
0 Replies

6. UNIX for Advanced & Expert Users

Backup of crontab itself

Hi all What is the best way of making backups (daily or week basis) of a crontab file? Scenario: one userid, acessed by a number of analysts, that has a crontab file contantly updated. It's a large file, with hundreds of entries. Sometimes somebody deletes an entry that shoudn't be deleted.... (2 Replies)
Discussion started by: kzpchn
2 Replies

7. Shell Programming and Scripting

Help with Backup Shell Script for Network Device Configuration backup

HI all, im new to shell scripting. need your guidence for my script. i wrote one script and is attached here Im explaining the requirement of script. AIM: Shell script to run automatically as per scheduled and backup few network devices configurations. Script will contain a set of commands... (4 Replies)
Discussion started by: saichand1985
4 Replies

8. UNIX for Dummies Questions & Answers

Schedule backup with crontab/tar

Hello all, I am a complete newbie to Unix and therefor also to this forum. I have an assignment for Uni, and need your help to understand something. I need to use crontab and tar to schedule a weekly backup of a folder and its contents. I want the tarball to be stored in the users/float... (6 Replies)
Discussion started by: Float
6 Replies

9. Shell Programming and Scripting

Take backup of scripts listed in crontab

Hi, I'm trying to take backups of script files listed in cron tab but,my cron entry has value like this 10 3 * * * /usr/sbin/logadm 15 3 * * 0 /usr/lib/fs/nfs/nfsfind 30 3 * * * && /usr/lib/gss/gsscred_clean #10 3 * * * /usr/lib/krb5/kprop_script ___slave_kdcs___ 00,15,30,45 * * * *... (1 Reply)
Discussion started by: Sivarajan N
1 Replies
CRONTAB(1)							   User Commands							CRONTAB(1)

NAME
crontab - maintains crontab files for individual users SYNOPSIS
crontab [-u user] file crontab [-u user] [-l | -r | -e] [-i] [-s] crontab -n [ hostname ] crontab -c DESCRIPTION
Crontab is the program used to install, remove or list the tables used to serve the cron(8) daemon. Each user can have their own crontab, and though these are files in /var/spool/, they are not intended to be edited directly. For SELinux in MLS mode, you can define more crontabs for each range. For more information, see selinux(8). In this version of Cron it is possible to use a network-mounted shared /var/spool/cron across a cluster of hosts and specify that only one of the hosts should run the crontab jobs in the particular directory at any one time. You may also use crontab(1) from any of these hosts to edit the same shared set of crontab files, and to set and query which host should run the crontab jobs. Running cron jobs can be allowed or disallowed for different users. For this purpose, use the cron.allow and cron.deny files. If the cron.allow file exists, a user must be listed in it to be allowed to use cron If the cron.allow file does not exist but the cron.deny file does exist, then a user must not be listed in the cron.deny file in order to use cron. If neither of these files exists, only the super user is allowed to use cron. Another way to restrict access to cron is to use PAM authentication in /etc/security/access.conf to set up users, which are allowed or disallowed to use crontab or modify system cron jobs in the /etc/cron.d/ directory. The temporary directory can be set in an environment variable. If it is not set by the user, the /tmp directory is used. OPTIONS
-u Appends the name of the user whose crontab is to be modified. If this option is not used, crontab examines "your" crontab, i.e., the crontab of the person executing the command. Note that su(8) may confuse crontab, thus, when executing commands under su(8) you should always use the -u option. If no crontab exists for a particular user, it is created for him the first time the crontab -u command is used under his username. -l Displays the current crontab on standard output. -r Removes the current crontab. -e Edits the current crontab using the editor specified by the VISUAL or EDITOR environment variables. After you exit from the editor, the modified crontab will be installed automatically. -i This option modifies the -r option to prompt the user for a 'y/Y' response before actually removing the crontab. -s Appends the current SELinux security context string as an MLS_LEVEL setting to the crontab file before editing / replacement occurs - see the documentation of MLS_LEVEL in crontab(5). -n This option is relevant only if cron(8) was started with the -c option, to enable clustering support. It is used to set the host in the cluster which should run the jobs specified in the crontab files in the /var/spool/cron directory. If a hostname is supplied, the host whose hostname returned by gethostname(2) matches the supplied hostname, will be selected to run the selected cron jobs subsequently. If there is no host in the cluster matching the supplied hostname, or you explicitly specify an empty hostname, then the selected jobs will not be run at all. If the hostname is omitted, the name of the local host returned by gethostname(2) is used. Using this option has no effect on the /etc/crontab file and the files in the /etc/cron.d directory, which are always run, and considered host-specific. For more information on clustering support, see cron(8). -c This option is only relevant if cron(8) was started with the -c option, to enable clustering support. It is used to query which host in the cluster is currently set to run the jobs specified in the crontab files in the directory /var/spool/cron , as set using the -n option. SEE ALSO
crontab(5), cron(8) FILES
/etc/cron.allow /etc/cron.deny STANDARDS
The crontab command conforms to IEEE Std1003.2-1992 (``POSIX''). This new command syntax differs from previous versions of Vixie Cron, as well as from the classic SVR3 syntax. DIAGNOSTICS
An informative usage message appears if you run a crontab with a faulty command defined in it. AUTHOR
Paul Vixie <vixie@isc.org> Colin Dean <colin@colin-dean.org> cronie 2012-11-22 CRONTAB(1)
All times are GMT -4. The time now is 09:37 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy