Transition Guide

Hardware refresh
Sectra PACS, Version 19.1.8, May 2017
 About this document

The purpose of this document is to be a guideline for how to move a Sectra PACS from one Windows
system to another Windows system. For example when replacing the server hardware. The process is
known as a transition to new hardware or simply a hardware refresh.

Table 1, “Available transition targets, and their corresponding documentation suffix” describes the
supported transition targets, meaning the type of system that the Sectra PACS is moved to, and the
corresponding suffix used for the deployment documentation. Please make sure this guide matches your
system solution.

Table 1 Available transition targets, and their corresponding documentation suffix

This Operating system Database engine System type Suffix
guide

Windows Server 2008 R2 SQL Server 2008 R2 Single server Single

Windows Server 2008 R2 SQL Server 2008 R2 Failover cluster Cluster

Windows Server 2012 R2 SQL Server 2012 Single server Single

Service Pack 1

Windows Server 2012 R2 SQL Server 2012 Failover cluster Cluster

Service Pack 1

Sectra PACS, Version 19.1.8, May 2017 About this document ii

 Contents

About this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ii

1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.1 Related documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.2 Intended use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.3 General safety regulations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

2 Getting started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.1 Assumptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

3 Preparing the new operating environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

3.1 Planning the transition of file storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
3.2 Planning the transition of network names and IP addresses . . . . . . . . . . . . . . . . . . . . . . . . 6
3.3 Installing the new operating environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

4 Preparing the temporary Sectra PACS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

4.1 Acquiring licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
4.2 Installing a temporary Sectra PACS Core . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
4.3 Installing Sectra Deployment Framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
4.4 Deploying temporary Sectra Healthcare System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
4.5 Removing temporary Sectra PACS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

5 Preparing for transition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

5.1 Managing ImageServer/s image data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
5.2 Managing ImageServer/s services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
5.3 Cleaning up filing queues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
5.4 Managing databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

6 Switching to new system (requires downtime) . . . . . . . . . . . . . . . . . . . . . . . . . . 25

6.1 Completing pre-transition checklists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
6.2 Stopping Sectra PACS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
6.3 Moving network names and IP addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
6.4 Synchronizing ImageServer/s storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
6.5 Moving databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
6.6 Starting WISE in the new environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
6.7 Starting IDS7 in the new environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
6.8 Adjusting and verifying access to existing images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Sectra PACS, Version 19.1.8, May 2017 Contents iii

 Contents

6.9 Adjusting settings for future images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

6.10 Adjusting ImageServer/fs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
6.11 Completing transition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

7 Post transition tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

A Handling network names and IP addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

A.1 Network name transition principles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
A.2 About the transition of an existing network name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
A.3 Best practice for network names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

B Handling storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
B.1 Storage transition principles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
B.2 Keeping the existing storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
B.3 Using SAN mirroring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
B.4 Using file copying . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
B.5 Removing an obsolete base folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

C Handling registry settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

C.1 Exporting registry keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
C.2 Adjusting the exported registry files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
C.3 Importing registry keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Sectra PACS, Version 19.1.8, May 2017 Contents iv

 1 Introduction

The following topics are included in this chapter:

■ Related documents

■ Intended use

■ General safety regulations

This transition guide for Sectra PACS describes different scenarios and considerations when hardware
is to be replaced in a Windows based Sectra PACS system.

1.1 Related documents

[1] Sectra Installation Guide Sectra PACS

[2] Sectra System Administrator's Guide ImageServer/fs, ImageServer/xd, ImageServer/os

[3] Sectra System Administrator's Guide ImageServer/s

[4] System Administrator's Guide Sectra Healthcare System

[5] System Administrator's Guide WISE

[6] Sectra User's Guide IDS7

1.2 Intended use

Sectra Workstation

Sectra Workstation is intended for the display, manipulation and diagnostic review of medical images
(e.g. DICOM, jpeg, mpeg) and other related medical information. It can show images from different
sources and interface with various image storage and printing devices. Areas of application include e.g.
radiology (e.g. CR, DX, CT, MR, US), mammography, cardiology and pathology. Typical users are
trained medical professionals, including, but not limited to physicians, radiologists, nurses, medical
technicians and assistants.

Lossy compressed radiological images and DICOM “for processing” images are not intended for
diagnostic review.

In the United States only:

• Mammographic images must be reviewed on a monitor approved by FDA for mammographic images

• Sectra Workstation is not intended for primary diagnosis of digital pathology images

Sectra PACS, Version 19.1.8, May 2017 Introduction 1

 General safety regulations 1.3

Sectra UniView, the web-based model of Sectra Workstation, is primarily intended for reference viewing
on both stationary and mobile platforms. It is not intended for replacing a full diagnostic workstation
but can be used on stationary platforms for diagnostic review of medical images except mammograms.
For diagnostic review of radiological images full image quality mode must be used.

Note: The user is responsible for the quality, accuracy and adequacy of all information imported or entered
into Sectra Workstation, whether videos or photographs, audio or text. Further, the user is responsible
for the clinical adequacy of the viewing device used (e.g., size, resolution and contrast).

Sectra Core

Sectra Core is intended for the management, archiving, and communication of medical images and other
related medical information. It can manage images from different sources and interface with various
other systems, e.g., Electronic Medical Records (EMR), Radiological Information Systems (RIS) and
Laboratory Information Systems (LIS). Sectra Core uses DICOM and similar interface standards.

Typical users are trained professionals, including, but not limited to, medical technicians, system
administrators and IT staff.

1.3 General safety regulations

Please observe the following important safety points when using Sectra products:

• Make sure you follow the recommendations provided by the supplier of all hardware equipment
that is used together with Sectra products.

• It is mandatory that you have the necessary skills on how to use the products before using them for
any patient examinations. Only use the products for applications for which you have been properly
trained. Do not use the products for any purpose other than those for which they are intended.

• To achieve mandatory skills, you can either attend introductory training as organized by the
healthcare provider, licensee or supplier, or familiarize yourself with all supplied user documentation
and training material.

• Do not use the products with any other products except for those that the supplier of your PACS
or RIS recognizes as compatible.

• Operation of the products without proper training, for unintended purposes or with incompatible
equipment could lead to fatal or other serious personal injury.

Sectra PACS, Version 19.1.8, May 2017 Introduction 2

 2 Getting started

The following topics are included in this chapter:

■ Assumptions

This document describes the transition of a Sectra PACS from an existing Windows operating
environment to a new Windows Server operating environment. This transition procedure is typically
used when replacing hardware, also known as a hardware refresh. It is often combined with an upgrade
of Sectra PACS.

The replacement of hardware in a system running Sectra PACS involves a lot of aspects and requires
thorough preparations to minimize the downtime required.

Important: The reader is assumed to be an experienced Sectra PACS engineer with knowledge on how to deploy
Sectra PACS. In this document, only transition specific procedures are described in more detail.

The first chapters describe the preparations. The actual transition event is described in chapter 6
Switching to new system (requires downtime). More in-depth descriptions, and descriptions of alternative
methods, are collected in the appendices.

2.1 Assumptions
The following is assumed in this guide:

Sectra PACS

• Sectra PACS will be upgraded at the same time as moving it from the old to the new hardware

• The existing system runs IDS7, meaning that the transition of Sectra Healthcare System is covered

• Any use of IDS5 is out of the scope

• Base folder structure remains the same. That is, all existing base folders will be moved as they are
with the same content. However, the path to them may change.

• System is mission critical. Large efforts will be made, by thorough planning and careful preparations,
to minimize the downtime.

• The network names and IP addresses currently in use in the existing system will be moved together
with the Sectra PACS to the new operating environment. See also section 3.2 Planning the transition
of network names and IP addresses.

Storage

See also section B.1 Storage transition principles.

• The database files (WISE Database and Sectra Healthcare Database) are copied to new storage

Sectra PACS, Version 19.1.8, May 2017 Getting started 3

 Assumptions 2.1

• New storage is available for basic failover clustering services

• The ImageServer/s file systems are copied to new storage

• The ImageServer/fs file systems remains the same

The new system

• The new operating environment is independent and can be built up in parallel with the running
system

• The new system is based on Windows Server and SQL Server

• The new system consist of:

• A two-node failover cluster running Sectra PACS Core services like WISE, ImageServer/s,
ImageServer/fs and Sectra Healthcare Database (including Sectra Deployment Database)

• Two or more application server nodes in a hardware load balanced configuration running Sectra
Deployment Server and Sectra Healthcare Server

• A separate single server at a satellite site running an extra ImageServer/s and Sectra Satellite
Server

Sectra PACS, Version 19.1.8, May 2017 Getting started 4

 3 Preparing the new operating environment

The following topics are included in this chapter:

■ Planning the transition of file storage

■ Planning the transition of network names and IP addresses

■ Installing the new operating environment

This chapter outlines preparations and installation of the new operating environment, excluding the
Sectra PACS software.

3.1 Planning the transition of file storage

See also

• appendix B Handling storage

• section 5.1 Managing ImageServer/s image data

• section 5.4 Managing databases

3.1.1 Preparing a safe location file system

The transition from the current hardware to the new hardware requires file systems in a safe location
available for storing PACS data during the transition. The size and the location of this or these file
systems depend very much on the current system and what the new system will look like.

The best is if the current file systems for the PACS data can be considered as safe locations. For example
if the file system that holds the filed examinations and/or the online examinations will not be affected
by the transition.

Define safe location file system

1. Define a file location where important Sectra PACS data can be stored and accessed during the
transition.

2. Download software needed, like operating system updates, database engine software and Sectra
PACS software.

Sectra PACS, Version 19.1.8, May 2017 Preparing the new operating environment 5
 Planning the transition of network names and IP addresses 3.2

3.2 Planning the transition of network names and IP

addresses
This document assumes that the network names and IP addresses currently in use by the Sectra PACS
services moves with the Sectra PACS to the new system, as this is the most common way and has the
least impact on external systems.

When performing a transition of Sectra PACS from one system to another, new temporary network
names and IP addresses will be required during the transition.

See also

• section A.1 Network name transition principles

• section A.2 About the transition of an existing network name

• section A.3 Best practice for network names

• section 5.2.1 Copying existing hosts files

Define network names and IP addresses

1. Create a list of network names and IP addresses for the site. Include the network names for both
the existing system and the new system.

2. Contact the network responsible and acquire temporary network names and IP addresses to be used
during the transition.

3. Verify that all the network names are defined in the Domain Name System, DNS, and associated
with the correct IP address (either directly, or via an alias). Use the Windows command nslookup.

3.3 Installing the new operating environment

This is an outline of the installation steps for the new operating environment, excluding the Sectra PACS
software. Details are covered by the normal installation procedures.

Install new hardware and the new operating environment

1. Setup hardware

Install new hardware such as new servers, new storage and new network equipment.

