10 More Discussions You Might Find Interesting
1. AIX
Hello All,
I am trying to clone an entire AIX virtual machine to a new virtual machine including all partitions and OS.Can anyone help me on the procedure to follow? I am not really sure on how it can be done.Thanks in advance.
Please use CODE tags for sample input, sample output, and for code... (4 Replies)
Discussion started by: gull05
4 Replies
2. Solaris
Hello i am new on Solaris, and i need to migrate my old AIX 5.3 to Solaris 11.2
Now i have all apps working fine but i have the backup cause i was reading and i have not idea about what method must i choose.
Btw on AIX i had a mksysb backup to restore all system and obviously another backups to... (4 Replies)
Discussion started by: thorin666
4 Replies
3. Solaris
I have backed up the contents of my Solaris 10 machine in its entirety, and I'm trying to figure out if I can somehow use this archive to restore my old system just as it was on a new machine. Assuming I have all files from my old machine backed up, is this possible?
What I've been trying to do... (6 Replies)
Discussion started by: unblockable
6 Replies
4. UNIX for Advanced & Expert Users
Hi All,
I have successfully backup & restore (using tar) one of my Debian Lenny Servers.
On the restore server (standby machine), everytime i have to erase the disk & extract the tar backup.
I want to extract the tar on the running restore server on a directory for e.g /systembackup-01,... (11 Replies)
Discussion started by: coolatt
11 Replies
5. HP-UX
Hello,
I'm still new in HP-UX backup and I want to do a FULL BACKUP of HP-UX server to TAPE device. After reading on several forums and posts, i have list down several steps on how to do a full backup on HP-UX with fbackup. I would like the gurus here to comment/advise on the steps below
1)... (4 Replies)
Discussion started by: miskin
4 Replies
6. UNIX for Dummies Questions & Answers
I would like to know if I can do a full system back
up on my Unix Sco openserver 5.0.5 Machine. If so, What
is the syntax to do this or where can I find this
information at?
Also, is it possible to make this tape bootable so
that I can easily do a full system restore? Any
information on... (2 Replies)
Discussion started by: nellenodrog
2 Replies
7. Solaris
I have unix server with OS 5.8 ,,,
I tried ufsdump 0ua -f /dev/rmt/0 / to perform full system backup on tape but I failed could any one give a procedure for full system backup on solaris machine using tapes??? (1 Reply)
Discussion started by: mm00123
1 Replies
8. UNIX for Dummies Questions & Answers
hi,
Recently, I had receive one system. it's run on the unix tru64 server.
I looking some log files when i know don't work few months age system backup to tape.
Below error:
INFO:Tape backups to tape tape0 starting
for backup list:
slot2:/disk4
Backup Command Variable... (0 Replies)
Discussion started by: Tlg13team
0 Replies
9. Linux
Please help. I am new to linux. I wrote a script to run the backup on lunix machine but the job gave me an error. I am using Linux 2.6.14.3. Below is the sample of my script can anyone tell me where went wrong? Thanks in advance.
#!/bin/sh
dat=$(date +%d%b%y)... (5 Replies)
Discussion started by: clement
5 Replies
10. UNIX for Dummies Questions & Answers
I am new to UNIX and need help in cloning a HPUX 10.2 Ace 5, can anybody please guide me in making a full system backup.
Real Chess (0 Replies)
Discussion started by: real-chess
0 Replies
AMADMIN(8) System Manager's Manual AMADMIN(8)
NAME
amadmin - administrative interface to control Amanda backups
SYNOPSIS
amadmin config command [ command options ]
DESCRIPTION
Amadmin performs various administrative tasks on the config Amanda configuration.
See the amanda(8) man page for more details about Amanda.
COMMANDS
Commands that take a hostname [ disks ] parameter pair operate on all disks in the disklist for that hostname if no disks are specified.
Where hostname is also marked as being optional, the command operates on all hosts and disks in the disklist. Both hostnames and disk are
special expression, see the "HOST & DISK EXPRESSION" section of amanda(8) for a description.
version
Show the current version and some compile time and runtime parameters. The config parameter must be present but is ignored.
force-bump [ hostname [ disks ]* ]+
Force the disks on hostname to bump to a new incremental level during the next Amanda run.
force-no-bump [ hostname [ disks ]* ]+
Force the disks on hostname to not bump to a new incremental level during the next Amanda run.
unforce-bump [ hostname [ disks ]* ]+
Undo a previous force-bump or force-no-bump command.
force [ hostname [ disks ]* ]+
Force the disks on hostname to do a full (level 0) backup during the next Amanda run.
unforce [ hostname [ disks ]* ]+
Undo a previous force command.
reuse tapelabel [ ... ]
The tapes listed will be available for reuse at their point in the tape cycle.
no-reuse tapelabel [ ... ]
The tapes listed will not be reused when their turn comes up again in the tape cycle. Note that if this causes the number of reus-
able tapes to drop below the amanda.conf tapecycle value, Amanda will request new tapes until the count is satisfied again.
due [ hostname [ disks ]* ]*
Show when the next full dump is due.
find [ --sort hkdlb ] [ hostname [ disks ]* ]*
Display all backups currently on tape or in the holding disk. The tape label or holding disk filename, file number, and status are
displayed.
The --sort option changes the sort order using the following flags:
h host name
k disk name
d dump date
l backup level
b tape label
An uppercase letter reverses the sort order for that key. The default sort order is hkdlb.
delete [ hostname [ disks ]* ]+
Delete the specified disks on hostname from the Amanda database.
Note: if you do not also remove the disk from the disklist file, Amanda will treat it as a new disk during the next run.
tape Display the tape(s) Amanda expects to write to during the next run. See also amcheck(8).
bumpsize
Display the current bump threshold parameters, calculated for all backup levels.
balance
Display the distribution of full backups throughout the dump schedule.
export [ hostname [ disks ]* ]*
Convert records from the Amanda database to a text format that may be transmitted to another Amanda machine and imported.
import Convert exported records read from standard input to a form Amanda uses and insert them into the database on this machine.
disklist [ hostname [ disks ]* ]*
Display the disklist information for each of the disks on hostname (or all hosts). Mostly used for debugging.
info [ hostname [ disks ]* ]*
Display the database record for each of the disks on hostname (or all hosts). Mostly used for debugging.
EXAMPLES
Request three specific file systems on machine-a get a full level 0 backup during the next Amanda run.
$ amadmin DailySet1 force machine-a / /var /usr
amadmin: machine-a:/ is set to a forced level 0 tonight.
amadmin: machine-a:/var is set to a forced level 0 tonight.
amadmin: machine-a:/usr is set to a forced level 0 tonight.
Request all file systems on machine-b get a full level 0 backup during the next Amanda run.
$ amadmin DailySet1 force machine-b
amadmin: machine-b:/ is set to a forced level 0 tonight.
amadmin: machine-b:/var is set to a forced level 0 tonight.
amadmin: machine-b:/usr is set to a forced level 0 tonight.
amadmin: machine-b:/home is set to a forced level 0 tonight.
Undo the previous force request for /home on machine-b. The other file systems will still get a full level 0 backup.
$ amadmin DailySet1 unforce machine-b /home
amadmin: force command for machine-b:/home cleared.
Locate backup images of /var from machine-c. The tape or file column displays either a tape label or a filename depending on whether the
image is on tape or is still in the holding disk. If the image is on tape, the file column tells you which file on the tape has the image
(file number zero is a tape label). This column shows zero and is not meaningful if the image is still in the holding disk. The status
column tells you whether the backup was successful or had some type of error.
$ amadmin DailySet1 find machine-c /var
date host disk lv tape or file file status
2000-11-09 machine-c /var 0 000110 9 OK
2000-11-08 machine-c /var 2 000109 2 OK
2000-11-07 machine-c /var 2 /amanda/20001107/machine-c._var.2 0 OK
2000-11-06 machine-c /var 2 000107 2 OK
2000-11-05 machine-c /var 2 000106 3 OK
2000-11-04 machine-c /var 2 000105 2 OK
2000-11-03 machine-c /var 2 000104 2 OK
2000-11-02 machine-c /var 2 000103 2 OK
2000-11-01 machine-c /var 1 000102 5 OK
2000-10-31 machine-c /var 1 000101 3 OK
Forget about the /workspace disk on machine-d. If you do not also remove the disk from the disklist file, Amanda will treat it as a new
disk during the next run.
$ amadmin DailySet1 delete machine-d /workspace
amadmin: machine-d:/workspace deleted from database.
amadmin: NOTE: you'll have to remove these from the disklist yourself.
Find the next tape Amanda will use (in this case, 123456).
$ amadmin DailySet1 tape
The next Amanda run should go onto tape 123456 or a new tape.
Show how well full backups are balanced across the dump cycle. The due-date column is the day the backups are due for a full backup. #fs
shows the number of filesystems doing full backups that night, and orig KB and out KB show the estimated total size of the backups before
and after any compression, respectively.
The balance column shows how far off that night's backups are from the average size (shown at the bottom of the balance column). Amanda
tries to keep the backups within +/- 5%, but since the amount of data on each filesystem is always changing, and Amanda will never delay
backups just to rebalance the schedule, it is common for the schedule to fluctuate by larger percentages. In particular, in the case of a
tape or backup failure, a bump will occur the following night, which will not be smoothed out until the next pass through the schedule.
The last line also shows an estimate of how many Amanda runs will be made between full backups for a file system. In the example, a file
system will probably have a full backup done every eight times Amanda is run (e.g. every eight days).
$ amadmin DailySet1 balance
due-date #fs orig KB out KB balance
-------------------------------------------
11/10 Mon 21 930389 768753 +5.1%
11/11 Tue 29 1236272 733211 +0.2%
11/12 Wed 31 1552381 735796 +0.6%
11/13 Thu 23 1368447 684552 -6.4%
11/14 Fri 32 1065603 758155 +3.6%
11/15 Sat 14 1300535 738430 +0.9%
11/16 Sun 31 1362696 740365 +1.2%
11/17 Mon 30 1427936 773397 +5.7%
11/18 Tue 11 1059191 721786 -1.3%
11/19 Wed 19 1108737 661867 -9.5%
-------------------------------------------
TOTAL 241 12412187 7316312 731631 (estimated 8 runs per dumpcycle)
FILES
/etc/amanda/config/amanda.conf
AUTHOR
James da Silva <jds@cs.umd.edu>
University of Maryland, College Park
SEE ALSO
amanda(8), amcheck(8), amdump(8), amrestore(8)
AMADMIN(8)