it maybe a lot of work without any tools but for this question:
How can we backup user data (not OS) on regular basis using OS commands ? incremental or full backups ?
Since you are taking a mksysb and hopefully on a remote server, depending on what the situations are like, allocate a new LUN make this a backup drive, use something like rsync to make the backups for you. I'm not really sure this will do incremental backups though.
Here is some info from rsync:
Code:
Rsync copies files either to or from a remote host, or
locally on the current host (it does not support copying
files between two remote hosts).
Hi.... everyone could help me to understand how to do a backup of my servers .. operating systems is sun solaris 8 .
I have some question about ....
1) Is better backup phisical disk or partition ???
i sow the command is ufsdump 0cfu /expbck/bcksunver/c0t0d0s5 dev/dsk/c0t0d0s5 to... (4 Replies)
I have several H80 machines, all with AIX 4.3.3. On these machines I have mksysb running for rootvg backups and savevg for non-rootvg backups.
I'm trying to get a list of files on the tapes, but I can't seem to do it with tar for the mksysb images. I keep getting the directory checksum errors?... (3 Replies)
Hello!
i have a blank harddrive and a complete tape backup of the workstation.
the backup is made with F-Backup.
Now my question is:
how can i restore my workstation?
thanks for every idea!
paul tittel
hup-si (3 Replies)
I am trying to do a restore on a backup tape (DDS2) and am having a little trouble. For one, I dont know how the tape was made, whether is was tar, cpio, dump..etc. Anyone know how to restore a tape without knowing the format of the backup? (5 Replies)
Dear All ;
first how are you every body I'm just subscribed in your forum and i hope i found what i searched for along time .
I'm not a Solaris specialist but i read more to build a Network Management Station depends on Solaris as OS and it is working good now .
my problem is how to perform... (16 Replies)
Hi experts, i got a question.
i have a production server with two Volume Group(VG) which are rootvg and datavg. Both of these VGs are 256 PP SIZE.
On Disaster Recovery Server (DR server) contains two empty hardisks for restoring rootvg and datavg from production server. This two hardisks are... (7 Replies)
hi,
my requirement goes something like this:
In current setup, we have SPARC server running Solaris10 5/08. Out of 3 HDD available, 2 HDD (other than root) were zpool-ed and 3 zones were created.
Now, we have bought a new server with similar H/W config and planning to move the zones... (1 Reply)
Hi,
I need to back up a RH file system (96G).
The files are oracle .dbf format some of which are 5G in size.
I know that tar has got a size restriction of 2G so I cannot use this.
Can anyone recommend an alternative way of backuping up this FS?
I have been looking at dump but this... (6 Replies)
Hi all,
I'm trying to get an understanding of swap. This is what I see:
Memory: 8192M real, 1697M free, 5693M swap in use, 10G swap free
My question(s): If I have available RAM, why am I using swap? Or am I reading this wrong (been known to happen).
Thanks much,
~K (8 Replies)
Discussion started by: kuriosity_prime
8 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)