09-17-2014
Glad to know you are working again. Might be time to get a backup and test your DR plans. What do you go for?
- Your own hardware always running/replicating at another site
- Your own hardware but idle and overwritten with your production system when you need it
- A 3rd party supplier at another site with a blank machine that you overwrite when you need it
That leads on to two questions:-
- If it's an overwrite, what tool do you use to get the first boot of your recovered OS.
- If it's always running & replicating, how do you protect yourself from a catastrophic error being replicated, rather than just hardware failure?
Regards,
Robin
10 More Discussions You Might Find Interesting
1. Solaris
When I installed the SOLARIS 10 OS first time, the desktop would not start up, this was because of network setup. Reinstalled worked. After a week due to some problem I had to reinstall OS, installation went fine and but when i reboot I get this error.
cannot find mis/krtld
boot error loading... (0 Replies)
Discussion started by: johncy_j
0 Replies
2. Solaris
Hi all,
This is my first post here :) Hope some guru here will be able to help ...
I'm in a predicament - my Ultra 60 worked fine before it was put into storage a year ago ... now, I've set it up in my PC room and I get the following message on startup:
Can't open input device.
Keyboard... (3 Replies)
Discussion started by: montezumola
3 Replies
3. Solaris
I have sparc Station 20 which is crashed and doesn't boot from the OK prompt except gives me bunch of errors. How can i retrieve my data from the root drive before go for re-installation. This system has Veritas Volume manager on it don't know the version but assume its 2.xxx.
Thanks
-Adeel (0 Replies)
Discussion started by: deal732
0 Replies
4. Shell Programming and Scripting
Hello, the ls -d command to only list directories in a directory doesn't seem to work on Solaris and the man command says to use that combination: ls -d
Anyone have the same problem and find a resolve?
Thanks
BobK (9 Replies)
Discussion started by: bobk544
9 Replies
5. UNIX for Dummies Questions & Answers
at the end of October i upgraded the distro to 8.10 at first it seemed fine until i restarted my machine the boot seqence started i logged in after that nothing? tried booting again and the same thing happened did i do something wrong during the upgrade to 8.10 did everything the computer asked me... (1 Reply)
Discussion started by: ksnovice
1 Replies
6. Ubuntu
Hey i am running both ubuntu 10.10 and windows 7, trying to make the default boot be windows 7 instead of ubuntu but it doesn't want to work. Ive tried changing default in the grub file it didnt work, then i installed startup-manager and set windows 7 as the OS and it still boots into ubuntu. Thx... (3 Replies)
Discussion started by: Era555
3 Replies
7. Solaris
I am trying to install Solaris x86 using the Jumpstart server. I run the add_install_client command with appropriate options, and reboot my x86 Target box. The installation starts fine and unattended. After the installation completes and the target goes for a re-boot, it does not boot from the HDD... (9 Replies)
Discussion started by: hemalsid
9 Replies
8. Solaris
Hi,
I am running into a some problems creating a dual boot system of 2 solaris instances using ZFS file system and I was wondering if someone can help me out.
First some back ground. I have been asked to change the file system of our server from UFS to ZFS. Currently we are using Solaris... (3 Replies)
Discussion started by: estammis
3 Replies
9. AIX
any ideas ??????? (2 Replies)
Discussion started by: livehho
2 Replies
10. Solaris
Hello,
I have a problem with my machine that won't boot properly.
The story is that I installed a software called apcupsd, which is a control application for my APC battery UPS. I have used version 3.14.10 earlier, but as part of restoring my previously crashed os harddrive I wanted to... (18 Replies)
Discussion started by: Zorken
18 Replies
lsmsad(8) System Manager's Manual lsmsad(8)
NAME
lsmsad - Starts the Storage Administrator (SA) daemon
SYNOPSIS
/usr/sbin/lsmsad
DESCRIPTION
The SA daemon, lsmsad, is a process required by lsmsa, the SA graphical user interface (GUI). The daemon issues commands and obtains system
information on behalf of SA.
The SA daemon runs on a Tru64 UNIX system on which LSM is initialized and running. The SA client runs on any machine that supports the
Java Runtime Environment.
The SA daemon is automatically started at boot time. Under normal conditions, the daemon does not need to be run manually.
If SA does not start during the boot process, enter:
/sbin/init.d/lsmsa stop
To restart SA, enter:
/sbin/init.d/lsmsa start
Only one SA daemon can be running on a system at a given time. If a second SA daemon attempts to start, it will fail.
RESTRICTIONS
You must be root user to run lsmsad.
FILES
The script that starts lsmsad at boot time. The command log file that tracks SA tasks. The access log file that tracks login to SA. The
server log file that tracks server startup information and server errors. The log maintenance shell script that saves and compresses log
files.
SEE ALSO
lsmsa(8), volintro(8)
lsmsad(8)