A hardware refresh is an excellent opportunity to increase the size of the database disk. Over time
the database files increase in size. The new disks should be sized to have at least 50% free space.
The procedures described in this guide assume new database file systems.

2. Setup virtual environments

In case a virtual environment is to be used, prepare it for usage.

Sectra PACS, Version 19.1.8, May 2017 Preparing the new operating environment 6
 Installing the new operating environment 3.3

3. Install Windows

Install Windows Server on all new hosts. Use the network names and IP addresses defined in
section 3.2 Planning the transition of network names and IP addresses.

4. Initialize Windows

Initialize Windows roles and features, like Internet Information Server (IIS), .NET Framework,
failover clustering, etc.

Apply Windows security updates.

5. Install two instances of SQL Server

Create two new resource groups in the failover cluster with one SQL Server instance each. One for
the WISE Database, and one for the Sectra Healthcare Database and the Sectra Deployment
Database.

Use a temporary network name and a temporary IP address for the “WISE” instance. They will
later be replaced by the network name and IP address currently in use by the running WISE server.

If Sectra Healthcare System is in use in existing system, then use a temporary network name and IP
address for the “SHDB1” instance, otherwise apply a new permanent network name and IP address.

1. Install SQL Server, instance “WISE”, according to the Installation Guide Sectra PACS [1].

2. Install SQL Server, instance “SHDB1”, according to the Installation Guide Sectra PACS [1].

3. Install SQL Server service packs and security updates for both instances.

Note: The instance names “WISE” and “SHDB1” are the recommended default names. The names can
be changed but it is not covered by this document.

6. Prepare additional cluster groups

Prepare cluster groups for ImageServer/s and ImageServer/fs. That is, create the cluster groups,
add disk volumes and apply temporary or new permanent network names and IP addresses.

7. Setup load balancing

If network load balancing will be used in the new system, configure it and try it out.

As network load balancing is about handling of network names and IP addresses, most of the load
balancing configuration can be tried out in advance. It is only monitoring of Sectra applications that
has to wait until the services are installed.

8. Apply security settings

In case https (SSL/TLS) is to be used it should be applied and tried out in advance. Especially if
used in a network load balancing scenario.

Make sure existing firewall rules are adopted to allow traffic to and from the new hosts. Consider
for example in- and out-going teleradiology.

Sectra PACS, Version 19.1.8, May 2017 Preparing the new operating environment 7
 4 Preparing the temporary Sectra PACS

The following topics are included in this chapter:

■ Acquiring licenses

■ Installing a temporary Sectra PACS Core

■ Installing Sectra Deployment Framework

■ Deploying temporary Sectra Healthcare System

■ Removing temporary Sectra PACS

To verify the new operating environment, and to be able to prepare configurations, a new temporary
Sectra PACS will be created in the new operating environment.

Note: Installing a temporary Sectra PACS is highly recommended but not required. Install the components
and apply the configurations needed to validate the new operating environment.

Important: The data entered into this temporary Sectra PACS will be discarded. Do not enter any patient data
that needs to be preserved!

4.1 Acquiring licenses

A WISE license key works only on the host it was created for. As the WISE component now will be
moved to new hardware, a new WISE license key is required. When WISE runs in a failover cluster,
one WISE license key for each cluster node is required.

All other PACS license keys are related to the LTU (license to use) of the WISE license key. Other
license keys can be kept if the WISE LTU remains the same. A new WISE LTU requires that all license
keys in the PACS are replaced. An example of a WISE license key with the LTU marked:

WISE-0-2-HW-1-14-0-20350421-ANOT5DVC22-ANOT5DVC22-
69B399C19F00B449EFBD81852FD11C9D7D

Acquire licenses

1. Order two new WISE licenses for the new operating environment, one for each failover cluster
node.

2. If upgrading to a new major version of Sectra PACS and/or changing the WISE LTU, order a
complete set of new license keys for the new version.

Sectra PACS, Version 19.1.8, May 2017 Preparing the temporary Sectra PACS 8
 Installing a temporary Sectra PACS Core 4.2

4.2 Installing a temporary Sectra PACS Core

By installing the Sectra PACS Core, new Sectra PACS licenses can be verified. A blank WISE Database
will be created on the new hardware. When verified, the data in this temporary Sectra PACS Core will
be removed, see section 4.5 Removing temporary Sectra PACS.

Tip: In case extensive changes have been made to the registry settings in the existing system, it might be
beneficial to copy the registry settings to the new environment before installing. See appendix C Handling
registry settings.

Install temporary Sectra PACS Core

1. Run the WISE installation.

2. Run the WISE language pack installation.

3. Run the ImageServer/s installation.

4. Run the ImageServer installation (ImageServer/fs or ImageServer/xd).

5. Use inst_tool to create cluster resources.

6. Take the cluster resources off-line, move the resource groups to the second node and repeat the
steps above on the second node as well.

4.3 Installing Sectra Deployment Framework

Before performing the transition, a new Sectra Deployment Framework must be set-up to be able to
deploy and verify Sectra PACS in the new environment. That is, during the preparations two Sectra
Deployment Frameworks are needed in parallel.

The following procedure outlines the installation of the Sectra Deployment Framework in the new
environment. This will become the final Sectra Deployment Framework. The Sectra Deployment
Framework running in the old environment will be decommissioned.

Tip: If the system cover parts not effected by the transition, like other software than Sectra PACS or hosts
that will remain untouched, it might be beneficial to use a copy of the existing Sectra Deployment
Database as the basis for the new Sectra Deployment Framework. If needed, this is carried out on a
case by case basis and is not covered here.

The installation procedures and preparations are described in detail in Installation Guide Sectra PACS
[1].

Install the Sectra Deployment Framework

1. Create folders for the Sectra Deployment Database files.

2. Create a new Sectra Deployment Database.

3. Install one or more Sectra Deployment Servers.

4. Upload the software for the Sectra Healthcare System services to the Sectra Deployment Server.
That is, install the Sectra Deployment Packages.

Sectra PACS, Version 19.1.8, May 2017 Preparing the temporary Sectra PACS 9
 Deploying temporary Sectra Healthcare System 4.4

5. Install Sectra Deployment Agents.

See also

• section 6.5.2 Moving the Sectra Healthcare Database

• section 6.7 Starting IDS7 in the new environment

• chapter 7 Post transition tasks

4.4 Deploying temporary Sectra Healthcare System

Deploy temporary Sectra Healthcare System

1. Use Sectra Deployment Manager to deploy the Sectra Healthcare System components.

2. Use Sectra Enterprise Manager to connect the Sectra Healthcare System to the WISE server.

3. Use WISE/tools to apply licenses.

4. Verify with IDS7.

4.5 Removing temporary Sectra PACS

Once the temporary system and the new operating environment has been verified, the temporary data
must be removed before performing the transition.

Note: The Sectra PACS software remains. Only data stored in Sectra PACS will be removed.

Remove data in temporary system

1. Halt all the Sectra PACS services in the temporary system.

2. Detach and remove the temporary WISE Database.

3. Detach and remove the temporary Sectra Healthcare Database.

4. Remove all thumbnail images in the temporary system by deleting the contents of the thumbnail
directory. Leave shared thumbnail directories.

5. Remove all base folders in the temporary system by deleting the base folder directories. Leave shared
base folder directories.

6. On the temporary system, delete all examination directories from the ImageServer/fs file systems.
That is, delete all year-directories and all their contents. Leave the isarchive directory as it is.

Sectra PACS, Version 19.1.8, May 2017 Preparing the temporary Sectra PACS 10
 5 Preparing for transition

The following topics are included in this chapter:

■ Managing ImageServer/s image data

■ Managing ImageServer/s services

■ Cleaning up filing queues

■ Managing databases

This chapter describes how to prepare as much as possible before performing the actual transition, by
for example transferring data and applying configurations.

5.1 Managing ImageServer/s image data

The image data is stored on the file systems of ImageServer/s. It is assumed that the content of the
ImageServer/s file systems will be transferred to new file systems in the new operating environment.
The transition of the image data to the new system can be time-consuming, as it often is large amounts
of data to be transferred. As much as possible of the image data must be copied in advance, before the
transition event.

The image data is organized into base folders and thumbnail images. The image data is accessed via file
shares. See Table 5.1, “Transition of ImageServer/s image data”.

See also

• section 3.1 Planning the transition of file storage

• appendix B Handling storage

Sectra PACS, Version 19.1.8, May 2017 Preparing for transition 11

 Managing ImageServer/s image data 5.1

Table 5.1 Transition of ImageServer/s image data

Image data Transition details See

Base folders The base folders contain full sized images, as well as copies of them in different • section 5.1.1 Identifying
representations. This is usually large amounts of data. ImageServer/s base folders

Since the content of the base folders is constantly changing when Sectra PACS is • section 5.1.5 Start
in use, for example new images are added and old images are purged, the copying transferring ImageServer/s
process becomes more of a file system synchronization process. base folders

To reduce the time the transfer of the image data will take it is recommended to • section 6.4 Synchronizing
reduce the amount of image files stored on ImageServer/s to a minimum, if the ImageServer/s storage
system owner agrees to do so.
• section 6.8.1 Changing base
folder locations

Thumbnails Thumbnail images are small sized copies of the full sized images. They are never • section 5.1.2 Identifying
deleted. ImageServer/s thumbnail
image locations
When performing a transition, the total size of the thumbnail images is usually not
a problem. The challenge is instead to handle the large amount of small files to be • section 5.1.6 Creating new
copied. location for thumbnail
images in the old system
Best practice is to define a new parallel location for new thumbnails. By this, the
existing folder of thumbnail image files becomes static. This enables the (now static) • section 5.1.7 Start
folder of thumbnail images to be copied only once. The second (new) location will not transferring ImageServer/s
contain as much data and is easily copied during the transition event. thumbnail images

Consider the file block size when creating file systems for thumbnails. Although each • section 6.4 Synchronizing
thumbnail image file is small (approx 5 KB), it will allocate a full file system block on ImageServer/s storage
the file system. Using a file system with large file system blocks to store thumbnail
images will thus waste disk space. • section 6.8.2 Changing the
location for existing
thumbnail images

• section 6.9.1 Changing

locations for new thumbnail
images

File shares The file shares in use on the existing system must be created on the new system. • section 5.1.3 Creating
shares in new system

5.1.1 Identifying ImageServer/s base folders

Create a list of all base folders and the amount of data they contain. Decide for each base folder which
ImageServer/s host in the new system that will hold the base folder. There are different types of base
folders:

type_id=0 A “normal” base folder that holds online examinations. The printout of type_id=0 is
normally suppressed when using wdump.

type_id=1 Indicates the archive base folder (there is only one per PACS).

type_id=2 A teleradiology base folder. It points out a teleradiology destination. The name-string
will show up as a possible sending destination in IDS7.

