Lets assume the following;
NFS Server IP is 192.168.10.50
The NFS server exported directory is /ir110
The SCS NIC hme0 is 192.168.10.100
The script files are in the /ir110 directory
A. Create the NFS
You must create a NFS server with read/write permissions so the
iR110/150 SCS can upload files
I cant help you with NFS server configuration options here. There
are to many OS's and versions
Just ensure that 192.168.10.100 has read/write permissions
B. Boot SCS from OS CD
Use init 0 or whatever safe means to get the the ok prompt
Then type boot cdrom -s
C. Configure the SCS NIC and mount NFS
After the SCS boots up type the following
#ifconfig hme0
192.168.10.100
(Gives the SCS's on board NIC (nearest to the video connector) an IP
address)
#ifconfig hme0
up
(Brings this NIC interface up)
#
mount 192.168.10.50:/ir110 /mnt
(Mounts the NFS directory /ir110 onto the mount point /mnt)
D. Obtain, decompress and check
the permissions of the scripts
You can get the ir110-backup-scripts.zip file
here
I zipped the two scripts to bypass IE download issues
Unzipping the file will reveal 2 scripts called "upload" and "download"
Copy these 2 scripts to the NFS server's /ir110 directory
On the SCS, cd to the /mnt directory
You should be able to use ls and see the scripts you just copied
Now just to be safe, lets copy the scripts to the SCS's /tmp directory
#cp /mnt/upload
/tmp
(Copies the script upload to the SCS under /tmp)
#cp /mnt/download
/tmp
(Copies the script download to the SCS under /tmp)
#cd
/tmp
(CD to /tmp)
Now we have to check the permissions on the scripts
If you unzipped ir110-backup-scripts.zip on a Dos/Windows machine the
file permissions will be lost
If you unzipped ir110-backup-scripts.zip on a Unix/Linux box, the
permissions will not be lost
Do this procedure to check and change the permissions if required
Do a ls -la
Ensure root has execute permissions on the files "download" and
"upload" like the
red x in
this example
-rwxr--r-- 1
root wheel 222 Feb 27 22:12 download
-rwxr--r-- 1
root wheel 214 Feb 27 22:12 upload
If you see this;
-rw-r--r-- 1
root wheel 222 Feb 27 22:12 download
-rw-r--r-- 1
root wheel 214 Feb 27 22:12 upload
The
red - indicates that
root
does not have execute
permissions on these files
You will need to use
chmod to
change this
#chmod u+x upload
#chmod u+x download
Do another ls -la to confirm the permissions are set correctly
E. Executing the scripts
From the /tmp directory, the scripts are executed as follows
To upload the SCS hard disk to an image called backup.bz2, type the
following
./upload backup.bz2
The upload will take 3-4 hours to complete so please be patient
To download an image called backup.bz2 to the SCS, type the
following
./download backup.bz2
The download process will take a minumum of 45-60 minutes to
complete
F. Optionally "zero" the hard disk
If you are doing a fresh install, you may want to consider "zeroing"
the hard drive
This will write zero's to the entire hard disk
Any old hard disk data will be overwritten by zero's
This will make your backups signicantly smaller
More info on this
here
Here is how
Use the OS CD as follows
# init 0
ok boot cdrom -s
#dd if=/dev/zero of=/dev/rdsk/c0t0d0s2 bs=2048k
This process should take less than 30 minutes
Note:
Using dd after zeroing the drive may result in errors lile
Warning: /pci@1f,0/pci@1,1/ide3/dad@0,0 (dad0):
corrupt label - wrong magic number
dd: /dev/rdsk/c0t0d0s2: open: I/O error
See Step 14 below to get around this error
G. You may want to test the uploaded
file integrity
If bzip2 is installed on the NFS server simply type this
bzip2 -t -v filename.bz2
bzip2 -t -v will finish with "ok" if the file is good
bzip2 -t -v will finish with Data integrity (CRC) error is the file is
corrupt
It took 40 minutes on a P2 running FreeBSD to check a 760MB backup file