08-29-2010
mksysb using NIM
I am implementing mksysb backups using NIM. I am using nimsh as client communication and mksysb backup are working fine, but this requires remote logon to be enabled for root.
Any thoughts on how can I implement mksysb backups using NIM without enabling remote logon for "root" ?
10 More Discussions You Might Find Interesting
1. AIX
I have multiple LPARS on p650 with mix of AIX5.2 and AIX5.1 with different rml level
My understanding is creating mksysb nim on NIM server is for new installation of LPARS
Then;
How do I do mksysb backup on existing lpars for recovery purpose or how do I do all mksysb to a NFS mounted Filesystem... (1 Reply)
Discussion started by: melindaj
1 Replies
2. UNIX for Advanced & Expert Users
Hi,
I'm trying to use my NIM server to get a mksysb of an lpar on another machine on my network.
I'm trying to define a resource through smitty and i've entered the resource name, Server of resource & location of resource, they are as follows
Resource Name : gmt_fail_mksysb
Server of... (1 Reply)
Discussion started by: KeesH
1 Replies
3. Shell Programming and Scripting
#!/bin/ksh
#
# nim_mksysb
# get mksysb from each client machine specified with -m. If no
# machines specified, get mksysb from ALL machines. -r flag says
# remove oldest existing mksysb for the machines being backed up.
# use -n no_make flag with -r to remove a generation of mksysb,
#... (0 Replies)
Discussion started by: barkath
0 Replies
4. UNIX for Dummies Questions & Answers
Hello, help me please.
I am trying to create a mksysb bakup using nim. I am geting this error, how to correct it ? :
Command : failed stdout: yes stderr: no
+---------------------------------------------------------------------+
System Backup Image Space Information
(Sizes are displayed in... (4 Replies)
Discussion started by: astjen
4 Replies
5. AIX
Can a NIM client mksysb restore be performed via NIM (smitty nim) without the NIM client machine having the NIM server's IP and hostname in its /etc/hosts file? (10 Replies)
Discussion started by: kah00na
10 Replies
6. AIX
Hi,
I am trying to backup a system ("client") through a slow network using "nim mksysb" on a nim server ("master")
The backup starts, but doesn't success.
Thanks if you can help me to resolve this problem :
Creating information file (/image.data) for rootvg...
Creating list of files to... (2 Replies)
Discussion started by: astjen
2 Replies
7. AIX
Hello,
I need to install "bos.adt.libm 5.3.0.0" on a server (AIX5.3 power 5).
How to install it from a nim mksysb of an another partition ?
Thank you (3 Replies)
Discussion started by: astjen
3 Replies
8. AIX
Hi All,
Please excuse the possibly naive question but I'm trying to clone/install a new AIX 5.3 LPAR on a p570 from a mksysb image file using nim. Has anyone done this before and if so, what would the exact command look like?
Does it even remotely resemble something like
nim -o... (1 Reply)
Discussion started by: combustables
1 Replies
9. AIX
Hi,
I just want to ask whether anyone has experience on restoring mksysb backup in NIM. We have taken the mksysb backup and the SPOT has been configured on NIM also. I just want to know the checkpoints before doing this. Is there any checkpoints we need to do? Do we need to unmirrorvg? This... (12 Replies)
Discussion started by: depam
12 Replies
10. AIX
Hi,
i backed up a test LPAR using mksyb utility on AIX. and transferred it to NIM server via NFS.
I want to create a SPOT using this mksysb . Please explain me the procedure. And got something online, but that procedure is different.
Please respond. (5 Replies)
Discussion started by: System Admin 77
5 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)