Sponsored Content
Operating Systems AIX AIX 5.2 Maksysb Image backup/restore Post 302205125 by dayinthelife on Friday 13th of June 2008 02:35:54 PM
Old 06-13-2008
AIX 5.2 Maksysb Image backup/restore

Hello,

I am new to AIX, as I was primarily working on HP-UX servers.

We have some production servers and a couple of lab servers. We have upgraded over 40 servers from 5.2 to 5.3 running a particular application(1) using the golden 5.3 upgraded servers copy of makesysb. We have only two servers left to migrate from 5.2 to 5.3. These servers are running a different application(2) which has a Primary and Replica status.

The OS configurations are the same on the two servers application(2), but different than the 40 application(1) servers. We were wanting to peform a makesysb on the Primary AIX 5.2 server/application(2) and send it to a DAT tape. We would then take the DAT tape makesysb and install it on one of our LAB servers. We would then upgrade the lab server to 5.3 and create a makesysb. It sounds so simple!

The problem is we received a system email stating some of the following:

* Installing from a tape backup whose boot image is too large
* Backing up DMAPI filesystems
* 0512-064


Installing from a tape backup whose boot image is too large



This makes it sound like we are not going to be able to restore our lab server with the Primary AIX 5.2 makesysb.

How do we get a good makesysb from an AIX 5.2 server?
How do we install it on our LAB server?

Thank you!
 

10 More Discussions You Might Find Interesting

1. 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

2. AIX

AIX backup and restore

Hello, Some background so you can see what I'm trying to do on AIX: In Windows its possible to partition a single hard drive into 2 separate logical paritions which may appear as a C and a D drive. It is then possible to to use 3rd party software such as Power Quest Drive Image to create a... (3 Replies)
Discussion started by: quickfirststep
3 Replies

3. Filesystems, Disks and Memory

Boot Sequence changed After Image Restore

Hello All, I backed up my RHEL 4 as an image. Then I restored the image on my machine. Everything went fine but I dont get the normal boot sequence as it used to come when I freshly installed RHEL4. The messages that are shown when the system boots are something like- " ..... EXT3-fs:... (2 Replies)
Discussion started by: shamik
2 Replies

4. Solaris

flar restore with svm mirrors failing to create boot image

In a Solaris9 environment I'm trying to restore flash archive (flar) with SVM mirrored devices to same server via jumpstart server and it is failing to create boot file and drops down to a command prompt in single user mode, metastat -i and metastat -p output looks good when compared to the ones... (0 Replies)
Discussion started by: mbak
0 Replies

5. AIX

AIX Tivoli Image Restore

Dear Team: I am new to this Forum and I need your help for my AIX restoration problem its very urgent my problem as follow failure I have a Tivoli Storage Manger was installed on that server. I created backup image using Tivoli and it created a set of files each file is around 2GB so... (1 Reply)
Discussion started by: Firas_Abed
1 Replies

6. Red Hat

Backup / Restore

Hi, I need to back up a RH file system (96G). The files are oracle .dbf format some of which are 5G in size. I know that tar has got a size restriction of 2G so I cannot use this. Can anyone recommend an alternative way of backuping up this FS? I have been looking at dump but this... (6 Replies)
Discussion started by: Duffs22
6 Replies

7. AIX

[Tip] Backup and restore on AIX

Pretty penny's. Just remember that mksysb and savevg are just front-ends for backup. In other words, backups on AIX are organized by volume groups. mksysb is specialized for rootvg and savevg is used for other volume groups. Ignoring that rootvg also creates files needed to boot a system... (1 Reply)
Discussion started by: MichaelFelt
1 Replies

8. AIX

Restore mksysb image on cloned LPAR

Hi Folks, How to restore mksysb image on LPAR which is already having cloned AIX OS installed on hdisk0 (nothing configured, only full partition image is sitting on hdisk0) Let me know. Thank a lot. (1 Reply)
Discussion started by: snchaudhari2
1 Replies

9. Solaris

Solaris 10 Restore from flar image

Hi! I want to migrate Sun Fire v240 server (sun4u) with Solaris 10 update 6 to LDOM virtual host (sun4v). I was mount NFS directory from another server in /mnt and did this steps on v240 1) I add to the /var/sadm/system/admin/.platform PLATFORM_GROUP=sun4v # cat... (1 Reply)
Discussion started by: pbubentsov
1 Replies

10. AIX

AIX 7.2 MKSYSB Backup and Restore Best Practices?

Hello, Running AIX 7.2 on Power9 bare-metal (no LPAR and no NIM server), in the process of creating a guide on MKSYSB process. I understand that MKSYSB is a backup of the rootvg and we can exclude stuff via exclude.rootvg file, the rest of the data volumes are mapped to the system as LUNs via... (7 Replies)
Discussion started by: c3rb3rus
7 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 Solaris Operating system. Tools to aid the migration from NIS+ to LDAP are available in the current Solaris release. 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.11 13 Aug 2004 nisrestore(1M)
All times are GMT -4. The time now is 10:18 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy