You are on page 1of 7

OPEN INFORMATION

E USER DESCRIPTION 1(7)


Uppgjord — Prepared Datum — Date Rev Dokumentnr — Document no
KI/ERA/LVN/P Anders Holmring 850 75867 2000-07-05 C 68/1553-HSC 103 12 Uen
Godkänd — Approved Kontr — Checked Tillhör/referens — File/reference

ERA/LVN/PC Magnus Bergström

User Description, Backup in Main Store

Copyright

© Ericsson Radio Systems AB 2000. All rights reserved. No part of this document may be
reproduced in any form without the written permission of the copyright holder.

Contents Page

1 Introduction 2

2 Glossary 2
2.1 Concepts 2
2.2 Abbreviations and Acronyms 2

3 Capabilities 2

4 Technical description 3
4.1 General 3
4.2 Memory 4
4.2.1 General 4
4.2.2 Stand-alone TRC Node 5
4.2.3 Stand-alone BSC or combined BSC/TRC Node 5
4.3 Reload time 5
4.4 Main changes in Ericsson GSM system R8/BSS R8.0 6

5 Engineering Guidelines 6

6 Parameters 6
6.1 Main controlling parameters 6
6.2 Additional parameters 6
6.3 Value ranges and defaults values 7

7 References 7

SEIF v2.3,
OPEN INFORMATION
E USER DESCRIPTION 2(7)
Datum — Date Rev Dokumentnr — Document no
2000-07-05 C 68/1553-HSC 103 12 Uen

1 Introduction

Archiving a copy of the software and data is necessary to ensure system


security. Therefore automatic dumps and complete system backup copy are
made. When doing this, certain functions and commands are blocked for use.

When using only the IOG as an interface to the system backup copy, a situation
can occur when there is not possibility to reload, due to no IOG access.

The purpose with BUMS is to reduce the time for reloading and dumping,
which reduces the time when certain commands are blocked.

The system backup copy contains the systems reloading information and is
usually stored on an external file medium, such as magnetic tape or hard
disk. At automatic and manual dump and system restart with reload, data is
transferred to and from the external file medium.

Backup in Main Store (BUMS) means that the whole or parts of the system
backup copy is stored in the Main Store (MS). The backup copy is called
MS-dump. When using BUMS at reload and dump, the MS-dump is
transferred between different memory areas in the MS.

2 Glossary

2.1 Concepts

MW The memory need is expressed with the number of MW. The


designation MW stands for 1 million 16 bit words.

2.2 Abbreviations and Acronyms

The memory can only be changed in one specific size, that is 16 MW.

BUMS Back Up in Main Store

DS Data Store

IO Input/Output

MS Main Store

PS Program Store

RS Reference Store

3 Capabilities

BUMS reduces the time when certain functions and commands are blocked
during output of a complete system backup copy and at automatic DS-dump.
It also reduces the time for reloading of the system backup copy. Reduced
OPEN INFORMATION
E USER DESCRIPTION 3(7)
Datum — Date Rev Dokumentnr — Document no
2000-07-05 C 68/1553-HSC 103 12 Uen

IO dependency is an option that can be achieved with BUMS. If the option is


used, reload and dump can be performed even if IO access is not available.

The memory requirement is raised when using BUMS.

4 Technical description

4.1 General
The system backup copy contains of three parts, the Program Store (PS),
Reference Store (RS) and Data Store (DS). The PS/RS-dump is a copy of the
allocated parts of the program store and the reference store. DS-dump is a
synonym for the small and large data-dumps. The large data-dump is a copy
of the reload-marked variables in the data store. The small data-dump is a
copy of certain variables in DS that are of great importance.

The system backup copy can be stored on an external medium, such as


magnetic tape or hard disk. The whole or parts of the system backup copy can
also be stored in the backup area in the Main Store (MS). This is called BUMS.

In the case where BUMS is used, the system backup copy will be loaded from
Main Store at reload into the memory areas PS, RS and DS.

