GRAU DATA AG
Grau Archiv Manager
Service document
Coop Norway
Author:
Axel Polster
Revision:
01
Datum:
22.04.16
Revisionshistorie
Version Author Beschreibung Datum
01 Axel Polster After migration 22.04.16
Inhaltsverzeichnis
1. Overview...............................................................................................3
1.1 purpose of documentation..................................................................................... 3
1.2 Dokumentationsprozess........................................................................................ 3
2. Information...........................................................................................4
2.1 points of contact.................................................................................................... 4
2.2 Locations............................................................................................................... 5
3. Hardware..............................................................................................6
3.1 Disks...................................................................................................................... 6
3.2 communication...................................................................................................... 7
4. Betrieb..................................................................................................8
4.1 configuration......................................................................................................... 8
4.2 backup................................................................................................................... 8
4.3 Changing of Host- or Domain Names.....................................................................9
4.4 Reboot, boot, shutdown......................................................................................... 9
4.5 important commands............................................................................................ 9
5. Support procedure.................................................................................9
Seite 2
1. Overview
1.1 purpose of documentation
Grau Data has created this document as compendium how the Grau Archive Manager
is implemented at customer site. It is not the software user or installation manual.
Software user or installation manuals are separate books (as pdf).
The point of this document is:
· description of primary components
· reference of technical question
· as reference for Grau Data support people if a problem is reported
· guide for important hints
· as guide what have to restore after a desaster
The document should be changed, if the enviroment will be changed.
1.2 Dokumentationsprozess
If there were changes in the GAM (Grau Archive Manager) enviroment. Please inform
Grau Data about the changes. Grau Data will changing the document and distributing
to the described persons.
Seite 3
2. Information
2.1 points of contact
Customer :
Coop Norge Handel AS
Visiting address:
Sinsenveien 45
0585 Oslo
[email protected]
partner of maintenance :
Wipro Technologies
[email protected]
[email protected]
GRAU DATA AG:
Marie-Curie-Straße 19
D – 73529 Schwäbisch Gmünd
Service:
+49 7171 187111
[email protected]
Service manager:
Kai Hambrecht
[email protected]
Seite 4
2.2 Locations
Customer:
Coop Norge Handel AS
Visiting address:
Sinsenveien 45
0585 Oslo
Seite 5
3. Hardware
GAM System is implemented as a virtual system on VMware ESX.
3.1 Disks
04/12/16 08:04
PV /dev/sde1 VG vgGAMcapacity_2 lvm2 [4.25 TiB / 253.97 GiB free]
PV /dev/sdd1 VG vgGAMcapacity_1 lvm2 [4.25 TiB / 253.97 GiB free]
PV /dev/sdc1 VG vgGAMperf lvm2 [698.97 GiB / 992.00 MiB free]
PV /dev/sdb1 VG vgGAMsys lvm2 [198.97 GiB / 28.97 GiB free]
Total: 4 [9.37 TiB] / in use: 4 [9.37 TiB] / in no VG: 0 [0 ]
Reading all physical volumes. This may take a while...
Found volume group "vgGAMcapacity_2" using metadata type lvm2
Found volume group "vgGAMcapacity_1" using metadata type lvm2
Found volume group "vgGAMperf" using metadata type lvm2
Found volume group "vgGAMsys" using metadata type lvm2
ACTIVE '/dev/vgGAMcapacity_2/dc20020' [1.00 TiB] inherit
ACTIVE '/dev/vgGAMcapacity_2/dc20021' [1.00 TiB] inherit
ACTIVE '/dev/vgGAMcapacity_2/dc20022' [1.00 TiB] inherit
ACTIVE '/dev/vgGAMcapacity_2/dc20023' [1.00 TiB] inherit
ACTIVE '/dev/vgGAMcapacity_1/dc10020' [1.00 TiB] inherit
ACTIVE '/dev/vgGAMcapacity_1/dc10021' [1.00 TiB] inherit
ACTIVE '/dev/vgGAMcapacity_1/dc10022' [1.00 TiB] inherit
ACTIVE '/dev/vgGAMcapacity_1/dc10023' [1.00 TiB] inherit
ACTIVE '/dev/vgGAMperf/lv_hsmfs01' [349.00 GiB] inherit
ACTIVE '/dev/vgGAMperf/lv_hsmfs02' [349.00 GiB] inherit
ACTIVE '/dev/vgGAMsys/lv_ivd' [10.00 GiB] inherit
ACTIVE '/dev/vgGAMsys/lv_ivd_log' [10.00 GiB] inherit
ACTIVE '/dev/vgGAMsys/lv_ivd_fri' [50.00 GiB] inherit
ACTIVE '/dev/vgGAMsys/lv_ivd_part' [50.00 GiB] inherit
ACTIVE '/dev/vgGAMsys/lv_ivd_buf' [50.00 GiB] inherit
Filesystem Size Used Avail Use% Mounted on
/dev/sda2 15G 3.6G 11G 26% /
udev 16G 212K 16G 1% /dev
tmpfs 47G 72K 47G 1% /dev/shm
/dev/sda1 1011M 62M 898M 7% /boot
/dev/sda6 6.0G 147M 5.5G 3% /home
/dev/sda10 6.0G 374M 5.3G 7% /opt
/dev/sda7 4.0G 73M 3.7G 2% /tmp
/dev/sda5 12G 3.6G 7.8G 32% /usr
/dev/sda8 9.9G 400M 9.0G 5% /var
/dev/mapper/vgGAMsyslv_ivd 9.9G 503M 8.9G 6% /var/opt/ivd
/dev/mapper/vgGAMsyslv_ivd_part 50G 767M 46G 2%
/var/opt/ivd/part
/dev/mapper/vgGAMsyslv_ivd_log 9.9G 332M 9.1G 4%
/var/opt/ivd/log
Seite 6
/dev/mapper/vgGAMsyslv_ivd_fri 50G 181M 47G 1%
/var/opt/ivd/fri
/dev/mapper/vgGAMsyslv_ivd_buf 50G 180M 47G 1%
/var/opt/ivd/diskbuf
/dev/mapper/vgGAMcapacity_1dc10020 1008G 990G 0 100%
/var/opt/ivd/dm/dc10020
/dev/mapper/vgGAMcapacity_1dc10021 1008G 990G 0 100%
/var/opt/ivd/dm/dc10021
/dev/mapper/vgGAMcapacity_1dc10022 1008G 990G 0 100%
/var/opt/ivd/dm/dc10022
/dev/mapper/vgGAMcapacity_1dc10023 1008G 849G 109G 89%
/var/opt/ivd/dm/dc10023
/dev/mapper/vgGAMcapacity_2dc20020 1008G 990G 0 100%
/var/opt/ivd/dm/dc20020
/dev/mapper/vgGAMcapacity_2dc20021 1008G 990G 0 100%
/var/opt/ivd/dm/dc20021
/dev/mapper/vgGAMcapacity_2dc20022 1008G 990G 0 100%
/var/opt/ivd/dm/dc20022
/dev/mapper/vgGAMcapacity_2dc20023 1008G 850G 108G 89%
/var/opt/ivd/dm/dc20023
/dev/mapper/vgGAMperflv_hsmfs01 326G 195G 114G 64% /hsm/hsmfs01
/dev/mapper/vgGAMperflv_hsmfs02 326G 231G 78G 75% /hsm/hsmfs02
3.2 communication
srvsap33.copp.no
copp.no
eth3 Link encap:Ethernet HWaddr 00:50:56:B9:4C:3C
inet addr:10.193.189.32 Bcast:10.193.189.255
Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:4456477 errors:0 dropped:13 overruns:0 frame:0
TX packets:1982453 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:21742518020 (20735.2 Mb) TX bytes:41650675431
(39721.1 Mb)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:55979415 errors:0 dropped:0 overruns:0 frame:0
TX packets:55979415 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:7612437599 (7259.7 Mb) TX bytes:7612437599 (7259.7
Mb)
Seite 7
4. Betrieb
4.1 configuration
2 Partitions with 1 disk capacity pool. Storage for the partitions are on different
locations.
Opentext will write one copy to hsmfs01 and a second copy to hsmfs02.
ESX farm
Grau Archivmanager
hsmfs01 hsmfs02
GAM DB
Capacity disks for Capacity disks for
hsmfs01 hsmfs02
(dc10020 - 25) (dc20020 - 25)
Mountpoints /hsm/hsmfs01 and /hsm/hsmfs02 are shared via NFS to opentext server.
Grau Archivmanager will archive all data to the capacity disks and replace files in
hsmfs with links (sparse files). Access to a file will automatically replace the data on
the hsmfs.
4.2 backup
The GAM Config and databases are backed up every day to /var/opt/ivd/backup .
This directory and /var/opt/ivd/log should be backed up with the normal customer
backup procedure.
All mountpoints under /var/opt/ivd/dm/…. Should be backed up with “incrementel for
ever” backup method, because this is the archive and it will NEVER changed.
No other parts of the system should be backed up.
Seite 8
4.3 Changing of Host- or Domain Names
If the host or domain name was changed, the functions of the Grau Archiv Manager
must be tested!
4.4 Reboot, boot, shutdown
Before you reboot or shutdown the Grau Archiv Manager, please stop the Software
('ivd stop').
Before booting the server be sure that the Storage is ONLINE.
After reboot or boot you should check if GAM is running well. For that please do:
“ivdpartition -l”
- all partitions must be shown as status “mounted”
4.5 important commands
ivd start #start the HSM function
ivd stop #stop the HSM function
ivdpartition -l #show the status of the GAM partitions, should be 'mounted'
ivdpartition -t PARTITIONNAME # show the partition space usage
ivdmedium -l #show status of known medias
ivdmedium –-mark-unusable BARCODE # GAM will not use medias, marked as „unusable“
ivdmedium –mark-good BARCODE # medias, marked as „good“, are usable
! do never mark dc10001 – dc10004 and dc20001 – dc20004 as „good“ , these were
medias from old dca901p GAM system and are never usable. Data was transfered to
dc10020 – 23 and dc20020 – 23 !
5. Support procedure
If a problem is occured with GAM, please contact Wipro Technologies first to clear up if
problems with ESX or storage is known.
If not, Coop No or Wipro can open a service request at Grau Data AG with the contact
data from 2.1 .
What do you have to provide, if open a support request:
- problem description
- what was done before?
- complete Log collection
(can be created with „ivd_logcollect“ command and will create a .bz2 file under
/var/opt/ivd/tmp)
Seite 9
