12-25-2017
Most admins have issues with automated backups that fill up the file system.
You have many options, including:
(1) Delete older backups that are not necessary and take up disk space;
(2) Move older backups to other servers, if you want to keep them;
(3) Increase your disk space by adding another drive, etc.
7 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hello,
Here is what I am trying to do.
We have an old Enterprise 250 which we want to phase out. So plan is to move everything running on the 250 to an unused Sun Fire V280R.
Here is what I decided to do:
1. Fresh Solaris 8 install on Sun 280R (disk0). Configure network and install... (1 Reply)
Discussion started by: mshafi
1 Replies
2. Solaris
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)
Discussion started by: Basha
16 Replies
3. Shell Programming and Scripting
Hi Buddies,
my pc has two CPU, so CPU1 and CPU2.
I have a perl "a.pl", when i "./a.pl", i can see the CPU1 is full or CPU2 is full, mean only one is full, another one is idle.
Wonderring what shall i do in order to let both CPU to process this a.pl.:(
Thanks (1 Reply)
Discussion started by: jimmy_y
1 Replies
4. Solaris
Hi all,
I have a problem, when I use script with 'expect', accidentally I was deleted root account by "userdel root". Unfortunately, it works, because no other root user login on it. Solaris document said that root cannot delete root, but in my case it works because it deleted by script, not... (7 Replies)
Discussion started by: joash
7 Replies
5. Shell Programming and Scripting
hi guys linux noob here wanting to learn linux scripting, i need help with a backup script that not only allows me to back up my files but restore them to my own personal directory, had a look at some of the coding from the scripts section on this site but still lost.
any help is much appreciated (8 Replies)
Discussion started by: burnie35
8 Replies
6. Solaris
Hi men,
I'm testing for my backup&restore job with ZFS.
My server have two disks. I wanna do backup&restore job like ufsdump utility:
Disk0 is rpool(root zpool) and disk1 (backup zpool) will be stored full backup replicates. When rpool zpool have problem, i can "boot cdrom -s" and use my... (5 Replies)
Discussion started by: tien86
5 Replies
7. What is on Your Mind?
Retro Games has announced that the C64 is back, this time full-sized with a working keyboard for the dedicated retro home-computer fan, available December 2019.
See also:
CNN:
Iconic 80s computer The Commodore 64 to return with fully-functional keyboard
YouTube:
The C64 | Trailer
... (2 Replies)
Discussion started by: Neo
2 Replies
LEARN ABOUT CENTOS
amdump
AMDUMP(8) System Administration Commands AMDUMP(8)
NAME
amdump - back up all disks in an Amanda configuration
SYNOPSIS
amdump [--no-taper] [--exact-match] [-o configoption...] config [host [disk...]...]
DESCRIPTION
Amdump is the main interface to the Amanda backup process. It loads the specified configuration and attempts to back up every disk
specified by the disklist(5). Amdump is normally run by cron.
The command optionally takes a set of DLE specifications (see amanda-match(7)) to narrow the DLEs that will be dumped. All disks are dumped
if no expressions are given.
If a file named hold exists in the configuration directory, amdump will wait until it is removed before starting the backups. This allows
scheduled backups to be delayed when circumstances warrant, for example, if the tape device is being used for some other purpose. While
waiting, amdump checks for the hold file every minute.
In some cases it is desirable to dump all Amanda clients to holding disk without writing anything to storage media. The --no-taper option
instructs Amanda to not start the taper, and thus enter degraded mode immediately.
See the amanda(8) man page for more details about Amanda.
OPTIONS
host [disk]*
Specify the host and disk on which the command will work -- see the description of DLE specifications in amanda-match(7).
--exact-match
The host and disk are parsed as exact values
-o configoption
See the "CONFIGURATION OVERRIDE" section in amanda(8).
EXAMPLE
Here is a typical crontab entry. It runs amdump every weeknight at 1 a.m. as user bin:
0 1 * * 1-5 bin /usr/local/sbin/amdump daily
Please see the crontab(5) or crontab(1) manual page for the correct crontab format for your system.
MESSAGES
amdump: waiting for hold file to be removed
The "hold" file exists and amdump is waiting for it to be removed before starting backups.
amdump: amdump or amflush is already running, or you must run amcleanup
Amdump detected another amdump or amflush running, or the remains of a previous incomplete amdump or amflush run. This run is
terminated. If the problem is caused by the remains of a previous run, you must execute amcleanup(8) and then rerun amdump.
EXIT CODE
The exit code of amdump is the ORed value of:
0 = success
1 = error
2 = a dle give strange message
4 = a dle failed
8 = Don't know the status of a dle (RESULT_MISSING in the report)
16 = tape error or no more tape
SEE ALSO
amanda(8), amcheck(8), amcleanup(8), amrestore(8), amflush(8), cron(8), amanda-match(7)
The Amanda Wiki: : http://wiki.zmanda.com/
AUTHORS
James da Silva <jds@amanda.org>
Stefan G. Weichinger <sgw@amanda.org>
Amanda 3.3.3 01/10/2013 AMDUMP(8)