Sectra PACS, Version 19.1.8, May 2017 Preparing for transition 12

 Managing ImageServer/s image data 5.1

It is not advisable to split or merge base folders during the transition. Old base folders must be moved
as they are, or emptied so that new ones can be created on the new system (how to reduce the amount
of examinations is described in section 5.1.4 Reducing ImageServer/s storage utilization).

Identify existing base folders

1. Use the following commands to list and store all base folders in the current system.

C:\> wdump bf > \temp\bf_list.txt

C:\> notepad \temp\bf_list.txt

2. Save the bf_list.txt file in a safe location.

3. To be able to estimate the time it will take to copy the base folders content, view the size of each
base folder. The path to each base folder is pointed out by the base folder's location-string. Only
base folders of type 0 are of interest.

See also

• section 5.1.5 Start transferring ImageServer/s base folders

• section 6.4 Synchronizing ImageServer/s storage

• section 6.8.1 Changing base folder locations

5.1.2 Identifying ImageServer/s thumbnail image locations

The path to the thumbnail images must be known to be able to move them to a new location.

List existing thumbnail image locations

1. View the configuration in the WISE database for thumbnail images.

C:\> wdump cfg MKSTAMP > \temp\mkstamp_cfg.txt

The path to the thumbnail images has the format file://hostname/thumbnails.

2. Save the mkstamp_cfg.txt file in a safe location.

Review existing thumbnail image locations

1. View the share properties for the thumbnails share. Identify the path to the shared folder on the
file system.

2. View the size of the thumbnail images.

See also

• section 5.1.6 Creating new location for thumbnail images in the old system

• section 5.1.7 Start transferring ImageServer/s thumbnail images

• section 6.4 Synchronizing ImageServer/s storage

• section 6.8.2 Changing the location for existing thumbnail images

Sectra PACS, Version 19.1.8, May 2017 Preparing for transition 13

 Managing ImageServer/s image data 5.1

• section 6.9.1 Changing locations for new thumbnail images

5.1.3 Creating shares in new system

To be able to create an exact copy of the existing installation, all existing shares must be recreated in
the new environment.

View existing file shares

1. Log on to the existing failover cluster hosting ImageServer/s

2. For each of the current Sectra PACS shares (folders$, folders2$, thumbnails$, ShsFileCenter$,
etc.) review the following in the cluster manager:

• The name of the share

• The security settings (access properties) of the share

• Cluster dependencies for the resource

• The path to the shared folder

• The security settings of the shared folder

Create new file shares

1. Log on to the new failover cluster hosting ImageServer/s

2. Create the same folders and shares as in the existing system. Remember to add a “$” in the end to
make them hidden.

Tip: Apply strict security settings on folder level to prevent unauthorized access. This protects the file
systems both when accessed locally as well as when accessed via the share. The share can then
be configured to shared to everyone without compromising security.

5.1.4 Reducing ImageServer/s storage utilization

In order to reduce the amount of data to be transferred, agreements can be made with the system owner
to temporarily reduce the amount of data stored on the ImageServer/s file systems by applying more
aggressive purging rules in Sectra Autofiler.

Tip: Look especially into base folders containing temporary data, like base folders used when fetching from
archive or when sending with teleradiology. They might contain data that can be purged without effecting
the users.

To reduce ImageServer/s storage utilization

1. Configure Sectra Autofiler to reduce the amount of examinations stored in ImageServer/s base
folders.

See also

• section B.5 Removing an obsolete base folder

Sectra PACS, Version 19.1.8, May 2017 Preparing for transition 14

 Managing ImageServer/s image data 5.1

5.1.5 Start transferring ImageServer/s base folders

This applies if the ImageServer/s file systems should be copied to new storage. See appendix B Handling
storage.

As the copying takes long time, it is important to start transferring the content of the existing
ImageServer/s base folders as early as possible. Perform copy tests early in the project to get a feel for
how long the transfer will take. Start the initial copy at least two weeks before the transition date and
then run incremental copy jobs to keep the file systems in sync once a day leading up to the transition.
The more recent these jobs have been run before the transition, the faster the last sync during downtime
will be.

Initiate transfer of base folder content

1. Start transferring the data stored in existing base folders in the old system to the new storage system
in the new operating environment. The use of robocopy is recommended, see section B.4 Using
file copying.

2. Set up a scheduled job, or introduce a manual procedure, to synchronize old and new storage systems
at least once a day. Use for example robocopy /mir.

See also

• section 6.4 Synchronizing ImageServer/s storage

5.1.6 Creating new location for thumbnail images in the old system
Before the transfer of the thumbnails will start, it is recommended to create a new, second, thumbnail
location on the old system. All new thumbnail images created after this point in time will then be created
in the second location.

The first location, containing the vast majority of the thumbnail images, will by that become static. This
facilitates the content of the first location to be copied before the transition without the need for
continuous synchronization. The second location will contain only a limited number of thumbnail images
that needs to be synchronized during the downtime.

Sectra PACS, Version 19.1.8, May 2017 Preparing for transition 15

 Managing ImageServer/s image data 5.1

This method can save a lot of time since the thumbnail synchronization can be a large part of the
downtime required for the transition.

Note: The new (second) location will not replace the first location. Both locations will exist also after the
transition, but new thumbnail images will only be created in the second location.

Note: When adjusting network names for thumbnail images, remember to use the network name associated
with the ImageServer/s application (rather than the network name of the physical host). See also
section A.3 Best practice for network names.

Table 5.2 Thumbnail configuration example

Item First location Second location

ImageServer/s host iss2 iss2

Directory E:\thumbnails E:\tn2

Shared as \\iss2\thumbnails$ \\iss2\tn2$

Thumbnail configuration string file://iss2/thumbnails$ file://iss2/tn2$

5.1.6.1 Creating a second thumbnail share

Create new thumbnail directory and share

1. Log on to the existing ImageServer/s host.

2. Create the new (second) location directory for thumbnail images on the ImageServer/s file system,
E:\tn2. Apply the same access control list as used for the first location.

3. Create the corresponding file share in the failover cluster, \\iss2\tn2$. Apply the same access
control list as used for the first location.

4. Verify access to the new share.

5. Remember to create the corresponding share in the new operating environment as well.

See also

• section 5.1.3 Creating shares in new system

5.1.6.2 Switching to the second thumbnail location

Important: This will change the creation of thumbnail images for the system in production. To minimize the impact,
it is recommended to perform it at off-peak hours.

See also

• section 5.1.2 Identifying ImageServer/s thumbnail image locations

• System Administrator's Guide ImageServer/s [3] for details on changing thumbnail locations with
w_config_misc.

Adjust the location for new thumbnail images

1. Log on to the existing WISE host.

Sectra PACS, Version 19.1.8, May 2017 Preparing for transition 16

 Managing ImageServer/s image data 5.1

2. Launch w_config_misc and select Set location for thumbnails.

3. Select Change default configuration. View and adjust the default location for new thumbnail
images.

Select Done to save the modified configuration. Select Set location for thumbnails again to review
the modified configuration.

4. Use Remove configuration for server to remove all server specific thumbnail image locations.
Save and review the modified configuration.

5. If there are more than one ImageServer/s in the new system, server specific thumbnail locations
must be defined:

For each ImageServer/s, use Add/Change configuration for server to create a new server specific
thumbnail location. Save and review the modified configuration.

If there is only one ImageServer/s, the default location is enough.

5.1.6.3 Verifying the second thumbnail location

Verify that the new locations work by sending in new images to the system. It is important that no new
thumbnails are created in the old locations.

Verify the modified configuration for new thumbnail images

1. To be able to validate the new configuration, increased logging is required on image import:

For each ImageServer/s, select a DICOM Storage SCP configuration to be used when validating.
Use Sectra Enterprise Manager to set the import log level to Image and exam folder id (w_store
-V e) .

2. To apply the modified thumbnail configuration, restart the DICOM Storage SCP Monitor service
on each ImageServer/s.

3. Import one image to the selected DICOM Storage SCP on each ImageServer/s. View the import
log and look for the entry Written stamp image to.... There should be no “stamp” errors.

4. When validated, restore the logging level for the DICOM Storage SCP.

5.1.7 Start transferring ImageServer/s thumbnail images

As no more thumbnail images are created in the first thumbnail location (see section 5.1.6 Creating new
location for thumbnail images in the old system), the content can now be copied to the new location in
the new operating environment.

Keep in mind that copying thumbnails takes a lot more time than anticipated due to the amount of files
involved. It can take several days, up to a week to just copy the thumbnails.

Start transfer of thumbnail images

1. Start transferring the thumbnail images in the same way as the base folders, see section 5.1.5 Start
transferring ImageServer/s base folders.

Sectra PACS, Version 19.1.8, May 2017 Preparing for transition 17

 Managing ImageServer/s image data 5.1

2. Even though a new thumbnail location has been created it is recommended to do at least one
incremental copy of the first thumbnail location, just to be sure that no additional thumbnails have
been created in the first location.

5.1.8 Preparing commands for base folder location changes

By preparing scripts for changing base folder location before the transition, downtime can be saved.

When changing the path of a base folder, both the WISE Database and the Sectra Healthcare Database
must be adjusted at the same time.

See also

• section 5.1.1 Identifying ImageServer/s base folders

• section 6.8.1 Changing base folder locations

Prepare base folder change commands

1. Prepare base folder changes in the WISE Database

For each base folder (to be modified), compile the full w_change_location command including
base folder id, old location string and new location string. See section 5.1.8.1 About modifying base
folder paths in the WISE Database.

Store all commands in a text or batch file.

2. Prepare base folder changes in the Sectra Healthcare Database

Prepare how to change the base folder paths stores in the Sectra Healthcare Database. See
section 5.1.8.2 About modifying base folder paths in the Sectra Healthcare Database

Tip: By preparing test data in each base folder, the time for the verification of changed base folders can
be reduced. See also section 6.8.3 Viewing existing images in IDS7.

5.1.8.1 About modifying base folder paths in the WISE Database

Base folders are defined in the WISE Database and can be modified with the command
w_change_location. In the WISE Database, the path to each image (and other stored object) may
include the path to the base folder. It is handled by w_change_location.

To change the base folder path of a base folder in the WISE Database, compile the full
w_change_location command including base folder id, old location string and new location string.

Example:
w_change_location -v -b <bf_id> -o <old_path> -n <new_path>

Here is an example of a script created at one site:

w_change_location -b 1 -o file://tbprs/folders$/default -n file://tbpr30/folders$/default
w_change_location -b 4 -o file://tbprs/folders$/lab_3_4 -n file://tbpr30/folders$/lab_3_4
w_change_location -b 5 -o file://tbprs/folders$/dsi -n file://tbpr30/folders$/dsi
w_change_location -b 7 -o file://tbprs/folders$/us -n file://tbpr30/folders$/us
w_change_location -b 8 -o file://tbprs/folders$/lab_13_14 -n file://tbpr30/folders$/lab_13_14
w_change_location -b 9 -o file://tbprs/folders$/ct -n file://tbpr30/folders$/ct

