Sponsored Content
Operating Systems AIX How to backup and restore Linux uisng NIM. Post 302203473 by rdkumarj on Monday 9th of June 2008 01:56:24 AM
Old 06-09-2008
How to backup and restore Linux uisng NIM.

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 i want the same "mksysb" function be carried out for linux servers. Can somebody help me on this...

Thanks in Advance.
 

10 More Discussions You Might Find Interesting

1. HP-UX

F-Backup restore

Hello! i have a blank harddrive and a complete tape backup of the workstation. the backup is made with F-Backup. Now my question is: how can i restore my workstation? thanks for every idea! paul tittel hup-si (3 Replies)
Discussion started by: paultittel
3 Replies

2. AIX

AIX backup --> Linux Restore

Hi all, I have a large number of backup tapes which were originally written with the AIX "backup" command. I now need to convert these to "tar" format, but unfortunately I no longer have access to an AIX machine. I have been able to connect the old tape drive (3590) to a Linux box and it works... (2 Replies)
Discussion started by: jauru
2 Replies

3. AIX

AIX NIM backup with Firewall

Hi- I'm using NIM functionality (AIX5.3) to backup all AIX Servers but some Servers are in the DmZ and many tcpip ports (nfs, ping,etc...) should be open and... it's really a security risks! As anyone experience about NIM Backup through Firewall? Which tcpip ports should be open? Could we... (1 Reply)
Discussion started by: nymus7
1 Replies

4. AIX

NIM client mksysb restore

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

5. AIX

help with NIM backup error

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

6. AIX

backup NIM client

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

7. AIX

Single file restore from NIM backup

Hi, I've recently implemented a NIM backup procedure for 2 virtual AIX5.3 environments running on a JS22 blade server. The images transfer to an old p620 box connected to some old SSA storage, each server backs up a mksysb and a savevg image. Now seeing as this method should be replacing our... (3 Replies)
Discussion started by: thinboyslim
3 Replies

8. AIX

VIO restore from NIM dosen't work

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

9. AIX

NIM Restore hangs at the start

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

10. AIX

Disabling cron after NIM restore

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
nisrestore(1M)						  System Administration Commands					    nisrestore(1M)

NAME
nisrestore - restore NIS+ directory backup SYNOPSIS
nisrestore [-fv] backup-dir directory... nisrestore [-fv] -a backup-dir nisrestore -t backup-dir DESCRIPTION
nisrestore restores an existing backup of a NIS+ directory object that was created using nisbackup(1M). The backup-dir is the UNIX direc- tory that contains the NIS+ backup on the server being restored. The nisrestore command can be used to restore a NIS+ directory object or a complete NIS+ database. It also can be used as an "out of band" fast replication for a new replica server being initialized. The rpc.nisd(1M) daemon must be stopped before running nisrestore. The first synopsis is used to restore a single directory object or a specified list of directory objects. The directory can be partially qualified or fully qualified. The server being restored will be verified against the list of servers serving the directory. If this server is not configured to serve this object, nisrestore will exit with an error. The -f option will override this check and force the operation. The second synopsis will restore all of the directory objects contained in the backup-dir. Again, the server will be validated against the serving list for each of the directory objects in the backup-dir. If one of the objects in the backup-dir are not served by this server, nisrestore will exit with an error. The -f option will override this check and force the operation. The -a option will attempt to restore all NIS+ objects contained in the backup-dir. If any of these objects are not served by the server, nisrestore will exit with an error. If the backup-dir contains objects that are not served by the server, nisrestore must be executed with- out the -a option and the specific directory objects listed. The -f option will disable verification of the server being configured to serve the objects being restored. This option should be used with care, as data could be inadvertently restored to a server that doesn't serve the restored data. This option is required in the case of restoring a single server domain (master server only) or if the other NIS+ servers are unavailable for NIS+ lookups. The combination of options -f and -a should be used with caution, as no validation of the server serving the restored objects will be done. New replicas can be quickly added to a namespace with the nisrestore command. The steps are as follows. Configure the new replica on the master server (see nisserver(1M)): master# nisserver -R -h replica Temporarily stop the rpc.nisd server process on the new replica server: replica# svcadm disable -t network/rpc/nisplus:default Create a backup of the NIS+ database on the master, which will include the new replica information. See nisbackup(1M). The /backup will need to be exported to the new replica. See share_nfs(1M). master# nisbackup -a /backup Restore the backup of the NIS+ database on the new replica. Use the -f option if nisrestore is unable to lookup the NIS+ objects being restored. The backup should be available through nfs or similar means. See share_nfs(1M). replica# nisrestore -f -a //nfs-mnt/backup Restart the rpc.nisd(1M) process on the new replica, and the server will immediately be available for service: replica# svcadm enable network/rpc/nisplus:default OPTIONS
The following options are supported: -a Restores all directory objects included in the backup-dir partition. -f Forces the restoration of a directory without the validation of the server in the directory object's serving list. -t Lists all directory objects contained in backup-dir. -v Verbose option. Additional output will be produced upon execution of the command. OPERANDS
The following options are supported: backup-dir The UNIX directory that contains the data files for the NIS+ directory objects to be restored. directory The NIS+ directory object(s) to be restored. This can be a fully or partially qualified name. EXAMPLES
Example 1: Restoring the Directory Object on a Replica Server from a Local UFS Partition To restore the org_dir directory object of the domain foo.com on a replica server from a local ufs partition named /var/backup: replica_server# nisrestore /var/backup org_dir.foo.com. Example 2: Forcing the Restore of a Backed up NIS+ Namespace to a Replica Server From the Backup Partition To force the restore of an entire backed up NIS+ namespace to a replica server from the backup partition named /var/backup: replica_server# nisrestore -f -a /var/backup Example 3: Restoring the Subdomain on a Master Server From a Backup that Includes Other Directory Objects To restore the subdomain sub.foo.com on a master server, from a backup that includes other directory objects: master_server# nisrestore /var/backup sub.foo.com. org_dir.sub.foo.com. groups_dir.sub.foo.com. EXIT STATUS
0 Successful completion. 1 An error occurred. FILES
/backup-dir/backup_list This ASCII file contains a list of all the objects contained in this backup-dir directory. This information can be displayed with the -t option. /backup-dir/directory-object A subdirectory that is created in the backup-dir which contains the directory-object backup. /backup-dir/directory-object/data A subdirectory that contains the data files that are part of the directory-object backup. /backup-dir/directory-object/last.upd This data file contains timestamp information about the directory-object. /backup-dir/directory-object/data.dict A NIS+ data dictionary for all of the objects contained in this directory-object backup. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWnisu | +-----------------------------+-----------------------------+ SEE ALSO
svcs(1), nis+(1), nisdefaults(1), nisbackup(1M), nisserver(1M), rpc.nisd(1M), share_nfs( 1M), svcadm(1M), nisfiles(4), attributes(5), smf(5) NOTES
NIS+ might not be supported in future releases of the SolarisTM Operating Environment. Tools to aid the migration from NIS+ to LDAP are available in the Solaris 9 operating environment. For more information, visit http://www.sun.com/directory/nisplus/transition.html. The NIS+ service is managed by the service management facility, smf(5), under the service identifier: svc:/network/rpc/nisplus:default Administrative actions on this service, such as enabling, disabling, or requesting restart, can be performed using svcadm(1M). The ser- vice's status can be queried using the svcs(1) command. SunOS 5.10 13 Aug 2004 nisrestore(1M)
All times are GMT -4. The time now is 04:30 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy