Servicios

Web hosting
Ver »
Páginas Web
Ver »
Soporte UNIX
Ver »
UNIX TIPS
Ver »

BACKUP & RESTORE SOFTWARE SMS SF E25K

****** Monitoreo de Plataforma ******************

System Controller Environment Variables

SMSOPT=/opt/SUNWSMS
SMSETC=/etc/opt/SUNWSMS
SMSVAR=/var/opt/SUNWSMS
SMSLOGGER=/var/opt/SUNWSMS/adm

Para monitorear cualquier cambio visulizar messages de la plataforma: cd $SMSLOGGER/plattform
Para monitorear cualquier dominio: cd $SMSLOGGER/LETRA-DOMINIO

sc0 # su - sms-svc
cintra2sc0:sms-svc:1> env
HOME=/export/home/sms-svc
PATH=/opt/SUNWSMS/bin:/usr/dt/bin:/usr/ccs/bin:/usr/sbin:/usr/bin:/usr/ucb:.
LOGNAME=sms-svc
HZ=100
TERM=vt100
SHELL=/bin/csh
MAIL=/var/mail/sms-svc
TZ=Mexico/General
PWD=/export/home/sms-svc
USER=sms-svc
SMSOPT=/opt/SUNWSMS
SMSETC=/etc/opt/SUNWSMS
SMSVAR=/var/opt/SUNWSMS
SMSLOGGER=/var/opt/SUNWSMS/adm
LD_LIBRARY_PATH=/opt/SUNWSMS/lib:/usr/lib
MANPATH=/opt/SUNWSMS/man:/usr/man
EDITOR=/usr/bin/vi
sc0:sms-svc:2>

******HACER UN BACKUP DEL SW SMS******

1. Detener Failover

   scmain20:sms-svc:1> setfailover off

2. Detener el SW de SMS

   # /etc/init.d/sms stop

3. Hacer el respaldo de los archivos de
   configuracion de SMS

   # smsbackup /var/tmp

4. Levantar el SW de SMS

   # /etc/init.d/sms start

5. Levantar Failover

   scmain20:sms-svc:2> setfailover on


*****HACER UN RESTORE DEL SW SMS******

1. Detener Failover

   scmain20:sms-svc:1> setfailover off

2. Detener el SW de SMS

   # /etc/init.d/sms stop

3. Hacer la restauracion de los archivos de
   configuracion de SMS

   # smsrestore /var/tmp/sms_backup.1.5.cpio

4. Levantar el SW de SMS

   # /etc/init.d/sms start

5. Levantar Failover

   scmain20:sms-svc:2> setfailover on

******** VALIDAR STATUS DEL FAILOVER ************

sc0:sms-svc:11> showfailover
SC Failover Status:     ACTIVE
C1: UP

******** Displaying the SC Role ******************

sc0:sms-svc:12> showfailover -r
MAIN
sc0:sms-svc:13>

Regresar


Random TIPS

EFFICIENT COMMANDS
In anytime I see someone code inefficiently. Here are three of the most common mistakes, followed by a better way to do the same thing.
Bad: cat somefile | grep something
Better: grep something somefile
Why: You're running one program (grep) instead of two (cat and grep).
Bad: ps -ef | grep something | grep -v grep
Better: ps -ef | grep [s]omething
Why: You're running two commands (grep) instead of three (ps and two greps).
Bad: cat /dev/null > somefile
Better: > somefile
Why: You're running a command (cat) with I/O redirection, instead of just redirection.
Although the bad way will have the same result, the good way is far faster. This may seem trivial, but the benefits will really show when dealing with large files or loops.

free counters