10-15-2009
Hi TBS,
Depends on what control you have over the environment...
If you are root everywhere then probably it will be easiest to NFS export the mksysb / savevg on the p620 and mount it up on the client and then do all the work on the client over the NFS mount.
If you have restrictions with NFS exports then restore it on the p620 to a tmp directory and ftp / scp / etc. to the client.
Savevg is just the same as a mksysb but without all the boot info, they both use the backup command under the covers so you can list / restore just the same.
10 More Discussions You Might Find Interesting
1. AIX
Hi
I have a single large file 11gb that I need to copy/backup to tape then restore on another system. I tried tar but that complained about the file being too large
Anyone have any suggestions how I can do this with AIX 5.2
Much appreciated. (3 Replies)
Discussion started by: Alvescot
3 Replies
2. AIX
Hi Friends,
I've a hard question to ask. I have a NIM server running on AIX 5.3. Now my requirement is that , " From This NIM Server i would like to take the Image of Linux servers ". I mean that using NIM server i should be able to backup / restore the linux Servers.
In Simple terms... (3 Replies)
Discussion started by: rdkumarj
3 Replies
3. 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
4. AIX
Hello all....
I am trying to backup a client from the NIM master. While doing so, I get this error:
backup: 0511-089
can not open /tmp/6282.mnt0/<hostname>_mksysb_<date>
0042-001 m_mkbosi: processing error encountered on client
0042-001 m_mkbosi: processing error encountered on master... (0 Replies)
Discussion started by: solaix14
0 Replies
5. AIX
Hello everyone
I would like to hear your opinions about this procedure to backup a client to my nim master
1.-I got a cron that make a mksysb from x machine
2.-This mksysb I send by ftp to my nim master.
3.-When I got it in the nim master machine. I create a mksysb resource from this... (2 Replies)
Discussion started by: lo-lp-kl
2 Replies
6. AIX
Hello guys
I have been trying to restore a VIO server from NIM using the nim_resource.tar file created from the same VIO lpar. The restoration goes fine and after 99% I get the following error
0516-304 putlvodm: Unable to find device id 000b5f62263b70a50000000000000000 in the Device... (1 Reply)
Discussion started by: balaji_prk
1 Replies
7. Solaris
Hi all
I have a DLT tape in that tape backup is there is in veritas volume format and i want to restore it in ufs file system how can i do it?
right now i don't have veritas file system setup. i have only ufs file sysytem
please help some production data is to be restore.
backup was taken... (0 Replies)
Discussion started by: nikhil kasar
0 Replies
8. AIX
Hello Gurus,
I have a couple of questions, I'm trying to do a mksysb restore from backup and it has just hung at the start.
RS/6000 Firmware
Version TCP05287
(c) Copyright IBM Corp. 2000 All rights reserved.
-------------------------------------------------------------------------------... (8 Replies)
Discussion started by: elcounto
8 Replies
9. AIX
Hi,
I have taken a backup of filesystem " /backup " by using backupby file name command on tape
Mount volume 1 on /dev/rmt0.
Press Enter to continue. Backing up to /dev/rmt0.
Cluster 51200 bytes (100 blocks).
Volume 1 on /dev/rmt0
a 0 /backup
a 543 /backup/abc_log ... (3 Replies)
Discussion started by: m_raheelahmed
3 Replies
10. AIX
Hi Guys,
We normally have a backup and restore nightly on our Prod machines. We do this via customized script and all unattended. The dilemma that I'm having is the disabling of the cron after the restore.
I created a nim script to disable the cron after the restore has been completed. But... (6 Replies)
Discussion started by: kaelu26
6 Replies
mountd(8) System Manager's Manual mountd(8)
NAME
mountd - Services remote NFS compatible mount requests
SYNOPSIS
mountd [-d] [-i] [-n] [-s] [exportsfile]
FLAGS
Verifies the Internet addresses of hosts that make mount and unmount requests. If a client's address cannot be translated into a host name
by the gethostbyaddr() function and then translated back into the same Internet address by the gethostbyname() function, the request is
rejected.
This option requires the BIND service for Internet address resolution. It offers the highest level of security, especially when
combined with the -i option. Turns on Internet address verification and domain checking. If you are running the BIND service,
mountd verifies that a host making a mount or unmount request is in the server's domain. Allows non-root mount requests to be
served. This should only be specified if there are clients such as PC's that require it. ULTRIX BSD is allowed non-root mount
requests by default. Use the -n flag to allow non-root mount requests. Verifies the Internet address of hosts that make mount and
unmount requests. If a client's address cannot be translated into a host name by the gethostbyaddr() function, the request is
rejected. If you are running the BIND service, the BIND server is used to translate the address. If you are not, the /etc/hosts
file is used.
If the -i option is not used and a client's address cannot be translated, the address is converted to a string of the form
xx.xx.xx.xx. This allows access to exported file systems that do not specify a list of allowed hostnames.
The -i option is automatically enabled when either the -d or the -s option is specified. Turns on Internet address verification and
subdomain checking. If you are running the BIND service, mountd verifies that a host making a mount or unmount request is in the
server's domain or subdomain.
DESCRIPTION
The mountd daemon is the server for NFS protocol mount requests from clients. The mountd daemon responds to requests from remote computer
systems to mount directories. When it receives a SIGHUP signal, mountd rereads the exports file. If you are on an NFS client and want to
have changes to the export options on existing NFS client mounts take effect immediately, issue the showmount -e command and specify the
name of the host that is exporting the directory or file system (where the exports file is located). This ensures that NFS is aware of the
export list and options.
The optional exportsfile argument specifies an alternate location for the exports file. /etc/exports is the default.
Note, NFS Version 2 can export partitions that are greater than 2 gigabytes. However, they appear as 2 gigabyte partitions when viewed
from NFS clients.
FILES
Specifies the command path Contains a list of directories that can be exported Contains a table of local file systems mounted by remote NFS
clients Contains errors logged by the mountd daemon
RELATED INFORMATION
Commands: nfsstat(8), nfsd(8), portmap(8), showmount(8)
Files: exports(4), mountdtab(4) delim off
mountd(8)