02-28-2020
No.
I do not recommend those file systems.
Your are better off running ext4, a RAID configuration (I run RAID1, but do not depend on it), and doing regular backups on your data based on your risk management model (this is the most critical).
Nothing beats a strong filesystem and a very well thought out backup and recovery plan.
That is my view. YMMV
On the desktop, I run macOS and have a similar strategy. I make full backups often, based on the activity on the system. The more activity and files (and the nature of the files) created, the more frequent the backups.
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
We are looking into buying a new software, billing software that is, and want to know if you can run that on the same UNIX server as another major software?
Is there a limit to the different types of software Unix can run, or is it like windows where you can install as many as you like?
... (2 Replies)
Discussion started by: hoz
2 Replies
2. UNIX for Advanced & Expert Users
Hi there.
I've been tasked with making a new design for our Unix systems :eek:
Now the question I have is;
How many LPARs can a p570 hold WITHOUT using a VIO Server.
Many Thanks
Kees (1 Reply)
Discussion started by: KeesH
1 Replies
3. Red Hat
Hi.
I downloaded a package that could only be installed on RHEL5, and not 4 or 3, so I got the source in order to compile it on RHEL 3 so hopefully it will work on all versions.
So I have the source for a working package, but when I build it in RHEL 3 and then try to install it in RHEL 5, it... (6 Replies)
Discussion started by: Boaz
6 Replies
4. Filesystems, Disks and Memory
I'm looking for a means to ensure that servers in the two or three datacenters, connected in a ring via IP through two ISPs, can distribute load and/or replicate data among at least two SAN-class disk devices.
I want to evaluate several solutions, and I'm open to solutions ranging from free,... (6 Replies)
Discussion started by: otheus
6 Replies
5. Solaris
I've got a Solaris 11 Express installed on my machine. I have created a raidz2 zpool named shares and a simple one-disc zpool named backup. I have made a script that would send a daily snapshot of shares to backup.
I use these commands
zfs snapshot shares@DDMMRRRRHHMM
zfs send -i shares@....... (10 Replies)
Discussion started by: RychnD
10 Replies
6. UNIX for Advanced & Expert Users
I wonder if anyone could assist with some problems I'm having with Linux Capabilities and their use when using the commands "nice" and "schedtool".
I run a couple of PCs, one is an elderly AMD Sempron 2800+ (32-bit, 2GHz clock and 3GB memory) that is used as a family multimedia system running... (3 Replies)
Discussion started by: MikeGM
3 Replies
7. Linux
So I'm having a problem getting a Broadcom BCM4312 wireless controller to work under the broadcom-wl module
$uname
Linux 3.8.11-200.fc18.x86_64 #1 SMP Wed May 1 19:44:27 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
lspci -v
05:00.0 Network controller: Broadcom Corporation BCM4312 802.11b/g... (2 Replies)
Discussion started by: Skrynesaver
2 Replies
8. UNIX for Advanced & Expert Users
Hi
I'm trying to compile my linux kernel with CONFIG_SECURITY_CAPABILITIES=y.
any idea what this thing does ??
Also another question , If I compile the kernel that I'm currently using , what'll happen ?
~cheers (3 Replies)
Discussion started by: leghorn
3 Replies
9. What is on Your Mind?
Hi All,
How worried is everyone about the Dirty Cow Linux exploit? Has anybody experienced attacks yet?
From the research I've done it seems that the exploit is "reliable" (that is it works nearly every time on vulverable systems) which is not good news.
We all believe that Unix/Linux... (3 Replies)
Discussion started by: hicksd8
3 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)