Dumping NIM objects to a script
Saturday, January 20. 2007
With all the latest improvements to NIM like "alternate master" and the like, I recently ran across something it doesn't do automatically: Copying a subset of a NIM servers objects to another server.
At work, we have several different NIM masters in different locations. All of them serve the same resources but with different clients. We use rsync to keep the actual data on disk in sync and create NIM objects accordingly(which means that we create SPOTs only once, at the "master master" and copy the SPOT data to the other machines and simply add the SPOT object to NIM without recreating the whole thing).
When the rootvg of one of our servers failed, I simply sent a set of harddisks there, containing nothing more than the base operating system and an old copy of the NIM instance. I didn't need to care about the actual installation images, because they were on a RAID5, but the NIM database was out of sync with what was on the disk.
At work, we have several different NIM masters in different locations. All of them serve the same resources but with different clients. We use rsync to keep the actual data on disk in sync and create NIM objects accordingly(which means that we create SPOTs only once, at the "master master" and copy the SPOT data to the other machines and simply add the SPOT object to NIM without recreating the whole thing).
When the rootvg of one of our servers failed, I simply sent a set of harddisks there, containing nothing more than the base operating system and an old copy of the NIM instance. I didn't need to care about the actual installation images, because they were on a RAID5, but the NIM database was out of sync with what was on the disk.
Continue reading "Dumping NIM objects to a script"
