Sponsored Content
Full Discussion: NIMADM migration 5.3 to 7.1
Operating Systems AIX NIMADM migration 5.3 to 7.1 Post 302659575 by bakunin on Thursday 21st of June 2012 07:05:06 AM
Old 06-21-2012
Just an idea: NIM can become pretty capricious if directories in NIMs working directories are being exported independently (even if only exported indirectly via exporting super-directories of them).

It might be a good idea to have a look in /etc/exports and clean up every entry regarding NIMs working directories or supersets of these prior to attempting any NIM operation.

This is - alas - a part not all too predictable about NIM.

I hope this helps.

bakunin
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Migration

Is it possible to migrate a UNIX program and use it in a NetWare or Windows 2000 network? I have a client that must have one of those two operating systems for the new program that they want. However, they've been using an older UNIX program for about 7 years and they want to be able to refer to... (7 Replies)
Discussion started by: refram
7 Replies

2. UNIX for Advanced & Expert Users

migration

hi, is there any tool that i can use to update my scripts (SH scripts) form Unix to linux. please mention any useful websites. thanx in advance (2 Replies)
Discussion started by: omran
2 Replies

3. UNIX for Advanced & Expert Users

Migration

Hi all, Would appreciate advise on my situation. Currently server A is in production. Server A takes in data from Server X, does some processing and send to server Y. We are going to develop a different system in server B, something like an enhanced version of A. Server A will be retired once... (2 Replies)
Discussion started by: new2ss
2 Replies

4. Shell Programming and Scripting

code migration

Hi, I am working on migration project. thier are 50,000 scripts. As we are doing 70% of automization for changing the scripts. The remaining 30% doing manually. After doing manual changes i have to find the wheather the change is dont or not and also clode review process. Is there any... (2 Replies)
Discussion started by: unihp1
2 Replies

5. UNIX for Advanced & Expert Users

Migration of users

We are about to get a new server and I need to prepare for migration to the new one. This will be my first migration so I'm sure I will be learning alot. My current server is running CentOS 4.x and I want to move to a sever running Centos 5.x , thought it would make things easier. The old... (1 Reply)
Discussion started by: mcraul
1 Replies

6. AIX

Migration using nimadm

Hi , I am planning to upgrade nim client server from AIX 5.3 to AIX 6.1 using nimadm. My nim master is a 6.1 TL5 with the bos.alt_disk_install.rte 6.1.5.0 installed. I want to upgrade client at 6.1 TL4 level using the 6.1 TL4 lpp_source and spot. Question : As per the ibm information it... (0 Replies)
Discussion started by: mk8570
0 Replies

7. AIX

Server migration

Hi, Existing several p5 server with lpar (aix5.3), also implemented with hacmp. And now planning to buy new set of server (installing aix7.1)and SAN to replace the existing server. My question is, how to perform data migration from old server/SAN to new server/SAN. Suppose I install... (6 Replies)
Discussion started by: Oceanlo2013
6 Replies

8. AIX

SAN Migration

Hi all, We are migrating our SAN storage from HSV360 to 3PAR. The system runs aix 6.1 version with HACMP. Please let me know what are requirements from OS side and how are the data copied to the new disks. (10 Replies)
Discussion started by: ElizabethPJ
10 Replies

9. AIX

Lpar migration

We have a 2 node oracle rac cluster one node is in frame 1 and other is in frame 2 Now,because of some hardware failure(processor card and cable) in frame 1 we will failover database services from lpar in frame 1 to lpar(oracle rac cluster node2) in frame2 and the entire replacement of hardware... (9 Replies)
Discussion started by: admin_db
9 Replies

10. AIX

AIX - FC Switch migration, SAN Migration question!

I'm New to AIX / VIOS We're doing a FC switch cutover on an ibm device, connected via SAN. How do I tell if one path to my remote disk is lost? (aix lvm) How do I tell when my link is down on my HBA port? Appreciate your help, very much! (4 Replies)
Discussion started by: BG_JrAdmin
4 Replies
migrate(8)						      System Manager's Manual							migrate(8)

