Article

(View Disclaimer)

ENVIRONMENT: Windows OS (others could work as well)
ZENworks 7 and NetWare 6.5

Scenario:

• Desktop Windows OS has crashed.
• Need to get lots of files off the computer and onto the server.
• Have network access but no available USB drive.
• Do have ZENworks for Desktops (have done this with version 7).
• Do have NFS services running on NetWare server (in this scenario the server IP address is 10.1.1.08).

Solution

1. Make sure ZfD is up and running on server and sufficient hard drive space exists.
2. Setup an NFS export - these are from my configuration.
3. Add this line to the PATHTAB file (sys:/etc)
   /vols/images images:\
4. Add this line to the EXPORTS file (sys:/etc)
   /images -rw=@10.1.0.0/16 -root=@10.1.0.0/16 (I am allowing an entire subnet to gain access to this mount - obvious security issue but I am only using it as a temporary location)
5. Restart NFS services at the server.
6. Call the bash shell at the console and issue df command and verify successful mount.
7. XNFS.LOG file (sys:/etc/nfs) will help isolate any configuration or connection errors
8. Boot work station utilizing PXE boot service and choose "... maintenance mode".
9. At the Linux prompt issue the df command:
   /rootfs
   /tempfs
   /dev/ram2
   should be returned.
10. Create two directories. I use /local and /remote.
    mkdir /local
    mkdir /remote
11. If your computer uses an IDE drive your hard disk is probably /dev/hda. If unsure, the ZENworks Imaging Partition tool can be used to discover the current device.
12. Mount the two locations:
    mount /dev/hda1 /local
    mount 10.1.1.108:/images /remote
13. The remote mount may take a while and the NFS server must be able to resolve a hostname for the computer. I have a dynamic range of IP addresses I use for transient machines so at this point I look at the XNFS.LOG file (sys:/etc/nfs) to verify the IP address of the workstation and to verify the workstation is actually making the request. I then edit the hosts file on the server to reflect the name of the device.
    e.g. 10.1.248.133 temp.lcps.internal temp
14. Then issue the second (remote) mount command again.
15. Use the df command to verify the mount points.
16. Create a directory for your recover:
    mkdir /remote/recover
17. If all is well, change to the directory level of the /local mount point from which the file recovery is to take place.

    This example is attempting to recover the "Documents and Settings" folder.

    cd "/local/Documents and Settings"

    The quotes handle the spaces in the folder name.

18. Then issue a simple copy command such as
    cp -rpf . /remote/recover
19. Other tools can be employed if so desired (find, cpio, tar, etc.).
20. Since files are copying to a NetWare server, grant access rights to the user, map the recovery location for the user and let the user sort what is needed from what is not.
21. Remember to close up your open NFS mount when finished.
    Just "rem" the EXPORTS file so everything is there when needed.

If you have any questions you may contact James at jhammond@lcps.k12.nm.us

Disclaimer: As with everything else at Cool Solutions, this content is definitely not supported by Novell (so don't even think of calling Support if you try something and it blows up).

It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test, test, test before you do anything drastic with it.