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

Document upgrade for SP 8.1.7

Browse Source
This commit is contained in:
Deon George 2019-05-06 15:23:13 +10:00
parent 1afeb05cd5
commit 74f83c14ce
No known key found for this signature in database
GPG Key ID: 7670E8DC27415254
1 changed files with 12 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

25
source/server/upgrade.md
View File

@ -10,6 +10,8 @@ related:
- { page: "recover", title: "Recovering the SP Database" } - { page: "recover", title: "Recovering the SP Database" }
--- ---
# Upgrading Spectrum Protect Server (in a container) # Upgrading Spectrum Protect Server (in a container)
*Updated for Spectrum Protect 8.1.7!*
> **NOTES**: > **NOTES**:
> * 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.
> * Upgrading needs special thought. > * Upgrading needs special thought.
@ -81,7 +83,7 @@ ANS8002I Highest return code was 0.
<small>**NOTE**: Don't use `docker stop` to stop your SP server. <small>**NOTE**: Don't use `docker stop` to stop your SP server.
By default docker sends a SIGTERM signal to the containers process 1 and then waits 10 seconds for it to die. If it hasn't died, it will then send it a SIGKILL. By default docker sends a SIGTERM signal to the containers process 1 and then waits 10 seconds for it to die. If it hasn't died, it will then send it a SIGKILL.
While you can control the timeout between the SIGTERM and SIGKILL signal and you can even control which kill signal is sent, I haven't explored what signals SP will act on. So as a recommendation, always use SP `halt` command to stop an SP server.</small> While you can control the timeout between the SIGTERM and SIGKILL signal and you can even control which kill signal is sent, Spectrum Protect does correctly handle SIGTERM and will start to shutdown, so if you do want to use `docker stop` to shutdown Specturm Protect, make sure you start it with the appropriate `--stop-timeout`, since 10s is likely not enough time. As a recommendation, I always use SP `HALT` command to stop an SP server.</small>
## If you can, snapshot your persistent storage. ## If you can, snapshot your persistent storage.
If you can snapshot your persistent storage that you provide to the SP Docker Container, that will save you doing a "restore db" if something goes pair shaped. If you can snapshot your persistent storage that you provide to the SP Docker Container, that will save you doing a "restore db" if something goes pair shaped.
@ -106,7 +108,7 @@ Filesystem 1K-blocks Used Available Use% Mounted on
### You need to do a one-time start of the container with the option `upgrade`. ### You need to do a one-time start of the container with the option `upgrade`.
`docker run --detach=true --hostname=tsm --interactive=false -v $TSM_USER:/tsm -v $TSM_DB:/database --privileged=true --rm=false --tty=false --name=spectrumprotect ibm/spectrumprotect:8.1.4 upgrade` `docker run --detach=true --hostname=tsm --interactive=false -v $TSM_USER:/tsm -v $TSM_DB:/database --privileged=true --rm=false --tty=false --name=spectrumprotect ibm/spectrumprotect:8.1.7 upgrade`
<small>**NOTE**: You can see the console by running `docker logs -f spectrumprotect` to make sure the upgrade works as expected. Once you see success, you can delete the container with `docker rm -v spectrumprotect`.</small> <small>**NOTE**: You can see the console by running `docker logs -f spectrumprotect` to make sure the upgrade works as expected. Once you see success, you can delete the container with `docker rm -v spectrumprotect`.</small>
@ -134,15 +136,15 @@ DBI1070I Program db2iupdt completed successfully.
### Normal Run ### Normal Run
Spectrum Protect is ready to run on the new version as normal. The first time it runs at a later release, you should see some `ANR0276I` messages. Spectrum Protect is ready to run on the new version as normal. The first time it runs at a later release, you should see some `ANR0276I` messages.
`docker run --detach=true --hostname=tsm --interactive=false -v $TSM_USER:/tsm -v $TSM_DB:/database -v $TSM_DATA:/data --memory=16g -p 1500:1500 -p 1543:1543 --privileged=true --rm=false --restart=no --tty=false --name=spectrumprotect ibm/spectrumprotect:8.1.4` `docker run --detach=true --hostname=tsm --interactive=false -v $TSM_USER:/tsm -v $TSM_DB:/database -v $TSM_DATA:/data --memory=16g -p 1500:1500 -p 1543:1543 --privileged=true --rm=false --restart=no --tty=false --name=spectrumprotect ibm/spectrumprotect:8.1.7`
```plain Expected Output ```plain Expected Output
ANR7800I DSMSERV generated at 16:03:41 on Nov 17 2017. ANR7800I DSMSERV generated at 00:18:30 on Feb 5 2019.
IBM Spectrum Protect for Linux/x86_64 IBM Spectrum Protect for Linux/x86_64
Version 8, Release 1, Level 4.000 Version 8, Release 1, Level 7.000
Licensed Materials - Property of IBML Licensed Materials - Property of IBM
(C) Copyright IBM Corporation 1990, 2017. (C) Copyright IBM Corporation 1990, 2017.
All rights reserved. All rights reserved.
@ -151,15 +153,12 @@ restricted by GSA ADP Schedule Contract with IBM Corporation.
ANR7801I Subsystem process ID is 7. ANR7801I Subsystem process ID is 7.
... ...
ANR0275I Detected schema change for table SD.Pool.Clusters, attempting to ANR0275I Detected schema change for table Activity.Log, attempting to
reconcile. reconcile.
ANR0276I Schema reconciliation for table SD.Pool.Clusters succeeded. ANR0276I Schema reconciliation for table Activity.Log succeeded.
ANR0275I Detected schema change for table SD.Containers, attempting to ANR0275I Detected schema change for table Server.Connect, attempting to
reconcile. reconcile.
ANR0276I Schema reconciliation for table SD.Containers succeeded. ANR0276I Schema reconciliation for table Server.Connect succeeded.
ANR0275I Detected schema change for table SD.Replicated.Stgpools, attempting to
reconcile.
ANR0276I Schema reconciliation for table SD.Replicated.Stgpools succeeded.
... ...
IBM Spectrum Protect:SERVER1> IBM Spectrum Protect:SERVER1>
``` ```