2013년 6월 13일 목요일
Avamar Rman Tapble space 복구 방법
|
(1) 복구 확인용 테이블스페이스 및 테이블 생성
OS> sqlplus / as sysdba SQL> create tablespace test_ts datafile '/legato/oracle/oradata/master/test.dbf' size 10m; SQL> alter user sys quota unlimited on test_ts; SQL> create table sys.test tablespace test_ts as select 1 as no, sysdate as date1 from dual; SQL> exit
OS> rman target /
RMAN> CONFIGURE CONTROLFILE AUTOBACKUP
OFF;
RMAN> report schema;
using target database control file
instead of recovery catalog
Report of database schema
List of Permanent Datafiles
===========================
File Size(MB) Tablespace RB segs Datafile Name
---- -------- --------------------
------- ------------------------
1
510 SYSTEM *** /legato/oracle/oradata/master/system01.dbf
2
210 UNDOTBS1 ***
/legato/oracle/oradata/master/undotbs01.dbf
3
430 SYSAUX ***
/legato/oracle/oradata/master/sysaux01.dbf
4
22 USERS ***
/legato/oracle/oradata/master/users01.dbf
5
300 SPLEXT ***
/legato/oracle/oradata/master/splext01.dbf
6
1000 ALST *** /legato/oracle/oradata/master/alst01.dbf
7
100 SUJI *** /legato/oracle/oradata/master/suji01.dbf
8
2400 QCO *** /legato/oracle/oradata/master/qco01.dbf
9
500 LIVE *** /legato/oracle/oradata/master/live.dbf
10
1024 SPLEXEE *** /legato/oracle/oradata/master/splexee01.dbf
11
10 TEST_TS *** /legato/oracle/oradata/master/test.dbf
List of Temporary Files
=======================
File Size(MB) Tablespace Maxsize(MB) Tempfile Name
---- -------- --------------------
----------- --------------------
1
269 TEMP 32767
/legato/oracle/oradata/master/temp01.dbf
(2) 데이터 파일과 컨트롤 파일 백업
RMAN> backup database;
… 생략 …
RMAN> backup current controlfile format
'/u01/app/oracle/oradata/devdb_fra/DEVDB/controlfile001.bck';
… 생략 …
RMAN> sql 'alter system switch logfile';
RMAN> sql 'alter system switch logfile'; RMAN> sql 'alter system switch logfile';
RMAN> sql 'alter system switch logfile';
RMAN> sql 'alter system switch logfile';
(3) 테이블 스페이스 삭제
RMAN> sql 'drop tablespace test_ts including contents and datafiles'; -테이블스페이스 삭제 RMAN> exit
OS> tail -n 20
$ORACLE_HOME/rdbms/log/alert_devdb.log
master:root:/usr/bin]tail -f /legato/oracle/admin/master/bdump/alert_master.log
media 'avtar007'
handle 'CONTROLFILE.master.c-2799742462-20111026-04'
Wed Oct 26 18:26:04 2011
drop tablespace test_ts including
contents and datafiles
Wed Oct 26 18:26:20 2011
Deleted file
/legato/oracle/oradata/master/test.dbf
Starting control autobackup
Control autobackup written to DISK device
handle '/legato/oracle/orahome/dbs/c-2799742462-20111026-05'
Completed: drop tablespace test_ts
including contents and datafiles
^Cmaster:root:/usr/bin]date
Wed Oct 26 18:32:38 KORST 2011
18시 27분 시점으로 복구
(4) 테이블스페이스 삭제 상황이므로 컨트롤 파일과 모든 데이터 파일을 복원하고 복구
OS> export NLS_DATE_FORMAT='YYYY-MM-DD HH24:MI:SS' OS> export NLS_LANG=american OS> rman target /
RMAN> shutdown immediate
RMAN> startup nomount RMAN>
set dbid=2799742462;
set controlfile autobackup format for
device type sbt to 'CONTROLFILE.master.%F';
run {
allocate channel c1 type sbt
PARMS="SBT_LIBRARY=/usr/local/avamar/lib/libobk_avamar64.so,ENV=(PATH=/usr/sbin:/usr/bin:/sbin:/usr/local/avamar/bin)"
format '%d_%U';
send '"--prefix=10g/master/"' ;
send
'"--flagfile=/usr/local/avamar/var/avtar.txt"' ;
restore controlfile from
'CONTROLFILE.master.c-2799742462-20111026-04';
release channel c1;
}
RMAN> startup mount
RMAN> run {
allocate channel c1 type sbt
PARMS="SBT_LIBRARY=/usr/local/avamar/lib/libobk_avamar64.so,ENV=(PATH=/usr/sbin:/usr/bin:/sbin:/usr/local/avamar/bin)"
format '%d_%U';
send
'"--prefix=10g/master/"' ;
send
'"--flagfile=/usr/local/avamar/var/avtar.txt"' ;
restore database;
release channel c1;
}
(5) 복구 확인
RMAN> report schema; Report of database schema
List of Permanent Datafiles
=========================== File Size(MB) Tablespace RB segs Datafile Name ---- -------- -------------------- ------- ------------------------ RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03002: failure of report command at 05/18/2010 17:54:41 RMAN-20021: database not set RMAN-06031: could not translate database keyword RMAN> exit
OS> rman target /
RMAN> report schema;
using target database control file
instead of recovery catalog
Report of database schema
List of Permanent Datafiles
=========================== File Size(MB) Tablespace RB segs Datafile Name ---- -------- -------------------- ------- ------------------------ 1 200 SYSTEM *** /u01/app/oracle/oradata/devdb/system01.dbf 2 120 UNDOTBS01 *** /u01/app/oracle/oradata/devdb/undotbs01.dbf 3 200 SYSAUX *** /u01/app/oracle/oradata/devdb/sysaux01.dbf 4 10 UNDO01 *** /u01/app/oracle/oradata/devdb/undo01.dbf 5 10 USER_TAB_TS *** /u01/app/oracle/oradata/devdb/user_tab_ts.dbf 6 5 USER_IND_TS *** /u01/app/oracle/oradata/devdb/user_ind_ts.dbf 7 10 TEST_TS *** /u01/app/oracle/oradata/devdb/test_ts.dbf
List of Temporary Files
======================= File Size(MB) Tablespace Maxsize(MB) Tempfile Name ---- -------- -------------------- ----------- -------------------- 1 20 TEMP 2048 /u01/app/oracle/oradata/devdb/temp01.tmp 2 10 TEMP01 10 /u01/app/oracle/oradata/devdb/temp01.dbf
RMAN> exit
OS> sqlplus / as sysdba SQL> select * from sys.test;
NO DATE1
---------- ------------------- 1 2010-05-18 17:36:59 SQL> exit
(6) 정리
OS> rman target / RMAN> show retention policy; RMAN> crosscheck database; RMAN> crosscheck archivelog all; RMAN> report obsolete; RMAN> delete obsolete; RMAN> list backup by file; RMAN> exit | ||||
|
|
Avamar Time sync 방법
Avamar Time Sync
NTP Server 없을 때
root@avamar:~/>: su - dpnid
dpn@avamar:~/>: ssh-agent bash
dpn@avamar:~/>: ssh-add ~/.ssh/dpnid
dpn@avamar:~/>: asktime
asktime: INFO: [asktime version 4.1.1-340 (1.6)]
asktime: INFO: Logging to /usr/local/avamar/var/asktime.log
asktime: INFO: The name "ntp" did not resolve to any DNS "IN A"
resource records.
If you wish asktime to suggest a list of internal time servers
automatically, then ask your hostmaster to create one
or more "IN A" resource records for the name "ntp"
in the "gangbuk.go.kr" zone.
For example:
ntp IN A 10.0.254.19
ntp IN A 192.168.100.5
ntp IN A 192.168.100.7
Creating DNS resource records for "ntp" is optional; you
will have other opportunities to enter time server information.
Continue?
y(es), n(o), q(uit/exit): y
--------------------------------------------------------
Do you wish to use U.S. public Internet time servers such as
those offered by NIST or the U.S. Naval Observatory?
Please note the following issues with public time servers:
1. NETWORK CONFIGURATION: In order to use public Internet time
servers your site must allow port 123/udp traffic to and
from the selected Internet time servers.
2. SECURITY: Your site security policy might forbid the use
of Internet time servers. Consider setting up two or
more internal NTP time servers instead.
3. APPROPRIATE USE: Some of the U.S. public time servers known
to asktime are intended to be used only by clients within
specific U.S. time zones. If you use one of these time
servers, then asktime infers that you are using the
corresponding local time zone.
(Your previous answer was: "n".)
y(es), n(o), q(uit/exit): n
--------------------------------------------------------
Are there other external time servers that you
would like to use?
(Your previous answer was: "n".)
y(es), n(o), q(uit/exit): n
--------------------------------------------------------
Do you have a dedicated Axion subnet configuration, e.g., 2##.##.##.0/25?
Answer y(es) if only Axion nodes reside in the subnet;
n(o) if non-Axion nodes share the subnet
(Your previous answer was: "y".)
y(es), n(o), q(uit/exit): y
--------------------------------------------------------
This host, "avamar.backup.com", is a member of subnet 2##.##.##.0/25.
Use this subnet?
y(es), n(o), q(uit/exit): y
--------------------------------------------------------
Use this previously specified local time zone?
Asia/Seoul
y(es), n(o), q(uit/exit): y
--------------------------------------------------------
Do you wish to configure the default set of nodes?
Answering y(es) configures this set of nodes:
#.s -- all utility/services nodes,
#.# -- all data nodes.
Answering n(o) will afford you the opportunity to
configure other MCS nodes and/or individual nodes.
y(es), n(o), q(uit/exit): y
--------------------------------------------------------
Generating time configuration files...
[mktime.custom version 1.2]
--------------------------------------------------------
The time configuration files have been created
in the following directory:
/usr/local/avamar/var/time-config-files
Do you wish to proceed with installation of these
files on the selected nodes?
Answering y(es) will proceed with installation.
Answering n(o) will not proceed, but will leave
available for future use the answers you have
made to the preceding configuration questions.
Answering q(uit) will exit WITHOUT saving your
answers.
y(es), n(o), q(uit/exit): y
--------------------------------------------------------
We need an approximately correct initial date and time.
Here is the current date and time on this host, avamarex.gangbuk.go.kr:
Fri May 22 11:00:56 KST 2009
Please pay close attention to the MONTH, DAY, and YEAR
as well as the time.
Is this approximately correct (within a minute or two)?
y(es), n(o), q(uit/exit): y
--------------------------------
Distributing and installing time configuration files.
Please allow a minimum of 5 minutes. More time may
be required, depending on the number of nodes in the
Axion system and how busy those nodes are.
If you wish to watch this process, apply this command
in another window:
tail -f /usr/local/avamar/var/timedist.log
You may also find it helpful to monitor the following
file on each node (starting with 0.s):
/usr/local/avamar/var/timesyncmon.log
Time now: Fri May 22 11:00:58 KST 2009
Please wait...
--------------------------------------------------------
Do you wish to wait and watch for time synchronization?
y(es), n(o), q(uit/exit): y
asktime: INFO: Status monitoring key:
x ntpd not running on one or more nodes (should auto-correct quickly)
o no clock selected yet on one or more nodes
. unsatisfactory clock selections on one or more nodes
< insufficient time server contacts on one or more nodes
> offset still greater than 2 s on one or more nodes
) offset still greater than 1 s on one or more nodes
} offset still greater than 500 ms on one or more nodes
| offset still greater than 250 ms on one or more nodes
* possible convergence seen (offset <= 250 ms on all nodes)
Notes:
- Ideally you will see something like this: "ooxxooooooooooooooo........***"
- If you interrupt monitoring with control-C, there may be a delay
of a few seconds before monitoring stops.
Commencing 60 monitoring passes, with 10-second intervals
between passes. Time now: Fri May 22 11:13:40 KST 2009
ooooooooooooooooooooooooooooooooooooooooooooooooooooooo***
--------------------------------------------------------
We appear to have time synchronization.
Time now on this host: Fri May 22 11:23:57 KST 2009
Do you wish to see the results?
y(es), n(o), q(uit/exit): y
Using /usr/local/avamar/var/probe.out
(0.s) ssh -x admin@2##.##.##'/usr/sbin/ntpq -pn 2>&1'
remote refid st t when poll reach delay offset jitter
==============================================================================
*127.127.1.0 LOCAL(0) 8 l 25 64 377 0.000 0.000 0.001
(0.0) ssh -x admin@211.34.96.15 '/usr/sbin/ntpq -pn 2>&1'
remote refid st t when poll reach delay offset jitter
==============================================================================
*2##.##.##.## LOCAL(0) 9 u 41 64 17 0.132 1.346 1.848
(0.1) ssh -x admin@211.##.##.## '/usr/sbin/ntpq -pn 2>&1'
remote refid st t when poll reach delay offset jitter
==============================================================================
*2##.##.##.## LOCAL(0) 9 u 37 64 17 0.127 4.184 2.999
2##.##.##.## .INIT. 16 u 34 64 0 0.000 0.000 4000.00
(0.2) ssh -x admin@211.##.##.## '/usr/sbin/ntpq -pn 2>&1'
remote refid st t when poll reach delay offset jitter
==============================================================================
*2##.##.##.## LOCAL(0) 9 u 37 64 17 0.125 1.608 1.130
2##.##.##.## .INIT. 16 u 34 64 0 0.000 0.000 4000.00
Using /usr/local/avamar/var/probe.out
(0.s) ssh -x admin@2##.##.##.## '/bin/date'
(0.0) ssh -x admin@2##.##.##.## '/bin/date'
(0.1) ssh -x admin@2##.##.##.## '/bin/date'
(0.2) ssh -x admin@2##.##.##.## '/bin/date'
Fri May 22 11:24:07 KST 2009
Fri May 22 02:24:07 UTC 2009
Fri May 22 02:24:07 UTC 2009
Fri May 22 02:24:07 UTC 2009
--------------------------------------------------------
Done.
NOTES:
* Time on this host is: Fri May 22 11:24:07 KST 2009
dpn@avamarex:~/>:
==============================================================================
==============================================================================
==============================================================================
==============================================================================
NTP Server 있을 때
root@avamar:~/>: su - dpnid
dpn@avamar:~/>: ssh-agent bash
dpn@avamar:~/>: ssh-add ~/.ssh/dpnid
dpn@avamar:~/>: asktime
asktime: INFO: [asktime version 4.1.1-340 (1.6)]
asktime: INFO: Logging to /usr/local/avamar/var/asktime.log
asktime: INFO: The name "ntp" did not resolve to any DNS "IN A"
resource records.
If you wish asktime to suggest a list of internal time servers
automatically, then ask your hostmaster to create one
or more "IN A" resource records for the name "ntp"
in the "backup.com" zone.
For example:
ntp IN A 10.0.254.19
ntp IN A 192.168.100.5
ntp IN A 192.168.100.7
Creating DNS resource records for "ntp" is optional; you
will have other opportunities to enter time server information.
Continue?
y(es), n(o), q(uit/exit): y
--------------------------------------------------------
Do you wish to use U.S. public Internet time servers such as
those offered by NIST or the U.S. Naval Observatory?
Please note the following issues with public time servers:
1. NETWORK CONFIGURATION: In order to use public Internet time
servers your site must allow port 123/udp traffic to and
from the selected Internet time servers.
2. SECURITY: Your site security policy might forbid the use
of Internet time servers. Consider setting up two or
more internal NTP time servers instead.
3. APPROPRIATE USE: Some of the U.S. public time servers known
to asktime are intended to be used only by clients within
specific U.S. time zones. If you use one of these time
servers, then asktime infers that you are using the
corresponding local time zone.
y(es), n(o), q(uit/exit): n
--------------------------------------------------------
Are there other external time servers that you
would like to use?
y(es), n(o), q(uit/exit): y
--------------------------------------------------------
Please enter the IP addresses of the external
time servers, one per line, in the form
A.B.C.D, e.g. 192.168.100.5.
Time servers may also be specified as host names,
provided that those names will resolve.
Press Enter or Return after each response.
An empty response (a blank line) ends the list.
[00] 203.248.240.140
[01] 123.214.172.108
[02]
203.248.240.140 (보라넷 타임 서버)
123.214.172.108 (이화여대 타임 서버)
This is the list that you entered:
203.248.240.140
123.214.172.108
Is this list correct?
y(es), n(o), q(uit/exit): y
--------------------------------------------------------
Use this previously specified local time zone?
Asia/Seoul
y(es), n(o), q(uit/exit): y
--------------------------------------------------------
Generating time configuration files...
[mktime.custom version 1.2]
--------------------------------------------------------
The time configuration files have been created
in the following directory:
/usr/local/avamar/var/time-config-files
Do you wish to proceed with installation of these
files on the selected node?
Answering y(es) will proceed with installation.
Answering n(o) will not proceed, but will leave
available for future use the answers you have
made to the preceding configuration questions.
Answering q(uit) will exit WITHOUT saving your
answers.
y(es), n(o), q(uit/exit): y
--------------------------------------------------------
We need an approximately correct initial date and time.
Here is the current date and time from NTP, but
with year and time zone from this host:
Thu Jul 9 17:20:35 KST 2009
Please pay close attention to the MONTH, DAY, and YEAR
as well as the time.
Is this approximately correct (within a minute or two)?
y(es), n(o), q(uit/exit): y
--------------------------------
Distributing and installing time configuration files.
Please allow a minimum of 3 minutes. More time may
be required, depending on the number of nodes in the
Axion system and how busy those nodes are.
If you wish to watch this process, apply this command
in another window:
tail -f /usr/local/avamar/var/timedist.log
You may also find it helpful to monitor the following
file on each node (starting with 0.s):
/usr/local/avamar/var/timesyncmon.log
Time now: Thu Jul 9 17:20:58 KST 2009
Please wait...
--------------------------------------------------------
Do you wish to wait and watch for time synchronization?
y(es), n(o), q(uit/exit): y
]asktime: INFO: Status monitoring key:
x ntpd not running on one or more nodes (should auto-correct quickly)
o no clock selected yet on one or more nodes
. unsatisfactory clock selections on one or more nodes
< insufficient time server contacts on one or more nodes
> offset still greater than 2 s on one or more nodes
) offset still greater than 1 s on one or more nodes
} offset still greater than 500 ms on one or more nodes
| offset still greater than 250 ms on one or more nodes
* possible convergence seen (offset <= 250 ms on all nodes)
Notes:
- Ideally you will see something like this: "ooxxooooooooooooooo........***"
- If you interrupt monitoring with control-C, there may be a delay
of a few seconds before monitoring stops.
Commencing 60 monitoring passes, with 10-second intervals
between passes. Time now: Thu Jul 9 17:21:07 KST 2009
.........................***
--------------------------------------------------------
We appear to have time synchronization.
Time now on this host: Thu Jul 9 17:25:54 KST 2009
Do you wish to see the results?
y(es), n(o), q(uit/exit): y
Using /usr/local/avamar/var/probe.out
(0.0) ssh -x admin@203.###.###.### '/usr/sbin/ntpq -pn 2>&1'
remote refid st t when poll reach delay offset jitter
==============================================================================
*203.248.240.140 122.199.249.2 4 u 42 64 377 4.802 -1.127 2.342
123.214.172.108 .INIT. 16 u - 64 0 0.000 0.000 4000.00
127.127.1.0 LOCAL(0) 8 l 45 64 377 0.000 0.000 0.001
Using /usr/local/avamar/var/probe.out
(0.0) ssh -x admin@203.###.###.###'/bin/date'
Thu Jul 9 17:30:32 KST 2009
--------------------------------------------------------
Done.
NOTES:
* Time on this host is: Thu Jul 9 17:30:32 KST 2009
dpn@avamar:~/>:
NTP Server 없을 때
root@avamar:~/>: su - dpnid
dpn@avamar:~/>: ssh-agent bash
dpn@avamar:~/>: ssh-add ~/.ssh/dpnid
dpn@avamar:~/>: asktime
asktime: INFO: [asktime version 4.1.1-340 (1.6)]
asktime: INFO: Logging to /usr/local/avamar/var/asktime.log
asktime: INFO: The name "ntp" did not resolve to any DNS "IN A"
resource records.
If you wish asktime to suggest a list of internal time servers
automatically, then ask your hostmaster to create one
or more "IN A" resource records for the name "ntp"
in the "gangbuk.go.kr" zone.
For example:
ntp IN A 10.0.254.19
ntp IN A 192.168.100.5
ntp IN A 192.168.100.7
Creating DNS resource records for "ntp" is optional; you
will have other opportunities to enter time server information.
Continue?
y(es), n(o), q(uit/exit): y
--------------------------------------------------------
Do you wish to use U.S. public Internet time servers such as
those offered by NIST or the U.S. Naval Observatory?
Please note the following issues with public time servers:
1. NETWORK CONFIGURATION: In order to use public Internet time
servers your site must allow port 123/udp traffic to and
from the selected Internet time servers.
2. SECURITY: Your site security policy might forbid the use
of Internet time servers. Consider setting up two or
more internal NTP time servers instead.
3. APPROPRIATE USE: Some of the U.S. public time servers known
to asktime are intended to be used only by clients within
specific U.S. time zones. If you use one of these time
servers, then asktime infers that you are using the
corresponding local time zone.
(Your previous answer was: "n".)
y(es), n(o), q(uit/exit): n
--------------------------------------------------------
Are there other external time servers that you
would like to use?
(Your previous answer was: "n".)
y(es), n(o), q(uit/exit): n
--------------------------------------------------------
Do you have a dedicated Axion subnet configuration, e.g., 2##.##.##.0/25?
Answer y(es) if only Axion nodes reside in the subnet;
n(o) if non-Axion nodes share the subnet
(Your previous answer was: "y".)
y(es), n(o), q(uit/exit): y
--------------------------------------------------------
This host, "avamar.backup.com", is a member of subnet 2##.##.##.0/25.
Use this subnet?
y(es), n(o), q(uit/exit): y
--------------------------------------------------------
Use this previously specified local time zone?
Asia/Seoul
y(es), n(o), q(uit/exit): y
--------------------------------------------------------
Do you wish to configure the default set of nodes?
Answering y(es) configures this set of nodes:
#.s -- all utility/services nodes,
#.# -- all data nodes.
Answering n(o) will afford you the opportunity to
configure other MCS nodes and/or individual nodes.
y(es), n(o), q(uit/exit): y
--------------------------------------------------------
Generating time configuration files...
[mktime.custom version 1.2]
--------------------------------------------------------
The time configuration files have been created
in the following directory:
/usr/local/avamar/var/time-config-files
Do you wish to proceed with installation of these
files on the selected nodes?
Answering y(es) will proceed with installation.
Answering n(o) will not proceed, but will leave
available for future use the answers you have
made to the preceding configuration questions.
Answering q(uit) will exit WITHOUT saving your
answers.
y(es), n(o), q(uit/exit): y
--------------------------------------------------------
We need an approximately correct initial date and time.
Here is the current date and time on this host, avamarex.gangbuk.go.kr:
Fri May 22 11:00:56 KST 2009
Please pay close attention to the MONTH, DAY, and YEAR
as well as the time.
Is this approximately correct (within a minute or two)?
y(es), n(o), q(uit/exit): y
--------------------------------
Distributing and installing time configuration files.
Please allow a minimum of 5 minutes. More time may
be required, depending on the number of nodes in the
Axion system and how busy those nodes are.
If you wish to watch this process, apply this command
in another window:
tail -f /usr/local/avamar/var/timedist.log
You may also find it helpful to monitor the following
file on each node (starting with 0.s):
/usr/local/avamar/var/timesyncmon.log
Time now: Fri May 22 11:00:58 KST 2009
Please wait...
--------------------------------------------------------
Do you wish to wait and watch for time synchronization?
y(es), n(o), q(uit/exit): y
asktime: INFO: Status monitoring key:
x ntpd not running on one or more nodes (should auto-correct quickly)
o no clock selected yet on one or more nodes
. unsatisfactory clock selections on one or more nodes
< insufficient time server contacts on one or more nodes
> offset still greater than 2 s on one or more nodes
) offset still greater than 1 s on one or more nodes
} offset still greater than 500 ms on one or more nodes
| offset still greater than 250 ms on one or more nodes
* possible convergence seen (offset <= 250 ms on all nodes)
Notes:
- Ideally you will see something like this: "ooxxooooooooooooooo........***"
- If you interrupt monitoring with control-C, there may be a delay
of a few seconds before monitoring stops.
Commencing 60 monitoring passes, with 10-second intervals
between passes. Time now: Fri May 22 11:13:40 KST 2009
ooooooooooooooooooooooooooooooooooooooooooooooooooooooo***
--------------------------------------------------------
We appear to have time synchronization.
Time now on this host: Fri May 22 11:23:57 KST 2009
Do you wish to see the results?
y(es), n(o), q(uit/exit): y
Using /usr/local/avamar/var/probe.out
(0.s) ssh -x admin@2##.##.##'/usr/sbin/ntpq -pn 2>&1'
remote refid st t when poll reach delay offset jitter
==============================================================================
*127.127.1.0 LOCAL(0) 8 l 25 64 377 0.000 0.000 0.001
(0.0) ssh -x admin@211.34.96.15 '/usr/sbin/ntpq -pn 2>&1'
remote refid st t when poll reach delay offset jitter
==============================================================================
*2##.##.##.## LOCAL(0) 9 u 41 64 17 0.132 1.346 1.848
(0.1) ssh -x admin@211.##.##.## '/usr/sbin/ntpq -pn 2>&1'
remote refid st t when poll reach delay offset jitter
==============================================================================
*2##.##.##.## LOCAL(0) 9 u 37 64 17 0.127 4.184 2.999
2##.##.##.## .INIT. 16 u 34 64 0 0.000 0.000 4000.00
(0.2) ssh -x admin@211.##.##.## '/usr/sbin/ntpq -pn 2>&1'
remote refid st t when poll reach delay offset jitter
==============================================================================
*2##.##.##.## LOCAL(0) 9 u 37 64 17 0.125 1.608 1.130
2##.##.##.## .INIT. 16 u 34 64 0 0.000 0.000 4000.00
Using /usr/local/avamar/var/probe.out
(0.s) ssh -x admin@2##.##.##.## '/bin/date'
(0.0) ssh -x admin@2##.##.##.## '/bin/date'
(0.1) ssh -x admin@2##.##.##.## '/bin/date'
(0.2) ssh -x admin@2##.##.##.## '/bin/date'
Fri May 22 11:24:07 KST 2009
Fri May 22 02:24:07 UTC 2009
Fri May 22 02:24:07 UTC 2009
Fri May 22 02:24:07 UTC 2009
--------------------------------------------------------
Done.
NOTES:
* Time on this host is: Fri May 22 11:24:07 KST 2009
dpn@avamarex:~/>:
==============================================================================
==============================================================================
==============================================================================
==============================================================================
NTP Server 있을 때
root@avamar:~/>: su - dpnid
dpn@avamar:~/>: ssh-agent bash
dpn@avamar:~/>: ssh-add ~/.ssh/dpnid
dpn@avamar:~/>: asktime
asktime: INFO: [asktime version 4.1.1-340 (1.6)]
asktime: INFO: Logging to /usr/local/avamar/var/asktime.log
asktime: INFO: The name "ntp" did not resolve to any DNS "IN A"
resource records.
If you wish asktime to suggest a list of internal time servers
automatically, then ask your hostmaster to create one
or more "IN A" resource records for the name "ntp"
in the "backup.com" zone.
For example:
ntp IN A 10.0.254.19
ntp IN A 192.168.100.5
ntp IN A 192.168.100.7
Creating DNS resource records for "ntp" is optional; you
will have other opportunities to enter time server information.
Continue?
y(es), n(o), q(uit/exit): y
--------------------------------------------------------
Do you wish to use U.S. public Internet time servers such as
those offered by NIST or the U.S. Naval Observatory?
Please note the following issues with public time servers:
1. NETWORK CONFIGURATION: In order to use public Internet time
servers your site must allow port 123/udp traffic to and
from the selected Internet time servers.
2. SECURITY: Your site security policy might forbid the use
of Internet time servers. Consider setting up two or
more internal NTP time servers instead.
3. APPROPRIATE USE: Some of the U.S. public time servers known
to asktime are intended to be used only by clients within
specific U.S. time zones. If you use one of these time
servers, then asktime infers that you are using the
corresponding local time zone.
y(es), n(o), q(uit/exit): n
--------------------------------------------------------
Are there other external time servers that you
would like to use?
y(es), n(o), q(uit/exit): y
--------------------------------------------------------
Please enter the IP addresses of the external
time servers, one per line, in the form
A.B.C.D, e.g. 192.168.100.5.
Time servers may also be specified as host names,
provided that those names will resolve.
Press Enter or Return after each response.
An empty response (a blank line) ends the list.
[00] 203.248.240.140
[01] 123.214.172.108
[02]
203.248.240.140 (보라넷 타임 서버)
123.214.172.108 (이화여대 타임 서버)
This is the list that you entered:
203.248.240.140
123.214.172.108
Is this list correct?
y(es), n(o), q(uit/exit): y
--------------------------------------------------------
Use this previously specified local time zone?
Asia/Seoul
y(es), n(o), q(uit/exit): y
--------------------------------------------------------
Generating time configuration files...
[mktime.custom version 1.2]
--------------------------------------------------------
The time configuration files have been created
in the following directory:
/usr/local/avamar/var/time-config-files
Do you wish to proceed with installation of these
files on the selected node?
Answering y(es) will proceed with installation.
Answering n(o) will not proceed, but will leave
available for future use the answers you have
made to the preceding configuration questions.
Answering q(uit) will exit WITHOUT saving your
answers.
y(es), n(o), q(uit/exit): y
--------------------------------------------------------
We need an approximately correct initial date and time.
Here is the current date and time from NTP, but
with year and time zone from this host:
Thu Jul 9 17:20:35 KST 2009
Please pay close attention to the MONTH, DAY, and YEAR
as well as the time.
Is this approximately correct (within a minute or two)?
y(es), n(o), q(uit/exit): y
--------------------------------
Distributing and installing time configuration files.
Please allow a minimum of 3 minutes. More time may
be required, depending on the number of nodes in the
Axion system and how busy those nodes are.
If you wish to watch this process, apply this command
in another window:
tail -f /usr/local/avamar/var/timedist.log
You may also find it helpful to monitor the following
file on each node (starting with 0.s):
/usr/local/avamar/var/timesyncmon.log
Time now: Thu Jul 9 17:20:58 KST 2009
Please wait...
--------------------------------------------------------
Do you wish to wait and watch for time synchronization?
y(es), n(o), q(uit/exit): y
]asktime: INFO: Status monitoring key:
x ntpd not running on one or more nodes (should auto-correct quickly)
o no clock selected yet on one or more nodes
. unsatisfactory clock selections on one or more nodes
< insufficient time server contacts on one or more nodes
> offset still greater than 2 s on one or more nodes
) offset still greater than 1 s on one or more nodes
} offset still greater than 500 ms on one or more nodes
| offset still greater than 250 ms on one or more nodes
* possible convergence seen (offset <= 250 ms on all nodes)
Notes:
- Ideally you will see something like this: "ooxxooooooooooooooo........***"
- If you interrupt monitoring with control-C, there may be a delay
of a few seconds before monitoring stops.
Commencing 60 monitoring passes, with 10-second intervals
between passes. Time now: Thu Jul 9 17:21:07 KST 2009
.........................***
--------------------------------------------------------
We appear to have time synchronization.
Time now on this host: Thu Jul 9 17:25:54 KST 2009
Do you wish to see the results?
y(es), n(o), q(uit/exit): y
Using /usr/local/avamar/var/probe.out
(0.0) ssh -x admin@203.###.###.### '/usr/sbin/ntpq -pn 2>&1'
remote refid st t when poll reach delay offset jitter
==============================================================================
*203.248.240.140 122.199.249.2 4 u 42 64 377 4.802 -1.127 2.342
123.214.172.108 .INIT. 16 u - 64 0 0.000 0.000 4000.00
127.127.1.0 LOCAL(0) 8 l 45 64 377 0.000 0.000 0.001
Using /usr/local/avamar/var/probe.out
(0.0) ssh -x admin@203.###.###.###'/bin/date'
Thu Jul 9 17:30:32 KST 2009
--------------------------------------------------------
Done.
NOTES:
* Time on this host is: Thu Jul 9 17:30:32 KST 2009
dpn@avamar:~/>:
피드 구독하기:
글 (Atom)