You are still missing mine. Unless you expect a crystal ball to predict what will happen in the future with currently healthy components, the only reasonable way to prevent their future faults is by monitoring events coming from them. This is what SMF is designed to do.
Alternatively, if your goal is really to react to something that hasn't happened yet, you can pro-actively replace each disk after a period of use significantly smaller than its MTBF.
If you just care about your data, use something like RAIDZ2 with hot spares. Your system will happily survive two disks crashing at the same time and will automatically replace them by the spares.
Attempting to update an 11.0 server with many non-global zones installed. pkg publisher is pkg.oracle.com/solaris/support.
FMRI = pkg://firstname.lastname@example.org,5.11-0.175.1.15.0.4.0:20131230T203500Z
When we run pkg update --accept the server contacts oracle, checks packages, finds about 700... (4 Replies)
Discussion started by: CptCarrot
2. Post Here to Contact Site Administrators and Moderators
I have been trying to install a particular software using remote linux server.
some thing like this:
rsh <host ID> /usr/sbin/swinstall -x autoreboot=true -s /tmp/<software> <Product name>.
The problem is whenever I try to install the product through a shell script the installation... (1 Reply)