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:~/>:

Avamar 사용 Port

Avamar 사용 Port

Avamar avregister 안되는 현상 조치 방법

Windows File-system

- Windows 서버의 Workgroup 또는 Hostname이 한글일 경우

•windows 경우 workgroup 또는 hostname이 한글일 경우 아바마에서 정상적으로 인식이 안되는 문제

   à 해결 방법 :

   1. Avamar 설치 디렉토리의 var의 디렉토리에 .avagent 파일을 생성

      .avagent 파일 내용

         --hostname=영문이름

         --listenport=28011(사용하지 않는 다른 번호를 입력)

    2.  시작 > 제어판 > 컴퓨터 관리 > services 에서 Backup Agent 서비스 re-start

        또는 Avamar 서버 등록

아바마 노드추가 작업 4.x, 5.x

작업 구분	작업 내용
작업 전 확인	1. 백업 진행 여부 확인 2. 노드 번호 확인 : nodenumbers 3. maintenance 관련 Activity 중지 suspend maintenance activity 실행(GUI) 4. Checkpoint 생성(GUI)
신규 노드 환경 설정	1. 노드 타입 변경 : /usr/local/avamar/install/scripts/change_nodetype –data 2. 노드 타입 변경 확인 : cat /usr/local/avamar/etc/node.cfg 3. Network 설정 : Setup으로 IP 정보 및 기본 Timezone 설정 4. Hostname 변경 5. Reboot
유틸리티 노드 환경 설정 및 노드 추가	1. 유틸리티 노드와 신규 노드간의 Network 상태 확인 신규 노드의 Reboot 완료 후 Ping Test 2. probe 파일 수정 /usr/local/avamar/var/probe.xml 백업 후 nodedb print로 현재 노드 리스트 확인 nodedb add node --addr=ip주소 -type=storage로 신규 노드 정보 추가 : nodedb print --nodes=0.all+ --addr –id로 추가 확인 3. Host 파일 수정 : /etc/hosts 파일에 신규 노드 IP 정보 추가 4. 전체 노드들의 시간 설정 : asktime 수행 5. 신규 노드 추가 : start.nodes --clean --nodes=신규 노드 번호 2>&1 | tee –a startingnode_1230.log
각 노드간의 Sync 상태 확인	1. balancemin 설정 값 확인 avmaint config --ava | grep balance avmaint config --ava balancemin=0 2. 상태 확인 : status.dpn으로 신규 노드 추가 확인 및 sync 상태 확인

DataDomain Tape move 방법

- Tape 확인
vtl tape show all - 명령어 수행시 전체 Tape목록 확인 Slot번호 압뒤를 확인 해야 함.
sysadmin@dd160# vtl tape show all barcode A00001L3
Processing tapes....
Barcode    Pool         Location           State      Size            Used (%)   Comp   Modification Time
--------   ----------   ----------------   -----   -------   -----------------   ----   -------------------
A00001L3   lvtek_TEST   lvtek_VTL slot 1   RW      200 GiB   38.6 GiB (19.31%)     2x   2013/04/04 14:28:18
--------   ----------   ----------------   -----   -------   -----------------   ----   -------------------
VTL Tape Summary
----------------
Total number of tapes:     1
Total pools:               1
Total size of tapes:       200 GiB
Total space used by tapes: 38.6 GiB
Average Compression:       2.3x
- Slot에서 Drive로 옮기는 방법
sysadmin@dd160# vtl tape move lvtek_VTL source slot 1 destination drive 1
... moved 1 tape(s)...
- Tape 확인 (Slot에서 Drive로 옮겨진것을 확인)
sysadmin@dd160# vtl tape show all barcode A00001L3
Processing tapes....
Barcode    Pool         Location            State      Size            Used (%)   Comp   Modification Time
--------   ----------   -----------------   -----   -------   -----------------   ----   -------------------
A00001L3   lvtek_TEST   lvtek_VTL drive 1   RW      200 GiB   38.6 GiB (19.31%)     2x   2013/04/04 14:28:18
--------   ----------   -----------------   -----   -------   -----------------   ----   -------------------
VTL Tape Summary
----------------
Total number of tapes:     1
Total pools:               1
Total size of tapes:       200 GiB
Total space used by tapes: 38.6 GiB
Average Compression:       2.3x

- Drive에서 Slot으로 옮기는 방법
sysadmin@dd160# vtl tape move lvtek_VTL source drive 1 destination slot 1
... moved 1 tape(s)...
- Drive에서 Slot으로 옮겨진것을 확인
sysadmin@dd160# vtl tape show all barcode A00001L3
Processing tapes....
Barcode    Pool         Location           State      Size            Used (%)   Comp   Modification Time
--------   ----------   ----------------   -----   -------   -----------------   ----   -------------------
A00001L3   lvtek_TEST   lvtek_VTL slot 1   RW      200 GiB   38.6 GiB (19.31%)     2x   2013/04/04 14:28:18
--------   ----------   ----------------   -----   -------   -----------------   ----   -------------------
VTL Tape Summary
----------------
Total number of tapes:     1
Total pools:               1
Total size of tapes:       200 GiB
Total space used by tapes: 38.6 GiB
Average Compression:       2.3x
Vtl Tape Move 명령어 .....
sysadmin@dd160# vtl tape move
Incorrect syntax "vtl tape move", showing help:
Commands matching "vtl tape move":
  vtl tape move <vtl> source {slot | drive | cap} {<src-address-list> | all}
                destination {slot | drive | cap} {<dst-address-list> | auto}
                                       Move tapes between elements in a
                                       Virtual Tape Library
  vtl tape move barcode <barcode> [count <count>] source <src-pool>
                destination <dst-pool>
                                       Move tapes between VTL pools