NAME
migrate - Move a file or file pages to another volume in an AdvFS file domain SYNOPSIS
/usr/sbin/migrate [-p pageoffset] [-n pagecount] [-s volumeindex] [-d volumeindex] filename OPTIONS
Specifies the volume index number of the volume to which the pages are to be migrated. You can determine the volume index number of the volumes in an AdvFS file domain by using the showfile -x command. If you do not specify the -d option, the AdvFS determines the destina- tion of the file or the file pages. The AdvFS moves the file or the file pages to any volume or volumes with available space. Specifies the number of pages to migrate, starting at the pageoffset value. The default page count is to EOF. If you do not specify the -n option, the migrate command migrates pages from the pageoffset value to the end of the file. Specifies the page offset of the first page to migrate. The first page of the file is page 0. The default page offset is 0. If you do not specify the -p option, the migrate command migrates pages starting at page 0 of the file. Specifies the volume index number of the volume from which the pages are to be migrated. Use the showfile -x command to determine the volume index number of the volumes in an AdvFS file domain. If you specify the -s option and the volume that contains the file does not contain any data extents of that file, the utility returns success without taking any action. You must use the -s option when you are migrating striped files. You can move pages of a striped file or a stripe file segment, which is the entire portion of a striped file that resides on the specified volume, to another volume. OPERANDS
Specifies the name of the file or file pages to be migrated from the volume. The file can be simple or striped. DESCRIPTION
The migrate utility moves the specified simple (unstriped) file to another volume in the same file domain. The utility also moves pages of a simple file or pages of a striped file segment to another volume (or volumes, if necessary) within the file domain. Because there are no read/write restrictions when using this command, you can migrate a file while users are reading it, writing to it, or both, without disrupting file I/O. File migration is transparent to users. When you run the migrate utility with only the -p and -n options, the utility attempts to allocate destination pages contiguously on one destination volume in the file domain. If there are not enough free, contiguous blocks to accomplish the move, the utility then attempts to allocate the pages to the next available blocks on the same volume. If there are not enough free blocks on the same volume, the utility then attempts to moves the file to the next available volume or volumes. The utility returns an error diagnostic if it cannot accomplish the move. You must use the -s, -n, and -p options in order to move pages of a striped file from one volume to another. Only those pages assigned to the source volume are moved to the destination volume: all pages in the file are not moved. You can use the migrate utility to move heavily accessed files or pages of files to a different volume in the file domain. Use the -d option to indicate a specific volume. Also, you can use the utility to defragment a specific file, because the migrate utility defragments a file whenever possible. NOTES
The migrate utility does not evaluate your migration decisions. As a result, you can move more than one striped file segment onto the same volume, which can defeat the purpose of striping the file. The number of stripes is determined by the number of extent maps for the file although a map may point to more than one volume. If you want to change the number of stripes for the file, you must re-create the file with the desired number of stripes. RESTRICTIONS
You can only perform one migrate operation on the same file at the same time. When you migrate a striped file, you can only migrate from one source volume at a time. You must be the root user to use this utility. EXIT STATUS
The utility returns a value of 0 (zero) on success, otherwise it returns a nonzero value and an error diagnostic. EXAMPLES
The following examples perform tasks using the migrate utility. To migrate the simple file abc from its current volume to any other volume in the file domain, enter: # migrate abc To migrate the simple file abc from volume 1 of a file domain to volume 6 of a file domain, enter: # migrate -s 1 -d 6 abc To migrate pages 10 through 99 (that is, 90 pages starting at page 10) of the simple file abc from its current vol- ume to volume 2 of the file domain, enter: # migrate -p 10 -n 90 -d 2 abc The following example migrates all the pages of a file that reside on a specified volume. A file, stripe_1, is striped across Volumes 1, 2, and 3 of a six-volume AdvFS file domain. To migrate the entire stripe file segment of the stripe_1 file that is on volume 1 to volume 4 of the domain, enter: # migrate -s 1 -d 4 stripe_1 The fol- lowing example moves some, but not all, file pages on one volume of a striped file to another volume in the file domain. Use the showfile command with the -x flag to determine the volume index, the page count, and the page offset for the volume. Then specify the pages you want to migrate. In this example the file str_file is striped across three volumes (1, 2, and 3) of a four volume file domain. To move some of the pages from volume 2 to volume 4, first identify the page offset and the page count for the pages you want to move: # showfile -x str_file Id Vol PgSz Pages XtntType Segs SegSz I/O Perf File 6.8007 2 16 123 stripe 3 8 async 69% str_file extentMap: 1 pageOff pageCnt volIndex volBlock blockCnt 0 8 3 67312 624 24 8 48 8 72 8 96 7 103 1 3 67952 64 120 3 extentCnt: 2 extentMap: 2 pageOff pageCnt volIndex volBlock blockCnt 8 8 4 67312 352 32 8 56 6 62 2 4 67696 64 80 2 82 6 4 67856 96 104 8 4 68080 128 extentCnt: 4 extentMap: 3 pageOff pageCnt volIndex volBlock blockCnt 16 8 1 76048 256 40 8 64 8 1 76320 128 88 8 1 76544 128 112 8 1 76720 128 extentCnt: 4 The showfile output shows that volume 4, as shown in extent map 2, contains a total of 40 pages of the striped file starting at page offset 8. You want to migrate the first 16 pages that reside on volume 4 to volume 2. The first eight pages to be moved start at page offset 8 and end at page offset 15. The next eight pages to be moved start at page offset 32 and end at page offset 39. So the range of pages you want to move (the value of the -n flag) is 32 pages; that is, 8 to 39 inclusive. (The other pages in the range are on other volumes because the file is striped.) The command will migrate only the pages from the specified volume in the speci- fied range. # migrate -p 8 -n 32 -s 4 -d 2 str_file Because you did not move all of the pages from volume 4 to volume 2, the file is now stored on four volumes. Note, that this does not change the stripe width of the file. There are still three extent maps. To confirm the migration, reissue the showfile command. Following is part of the output showing the new extent map 2: extentMap: 2 pageOff pageCnt volIndex volBlock blockCnt 8 8 2 51920 256 32 8 56 8 4 68592 256 80 8 104 8 4 68080 128 extentCnt: 4 SEE ALSO
Commands: showfdmn(8), showfile(8), stripe(8) Files: advfs(4) migrate(8)
All times are GMT -4. The time now is 05:27 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy