Our company recently upgraded our SAN solution and the SAN switch was an older model. Utilizing EMC’s SRDF migration utility was not a practical option because the 300+GB of data for one server would have been copied from the old SAN to a intermediate device before being copied to the new DMX. We utilize two HBAs per server for load sharing and redundancy. The question whether we could transfer the data between SANs by connecting one HBA to one SAN and the other HBA to the new SAN and simply copy the data and trustees.
How could this be done? I looked at several solutions.
- TOOLBOX is fast and copies long filenames on the same server, but does not copy Trustees. Nope.
- ZEN for Servers is an option, but we don’t use it and we don’t have the time frame. Nein.
- RSYNC could have worked but I know it tends to have problems with very large (2+GB) files on initial Sync. Next.
- Windows-based Ncopy? That would take forever and a differential copy on the final cut-over would be impossible. Whew.
What about Novell’s Server Consolidation/Migration Utility? And use the Server agents?
- Server based copy, no data copy through the client.
- Long filenames and trustees.
There was one question and I quickly found that it will indeed migrate data from one volume to another on the same server. Sweet.
This is what I did …
Give the World Wide Name (WWN) to the SAN engineer so the new target volume can be zoned. Once complete, connect the second HBA to the new SAN switch.
I’m a long time console guy so I use the command line utilities. Creating a new volume can be accomplished using iManager, NetWare Remote Manager (NRM) or ConsoleOne.
Create the New Volume
At the server console, load NSSMU and you should see the new unpartitioned space.
Look at each device on the left-hand side and use the arrow up/down keys to move. Highlight each device and look for the new device, (Hint: The new device will show very large “unpartitioned” space).
Highlight the new device and press F3 to initialize it for use.
Escape back to the main menu and select Pools. Press Ins to create a new Pool. Name the pool something meaningful relating to the new SAN, i. e., DMX-POOL.
Once the pool is created, escape back to the main menu and select Volumes. Press Ins to create a new Volume. At this point, the name of the volume doesn’t really matter because, later you are going to rename it for administrative reasons.
When you create the volume, you will see the new NSS partitioned space available. Assign all of it to the volume and when complete, exit the NSSMU Utility and back to the server console.
Type Volumes at the console and you should see the new volume you just created. If not, try mounting it to see if it mounts.
Create the Server Migration Script
Install the Novell Server Consolidation/Migration Utility on a workstation and load it.
Click ok on the splash screen.
This will be a NetWare to NetWare Consolidation.
In our example here we are not copying printers.
Create a New Project.
Enter the name of the project and where you want the files to be stored.
NOTE: Don’t worry about the location being local, when we verify the data and state the server-based copy, the utility will transfer the project files to the server.
If you are authenticated to eDirectory, then the name of your Tree will be in both fields. If not, then you can click on Login and browse to your target Tree.
On the top menu, click Project | Enable Server-Based Processing. The above window will appear.
On the left-hand side of the window, expand your Source volume. Select the folders you wish to copy, drag them to the Right-hand side (target) and drop them on the volume name. Note the Blue Arrows!
Note: This action does not copy or alter anything! This is what you intend to do. You can change it however you like at this time.
Once you are satisfied with your project, click Project and Verify and Copy Data.
This is the Verification Wizard. It will give you some more options for your consolidation.
Here is a list of the folders you dropped to the new volume and the source is listed on the left.
Because you enabled Server-based earlier, the “Yes” is selected for you.
Choose Always copy for the initial copy. When you move for your final cut-over, you will run this again and select Copy if newer to “refresh” the new volume with file changes.
I left this page as the default, since I wanted to copy everything to the new volume.
This page will allow you to exclude files, is desired. Again, I wanted a complete copy.
Make sure that your Tree, and username are correct. Enter your password. (This will be encrypted in the final XML file).
I left this unchecked because my new volume was larger than the existing. You don’t have to disable login for the initial copy. This utility does just fine with users accessing files while this takes place. The final cut-over copy should disallow users from accessing their files.
This screen informs you that the utility is ready to check the server(s) to ensure the copy can take place. It checks SMDR versions and whether the your user account has the necessary rights to perform this action.
This screen is the final part of the planning of the copy. It tells you that everything is cool and it will copy the necessary files, (nlms, and the project xml files) to the server. If you forgot anything or need to make changes, click Back now. Otherwise, click Proceed.
This screen tells you that the process has been created and you are done with the client side of this project. Click Close and proceed to the Server Console.
Server-Based Execution of the Project
If you run any server based antivirus software, is it faster if you unload them before you start the process. Also, ensure that the user performing this process, probably you, has no volume restrictions on the target volume.
At the server console, type:
NUWAGENT -a "projectname"
The screen will change and you will see the progress of the project. When it is complete, the agent exits and you will be returned to the server console screen.
Post Consolidation Tasks
I did this copy during the production day and only saw a 20% increase in utilization on the server. On the day we did the final cut over, I created a new project and chose to merge the existing directories, to only copy if newer and to disable login.
Once the final copy was completed. I dismounted both the existing and the new volumes.
I renamed the existing volume and then renamed the new volume to the old volume’s name.
Existing volume name: VOL1 New volume name: VOL2
Rename the existing volume to VOL3 Rename the new volume to VOL1
If other resources, i.e., ZENworks Application Objects are stored on this volume, the paths to the files will not have to change to reflect the volume change.
We used the Home Directory Changer from Cool Tools: https://www.novell.com/coolsolutions/tools/14312.html to change all the volumes back to VOL1. Renaming a volume changes this attribute in the user’s environment.
After we checked everything else, we were able to remove the fiber from the old SAN.