Sectra PACS, Version 19.1.8, May 2017 Preparing for transition 18

 Managing ImageServer/s image data 5.1

The list was generated with the following SQL script. The result was copied into a new batch file (.bat).

use wise
--Get a copy of the current base folders
select * from W_BASE_FOLDER;

--Generate w_change_location commands

--Replace the hostname in the location string by replacing the string
--tbprs (old hostname) with the string tbpr30 (new hostname)
use wise
select 'w_change_location -b ', wbf_id, '-o ', wbf_loc, '-n ', REPLACE(wbf_loc, 'tbprs', 'tbpr30')
from w_base_folder
where WBF_LOC like '%tbprs/%'
order by wbf_id;

5.1.8.2 About modifying base folder paths in the Sectra Healthcare Database
In the Sectra Healthcare Database, the path to each base folder is stored only once and other objects
refers to this path.

Changes to a base folder path is done by editing the database table RootDirectory in the Sectra
Healthcare Database (SectraHealthcareStorage). It can be performed from SQL Server Management
Studio and/or by executing SQL commands as described below.

Example on how to identify the GUID of the base folder object in the Sectra Healthcare Database:
SELECT guid FROM rootdirectory
WHERE path = 'file://tbprs/folders$/ct';

Guid
4A87A688-51D8-E011-AB18-005056000217

Example on how to update the base folder path:

Important: Executing this query will change the Sectra Healthcare Database. Prepare the command here, but
execute it in section 6.8.1 Changing base folder locations.

UPDATE rootdirectory
SET path = 'file://tbpr30/folders$/ct'
WHERE guid = '4A87A688-51D8-E011-AB18-005056000217';

(1 row(s) affected)

5.1.9 Preparing commands for thumbnail image location changes

If the ImageServer/s network name changes or if the path to the thumbnail shares changes during the
transition, downtime can be saved by preparing scripts for changing the location of existing thumbnails.

See also

• section 6.8.2 Changing the location for existing thumbnail images

Prepare thumbnail location change commands

1. For each thumbnail location (to be modified), compile the full w_change_location command
including thumbnail location identifier, old location string and new location string.

2. Store all commands in a text or batch file.

Here is an example of a script created at one site:

Sectra PACS, Version 19.1.8, May 2017 Preparing for transition 19

 Managing ImageServer/s services 5.2

w_change_location -t -o file://tbprs/thumbnails$ -n file://tbpr30/thumbnails$

w_change_location -t -o file://tbprs/tn2$ -n file://tbpr30/tn2$

5.2 Managing ImageServer/s services

ImageServer/s provides a number of services. The configuration for these services must be transferred.
See Table 5.3, “Transition of configuration for ImageServer/s services”.

Table 5.3 Transition of configuration for ImageServer/s services

Service Transition details See

DICOM The existing DICOM Storage SCP configuration follows with the WISE • section 5.2.1 Copying existing hosts files
Storage SCP Database to the new operating environment.
• section 5.2.2 Preparing DICOM Storage SCP
If the network name of the ImageServer/s host or the path to the configuration
location for temporary images (known as Image Root Directory or
in_dcm.) have changed during the transition, the DICOM Storage • section 6.9.2 Applying DICOM Storage SCP
settings
SCP configurations must be adjusted.

DICOM Q/R The DICOM Query/Retrieve SCP configuration is stored in the • section 5.2.1 Copying existing hosts files
SCP configuration file qrscp.def. There is one per ImageServer/s host.
The existing configuration must be copied to the new operating • section 5.2.3 Preparing DICOM
Query/Retrieve SCP configuration
environment.

Sectra The configuration of Sectra Autofiler must be done on each • section 5.2.4 Preparing Sectra Autofiler
Autofiler ImageServer/s host. configuration

DICOM DICOM Storage Backup is not covered by this guide. • System Administrator's Guide ImageServer/s
Storage [3]
Backup

5.2.1 Copying existing hosts files

Both the DICOM Storage SCP and the DICOM Query/Retrieve SCP services are normally restricted
to only allow access from known hosts. That is, hosts defined in the hosts file on the ImageServer/s
host or hosts defined in the DNS.

Copy hosts files

1. Copy the file %windir%\system32\drivers\etc\hosts from the existing ImageServer/s host to

the ImageServer/s host in the new operating environment.

2. Update the hosts file in accordance with changed network names and IP addresses, see section 3.2
Planning the transition of network names and IP addresses.

3. Repeat for all ImageServer/s hosts in the new operating environment.

Sectra PACS, Version 19.1.8, May 2017 Preparing for transition 20

 Managing ImageServer/s services 5.2

5.2.2 Preparing DICOM Storage SCP configuration

If the network name of the ImageServer/s host or the path to the location for temporary images (known
as Image Root Directory or in_dcm) have changed during the transition, the DICOM Storage SCP
configurations must be adjusted.

However, if no such changes are made, the existing DICOM Storage SCP configurations follows with
the WISE Database to the new operating environment and no adjustments are needed.

See also

• section 6.9.2 Applying DICOM Storage SCP settings

5.2.2.1 Extracting the current DICOM Storage SCP configuration

The DICOM Storage SCP configuration is stored in the WISE Database.

Store existing configuration

1. Log on

Log on to the existing WISE host.

2. Save current settings in a text file

Save the current DICOM Storage SCP settings in the WISE Database to a text file.
C:\> wdump cfg DCM_STORAGE_SCP_CONFIG > dcmstore_cfg.txt

5.2.2.2 Identifying blocks of configuration

The DICOM Storage SCP settings are organized in blocks of configuration data. Each block of data
starts with the line config_data: as shown in the example below. The id: field is a unique identifier
for this configuration data object. The type: and tag: fields show the type of data stored. The setting:
field is where the actual DICOM Storage SCP settings are stored.

The setting: field starts with the hostname of the ImageServer/s host and is then followed by a data
block (starts with “{”, contains several lines and ends with “}”). The config_data-block ends with the
field role:.

Example, with the id and the contents of the settings-field marked:

config_data:
id: 117
type: 0
tag: DCM_STORAGE_SCP_CONFIG
setting: test41 {
…
}
role: -1

Identify blocks of configuration

1. View the dcmstore_cfg.txt file. Identify the blocks of configuration data. Write down the id and
the hostname of the ImageServer/s host for each block.

Sectra PACS, Version 19.1.8, May 2017 Preparing for transition 21

 Managing ImageServer/s services 5.2

5.2.2.3 Compiling a new DICOM Storage SCP configuration

Compile the new configuration

1. Copy configuration file

Copy the dcmstore_cfg.txt file to a new text file. Add the hostname of the ImageServer/s host
to the filename. Example: dcmstore_cfg.testiss.txt

Create one new file for each ImageServer/s host. That is, create one configuration file for the
ImageServer/s resource group, but none for the cluster nodes.

2. Edit new configuration file

Edit the new configuration file (dcmstore_cfg.testiss.txt). Remove everything but the contents
of the “settings:”-tag for this host (testiss). Text both before and after the tag needs to be removed.

Modify the hostname from test41 to testiss.

The file, dcmstore_cfg.testiss.txt, will then have the following contents only:

testiss {
ctnstore {
timeout<20>
servers {
standard {
…configuration data…
}
}
senders
}
}

3. Apply transition changes

Edit the configuration files to adjust the parameters that changes due to the transition to the new
hardware. For example:

Image Root Directory: This is the directory where the images are temporarily stored during
the image import process. Should reside on an ImageServer/s file
system (where the base folders are located). For example;
“J:\folders\in_dcm”. Should be the same for all DICOM Storage
SCP servers on the same host.

Import Arguments: If the “-b id_string” argument is used, make sure that the images
are directed to the correct base folder.

4. Repeat

Remember to edit the configuration files for all ImageServer/s hosts.

5.2.3 Preparing DICOM Query/Retrieve SCP configuration

All configurations regarding the DICOM Query/Retrieve SCP are stored in one configuration file,
qrscp.def. There is one per ImageServer/s host.

The configuration file is located in SI_CONFIG_DIR\config\qrscp\def, where SI_CONFIG_DIR is an

ImageServer/s registry key. Use regenv to view it.

Sectra PACS, Version 19.1.8, May 2017 Preparing for transition 22

 Cleaning up filing queues 5.3

Copy DICOM Query/Retrieve SCP configuration

1. Copy the qrscp.def file from the existing system to the ImageServer/s host in the new operating
environment.

2. View the copied file and adjust the content if needed.

3. Repeat for each ImageServer/s host.

See also

• System Administrator's Guide ImageServer/s [3]

• chapter 7 Post transition tasks

5.2.4 Preparing Sectra Autofiler configuration

The configuration of Sectra Autofiler must be done on each ImageServer/s host.

The configuration is stored in

SI_CONFIG_DIR\local_config\_all_\autofiler\def\w_auto_filer.def, where SI_CONFIG_DIR
is an ImageServer/s registry key. Use regenv to view it.

Copy Sectra Autofiler configuration

1. Copy the w_auto_filer.def file from the existing system to the ImageServer/s host in the new
operating environment.

2. View the copied file and adjust the content if needed.

3. Repeat for each ImageServer/s host.

See also

• System Administrator's Guide ImageServer/s [3]

• chapter 7 Post transition tasks

5.3 Cleaning up filing queues

Verify that all examinations in the filing queue are successfully filed.

1. Check that all examinations in the filing queue are completed. Handle all failed jobs.

C:\> is_client get_archive_queue | findstr /V COMPLETED

This lists all queue jobs that have not completed successfully. See System Administrator's Guide
ImageServer/fs, ImageServer/xd, ImageServer/os [2] for information about how to handle failed
jobs.

Sectra PACS, Version 19.1.8, May 2017 Preparing for transition 23

 Managing databases 5.4

5.4 Managing databases

5.4.1 Locating database files

Before detaching the databases in section 6.5 Moving databases, the paths to the database files must be
known.

Locate WISE Database files

1. Log on to the existing WISE host as a Windows user with SQL Administrator access to the “WISE”
instance.

2. Launch SQL Server Management Studio and connect to the “WISE” instance.

3. In the SQL Server Management Studio, find the WISE Database in the tree view:

<hostname>\WISE->Databases->WISE

4. Right-click the database WISE and select Properties.

5. Select tab Files.

The column Path shows the location of the WISE Database files.

6. Use File Explorer to verify that the database files can be accessed.

Locate Sectra Healthcare Database files

1. Log on to the existing Sectra Healthcare Database host as a Windows user with SQL Administrator
access to the “SHDB1” instance.

2. Launch SQL Server Management Studio and connect to the “SHDB1” instance.

