1. The problem statement, all variables and given/known data:
Description
Bsafe The command creates a backup directory of each month at the command line (arguments of the script). The names of directories to copy will always be specified for the home user. To save copies of the script uses a specific directory, now called the backup directory. If the backup directory does not exist, the script should create it. Within the backup directory, the script should create a directory for each backup done (use a different name every time). Within this directory (the copy of the instant), each directory passed as argument of the script should be copied, including sub-directories and files, preserving dates and times of access and modification of them. Of course, the backup directory should not be copied into itself.
2. Relevant commands, code, scripts, algorithms:
3. The attempts at a solution (include all code and scripts):
the command, need create a backup file/directory if not exist at /home, and inside of that directory, each copy safe(the command), create a subdirectory inside of backup, example: backup1, backup2...((each directory passed as argument of the script should be copied, including sub-directories and files, preserving dates and times of access and modification of them)).
4. Complete Name of School (University), City (State), Country, Name of Professor, and Course Number (Link to Course):
University of leiria, Isla, leiria, Portugal, Unisla - Apresentação, Rosalina Pires
Last edited by pludi; 03-25-2010 at 05:33 PM..
Reason: code tags, please...
Hi everybody in the forum,
I want to create an empty file of say some 1MB ,i mean at the command line itself.How is this possible??????EEK! (4 Replies)
hey, I'm trying to create the command that will create a file named user.txt that contains the output of the command cut -d: -f1,5 /etc/passwd, and displays itself afterwards.
I don't know how to bridge cat > user.txt with cut -d: -f1,5 /etc/passwd, or how display it afterwards. Any help would... (2 Replies)
Hi,
I would like to develop a man page as the one we usually get when we execute man <command name>. This man page will be for a samll utility that i have written.
If this is not possible then what are the available possibilites for creating such help.
thanks in advance. (2 Replies)
Hi all. Suppose I have the following function in an executable file named "HOLA":
------------------------
function hola { echo "Hola ${@}."; }
------------------------
In addition, suppose that I want to execute the file so I can input my name next to ./HOLA. I mean,... (4 Replies)
How do you write a command line that displays the number of files in the working directory with names that end with the letter S? Thanks
---------- Post updated at 09:34 PM ---------- Previous update was at 09:33 PM ----------
for unix sorry (1 Reply)
Hello ,
I am newbie to UNIX platform .
I have read that there are two ways of creating files that is using
1.) Cat 2.) touch .
With Cat Command i am unable to create a File , i is saying No file or Directory exists
I logged in with root as user .
please help (7 Replies)
Hello senior members,
I am a fairly newbie here. I just want to ask one question that how can once create one's own command interpreter/ shell like bash in unix/linux.
I need to execute basic commands like pipes and i/o.
Any help in this matter ?? (3 Replies)
Currently using the below script to being all compressed files .gz files from source folder and appending to the target txt file uncompressed.
Teh target txt file is getting too large in size, right now the size of the target txt file is almost 350GB
hadoop fs -text... (3 Replies)
Hi All,
I am having command to run which will take argument as input file. Right now we are creating the input file by cat and executing the command
ftptransfer -i input file
cat >input file
file1
file2
cntrl +d
Is there a way I can do that in a single command like
... (1 Reply)
Discussion started by: arunkumar_mca
1 Replies
LEARN ABOUT DEBIAN
expire_backups
EXPIRE_BACKUPS(1) S3QL EXPIRE_BACKUPS(1)NAME
expire_backups - Intelligently expire old backups
SYNOPSIS
expire_backups [options] <age> [<age> ...]
DESCRIPTION
The expire_backups command intelligently remove old backups that are no longer needed.
To define what backups you want to keep for how long, you define a number of age ranges. expire_backups ensures that you will have at least
one backup in each age range at all times. It will keep exactly as many backups as are required for that and delete any backups that become
redundant.
Age ranges are specified by giving a list of range boundaries in terms of backup cycles. Every time you create a new backup, the existing
backups age by one cycle.
Example: when expire_backups is called with the age range definition 1 3 7 14 31, it will guarantee that you always have the following
backups available:
1. A backup that is 0 to 1 cycles old (i.e, the most recent backup)
2. A backup that is 1 to 3 cycles old
3. A backup that is 3 to 7 cycles old
4. A backup that is 7 to 14 cycles old
5. A backup that is 14 to 31 cycles old
Note If you do backups in fixed intervals, then one cycle will be equivalent to the backup interval. The advantage of specifying the age
ranges in terms of backup cycles rather than days or weeks is that it allows you to gracefully handle irregular backup intervals.
Imagine that for some reason you do not turn on your computer for one month. Now all your backups are at least a month old, and if
you had specified the above backup strategy in terms of absolute ages, they would all be deleted! Specifying age ranges in terms of
backup cycles avoids these sort of problems.
expire_backups usage is simple. It requires backups to have names of the forms year-month-day_hour:minute:seconds (YYYY-MM-DD_HH:mm:ss) and
works on all backups in the current directory. So for the above backup strategy, the correct invocation would be:
expire_backups.py 1 3 7 14 31
When storing your backups on an S3QL file system, you probably want to specify the --use-s3qlrm option as well. This tells expire_backups
to use the s3qlrm command to delete directories.
expire_backups uses a "state file" to keep track which backups are how many cycles old (since this cannot be inferred from the dates con-
tained in the directory names). The standard name for this state file is .expire_backups.dat. If this file gets damaged or deleted,
expire_backups no longer knows the ages of the backups and refuses to work. In this case you can use the --reconstruct-state option to try
to reconstruct the state from the backup dates. However, the accuracy of this reconstruction depends strongly on how rigorous you have been
with making backups (it is only completely correct if the time between subsequent backups has always been exactly the same), so it's gener-
ally a good idea not to tamper with the state file.
OPTIONS
The expire_backups command accepts the following options:
--quiet
be really quiet
--debug
activate debugging output
--version
just print program version and exit
--state <file>
File to save state information in (default: ".expire_backups.dat")
-n Dry run. Just show which backups would be deleted.
--reconstruct-state
Try to reconstruct a missing state file from backup dates.
--use-s3qlrm
Use s3qlrm command to delete backups.
EXIT STATUS
expire_backups returns exit code 0 if the operation succeeded and 1 if some error occured.
SEE ALSO
expire_backups is shipped as part of S3QL, http://code.google.com/p/s3ql/.
COPYRIGHT
2008-2011, Nikolaus Rath
1.11.1 August 27, 2014 EXPIRE_BACKUPS(1)