9
1 © Nokia Siemens Networks Presentation / Author / Date For internal use RNCFLM Safecopying

11_Safecopying

  • Upload
    kamel

  • View
    6

  • Download
    2

Embed Size (px)

Citation preview

Page 1: 11_Safecopying

1 © Nokia Siemens Networks Presentation / Author / DateFor internal use

RNCFLMSafecopying

Page 2: 11_Safecopying

2 © Nokia Siemens Networks Presentation / Author / DateFor internal use

At the end of this module, you will be able to:

Make a Fallback copy of current BU software buildVerify fallback build

Objectives

Page 3: 11_Safecopying

3 © Nokia Siemens Networks Presentation / Author / DateFor internal use

Two types of safecopying:Fallback copyingBackup copying

Safecopying

Page 4: 11_Safecopying

4 © Nokia Siemens Networks Presentation / Author / DateFor internal use

Two ways available:Copy the whole BU SW build to a new FB directoryUpdate only the files from BU to FB

Fallback Copying

Page 5: 11_Safecopying

5 © Nokia Siemens Networks Presentation / Author / DateFor internal use

Check if WDU in OMU is in normal WO (IHI). The WDU in the active OMU should be in normal working state• ZIHI:OMU,<OMU index>:WDU,<index of the WDU>;

Check that there is enough free space available for a fallback build on the OMU hard disks (WQO)• ZWQO:EX;

Check if BU build is the default software build (WQO)• ZWQO:CR;

Ensure that all computer units are in the normal WO (USI)• ZUSI:::FULL;

Before Fallback Copying

Page 6: 11_Safecopying

6 © Nokia Siemens Networks Presentation / Author / DateFor internal use

Fallback Copying

Three fallback copying alternatives:

Copy all files to a fallback build (WKS)– ZWKS:MODE=FULL,NAME=<FB name>,DIRE=<FB

directory>:<directory>,<directory>,…;

Update a fallback build with changed files (WKS)– ZWKS:MODE=ARCHIVE,:<directory>,<directory>,...;

Update all data files in the fallback build (WKS)– ZWKS:MODE=DATA:<directory>,<directory>,...;

Page 7: 11_Safecopying

7 © Nokia Siemens Networks Presentation / Author / DateFor internal use

Fallback Copying – Full Data

MAIN LEVEL COMMAND <___>

< WKS:MODE=FULL,NAME=CALLOK,DIRE=CALLOK:;

LOADING PROGRAM VERSION 4.3-0

FULL FALLBACK COPYING STARTED

FB-PACKAGE: CALLOK

DIRECTORY: CALLOK

COMMAND EXECUTED AND FUNCTION STARTED

Page 8: 11_Safecopying

8 © Nokia Siemens Networks Presentation / Author / DateFor internal use

Fallback Copying – Data Only

< WKI:;

LOADING PROGRAM VERSION 4.3-0

EXECUTION STARTED

RNC RNC03 2004-03-25 16:03:20 PAGE 1

UNIT: OMU

PHASE:

SENDING DUMPING REQUEST TO DATABASES

DB-INFO: OBJECT_FAMILY NAME DUMPING_STATE

0301 BAIDAT DUMPED

03E3 EQDATA DUMPED

02F0 ARFILE DUMPED

050A RAQUEL STARTED

COMMAND EXECUTED

MAIN LEVEL COMMAND <___>

< WKS:MODE=DATA::;

Page 9: 11_Safecopying

9 © Nokia Siemens Networks Presentation / Author / DateFor internal use

Check its status if you have created a new fallback build (WQO). The status of the new fallback build has to be FB.

• ZWQO:CR;a. Delete the new build directory if the status is UT

(WQD). If the fallback build status is UT , it must not be used. – ZWQD:DIRE=<directory name>:DIRE;

b. Take a new fallback copy (WKS)

Verifying FB Copying