3. In the SQL Server Management Studio, find the Sectra Healthcare Database in the tree view:

<hostname>\SHDB1->Databases->SectraHealthcareStorage

4. Right-click the database SectraHealthcareStorage and select Properties.

5. Select tab Files.

The column Path shows the location of the Sectra Healthcare Database files.

6. Use File Explorer to verify that the database files can be accessed.

Sectra PACS, Version 19.1.8, May 2017 Preparing for transition 24

 6 Switching to new system (requires
downtime)

The following topics are included in this chapter:

■ Completing pre-transition checklists

■ Stopping Sectra PACS

■ Moving network names and IP addresses

■ Synchronizing ImageServer/s storage

■ Moving databases

■ Starting WISE in the new environment

■ Starting IDS7 in the new environment

■ Adjusting and verifying access to existing images

■ Adjusting settings for future images

■ Adjusting ImageServer/fs

■ Completing transition

When all preparations are done, it is time to perform the transition of Sectra PACS to the new hardware.
This requires that Sectra PACS is stopped.

Sectra PACS, Version 19.1.8, May 2017 Switching to new system (requires downtime) 25
 Completing pre-transition checklists 6.1

6.1 Completing pre-transition checklists

These checklists are provided as a last checkpoint before stopping Sectra PACS, to make sure all
preparations that can be done are carried out.

Note: It might be that some checks are not applicable to all transition projects.

Table 6.1 ImageServer/s transition checklist

Check Result See

ImageServer/s resource group exists, with a temporary network chapter 3 Preparing the new operating environment
name and IP address

File shares are created section 5.1.3 Creating shares in new system

Base folder data is copied section 5.1.5 Start transferring ImageServer/s base
folders

Commands for modifying base folder locations are prepared section 5.1.8 Preparing commands for base folder
location changes

Thumbnail images are copied section 5.1.7 Start transferring ImageServer/s

thumbnail images

Commands for modifying thumbnail image locations are prepared section 5.1.9 Preparing commands for thumbnail image
location changes

New DICOM Storage SCP configuration is prepared section 5.2.2 Preparing DICOM Storage SCP
configuration

6.2 Stopping Sectra PACS

The existing Sectra PACS will now be stopped to allow the transition to be started.

Stop existing Sectra PACS

1. Stop the existing Sectra PACS services

2. Disable all Sectra PACS services in the existing system. This to make sure no services are started in
case the old hosts are rebooted.

6.3 Moving network names and IP addresses

It is now time to move the network names and IP addresses from the old system to the new system so
that external systems communicating with Sectra PACS ends up connecting to the services on the new
system.

Move network names and IP addresses

1. Perform the switching of network names and IP addresses according to section A.2 About the
transition of an existing network name.

Sectra PACS, Version 19.1.8, May 2017 Switching to new system (requires downtime) 26
 Synchronizing ImageServer/s storage 6.4

See also

• section 3.2 Planning the transition of network names and IP addresses

• appendix A Handling network names and IP addresses

6.4 Synchronizing ImageServer/s storage

This is the final synchronization of the image data copied from the old to the new storage of
ImageServer/s. Keep in mind that the host names might have changed for both the source and the target
system.

As this step can be very time consuming, it is advisable to continue with the other tasks.

See also

• section 3.1 Planning the transition of file storage

• section 5.1 Managing ImageServer/s image data

• appendix B Handling storage

Final storage synchronization for ImageServer/s

1. Make sure all Sectra PACS services are halted, on both old and new systems.

2. Perform the final synchronization of the ImageServer/s storage.

3. Stop and disable the storage synchronization.

Important: The storage synchronization must be disabled before importing new data in the new operating
environment. Otherwise there is a risk for accidental removal of data from the new storage.

6.5 Moving databases

The Sectra PACS databases will now be moved to the new SQL Server instances in the new operating
environment. They were installed in section 3.3 Installing the new operating environment.

6.5.1 Moving the WISE Database

The WISE Database will now be moved from the existing to the new system.

Detach database

1. Make sure the paths to the WISE Database files are known. See section 5.4.1 Locating database
files.

2. Make sure the WISE services are stopped, and that no database maintenance jobs are running. See
section 6.2 Stopping Sectra PACS.

3. In the SQL Server Management Studio, right-click the database WISE and select Tasks->Detach….

Sectra PACS, Version 19.1.8, May 2017 Switching to new system (requires downtime) 27
 Moving databases 6.5

4. Choose to drop connections but not to update index. An update of index may take a considerable
amount of time.

Click Ok in the confirmation dialog.

Transfer database files

1. Copy all the WISE Database files from the existing location to the new database location in the new
operating environment. Copy only the files under Data, Index and Log. There is no need to copy
the backup files.

Attach database files

1. Log on to the new WISE host in the new operating environment. Log on as a Windows user with
SQL Administrator access to the “WISE” instance.

2. Launch SQL Server Management Studio and connect to the “WISE” instance.

3. In the SQL Server Management Studio, right-click <hostname>\WISE->Databases and select

Attach....

4. In the Attach Databases window, under Databases to attach, click Add....

5. In the Locate Database Files window, locate the WISE_PRIMARY.mdf file and press OK.

6. In the Attach Databases window, the database files are now listed in Database details. Correct the
path to missing database files by pressing the “…”-button. When all database files are located, press
OK to attach the WISE Database.

6.5.2 Moving the Sectra Healthcare Database

The Sectra Healthcare Database will now be moved from the existing to the new system.

Note: The Sectra Deployment Database, located in the same SQL Server instance as the Sectra Healthcare
Database, will not be moved. See section 4.3 Installing Sectra Deployment Framework.

Detach database

1. Make sure the paths to the Sectra Healthcare Database files are known. See section 5.4.1 Locating
database files.

2. Make sure the Sectra Healthcare Server services are stopped, and that no database maintenance jobs
are running. See section 6.2 Stopping Sectra PACS.

3. In the SQL Server Management Studio, right-click the database SectraHealthcareStorage and
select Tasks->Detach….

4. Choose to drop connections but not to update index. An update of index may take a considerable
amount of time.

Click Ok in the confirmation dialog.

Sectra PACS, Version 19.1.8, May 2017 Switching to new system (requires downtime) 28
 Starting WISE in the new environment 6.6

Transfer database files

1. Copy all the Sectra Healthcare Database files from the existing location to the new database location
in the new operating environment. Copy only the files under Data, Index and Log. There is no
need to copy the backup files.

Attach database files

1. Log on to the new Sectra Healthcare Database host in the new operating environment. Log on as
a Windows user with SQL Administrator access to the “SHDB1” instance.

2. Launch SQL Server Management Studio and connect to the “SHDB1” instance.

3. In the SQL Server Management Studio, right-click <hostname>\SHDB1->Databases and select

Attach....

4. In the Attach Databases window, under Databases to attach, click Add....

5. In the Locate Database Files window, locate the SectraHealthcareStoragePrimary.mdf file and
press OK.

6. In the Attach Databases window, the database files are now listed in Database details. Correct the
path to missing database files by pressing the “…”-button. When all database files are located, press
OK to attach the Sectra Healthcare Database.

6.6 Starting WISE in the new environment

The moved WISE Database will now be upgraded by running the WISE installation program.

Upgrade the WISE Database

1. Start the WISE installation program on the node where the WISE group is partially online. The
Sectra PACS cluster resources should be offline but the group must still be online (disks online and
database running). Start a command prompt as administrator (“Run as administrator”) and then
start the installation program from there. The name of the installation program has the format
WISE.<version>.msi. Enter the new WISE license during the installation.

2. Run inst_tool to add the WISE services as cluster resources.

3. Start the service “SECTRA WISE Monitor”.

4. Use wdump st to verify the WISE server is responding.

See also

• section 4.2 Installing a temporary Sectra PACS Core

6.7 Starting IDS7 in the new environment

IDS7 is required when verifying Sectra PACS in the new environment. This section will make sure the
Sectra Healthcare System, and log on to IDS7, is working.

Sectra PACS, Version 19.1.8, May 2017 Switching to new system (requires downtime) 29
 Starting IDS7 in the new environment 6.7

See also

• chapter 4 Preparing the temporary Sectra PACS

• section 4.3 Installing Sectra Deployment Framework

Upgrade the Sectra Healthcare Database

1. Verify shares

This procedure requires the ImageServer/s and SHS file center shares to be accessible. See
section 5.1.3 Creating shares in new system.

2. Adjust path to SHS file center

If the path to the SHS file center share has changed (changed network name or share name), the
path should be corrected in the Sectra Healthcare Database before upgrading it.

Use SQL Server Management Studio to edit the table dbo.RootDirectory in the
SectraHealthcareStorage database. Adjust the path to the file center. More information about
how to update the file center path can be found in the Tech Note with ID TN-JSJG-8ZTLCQ.
The Tech Notes database is available on the Sectra Userweb, Sectra User Web1.

3. Upgrade SHDB

The Sectra Healthcare Database (SHDB) is now attached to SQL Server in the new operating
environment (see section 6.5.2 Moving the Sectra Healthcare Database).

Run Sectra PACS Setup to upgrade the Sectra Healthcare Database.

Adjust the Sectra Deployment Framework

Depending on the changes made in section 6.3 Moving network names and IP addresses, the Sectra
Deployment Framework might need adjustments. For details, see Installation Guide Sectra PACS [1].

1. Sectra Deployment Servers to Sectra Deployment Database

If the network name of the SQL Server SHDB1 instance has changed, the database connection
string of each Sectra Deployment Server must be adjusted.

2. Sectra Deployment Agents to Sectra Deployment Server

If the network name of the Sectra Deployment Server has changed, adjust the connection information
for each of the affected Sectra Deployment Agents.

3. Component settings in Sectra Deployment Framework

If needed, use Sectra Deployment Manager to adjust the component settings of the deployed software.

Start IDS7

1. Start SHS

Use Sectra Deployment Manager to start Sectra Healthcare Server.

1
https://userweb.sectra.se

Sectra PACS, Version 19.1.8, May 2017 Switching to new system (requires downtime) 30
 Adjusting and verifying access to existing images 6.8

2. Log on to Sectra Enterprise Manager

By logging on to Sectra Enterprise Manager, the Sectra Healthcare Database and the Sectra
Healthcare Server can be verified. No Sectra PACS Core connection or licenses are required.

3. Add licenses

Use WISE/tools to add and assign new licenses.

4. Log on to IDS7

Verify that IDS7 works, by logging on to the IDS7 workspace.

If needed, use Sectra Enterprise Manager to correct the connection to the WISE server.

Note: Images might not show up yet. See also section 6.8 Adjusting and verifying access to existing
images.

5. Stop SHS

To prevent users from logging on, stop Sectra Healthcare Server.

6.8 Adjusting and verifying access to existing images

This section describes how to make the adjustments required to view existing images in IDS7.