Not all parts has to be stored in the MS. It is possible to store just the DS or
to store DS and PS/RS. In the case were just DS is stored in the MS, and a
reload take place, the PS/RS will be conditional reloaded. The concept means
that PS/RS are checksummed before reloading. If no fault is found during
the checksumming, PS/RS will not be reloaded.

Table 1 '0' means dump is not stored in the main store, '1' means it is
stored in the main store.

PS/RS DS Action taken at reload


0 0 PS/RS conditional, DS from external medium
0 1 PS/RS conditional, DS from main store
1 1 PS/RS and DS from main store

The DS-dump that is placed in the MS exists in only one version and is
identical to the youngest version of the DS-dump on the external file medium.

After the MS dump has been loaded, it is marked as invalid. This guarantees
that the next reloading will be taken from the external file medium, in the case
there is another reload after a short time. The MS dump is marked invalid for
approximately one hour after a reload.

As an option, reduced IO-dependence secure the possibility to do repeated


reloads from main store as well as automatic output of the DS-dump, when
external medium access is not available. The option can be used only when
BUMS is active.

Activation of the function automatic output of the DS-dump is ordered by


command.
OPEN INFORMATION
E USER DESCRIPTION 4(7)
Datum — Date Rev Dokumentnr — Document no
2000-07-05 C 68/1553-HSC 103 12 Uen

When dumping to an external file medium the reloading is first dumped to the
main store. Thereafter a low priority job is started that copies the reloading
information to the reloading file.

4.2 Memory

4.2.1 General
The APZ memory limits are according to the table below. The maximum
values are specified and possible reduction steps within parenthesis.

Table 2 Memory Limits

APZ type PS DS RS
212 11 32 MW16 (16 MW steps) 192 MW16 (16 MW steps) 1 MW40
212 25 64 MW16 (fixed) 252 MW16 (fixed) 2 MW32
212 20 64 MW16 (fixed) 64 MW16 (64 MW steps) 2 MW32
212 30 96 MW16 (fixed) 512 MW16 (fixed) 32
MW16

The estimate include a 30% safety margin. This will ensure that enough
memory is available for function change and BUMS

Different formulas are given for APZ 212 11 for dependent (or 'tuned') SAE
settings of fixed SAE settings (where all SAEs with a few exceptions are set
high enough from the beginning).

The DS memory usage for APZ 212 11 with dependent SAE setting is
estimated according to the following formula;

BSC DS (MW16) = 1.3 * (82 + 0.022 * cell + 0.022 * TRX)

BSC/TRC DS (MW16) = 1.3 * (82 + 0.022 * cell + 0.022 * TRX + 0.00046


* traffic)

TRC DS (MW16) = 1.3 * ( 75 + 0.00046 * traffic)

The DS memory usage for APZ 212 11 with fixed SAE setting is estimated
according to the following formula;

