On Thu, Feb 13, 2003 at 09:30:30AM -0000, Clawson, Simon wrote:
However, there are methods of replicating the /etc data to another volume, then telling the filer to boot this as vol0. This would of course mean any NIS maps etc are broken until you change their paths, but the filer would be up and running quicker than if you were to have to restore the whole root volume first, and you would not be using two 72Gb disks for 40mb of data.
the only mounts that would change would be those on the root volume (vol0) that were specified in the maps as "filer:/qtree" instead of "filer:/vol/vol0/qtree" because suddenly "filer:/qtree" would be on the new root volume (vol1).
but since vol0 is down, those qtrees have bigger problems :)
now if vol0 is unbootable, but still serving data, then yes, the "filer:/qtree" mount paths would be broken. that is why it a good thing (tm) to always have NIS entries specified in terms of "filer:/vol/vol0/qtree" for mounts from the [vol0] root volume.
cheers -- email: lance_bailey@pmc-sierra.com box: Lance R. Bailey, unix Administrator vox: +1 604 415 6646 PMC-Sierra, Inc fax: +1 604 415 6151 105-8555 Baxter Place http://www.lydia.org/~zaphod Burnaby BC, V5A 4V7 Quick sysadmin test... Ever reverse engineer a program? Did it work afterwards? Did it work better?