6.8.1 Changing base folder locations

This will adjust the paths to the base folders, as prepared in section 5.1.8 Preparing commands for base
folder location changes.

To adjust the path to a base folder

1. Run w_change_location to change the base folder location for both new and existing examinations
in the WISE Database.

2. Use SQL Server Management Studio to edit the table dbo.RootDirectory in the
SectraHealthcareStorage database. Adjust the paths to the base folders. More information
about how to update the base folder paths can be found in the Tech Note with ID TN-JSJG-8LG97A.
The Tech Notes database is available on the Sectra Userweb, Sectra User Web2.

6.8.2 Changing the location for existing thumbnail images

This will adjust the paths to all existing thumbnail images in the system, as prepared in section 5.1.9
Preparing commands for thumbnail image location changes.

2
https://userweb.sectra.se

Sectra PACS, Version 19.1.8, May 2017 Switching to new system (requires downtime) 31
 Adjusting settings for future images 6.9

The configuration for future thumbnail images is adjusted in section 6.9.1 Changing locations for new
thumbnail images.

Note: When adjusting network names for thumbnail images, remember to use the network name associated
with the ImageServer/s application (rather than the network name of the physical host). See also
section A.3 Best practice for network names.

Adjust the location of existing thumbnail images

1. Log on to the new WISE host

2. Run w_change_location to change the paths to existing thumbnail images in the WISE Database.

6.8.3 Viewing existing images in IDS7

View existing images

1. Start SHS

2. Log on to IDS7. Verify that existing thumbnails and images can be viewed.

3. Stop SHS

6.9 Adjusting settings for future images

Before importing new images, the image import configuration must be adjusted.

6.9.1 Changing locations for new thumbnail images

The locations for future thumbnail images must be adjusted (it is assumed that network names or the
share names changed during the transition).

The paths to all existing thumbnail images already in the system is adjusted in section 6.8.2 Changing
the location for existing thumbnail images.

Note: When adjusting network names for thumbnail images, remember to use the network name associated
with the ImageServer/s application (rather than the network name of the physical host). See also
section A.3 Best practice for network names.

To adjust the locations for new thumbnail images

1. Log on to the new WISE host.

2. Launch w_config_misc and select Set location for thumbnails.

3. Select Change default configuration. View and optionally adjust the default location for new
thumbnail images.

Select Done to save the modified configuration. Select Set location for thumbnails again to review
the modified configuration.

Sectra PACS, Version 19.1.8, May 2017 Switching to new system (requires downtime) 32
 Adjusting settings for future images 6.9

4. Use Remove configuration for server to remove all server specific thumbnail image locations.
Save and review the modified configuration.

5. If there are more than one ImageServer/s in the new system, server specific thumbnail locations
must be defined:

For each ImageServer/s, use Add/Change configuration for server to create a new server specific
thumbnail location. Save and review the modified configuration.

If there is only one ImageServer/s, the default location is enough.

Before verifying, the DICOM Storage SCP configuration changes must be completed. The configuration
modified here will be verified in section 6.9.3 Verifying image import.

6.9.2 Applying DICOM Storage SCP settings

Apply the DICOM Storage SCP settings, as prepared in section 5.2.2 Preparing DICOM Storage SCP
configuration.

The procedure is to remove all DICOM Storage SCP settings from the WISE Database and then apply
the new configuration. The current configuration is saved to a text file before removing the settings
from the database.

Halt image import

Stop all SECTRA DICOM Storage SCP Monitor services on all ImageServer/s hosts.

1. Start Failover Cluster Manager

2. Mark resource group ImageServer/s group

3. Right-click on resource DICOM Storage SCP Monitor and select Take this resource offline

Delete cached configuration

The DICOM Storage SCP configuration is stored in the WISE Database, but each DICOM Storage
SCP service may store a copy of the configuration in a local file. These local files must be removed to
avoid that the cached configuration interferes with the new settings.

1. Delete the file <drive>:\ImageServerS_config\local_config\_all_\

ctnstore\def\ctn_admin.def

Backup and remove existing configuration

1. Save current settings in a text file

As a backup, save the current DICOM Storage SCP settings in the WISE Database to a text file.
Run the command on the new WISE host.
C:\> wdump cfg DCM_STORAGE_SCP_CONFIG > dcmstore_cfg.backup.txt

2. View the file

View the dcmstore_cfg.backup.txt file. Identify the blocks of configuration data. Write down
the id of each block.

Sectra PACS, Version 19.1.8, May 2017 Switching to new system (requires downtime) 33
 Adjusting settings for future images 6.9

config_data:
id: 117
type: 0
tag: DCM_STORAGE_SCP_CONFIG
…

Tip: To make sure no recent changes are missed, compare the dcmstore_cfg.backup.txt file with the
file saved when preparing the configuration. See section 5.2.2.1 Extracting the current DICOM
Storage SCP configuration.

3. Remove configuration from WISE Database

Remove all the DICOM Storage SCP configurations from the WISE Database. The example shows
how to remove the configuration with id 117 (as in the example above). You need to repeat this for
all the configuration data blocks found in the text file.

C:\> wrm cfg 117

C:\>

Verify that all configurations are gone. The command should return an error.

C:\> wdump cfg DCM_STORAGE_SCP_CONFIG

wdump: WISE Error: NO_MATCH (code: 34)
C:\>

Apply new configuration

1. Load new configuration data

Load the new configuration data, as prepared in section 5.2.2 Preparing DICOM Storage SCP
configuration, into the WISE Database. Replace the file name with the file name of the configuration
file created in previous action.

C:> w_config –v -f dcmstore_cfg.testiss.txt type=0