TRC, BSC, DS (MW16) = 1.3 * (123 + 0.013 * cell


BSC/TRC

cell = number of internal cells.

TRX = number of TRXs.

traffic = the incoming traffic intensity (Erlang) from the connected BSCs.
OPEN INFORMATION
E USER DESCRIPTION 5(7)
Datum — Date Rev Dokumentnr — Document no
2000-07-05 C 68/1553-HSC 103 12 Uen

4.2.2 Stand-alone TRC Node


4.2.2.1 APZ 212 11
The memory requirement for program store (PS) is 32 MW16 (2 memory
boards) when using BUMS, without BUMS 16 MW16 is enough (1 memory
board).

The memory requirement for DS when using dependent SAE settings is 98 to


101 MW16 which requires 7 memory boards (112 MW16).

The memory requirement for DS when using fixed SAE settings is 118 MW16
which requires 8 memory boards (128 MW16).
4.2.2.2 APZ 212 25
The processor can only be equipped with 64 MW16 PS and 252 MW16 DS
which is more than enough to handle the largest TRC.
4.2.2.3 APZ 212 20
The processor can only be equipped with 64 MW16 PS which is more than
enough. The memory requirement for DS/RS requires 3 memory boards
(192 MW16).
4.2.2.4 APZ 212 30
The processor can only be equipped with 96 MW16 PS and 512 MW16 DS
which is more than enough to handle the largest TRC.

4.2.3 Stand-alone BSC or combined BSC/TRC Node


4.2.3.1 APZ 212 11
The memory requirement for program store (PS) is 32 MW16 (2 memory
boards) when using BUMS, without BUMS 16 MW16 is enough (1 memory
board).

The memory requirement for DS when using dependent SAE settings is


107..155 MW16 which requires 6 to 10 memory boards.

The memory requirement for DS when using fixed SAE settings is 160 to 169
MW16 which requires 11 memory boards (176 MW16).
4.2.3.2 APZ 212 25
The processor can only be equipped with 64 MW16 PS and 252 MW16 DS
which is more than enough to handle the largest BSC/TRC.
4.2.3.3 APZ 212 20
The processor can only be equipped with 64 MW16 PS which is more than
enough. The memory requirement for DS/RS requires 3 memory boards
(192 MW16).
4.2.3.4 APZ 212 30
The processor can only be equipped with 96 MW16 PS and 512 MW16 DS
which is more than enough to handle the largest BSC/TRC.

4.3 Reload time


The measurements are not performed yet.
OPEN INFORMATION
E USER DESCRIPTION 6(7)
Datum — Date Rev Dokumentnr — Document no
2000-07-05 C 68/1553-HSC 103 12 Uen

4.4 Main changes in Ericsson GSM system R8/BSS R8.0

APZ 212 20 and APZ 212 30 is introduced.

5 Engineering Guidelines

It is reccommended to turn off BUMS during function change, then the extra
margin of 12 % can be excluded from the calculations in chapter 4.

6 Parameters

6.1 Main controlling parameters

The extent of system backup copy in main store are set with the command
System Functions Backup Main Store Backup Copy Extent Set, SYBMS.

STORE specifies which store that is to be included in the system backup


copy in main store.

IOREDEP specifies if reduced IO dependency on external medium is to be


chosen or not. This is at output of small and large DS dump to main store and
at automatic reloading from main store.

6.2 Additional parameters

An output of the system backup copy to main store is created with command
IO Subsystem Functions File Administration, Initiate, INFII. The following
parameters are used.

FILE is the output file name, maximum 12 characters.

VOL is the volume were the file is to be loaded, maximum 10 characters.

RLENGTH is the record length in number of octets.

EXP is the expansion factor. It tells by how many records a file shall be
expanded when it is full.

SIZE specifies the initial number of records in a file.

TYPE is the file type. It decides how the file shall be accessed.

FCLASS is the file class. It decides whether or not the output file shall have
subfiles.

BLK is the blocking factor. It states the number of records per block.
OPEN INFORMATION
E USER DESCRIPTION 7(7)
Datum — Date Rev Dokumentnr — Document no
2000-07-05 C 68/1553-HSC 103 12 Uen

6.3 Value ranges and defaults values

Table 3 Controlling parameters

Parameter Default Recommended Value range Unit


name value value
STORE NONE ALL ALL, DS, NONE
IOREDEP NO YES YES, NO
FILE 1-12 Characters
VOL 1-10 Characters
RLENGTH 10-4096 0ctets
EXP non-negative number
SIZE non-negative number
TYPE DIR, SEQ
FCLASS SPL SPL, CMP
BLK non-negative number

7 References

1 Function Specification, System backup copy in main store,


3/155 17-ANZ 211 51 Uen
2 Operational Instruction, System backup copy in main store,
Activate and change, 20/154 31-CNZ 211 142 Uen
3 Operational Instruction, System backup copy, Output, 21/154
31-CNZ 211 1075 Uen
4 Operational Instruction, New plant generation, Register, 12/154
31-CNZ 211 1075 Uen

You might also like