deon/spdocker
Archived
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

More updates for 8.1.8

Browse Source
This commit is contained in:
Deon George 2019-06-28 11:28:11 +10:00
parent c8aedc8a2d
commit f23fb997f2
No known key found for this signature in database
GPG Key ID: 7670E8DC27415254
2 changed files with 17 additions and 18 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
source/server/firstrun.md
View File

@ -10,11 +10,10 @@ related:
- { page: "recover", title: "Recovering the SP Database" } - { page: "recover", title: "Recovering the SP Database" }
--- ---
# First deployment of a Spectrum Protect Server (in a container) # First deployment of a Spectrum Protect Server (in a container)
*Updated for Spectrum Protect 8.1.7!*
> **NOTES**: > **NOTES**:
> * The following instructions are for a Spectrum Protect 8.1.7 instance. I used the same procedure described [here](/server) to build the Docker Image. The only difference is that I performed a new install using the installation media from the IBM public website. (Thus it was just an install, not an 8.1.0 install and followed by a 8.1.7 upgrade). > * The following instructions are for a Spectrum Protect 8.1.8 instance. I used the same procedure described [here](/server) to build the Docker Image. The only difference is that I performed a new install using the installation media from the IBM public website. (Thus it was just an install, not an 8.1.0 install and followed by a 8.1.8 upgrade).
> * Make sure you follow the guidelines for space required as presented in the [Knowledge Center](https://www.ibm.com/support/knowledgecenter/SSEQVQ_8.1.7/srv.install/t_srv_plan_capacity-linux.html). > * Make sure you follow the guidelines for space required as presented in the [Knowledge Center](https://www.ibm.com/support/knowledgecenter/SSEQVQ_8.1.8/srv.install/t_srv_plan_capacity-linux.html).
Our Docker Image will have the SP database in `/database`, the instance user in `/tsm` and storage pools in `/data`. Ultimately these will be volumes provisioned from the host and using host storage, or your preferred Docker persistent volume storage technology. Our Docker Image will have the SP database in `/database`, the instance user in `/tsm` and storage pools in `/data`. Ultimately these will be volumes provisioned from the host and using host storage, or your preferred Docker persistent volume storage technology.
> * The storage used in the example below is from the host file systems, passed to the container with Docker's `-v` option. > * The storage used in the example below is from the host file systems, passed to the container with Docker's `-v` option.
> * This implementation is using DISK or CLOUD storage pool storage. While accessing tape should be possible, I haven't explored what is required for that to work. > * This implementation is using DISK or CLOUD storage pool storage. While accessing tape should be possible, I haven't explored what is required for that to work.
@ -37,7 +36,7 @@ TSM_DATA=/srv/sp/data
The first init run will be to create the database layout, and to copy the initialise database (as performed when containerising SP) onto our persistent storage. The first init run will be to create the database layout, and to copy the initialise database (as performed when containerising SP) onto our persistent storage.
`docker run --detach=false --hostname=tsm --interactive=false -v $TSM_USER:/tsm.init -v $TSM_DB:/database.init --privileged=true --rm=true --restart=no --tty=false --name=spectrumprotect ibm/spectrumprotect:8.1.7 init1` `docker run --detach=false --hostname=tsm --interactive=false -v $TSM_USER:/tsm.init -v $TSM_DB:/database.init --privileged=true --rm=true --restart=no --tty=false --name=spectrumprotect ibm/spectrumprotect:8.1.8 init1`
You wont see any output, but if you look in your $TSM_USER path, you should see the familiar TSM instance owner files (like sqllib). The $TSM_DB directory should have sub directories created for the DB2 database, active and archive logs. You wont see any output, but if you look in your $TSM_USER path, you should see the familiar TSM instance owner files (like sqllib). The $TSM_DB directory should have sub directories created for the DB2 database, active and archive logs.
@ -59,7 +58,7 @@ drwxr-xr-x 2 201 201 4096 Mar 8 14:30 tsmdb
The second init run will now run the post-install setup for a new environment (`dsmserv formatdb` and then create the ADMIN user - using the macro file added during the build). The second init run will now run the post-install setup for a new environment (`dsmserv formatdb` and then create the ADMIN user - using the macro file added during the build).
`docker run --detach=false --hostname=tsm --interactive=false -v $TSM_USER:/tsm -v $TSM_DB:/database --privileged=true --rm=true --restart=no --tty=false --name=spectrumprotect ibm/spectrumprotect:8.1.7 init2` `docker run --detach=false --hostname=tsm --interactive=false -v $TSM_USER:/tsm -v $TSM_DB:/database --privileged=true --rm=true --restart=no --tty=false --name=spectrumprotect ibm/spectrumprotect:8.1.8 init2`
```tsm Expected Output ```tsm Expected Output
ANR7800I DSMSERV generated at 00:18:30 on Feb 5 2019. ANR7800I DSMSERV generated at 00:18:30 on Feb 5 2019.
@ -81,6 +80,6 @@ ANR1912I Stopping the activity log because of a server shutdown.
ANR0369I Stopping the database manager because of a server shutdown. ANR0369I Stopping the database manager because of a server shutdown.
``` ```
<small>**NOTE**: With 8.1.7 I noticed a lot of `DBI1306N` messages floating up the screen. That doesn't appear to be an actual problem.</small> <small>**NOTE**: With 8.1.8 I noticed a lot of `DBI1306N` messages floating up the screen. That doesn't appear to be an actual problem.</small>
The "init" steps will only need to be run the once for any "new" instance of SP. Thereafter, you'll start SP using the Normal steps documented [here](normalrun.html). The "init" steps will only need to be run the once for any "new" instance of SP. Thereafter, you'll start SP using the Normal steps documented [here](normalrun.html).

24
source/server/registry.md
View File

@ -6,13 +6,12 @@ related:
- { page: "firstrun", title: "Initial Container Setup" } - { page: "firstrun", title: "Initial Container Setup" }
- { page: "normalrun", title: "Normal Run of Container" } - { page: "normalrun", title: "Normal Run of Container" }
--- ---
# Spectrum Protect Server # Spectrum Protect Server <span class="badge btn-danger" style="background-color: #ac2925">Updated to 8.1.8</span>
*Updated for Spectrum Protect 8.1.7!*
```Dockerfile Server Dockerfile ```Dockerfile Server Dockerfile
# NAME deon/spdocker/server # NAME deon/spdocker/server
# VERSION 8.1.7 # VERSION 8.1.8
# BUILD docker build -t="deon/spdocker/server:8.1.7" . # BUILD docker build -t="deon/spdocker/server:8.1.8" .
# Since SP is supported on RHEL and its not available in docker, we'll use CentOS. # Since SP is supported on RHEL and its not available in docker, we'll use CentOS.
FROM centos:7 FROM centos:7
@ -23,10 +22,10 @@ RUN yum -y install http://yum.leenooks.net/CentOS/7/base/redhat-release-7-6.el7.
# Installation # Installation
COPY install.xml install-fp.xml /tmp/ COPY install.xml install-fp.xml /tmp/
# Download http://public.dhe.ibm.com/storage/tivoli-storage-management/maintenance/server/v8r1/Linux/8.1.7.000/x86_64/8.1.7.000-IBM-SPSRV-Linuxx86_64.bin to a local server (otherwise it will be slow). # Download http://public.dhe.ibm.com/storage/tivoli-storage-management/maintenance/server/v8r1/Linux/8.1.8.000/x86_64/8.1.8.000-IBM-SPSRV-Linuxx86_64.bin to a local server (otherwise it will be slow).
RUN SOURCE_URL=http://YOUR_SITE_URL_HERE && \ RUN SOURCE_URL=http://YOUR_SITE_URL_HERE && \
mkdir -p /tmp/build && cd /tmp/build && \ mkdir -p /tmp/build && cd /tmp/build && \
curl -SL ${SOURCE_URL}/8.1.7.000-IBM-SPSRV-Linuxx86_64.bin > tsm && chmod +x tsm && ./tsm && rm -f tsm && \ curl -SL ${SOURCE_URL}/8.1.8.000-IBM-SPSRV-Linuxx86_64.bin > tsm && chmod +x tsm && ./tsm && rm -f tsm && \
./install.sh -s -input /tmp/install-fp.xml -acceptLicense && \ ./install.sh -s -input /tmp/install-fp.xml -acceptLicense && \
rm -rf /tmp/build /tmp/install*xml rm -rf /tmp/build /tmp/install*xml
@ -67,15 +66,16 @@ RUN ln -sf /usr/share/zoneinfo/Australia/Melbourne /etc/localtime
**NOTES**: **NOTES**:
* I use the install-fp.xml which doesnt install the license libraries - since they are not available in the public download. * I use the install-fp.xml which doesnt install the license libraries - since they are not available in the public download.
* You'll find this image in my registery, you can `docker pull registry.leenooks.net/deon/spdocker/server:8.1.7` to get it - feel free to try it. * You'll find this image in my registery, you can `docker pull registry.leenooks.net/deon/spdocker/server:8.1.8` to get it - feel free to try it.
* The supporting files are in my [gitlab](http://dev.leenooks.net/deon/spdocker/tree/master) * The supporting files are in my [gitlab](http://dev.leenooks.net/deon/spdocker/tree/master)
* *An Importantly* Dont forget that the first time you use this image, you need to initialise SP - details are [here](firstrun.html)
# Spectrum Protect Operations Center # Spectrum Protect Operations Center
```Dockerfile Operations Center Dockerfile ```Dockerfile Operations Center Dockerfile
# NAME deon/spdocker/oc # NAME deon/spdocker/oc
# VERSION 8.1.7 # VERSION 8.1.8
# BUILD docker build -t="deon/spdocker/oc:8.1.7" . # BUILD docker build -t="deon/spdocker/oc:8.1.8" .
# Since SP is supported on RHEL and its not available in docker, we'll use CentOS. # Since SP is supported on RHEL and its not available in docker, we'll use CentOS.
FROM centos:7 FROM centos:7
@ -86,10 +86,10 @@ RUN yum -y install http://yum.leenooks.net/CentOS/7/base/redhat-release-7-6.el7.
COPY install-oc.xml /tmp/ COPY install-oc.xml /tmp/
# Installation # Installation
# Download http://public.dhe.ibm.com/storage/tivoli-storage-management/maintenance/server/v8r1/Linux/8.1.7.000/x86_64/8.1.7.000-IBM-SPSRV-Linuxx86_64.bin to a local server (otherwise it will be slow). # Download http://public.dhe.ibm.com/storage/tivoli-storage-management/maintenance/server/v8r1/Linux/8.1.8.000/x86_64/8.1.8.000-IBM-SPSRV-Linuxx86_64.bin to a local server (otherwise it will be slow).
RUN SOURCE_URL=http://SOURCE_URL && \ RUN SOURCE_URL=http://SOURCE_URL && \
mkdir -p /tmp/build && cd /tmp/build && \ mkdir -p /tmp/build && cd /tmp/build && \
curl -SL ${SOURCE_URL}/8.1.7.000-IBM-SPSRV-Linuxx86_64.bin > tsm && chmod +x tsm && ./tsm && rm -f tsm && \ curl -SL ${SOURCE_URL}/8.1.8.000-IBM-SPSRV-Linuxx86_64.bin > tsm && chmod +x tsm && ./tsm && rm -f tsm && \
./install.sh -s -input /tmp/install-oc.xml -acceptLicense && \ ./install.sh -s -input /tmp/install-oc.xml -acceptLicense && \
rm -rf /tmp/build /tmp/install*xml rm -rf /tmp/build /tmp/install*xml
@ -105,5 +105,5 @@ RUN sed -i 's#^installPath=#installPath=/opt/tivoli/tsm/ui#' /opt/tivoli/tsm/ui/
``` ```
**NOTES**: **NOTES**:
* You'll find this image in my registery, you can `docker pull registry.leenooks.net/deon/spdocker/oc:8.1.7` to get it - feel free to try it. * You'll find this image in my registery, you can `docker pull registry.leenooks.net/deon/spdocker/oc:8.1.8` to get it - feel free to try it.
* The supporting files are in my [gitlab](http://dev.leenooks.net/deon/spdocker/tree/oc) * The supporting files are in my [gitlab](http://dev.leenooks.net/deon/spdocker/tree/oc)