tag=DCM_STORAGE_SCP_CONFIG role=-1
w_config: wise_client status: 0
Adding config data
Result: config_data:
id: 119
type: 0
tag: DCM_STORAGE_SCP_CONFIG
setting: testiss { ctnstore {
timeout<20>
servers {
…
C:\>

Note: If the resulting setting: tag is empty, then something went wrong. The setting: tag should contain
the configuration from the text file. To remove the added configurations use the following commands,
where 119 corresponds to the id: of the config_data listed in the result above:

C:\> wdump –i 119 cfg |more (verifies that the ID is correct)

C:\> wrm cfg 119

2. Repeat

Remember to load the configuration files for all ImageServer/s hosts.

Sectra PACS, Version 19.1.8, May 2017 Switching to new system (requires downtime) 34
 Adjusting ImageServer/fs 6.10

6.9.3 Verifying image import

Once the configuration for base folders, thumbnail images and DICOM Storage SCPs are adjusted,
verify the adjusted configurations by importing test images. This will verify the configuration changes
made in:

• section 6.9.1 Changing locations for new thumbnail images

• section 6.9.2 Applying DICOM Storage SCP settings

Verify the modified configuration for new thumbnail images

1. Verify the configuration changes in Sectra Enterprise Manager.

In the cluster case, make sure that there are no DICOM Storage SCPs configured under the network
names of the cluster nodes. If there are, remove them.

2. Start the DICOM Storage SCP services.

3. Import test images to verify that new thumbnail images are created in the correct locations, and that
the import works.

See also section 5.1.6.3 Verifying the second thumbnail location.

6.10 Adjusting ImageServer/fs

This section describes how to adjust the ImageServer/fs component to the new environment.

6.10.1 Synchronizing ImageServer/fs storage

Final storage synchronization for ImageServer/fs

1. Make sure the ImageServer/fs services are halted, on both old and new systems.

2. Perform the final synchronization of the ImageServer/fs storage. See appendix B Handling storage.

3. Turn off the storage synchronization.

6.10.2 Verifying the archive

Verify the archive solution

1. Start the archive services.

2. Verify fetching from archive by performing manual retrievals using IDS7.

3. Verify filing of new examinations into the archive by performing manual archiving actions using
IDS7.

Sectra PACS, Version 19.1.8, May 2017 Switching to new system (requires downtime) 35
 Completing transition 6.11

6.11 Completing transition

Before start using Sectra PACS in the new operating environment, the system must be verified according
to the available quality control procedures.

The quality control procedures can be found in Installation Guide Sectra PACS [1].

Execute quality control procedures

1. Execute the quality control procedure for Sectra PACS Servers.

2. Execute the quality control procedure for IDS7.

3. If LiteView is deployed, execute the quality control procedure for LiteView.

4. If UniView is deployed, execute the quality control procedure for UniView.

Sectra PACS, Version 19.1.8, May 2017 Switching to new system (requires downtime) 36
 7 Post transition tasks

This chapter provide checklists of additional tasks to be performed and additional features that might
require testing and adjustments, if they are configured and in use.

WISE services

• View WISE server log files

• RIS Interface and HL7

• DICOM Modality Worklist SCP

• Sectra ImageServer Monitor services

ImageServer/s services

• DICOM Storage SCP

• DICOM Storage Backup

• DICOM Query/Retrieve SCP

• Teleradiology

• Sectra Autofiler. Wait with automatic archiving actions until manual archive fetching and retrieval
has been verified, see section 6.10.2 Verifying the archive.

Sectra Healthcare System services

• View Sectra Healthcare Server log files

• Confirm access to the SHS file center

• Save image/stack

• Printing

• Media import & export

• CPW, interconnected systems

• IPV, import of pictures and videos

• Mammography work flows

• EPR Integration (URL)

Other post transition tasks

• Decommission of old system

Sectra PACS, Version 19.1.8, May 2017 Post transition tasks 37

 • Configure Sectra Monitoring

Sectra PACS, Version 19.1.8, May 2017 Post transition tasks 38

 A Handling network names and IP addresses

The following topics are included in this appendix:

■ Network name transition principles

■ About the transition of an existing network name

■ Best practice for network names

A network name, or an IP address, defines how a component should communicate with another part of
the system. Network names are stored in many different configurations depending on the component
using them.

This appendix describes how to handle and change the network name and/or the IP address of Sectra
PACS components.

See also

• section 3.2 Planning the transition of network names and IP addresses

A.1 Network name transition principles

There are two main principles for how to handle network names and IP addresses during a transition.

This document assumes that the network names and IP addresses currently in use moves with the Sectra
PACS to the new system (according to the first principle), as this is the most common way and it has
the least impact on external systems.

However, since network name and/or IP address changes sometimes are required (the second principle),
information on how to perform such changes is provided as well.

Principle Benefits Drawbacks

Keep existing network names • External systems integrated with Sectra • The new system must look the same as
PACS, like a modality or another PACS the existing system (same number of
The network names and IP addresses
sending images, can continue without host etc)
currently in use by the Sectra PACS services
reconfiguration
in the existing system are moved together • Additional temporary network names and
with the Sectra PACS to the new operating • Users can connect in the same way as IP addresses are required during the
environment before the transition transition

See section A.2 About the transition of an • Firewall rules for incoming and outgoing • It must be possible to apply the existing
existing network name traffic will continue to work IP addresses to the new operating
environment (sometimes a new range of
• SSL certificates issued for the fully
IP addresses is required for the new
qualified domain name will still be valid
operating environment)

Sectra PACS, Version 19.1.8, May 2017 Handling network names and IP addresses 39
 Principle Benefits Drawbacks

Move to new network names • Flexible. This allows the system design • Extensive reconfiguring of services might
to be altered, like when introducing be required, both in Sectra PACS as well
New network names and IP addresses are
failover clustering, load balancing or as in other systems
applied to the new operating environment.
additional servers.
Sectra PACS services and integrated • Depends on other parties to perform
systems are reconfigured to use the new • The new system can be built in full scale configuration changes in external
names. in parallel, and new integrations can be systems
tried out in advance
• Higher risk that configurations are
missed and features fail after the
transition

A.2 About the transition of an existing network name

This section outlines how an existing IP address or network name is moved from the existing system
onto the new operating environment.

The following notations are used in Table A.1, “Transition of an IP address”:

IP1 Represents the IP address currently in use by the Sectra PACS component. This IP address is
configured in external systems, like in a modality sending images to ImageServer/s. This is the
IP address that will move with the services to the new operating environment when performing
the transition.

IP2 This IP address is a new temporary address applied to the new operating environment while
preparing it for the transition.

IP3 This IP address is a new temporary address that will be assigned to the old server when moving
the IP1 address from the old to the new server.

Having access to the old server, also after the transition, is of great value when configuring and
verifying the new system. It is also likely that sensitive data must be cleaned up before
decommission of the old server.

Sectra PACS, Version 19.1.8, May 2017 Handling network names and IP addresses 40
Table A.1 Transition of an IP address

Phase Computer A Computer B Comment

1
. Production on the existing system IP1 The existing system has a host with the IP address “IP1”

2
. Preparations - Building the new operating IP1 IP2 The new operating environment is installed in parallel by
environment the use of a new temporary IP address, “IP2”

3
. Transition - Release IP1 IP3 IP2 Before IP1 can be moved from Computer A to Computer
B, it must be released from Computer A:

1. Change to the new temporary IP3 on Computer A

2. Reboot Computer A to release the IP1 address and

update the DNS

4
. Transition - Apply IP1 to Computer B IP3 IP1 Apply IP1 to Computer B:

1. Change to IP1 on Computer B

2. Reboot Computer B to apply the IP1 address and

update the DNS

IP2 is now released and will no longer be used.

5
. Production on new system IP3 IP1 Computer A remains as a reference until production is
verified on new Computer B

6
. Old system decommissioned IP1 The old Computer A is decommissioned. IP3 is by that
released and will no longer be used.

See also

• section A.1 Network name transition principles

• section 3.2 Planning the transition of network names and IP addresses

A.3 Best practice for network names

Best practice when it comes to network names is to use separate network names for computers and Sectra
PACS components. With this mindset it becomes much easier to extend or modify the system in the
future. As a component always is addressed with a component unique network name, moving the
component to new host or introducing load balancing becomes much easier. If the network name of the
computer is used instead, and the component is moved, all instances accessing the moved component
must be reconfigured to use the new network name. See also section A.1 Network name transition
principles.

The tables below provide an overview of the network names that are likely to be used in a system running
Sectra PACS. Each network name should be associated with either an IP address or be a DNS Alias
associated with another network name.

Sectra PACS, Version 19.1.8, May 2017 Handling network names and IP addresses 41
Table A.2 Network names for physical or virtual hosts

Host Network name example Comment

CORE cluster - Node 1 MyClusterNode1.MyDomain.com The first node in a failover cluster.

CORE cluster - Node 2 MyClusterNode2.MyDomain.com The second node in a failover cluster.

CORE cluster - The cluster service MyCluster.MyDomain.com A Windows failover cluster require a separate network
name for the cluster service.

Application server 1 MyAppNode1.MyDomain.com The first node in a load balancing setup.

Application server 2 MyAppNode2.MyDomain.com The second node in a load balancing setup.

Application server 3 MyAppNode3.MyDomain.com Could be a separate application server located at a

satellite site.

Table A.3 Network names for Sectra PACS Core components

Sectra PACS component Network name example Comment

WISE MyWiseHost.MyDomain.com Used when accessing WISE services, like the WISE
server, the WISE Database or WISE/tools.

ImageServer/s MyFirstISsHost.MyDomain.com Used when accessing ImageServer/s services like the

DICOM Storage SCP or DICOM Q/R SCP, but also to
access shares of images.

ImageServer/s MySecondISsHost.MyDomain.com There might be more than one ImageServer/s.

ImageServer/fs MyISfsHost.MyDomain.com The archive host, running the ImageServer/fs service.

If the archive file system is provided by an external file

server, then the network name of the external file
server must also be known.

ImageServer/xd MyISxdHost.MyDomain.com When an external DICOM archive is used.

A separate name for the ImageServer/xd archive host

is not required as the recommendation is to always
run the ImageServer/xd service on the WISE host.

Control Tower MyControlTowerHost.MyDomain.com Used when accessing Control Tower.

CD/DVD Production Center MyCdDvdCenterHost.MyDomain.com Used when accessing CD/DVD Production Center.

Sectra PACS, Version 19.1.8, May 2017 Handling network names and IP addresses 42
Table A.4 Network names for Sectra Healthcare System component

Sectra Healthcare System Network name example Comment

component

Sectra Healthcare Database - SHDB MyShdbHost.MyDomain.com Used when accessing the SQL Server database engine
hosting the Sectra Healthcare Database and the Sectra
Deployment Database.

Sectra Healthcare Server - SHS MyShsHost.MyDomain.com The virtual network name for the Sectra Healthcare
Server services. This is the network name used by any
user or service connecting to the Sectra Healthcare
Server.

This network name might represent a load balanced

IP address distributing the calls to one or more hosts
running the Sectra Healthcare Server services.

Sectra Satellite Server - SSS MySatellite1Host.MyDomain.com The virtual network name for one group of Sectra
Satellite Server services. It is used by users and the
Sectra Healthcare Server services.

This network name might represent a load balanced

IP address distributing the calls to one or more hosts
running the Sectra Satellite Server services.

Sectra Satellite Server - SSS MySatellite2Host.MyDomain.com There might be more than one group of Sectra Satellite
Servers.

Sectra Deployment Server MyDeplServerHost.MyDomain.com The virtual network name for the Sectra Deployment
Server services. Used by Sectra Deployment Agents.

Sectra PACS, Version 19.1.8, May 2017 Handling network names and IP addresses 43
 B Handling storage

The following topics are included in this appendix:

■ Storage transition principles

■ Keeping the existing storage

■ Using SAN mirroring

■ Using file copying

■ Removing an obsolete base folder

B.1 Storage transition principles

This is an outline of the principles for how to perform the transition of storage during a transition of
Sectra PACS to new hardware. This applies to Sectra PACS databases, ImageServer/s and ImageServer/fs.

If possible, keeping the existing storage or utilizing SAN mirroring are the preferred principles. However,
since both these depends on the storage solution, this document describes the more general but perhaps
less effective method of file copying.

This document assumes that new storage is available for Sectra PACS database file systems and for
ImageServer/s file systems. The file systems of ImageServer/fs are assumed to be moved as they are, or
that they are provided by an external file share not affected by the hardware transition.

Principle Benefits Drawbacks

Keeping the existing storage • No data needs to copied • Requires temporary storage to be able
to prepare the new system
During the transition, the existing storage
is dismounted from the current system and • Critical re-connections of the storage
mounted to the new system during the transition event

See section B.2 Keeping the existing storage

Replacing the existing storage - using • Efficient data transfer • Additional temporary storage might be
SAN mirroring required in order to prepare the new
• It works seamlessly with very little
system
SAN mirroring is an option from the SAN performance impact to the running
Supplier. The new disks are configured and production system • The SAN must support it
connected to the new hardware. The SAN
then replicates every change block by block • It can be done in advance, with a last • SAN knowledge and work required
synchronization when performing the
between the disks.
transition
See section B.3 Using SAN mirroring
• Well suited for static file systems like
the ImageServer/fs file systems

Sectra PACS, Version 19.1.8, May 2017 Handling storage 44

 Principle Benefits Drawbacks

Replacing the existing storage - using • Independent of storage solution • Takes considerable amount of time
file copying

File copy is basically a file by file copy from

old disks to new disks

See section B.4 Using file copying

See also

• section 6.4 Synchronizing ImageServer/s storage

• section 6.10.1 Synchronizing ImageServer/fs storage

B.2 Keeping the existing storage

Tip: To keep track of the disk volumes, create a text file on each disk volume and name it according to the
drive letter and usage it had before the move, for example Disk_H_(ImageServerS).txt

Important: Take great care when presenting the file systems to the new failover cluster. Work with only one node
at a time. Accessing the file systems from different nodes may lead damaged file systems, requiring
time consuming disk checking.

B.3 Using SAN mirroring

Contact the SAN supplier for options regarding this work.

B.4 Using file copying

As the amount of image data stored in Sectra PACS is large, as well as constantly changing (at least for
ImageServer/s), the copying must run continuously.

To aid this work the Windows command tool robocopy.exe is recommended. It is included in Windows
Server. This utility has the built in ability to pick up where it left if the copy job was interrupted. It also
has functionality to act as a mirroring tool. See:

• Robocopy1 (Microsoft's Command-line Reference)

• Robocopy and a Few Examples2 (Microsoft TechNet Article)

When performing a transition of Sectra PACS, consider the following commands:

C:\> robocopy <source> <destination> /e /sec /r:0 /dcopy:t /np /log+:<logfile>

C:\> robocopy <source> <destination> /mir /r:0 /dcopy:t /np /log+:<logfile>

1
http://technet.microsoft.com/en-us/library/cc733145(v=WS.10).aspx
2
http://social.technet.microsoft.com/wiki/contents/articles/robocopy-and-a-few-examples.aspx

Sectra PACS, Version 19.1.8, May 2017 Handling storage 45

 <source> Specifies the path to the source directory.

<destination> Specifies the path to the destination directory.

/e Copy subdirectories, including empty directories.

/sec Copies files with security information. Can be slow in certain cases. If the proper
permissions is set on the destination folder before the copy, this is not needed.

/r:0 Specifies the number of retries on failed copies. 0 means no retries. Keep a very close
eye on the log files if this option is used so that no files will be missing on the target
system.

/dcopy:t Copy directory timestamps.

/mir To mirror a directory tree. If the destination directory exists, the destination directory
security settings are overwritten. An alternative to /mir without copying security
information is /e /purge.

/np No progress - do not display percentage copied on each file. Without this the logs
will be very large and the copy will be slower.

/log+:<logfile> Writes the status output to the log file. If the file exists, the output will be appended.
Use a file name containing both date and time for easy follow up.

Create scripts for copying the base folders. Use for example one script for each file system on the
originating system.

Start running the scripts well in advance to the transition to get the first copy of the short term storage
over to the new system. Then repeat the mirroring jobs as often as possible, like once each day or every
other day leading up to the transition. This ensures that the mirror is kept in sync and it will be much
quicker to do the final synchronization during the downtime. Keep track of the time each synchronization
takes to be prepared of how long it will take during downtime.

Since the copying is done between Windows machines it can have an impact network bandwidth. Make
sure the customer is aware of this and tolerant to any degraded performance during the copy jobs is run.

This is an example of a powershell script used during migration where S: is mapped to the old system.
The date command is in the script to record the progress during the copy:
date
robocopy S:\ds1\CR10 i:\folders_m1\CR10 /MIR /Log+:I:\migration_logs\ds1\CR10.log /NP /DCOPY:T
date
robocopy S:\ds1\CT10 i:\folders_m1\CT10 /MIR /Log+:I:\migration_logs\ds1\CT10.log /NP /DCOPY:T
date
robocopy S:\ds1\MG10 i:\folders_m1\MG10 /MIR /Log+:I:\migration_logs\ds1\MG10.log /NP /DCOPY:T
date
robocopy S:\ds1\MG11 i:\folders_m1\MG11 /MIR /Log+:I:\migration_logs\ds1\MG11.log /NP /DCOPY:T
date
robocopy S:\ds1\MG12 i:\folders_m1\MG12 /MIR /Log+:I:\migration_logs\ds1\MG12.log /NP /DCOPY:T
date
robocopy S:\ds1\NM10 i:\folders_m1\NM10 /MIR /Log+:I:\migration_logs\ds1\NM10.log /NP /DCOPY:T
date

B.5 Removing an obsolete base folder

If a base folder has become obsolete and will not be used in the new system, it should be removed.

Sectra PACS, Version 19.1.8, May 2017 Handling storage 46

 To remove an empty base folder

1. View the base folder in the WISE Database. The base folders were listed in section 5.1.1 Identifying
ImageServer/s base folders.

C:\> wdump –i <bf_id> bf

2. Check that no failed archive jobs exist (that may have copies of not yet filed examinations in the base
folder directory). Use one of the following:

• The Queue Window in IDS7

• Type the following command in a command window on the existing WISE host. There should
be no failed jobs.

C:\> is_client get_archive_queue |more

3. Check that the base folder is empty. The <bf_id> is the unique ID of the base folder. The response
should be “No match”.

C:\> wdump rf <bf_id>

4. Check that the base folder directory is empty. The location listed in the first step above gives the
location of the base folder directory.

5. Remove the base folder in the WISE Database. Be sure that you type the correct <bf_id>, since
there will not be any confirmation before the base folder is removed (it is however not possible to
remove a non-empty base folder).

C:\> wrm bf <bf_id>

6. Remove the base folder directory from the ImageServer/s file system.

Sectra PACS, Version 19.1.8, May 2017 Handling storage 47

 C Handling registry settings

The following topics are included in this appendix:

■ Exporting registry keys

■ Adjusting the exported registry files

■ Importing registry keys

Some engineers prefer to copy the Sectra registry settings from the old system to the new environment
before performing the transition. By doing so, the installation programs will apply the same settings as
in the existing system.

In most cases the registry changes are limited which makes this method more costly than beneficial.
However, there might be situations when it still is useful.

C.1 Exporting registry keys

This will export the registry keys for Sectra PACS Core servers.

Export registry keys

1. Open Regedit.exe

2. Browse to the Sectra key.

On a 32-bit system: HKEY_LOCAL_MACHINE\SOFTWARE\Sectra

On a 64-bit system: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Sectra

3. For each of the following sub-keys found, right click the key and select Export. Name the registry
export file according to the host from which it is exported.

• Sectra\Common

• Sectra\ImageServer

• Sectra\ImageServerS

• Sectra\WISE

4. Repeat this for all Sectra PACS Core hosts in the existing system.

Sectra PACS, Version 19.1.8, May 2017 Handling registry settings 48

 C.2 Adjusting the exported registry files
As the Sectra PACS services runs as 32-bit services on 64-bit operating systems, care must be taken to
update the paths both for the configuration files as well as the registry settings when moving from
Windows 32-bit to Windows 64-bit.

To adjust registry settings

1. Edit the registry files exported in section C.1 Exporting registry keys, one by one. Use for example
Notepad.exe.

2. Adjust all file paths. Search and replace all occurrences of \\Program Files\\ with \\Program
Files (x86)\\.

3. Adjust all registry key paths. Search and replace all occurrences of
HKEY_LOCAL_MACHINE\SOFTWARE\Sectra with
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Sectra.

4. If included, change the following registry settings:

Table C.1 [...\Sectra\ImageServer\Environment]

Key New value

WISE_HOST Change to the temporary hostname of the new WISE host.

Table C.2 [...\Sectra\ImageServerS\Environment]

Key New value

WISE_HOST Change to the temporary hostname of the new WISE host.

IMAGESERVER_S_HOST Change to the temporary hostname of the new ImageServer/s host.

Table C.3 [...\Sectra\WISE\Environment]

Key New value

WISE_HOST Change to the temporary hostname of the new WISE host.

5. Save the modified file and repeat the procedure for all exported registry files.

C.3 Importing registry keys

Import registry file to a failover cluster

1. Log on to the first node in the new failover cluster as a local administrator5.

2. Double click the adjusted registry file (*.reg from section C.2 Adjusting the exported registry files)
and answer yes to the import confirmations.

5
A local user or a domain user that is a member of the group Administrators on the local computer.

Sectra PACS, Version 19.1.8, May 2017 Handling registry settings 49

 3. Start regedit.exe and traverse down to the Sectra-hive. Open all keys to confirm that the settings
have been imported without problems.

4. Make sure paths to configuration files points at the shared disk storage, and not the local system
disks on the cluster node.

5. Export the Sectra registry settings from the first node, and import them on the second node.

If there are additional Sectra PACS Core hosts in the new system, import the registry file on them as
well.

Import registry file to a single server

1. Log on to one of the Sectra PACS Core host in the new system as a local administrator6.

2. Double click the adjusted registry file (*.reg from section C.2 Adjusting the exported registry files)
and answer yes to the import confirmations.

3. Start regedit.exe and traverse down to the Sectra-hive. Open all keys to confirm that the settings
have been imported without problems.

4. Repeat on additional Sectra PACS Core hosts in the new system.

6
A local user or a domain user that is a member of the group Administrators on the local computer.

Sectra PACS, Version 19.1.8, May 2017 Handling registry settings 50

 R
Index related documents, 1
robocopy, 45

S
safety regulations, 2
A SAN, 45
address, 39
scp, 20
alias, 41
Sectra Core, 1
application server, 41
Sectra Workstation, 1
attach, 27
share, 11
autofiler, 20
SHDB1, 27
SQL Server
B management studio, 27
base folder, 11
bf, 11 storage, 20, 44
area network (see SAN)
C
copy T
file, 45 thumbnail image, 11
tn, 11
D transition targets, ii
database, 27
detach, 27 W
dicom, 20 WISE
dns, 41 database instance, 27
domain name, 41

F
file copy, 45
file system
block size, 11

H
hostname (see network name)

I
image, 11
base folder, 11
thumbnail, 11
intended use, 1
ip address, 39
transition, 40

M
mirroring, 45

N
network name, 39
best practice, 41
transition, 40

Q
qr, 20
query/retrieve, 20

Sectra PACS, Version 19.1.8, May 2017 Index 51

LABEL
Product Sectra Workstation

Model IDS7

Version 19.1

UDI (01)07350092810036(8012)19.1

Manufacturer Sectra AB
Teknikringen 20
SE-58330 Linköping
Sweden
www.sectra.com

Contact www.sectra.com/medical/contact/support/

0434

Regulatory Clearance Statement

The quality system of Sectra AB [Sectra] conforms to ISO 9001, ISO 13485 and ISO 27001. All Sectra medical devices
have obtained regulatory clearance for those markets where Sectra sells and deploys its devices, e.g. EEA, USA, Canada,
Australia. For further regulatory information please contact Sectra.

Disclaimer
Sectra AB is not responsible for problems caused by changes in the operating characteristics of the computer hardware or
operating system, which are made after the delivery of the software, or for problems that occur as a result of the use of
Sectra software in conjunction with non-Sectra software other than the software explicitly covered in this documentation.
For a complete description of warranty, refer to the End User License Agreement supplied with the Sectra product.
Trademark and Patent Disclaimer
Sectra, Sectra Imtec and the Sectra logotype, are registered trademarks of Sectra AB. FIMAG and Image Exchange Portal
are registered trademarks of Burnbank Systems Ltd in the UK. IDS7, Sectra BizTrack, Sectra CloudFlex, Sectra DoseTrack,
Sectra IEP, Sectra Image Central, Sectra Image Lab, Sectra LiteView, Sectra UniView, Sectra One Connect, Sectra Open
Archive, Sectra VNA, Sectra UserInfluence, and WISE are trademarks of Sectra Imaging IT Solutions AB. Sectra Preop
Online and Sectra OneScreen are trademarks of Sectra AB. RxEye is a registered trademark of RxEye AB.

Windows is a registered trademark of Microsoft Corporation in the United States and other countries. Mac, Safari, and iPad
are registered trademarks of Apple Inc. in the United States and other countries. All other names/products by ® or ™ are
registered trademarks of the respective manufacturer.

The intellectual property of Sectra includes the following patents: U.S. patents 6,005,917; 6,226,393; 6,411,729;
6,763,257; 7,162,623; 7,532,214; 7,660,461; 7,689,539; 7,830,381; 7,936,930; 7,940,270; 8,131,033; 8,295,620;
8,693,752; 8,880,143; 9,053,574; 9,146,674; 9,265,472; 9,412,162. Japanese patent 3646122. European patents
0818971; 1046374; 2512341. Swedish patents 0203545; 0300951. Patents Pending in the U.S. and other countries.

Copyright and Legal Statement

© Sectra AB, Sweden, 2017

All rights are reserved. Reproduction or transmission in whole or part, in any form or by any means, electronic, mechanical
or otherwise, is prohibited without written consent of the copyright owner.

Copyrights and all other proprietary rights in any software and related documentation ("Software") made available to you
rest exclusively with Sectra AB. No title or ownership in the Software is conferred to you. Use of the Software is subject to
the end user license conditions as are available on request.

To the maximum extent permitted by law, you shall not decompile and/or reverse engineer the software or any part thereof.

Sectra AB
Teknikringen 20
SE-58330 Linköping
Sweden
Phone: +46 13 23 52 00
E-mail: info@sectra.se

For other regions please visit www.sectra.com/medical