NEC Storage ReplicationControl SQL Option User Manual

NEC Storage ReplicationControl
SQL Option User's Manual

© NEC Corporation 2001-2003
No part of the contents of this book may be reproduced or
transmitted in any form without permission of NEC Corporation.
The contents of this book may be modified without notice in the future.

Preface

This manual describes the NEC Storage ReplicationControl SQL Option.
By being applied in combination with a data replication function (DynamicDataReplication or RemoteDataReplication),
this product makes it possible to create a snapshot without stopping operations for the Microsoft® SQL Server 2000
database constructed on the NEC Storage series. This snapshot can be used for backups and parallel processing.
This enables 24-hour a day uninterrupted operation of the Microsoft SQL Server 2000 database.
If an error occurs while backing up the Microsoft SQL Server 2000 database using a data replication function, this product
is indispensable in reco vering data up to the moment of error occurrence by applying the transaction log backup.

This manual is for readers who have basic knowledge of Microsoft SQL Server 2000 as well as experience with backup
recovery. The data replication functions in the NEC Storage series that are used in this manual, are ex plained in the “NEC
Storage Manager Data Replication User’s Manual”.
For information related to Microsoft SQL Server 2000, refer to the Microsoft SQL Server 2000 Books Online.
Refer to the “NEC Storage Manager Manual Guide” (IS901) for the overview of NEC Storage Manager and the related
manuals.

Remarks

1. This manual explains functions implemented by the following program products:

2. This manual is applicable to the program products of the following versions:

• NEC Storage Manager and NEC Storage BaseProduct

• NEC Storage ReplicationControl

• NEC Storage ReplicationControl SQL Option

• NEC Storage DynamicDataReplication

• NEC Storage RemoteDataReplication

• NEC St orage Manager Ver2.1

• NEC Storage BaseProduct Ver2.1

• NEC Storage ReplicationControl Ver2.1

• NEC Storage ReplicationControl SQL Option Ver2.1

The term “iSM” in this text refers to as all the NEC Storage Manager program products.

3.

4.

This manual is based on the Microsoft SQL Server 2000 Enterprise Edition and the Microsoft SQL Server
2000 Standard Edition.
The term “data replication functions” used in this text refers to the functions provided by the NEC Storage

5.
DynamicDataReplication, NEC Storage RemoteDataReplication and NEC Storage ReplicationControl in
the NEC Storage series.
They differ from the “replication functions” provided by Microsoft SQL Server 2000.

6. The term “Microsoft SQL Server 2000” in this text refers to as either Microsoft SQL Server 2000
Enterprise Edition or the Microsoft SQL Server 2000 Standard Edition.
The term “MSCS” in this text refers to the Microsoft Cluster Server.

7.

8.

Trademarks and registered trademarks

• Microsoft® and Windows® are registered trademarks or trademarks of Microsoft Corporation in the

United States and other countries.

• V E RITAS, Backu p Exec, VERITAS Backup Exec, NetBackup, and VERITAS NetBackup are registered

trademarks or trademarks of VERITAS Software Corporation in the Unit ed States and other countries.

• ARCserve is a registered trademark of Computer Associates International, Inc. in the United States.

Other product names and company na mes, etc. are registered trademarks or trademarks of the associated
companies.

The First Edition in January 2002
The Fourth Edition in March 2003

Contents

Chapter 1 Data Replication Overview .............................................................................................................................. 1

1.1 Data Replication.......................................................................................................................................................... 1

1.2 Functions by Product .................................................................................................................................................. 2

1.3 Data Replication Advantages...................................................................................................................................... 4

1.4 Examples of Using Data Replication..........................................................................................................................6

Chapter 2 Overview of NEC Storage ReplicationControl SQL Option......................................................................... 7

2.1 Product Function......................................................................................................................................................... 7

2.2 Advantages of NEC Storage Replication Control SQL Option................................................................................... 7

2.3 System Configuration ................................................................................................................................................. 8

2.4 Examples of Using NEC Storage Repli cationControl SQL Option ......................................................................... 10

2.4.1 Backup .............................................................................................................................................................. 10

2.4.2 Parallel Processing of Search Operations ......................................................................................................... 12

2.4.3 Parallel Processing of Operations Accompanied by Update ............................................................................ 13

Chapter 3 Database System Configuration .................................................................................................................... 14

3.1 Database Configuration ............................................................................................................................................ 14

3.2 Data Replication System Design .............................................................................................................................. 16

3.3 Application to Backup System.................................................................................................................................. 16

3.3.1 Backup Types.................................................................................................................................................... 16

3.4 Concept of Parallel Processing in Other Nodes........................................................................................................ 17

3.4.1 Standby Server..................................................................................................................................................17

3.4.2 Log Distribution ................................................................................................................................................ 17

3.4.3 Server Accompanied by Update ....................................................................................................................... 17

3.4.4 Files Operated in Parallel.................................................................................................................................. 17

3.5 Operation Automatization......................................................................................................................................... 18

Chapter 4 Functions of NEC Storage ReplicationControl SQL Option......................................................................19

4.1 Snapshot Backup....................................................................................................................................................... 19

4.1.1 Snapshot Backup Operations............................................................................................................................20

4.1.2 Snapshot Restore Operations............................................................................................................................21

4.2 Commands ................................................................................................................................................................ 22

4.2.1 Snapshot Backup Command.............................................................................................................................22

4.2.2 Snapshot Restore Command.............................................................................................................................30

4.3 Metafile Handling.....................................................................................................................................................39

4.4 Access Restriction..................................................................................................................................................... 40

Chapter 5 Installation and Setting of NEC Storage Replic ationControl SQL Option...............................................41

5.1 Operating Environment............................................................................................................................................. 41

5.2 Software Installation ................................................................................................................................................. 41

5.3 Software Uninstallation ............................................................................................................................................ 42

5.4 Software Update........................................................................................................................................................ 42

5.5 Setting of NEC Storage ReplicationControl SQL Option ........................................................................................ 42

5.5.1 Replication Volume Preparation....................................................................................................................... 43

5.5.2 Database Creation ............................................................................................................................................. 43

5.5.3 Volume Assignment for Metafiles.................................................................................................................... 43

5.6 Setting of Microsoft SQL Server 2000 ..................................................................................................................... 43

5.6.1 Change of Worker Thread Maximum Number.................................................................................................44

Chapter 6 Operations of NEC Storage ReplicationControl SQL Option.................................................................... 45

6.1 Tape Backup ............................................................................................................................................................. 45

6.1.1 Backup .............................................................................................................................................................. 46

i

6.1.2 Multiple Database Backup................................................................................................................................ 50

6.1.3 Recovery ........................................................................................................................................................... 55

6.1.4 Multiple Database Recovery............................................................................................................................. 60

6.2 Disk Backup .............................................................................................................................................................. 65

6.2.1 Preparation........................................................................................................................................................ 65

6.2.2 Backup .............................................................................................................................................................. 66

6.2.3 Recovery ........................................................................................................................................................... 71

6.3 Parallel Operation on Another Node......................................................................................................................... 75

6.3.1 Operation as Standby Database......................................................................................................................... 75

6.3.2 Log Distribution ................................................................................................................................................ 78

6.3.3 Operation for Server Accompanied by Updat e................................................................................................. 79

Chapter 7 Measures for Errors........................................................................................................................................ 82

7.1 Error Detection Method............................................................................................................................................82

7.2 Errors Related to Database Con figurations............................................................................................................... 82

7.3 Errors Related to Metafile Configurations................................................................................................................ 83

Appendix A Notes.............................................................................................................................................................84

Index......................................................................................................................................................................................... 86

ii

Chapter 1 Data Replication Overview

1

Chapter 1 Data Replication Overview

To centrally manage the enormous amount of information accumulated by business operations and promote its

effective and efficient utilization, it is necessary to have a storage system that realizes a highly advanced

processing feature, large capacity memory and high reliability. The purpose of the data replication function is to

effectively operate this storage system.

1

1

1

.

.

.

1

1

1

D

D

D

a

a

a

t

t

t

a

a

a

R

R

R

e

e

e

p

p

p

l

l

l

i

i

i

c

c

c

a

a

a

t

t

t

i

i

i

o

o

o

n

n

n

Data replication, which is a function that creates a Replication Volume (RV) for a Business Volume

(MV: Master Volume), is stored in the disk array. The RV can achieve synchronization and segregation

from the MV at an arbitrary time. When synchronized, the MV and RV coincide with each other in

terms of their contents; thus, update the MV is instantly reflected in the RV. Through segregation at an

arbitrary time, the MV data can be kept in the RV. By using this RV, backup and searches can be

performed in parallel with on-line services, thus making it possible to increase online operation time.

Figure 1-1 Data Replication

NEC Storage DynamicDataReplication

Synchronization /

Segregation operations

NEC Storage RemoteDataReplication

Master

Volume

(MV)

Replication

Volume

(RV)

Parallel processing

(Backup/Search)

Master operations

(Online)

Business Server

Master

Volume

(MV)

Replication

Volume

(RV)

Chapter 1 Data Replication Overview

2

1

1

1

.

.

.

2

2

2

F

F

F

u

u

u

n

n

n

c

c

c

t

t

t

i

i

i

o

o

o

n

n

n

s

s

s

b

b

b

y

y

y

P

P

P

r

r

r

o

o

o

d

d

d

u

u

u

c

c

c

t

t

t

The following products are available for data replication.

•

NEC Storage DynamicDataReplication (DDR), NEC Storage DynamicDataReplication Ver2 (DDR

Ver2)

Creates an RV in the same disk array.

Supported by the NEC Storage2000/3000/4000 series

•

NEC Storage RemoteDataReplication (RDR), NEC Storage RemoteDataReplication Ver2 (RDR

Ver2)

Creates an RV between different disk arrays.

Supported by the NEC Storage3000/4000 series.

* The replication management function in NEC Storage Manager can be used by introducing NEC

Storage DynamicDataReplication or NEC Storage RemoteDataReplication.

•

NEC Storage ReplicationControl

Operates the replication function. Provides the CLI (Command Line Interface) and the API

(Application Program Interface).

•

NEC Storage ReplicationControl SQL Option

Creates a snapshot without stopping operations on Microsoft SQL Server 2000 database constructed

on the NEC Storage series.

Chapter 1 Data Replication Overview

3

The NEC Storage Manager product provides functions for the administrator to understand the disk

array configuration and operating state of the NEC Storage series with ease. The following products are

available for NEC Storage Manager.

•

NEC Storage Manager

Displays the components of the disk array ,monitors its state and notifies of its failure.

•

NEC Storage PerformanceMonitor

Monitors the performance of the disk array, collects its performance information and displays its

performance on a real-time basis.

Figure 1-2 Functions by Product

NEC Storage ReplicationControl

NEC Storage

DynamicDataReplication

NEC Storage

RemoteDataReplication

NEC Storage Manager Server

NEC Storage Manager Client

NEC Storage ReplicationControl

SQL Option

Chapter 1 Data Replication Overview

4

1

1

1

.

.

.

3

3

3

D

D

D

a

a

a

t

t

t

a

a

a

R

R

R

e

e

e

p

p

p

l

l

l

i

i

i

c

c

c

a

a

a

t

t

t

i

i

i

o

o

o

n

n

n

A

A

A

d

d

d

v

v

v

a

a

a

n

n

n

t

t

t

a

a

a

g

g

g

e

e

e

s

s

s

Data replications have the following advantages.

• Can create replications of a randomly selected MV at an arbitrary time.

−

Can disconnect the RV at an arbitrary time to use for another purpose.

− At the time of resynchronization, synchronization is achieved in a short time by the update

differential management function.

− Up to three RVs can be created.

Figure 1-3 Data Replication operation

• Provides the NEC Storage DynamicDataReplication in a disk array and the NEC Storage

RemoteDataReplication between the disk arrays with the same visibility (operability).

•

Considering reliability, the RAID configuration is adopted for replications as well.

− It is also possible to set a RAID type that differs from the original volume.

• Integrated control by NEC Storage Manager (GUI)

MV

RV

Disconnects replications at an arbitrary time to use
for another purpose.

MV

RV

Reflects the update information
successively.

Co

pying

Disconnect

Creates replications

instantly.

Resynchronized in a

short time through

differential

reflection.

■ Connected ■ Disconnected

U

p

date Update

Update

differential

· Manages the respective update information of

MVs and RVs as update differentials.

· With the update differential management function,

only the updated data is reflected, and the processing time can be
reduced. Since coinciding is processed in parallel with the MV access
in the disk array, it is wait until the differential data is completed.

· It is also possible to resynchronize with (restore to) the status of the RV.

AP AP backup

Resynchronization

Chapter 1 Data Replication Overview

5

NEC Storage Series

NEC Storage Manager

Operation Status Display Window

List Display Window

− Can unify the management of data replications by using NEC Storage Manager. Can display and

set the operational states of data replications through graphical interfaces.

Figure 1-4 Data Replication operation Display

•

Business Link

−

Can perform automatic operations based on linkage between backup software and job scheduling

software by using the CLI for NEC Storage ReplicationControl.

Chapter 1 Data Replication Overview

6

1

1

1

.

.

.

4

4

4

E

E

E

x

x

x

a

a

a

m

m

m

p

p

p

l

l

l

e

e

e

s

s

s

o

o

o

f

f

f

U

U

U

s

s

s

i

i

i

n

n

n

g

g

g

D

D

D

a

a

a

t

t

t

a

a

a

R

R

R

e

e

e

p

p

p

l

l

l

i

i

i

c

c

c

a

a

a

t

t

t

i

i

i

o

o

o

n

n

n

The RV that has been separated from the MV at an arbitrary time by using the data replication function

can be used for other purposes. Because the disconnected RV is independent from the MV, using the

RV will bring the following effects:

• Backup

−

High-speed backup

Online data replications can be created through simple operations. These replications can be

used as backups as they are. As the replications are created in the disk array they do not affect

the online system.

− Backup in parallel with online service

Saving to tapes, etc. can be done from RVs in parallel with MVs, thus making it unnecessary to

worry about online responses during saving.

•

Parallel processing

−

Executes the online and the search work simultaneously.

By making the RV data independent for the search work, the update work and the search work

can be operated without interference, thus solving the problem of competing for disk access and

the resulting deadlock.

− Simultaneous execution of batch processing

Execution time of batch processing can be substantially shortened by using RV.

•

Constructing an evaluation environment

−

Application evaluation

An environment for application evaluation can be constructed with ease by using an RV.

Chapter 2 Overview of NEC Storage ReplicationControl SQL Option

7

Chapter 2 Ov erv iew of NEC Storage

ReplicationControl SQL Option

2

2

2

.

.

.

1

1

1

P

P

P

r

r

r

o

o

o

d

d

d

u

u

u

c

c

c

t

t

t

F

F

F

u

u

u

n

n

n

c

c

c

t

t

t

i

i

i

o

o

o

n

n

n

By applying NEC Storage ReplicationControl SQL Option product in combination with the data

replication (NEC Storage DynamicDataReplication or NEC Storage RemoteDataReplication), the

Microsoft SQL Server 2000 database built on the NEC Storage series is able to create a snapshot

without suspending operations. Also, the snapshot is available in backup or parallel processing.

2

2

2

.

.

.

2

2

2

A

A

A

d

d

d

v

v

v

a

a

a

n

n

n

t

t

t

a

a

a

g

g

g

e

e

e

s

s

s

o

o

o

f

f

f

N

N

N

E

E

E

C

C

C

S

S

S

t

t

t

o

o

o

r

r

r

a

a

a

g

g

g

e

e

e

R

R

R

e

e

e

p

p

p

l

l

l

i

i

i

c

c

c

a

a

a

t

t

t

i

i

i

o

o

o

n

n

n

C

C

C

o

o

o

n

n

n

t

t

t

r

r

r

o

o

o

l

l

l

S

S

S

Q

Q

Q

L

L

L

O

O

O

p

p

p

t

t

t

i

i

i

o

o

o

n

n

n

NEC Storage ReplicationControl SQL Option enables round-the-clock, uninterruptible operation using

the Microsoft SQL Server 2000 database.

If an error occurs while backing up the Microsoft SQL Server 2000 database using a data replication,

NEC Storage ReplicationControl SQL Option is indispensable in recovering the data up to the moment

of error occurrence by applying the transaction log backup.

Chapter 2 Overview of NEC Storage ReplicationControl SQL Option

8

2

2

2

.

.

.

3

3

3

S

S

S

y

y

y

s

s

s

t

t

t

e

e

e

m

m

m

C

C

C

o

o

o

n

n

n

f

f

f

i

i

i

g

g

g

u

u

u

r

r

r

a

a

a

t

t

t

i

i

i

o

o

o

n

n

n

NEC Storage
Re

p

licationControl

NEC Storage
Re

p

licationControl

DB

(MV)

NEC Storage Manager

LAN

NEC Storage Dyna mi cDataReplication

Microsoft
SQL Server20 00

NEC Storage RemoteDataReplication

NEC Storage ReplicationContr ol SQL Option

Figure 2-1 System Configuration

To install and use the data replication, the following hardware devices are required.

(1) Disk array (NEC Storage Series)

The NEC Storage3000/4000 series disk array (the Replication Director is required separately)

equipped with a data replication (NEC Storage DynamicDataReplication; NEC Storage

RemoteDataReplication), or the NEC Storage 2000 series disk array applies.

(2) Management Server

Manages the data replication.

(3) Business Server

Operates data replications.

(4) Backup Server

Backs up data.

Business Server Backup Server

This product

Backup software

Tape drive

Management

Serve

r

Replication operation

NEC Storage series

(RV)

Volume

Replicat ion

Chapter 2 Overview of NEC Storage ReplicationControl SQL Option

9

The software performing data replication consists of the following components.

(1) NEC Storage ReplicationControl SQL Option

Makes it possible to make a snapshot without suspending operation of the Microsoft SQL Server

2000 database.

(2) NEC Storage ReplicationControl

Provides the command that checks the replication operation and state from the business server.

(3) NEC Storage Manager

Provides the function to display the operation status of NEC Storage DynamicDataReplication

and NEC Storage RemoteDataReplication and the pair volume settings. Installing NEC Storage

DynamicDataReplication and NEC Storage RemoteDataReplication makes it possible to use the

replication management function incorporated in the NEC Storage Manager.

(4) NEC Storage DynamicDataReplication

A function that facilitates data replication between the same disk arrays.

(5) NEC Storage RemoteDataReplication

A function that facilitates data replication between the different disk arrays.

The NEC Storage ReplicationControl SQL Option product operates in linkage with either of the

Microsoft software programs below.

(1) Microsoft SQL Server 2000 Enterprise Edition

(2) Microsoft SQL Server 2000 Standard Edition

Chapter 2 Overview of NEC Storage ReplicationControl SQL Option

10

2

2

2

.

.

.

4

4

4

E

E

E

x

x

x

a

a

a

m

m

m

p

p

p

l

l

l

e

e

e

s

s

s

o

o

o

f

f

f

U

U

U

s

s

s

i

i

i

n

n

n

g

g

g

N

N

N

E

E

E

C

C

C

S

S

S

t

t

t

o

o

o

r

r

r

a

a

a

g

g

g

e

e

e

R

R

R

e

e

e

p

p

p

l

l

l

i

i

i

c

c

c

a

a

a

t

t

t

i

i

i

o

o

o

n

n

n

C

C

C

o

o

o

n

n

n

t

t

t

r

r

r

o

o

o

l

l

l

S

S

S

Q

Q

Q

L

L

L

O

O

O

p

p

p

t

t

t

i

i

i

o

o

o

n

n

n

2

2

2

.

.

.

4

4

4

.

.

.

1

1

1

B

B

B

a

a

a

c

c

c

k

k

k

u

u

u

p

p

p

The operational application of making backup copies using an RV is described below.

(1) Backup from an RV to a magnetic tape medium

This is the backing up of an RV for an MV to a magnetic tape medium.

By synchronizing and separating the MV and the RV during the time period when the load on the

business operations that use the Microsoft SQL Server 2000 is lower, it is possible to back up

copies onto magnetic tape media without suspending the operations.

Since backup copies are made from RVs, MVs are not affected.

Figure 2-2 Backup from RVs

(a) During operation, keep the MV and the RV separate.

(b) If the load is lowered, synchronize and separate the MV and the RV.

(c) Execute the backup work concurrently with the business operation by using the separated

RV. After the backup is completed, the separated RV can be used as a disk backup.

Business Server Backup Server

Master

Volume

(MV)

Replication

Volume

(RV)

ProductionTas

k

Connected

Backup

Separated

Tape

Chapter 2 Overview of NEC Storage ReplicationControl SQL Option

11

(2) Using as a disk backup

This refers to the use of an RV as a backup copy of an MV. This can be used as a disk medium

backup without suspending operations because the MV and the RV are synchronized and

separated during the time period when the load on the business operations that use the Microsoft

SQL Server 2000 is lower.

When restoring data from the backup data, it is possible to use backup data even if data from the

RV to the MV is not completely copied. In the event that the data to access is not restored to the

MV, restoration is realized through data access to the RV, thus making it unnecessary for the user

to think about whether to use the MV or the RV.

This makes it becomes possible to substantially reduce the data recovery time.

Figure 2-3 Use of RV as Backup

(a) During operation, keep all MVs and RVs separate.

(b) If the load is lowered, synchronize and separate MV1 and RV1.

(c) Make backup copies by using RV1, RV2 and RV3 in order.

Master

Volume

(MV)

Separate

Connect/Separate

Separate

Separate

Separate

Connect/

Separate

Master

Volume

(MV)

Replication

Volume 1

(RV1)

Replication

Volume 2

(RV2)

Replication

Volume 3

(RV3)

Replication

Volume 1

(RV1)

Replication

Volume 2

(RV2)

Replication

Volume 3

(RV3)

Chapter 2 Overview of NEC Storage ReplicationControl SQL Option

12

2

2

2

.

.

.

4

4

4

.

.

.

2

2

2

P

P

P

a

a

a

r

r

r

a

a

a

l

l

l

l

l

l

e

e

e

l

l

l

P

P

P

r

r

r

o

o

o

c

c

c

e

e

e

s

s

s

s

s

s

i

i

i

n

n

n

g

g

g

o

o

o

f

f

f

S

S

S

e

e

e

a

a

a

r

r

r

c

c

c

h

h

h

O

O

O

p

p

p

e

e

e

r

r

r

a

a

a

t

t

t

i

i

i

o

o

o

n

n

n

s

s

s

By creating an RV of the business operation database, the database can be separated into different

volumes to execute the update work and the search work respectively. This makes it becomes possible

to execute the database search work without affecting the database update work.

The NEC Storage ReplicationControl SQL Option must be installed on the server performing the search

work.

The search work uses the standby database function on the Microsoft SQL Server 2000.

Figure 2-4 Parallel processing of Search Work

(a) When starting search work, the MV and the RV are synchronized and separated.

(b) Hereafter is applying the transaction log backup reflects, the updated part of the business

operation volume.

Master

database

Run as standby

data base

Af

ter the business operation is started

When starting the business operation

Reflecting the

update part

Update

work

Applying the

transaction log

Search

work

Master

Volume

(MV)

Replication

Volume

(RV)

Connect/

separate

Maste

r

Volume

(MV)

Replication

Volume

(RV)

Master

database

Chapter 2 Overview of NEC Storage ReplicationControl SQL Option

13

2

2

2

.

.

.

4

4

4

.

.

.

3

3

3

P

P

P

a

a

a

r

r

r

a

a

a

l

l

l

l

l

l

e

e

e

l

l

l

P

P

P

r

r

r

o

o

o

c

c

c

e

e

e

s

s

s

s

s

s

i

i

i

n

n

n

g

g

g

o

o

o

f

f

f

O

O

O

p

p

p

e

e

e

r

r

r

a

a

a

t

t

t

i

i

i

o

o

o

n

n

n

s

s

s

A

A

A

c

c

c

c

c

c

o

o

o

m

m

m

p

p

p

a

a

a

n

n

n

i

i

i

e

e

e

d

d

d

b

b

b

y

y

y

U

U

U

p

p

p

d

d

d

a

a

a

t

t

t

e

e

e

By creating and separating an RV of the business operation database, the database can be used by other

servers. This is used for constructing test environments.

When constructing an environment, replications of the database can be made without suspending

operations using the Microsoft SQL Server 2000. When the business operations load is lower, the MV

and the RV are synchronized and separated.

Figure 2-5 Parallel processing of Operations Accompanied by Update

(a) During the daytime, keep the MV and the RV separate.

(b) During the nighttime, stop parallel operation, synchronize and separate the MV and the RV.

(c) Execute the operation DB and the replication DB in parallel. (RV being the data of the previous

day)

Reflecting the

updated part

Nig

httime

Data from previous day

Update

work

Connect

Day

time

Search

work

Master

Volume

(MV)

Replication

Volume

(RV)

Business

Volume

(MV)

Master

database

Master

database

Separate

Replication

Volume

(RV)

Chapter 3 Database System Configuration

14

Chapter 3 Database System Configuration

Database configuration and concept of backups for the Microsoft SQL Server 2000 are briefly described below.

For details, refer to the Microsoft SQL Server 2000 Books Online.

3

3

3

.

.

.

1

1

1

D

D

D

a

a

a

t

t

t

a

a

a

b

b

b

a

a

a

s

s

s

e

e

e

C

C

C

o

o

o

n

n

n

f

f

f

i

i

i

g

g

g

u

u

u

r

r

r

a

a

a

t

t

t

i

i

i

o

o

o

n

n

n

The Microsoft SQL Server 2000 database consists of three files; the primary data file, the secondary

data file and the log file. The primary data file and the secondary data file are also simply called “data

file”.

Figure 3-1 Database Configuration

• Primary data file

One database always has one primary data file. As the starting point of the database, the primary

data file points to the locations of the secondary data and log files (File1.mdf in the diagram above).

The file name extension for the primary data file is .mdf.

• Secondary data file

As a data file, the secondary data file sometimes does not exist and sometimes multiple secondary

data files exist (File2.ndf, File3.ndf and File4.ndf).

The extension for the secondary data file is normally .ndf.

• Log file

Refers to the file where the log for recovery is stored. At least one file is required; sometimes, two or

more files also exist (File1.ldf and File2.ldf in the diagram above).

The file name extension for the log file is normally .ldf.

File group 1

File group 2

File1.mdf

File2.ndf

File3.ndf

File4.ndf

File1.ldf

File2.ldf

Data file

Log file

Database

Chapter 3 Database System Configuration

15

• File group

On Microsoft SQL Server 2000, this refers to a labeled aggregate of one or more files. A unit of

assignment or a unit of database management is called a file group.

The default file group is PRIMARY.

Although it is not necessary that file extensions, such as .mdf, .ndf, and .ldf, be used with the Microsoft

SQL Server 2000, those file extensions are useful for identifying file usage.

By backing up the transaction log from the log file when a data error occurs, it is possible to recover

data up to the point of error.

This makes it necessary to allocate the data file and the log file in different logical volumes.

To improve error resistibility, the data file and the log file are allocated to the logical volumes assigned

to different RANK.

For operational purposes, the NEC Storage ReplicationControl SQL Option targets all the files and file

groups included in the database. When specifying MV/RV with the parameters of snapshot

backup/restore commands, specify the MV/RV of all the files included in the database.

The data replication function operates in logical disk units. Therefore, when different database files

exist in a logical disk, all of the databases in the logical disk must be operated at the same time.

Furthermore, the Microsoft SQL Server 2000 controls the connections of users for each instance.

Therefore, it is not possible to refer to database information included in a different instance or

information on the files and file groups contained in the database. The NEC Storage

ReplicationControl SQL Option checks that the specified databases properly correspond to the

operation target logical disks. However, when database files included in different instances exist in

logical disks, it does not check the relationship between the databases and the logical disks. Therefore,

when operating with multiple instances, be sure to specify all necessary databases and logical disks.

The NEC Storage ReplicationControl SQL Option does not specify a static point on other files than

those of database. Place only database files in the backup-target MV.

Chapter 3 Database System Configuration

16

3

3

3

.

.

.

2

2

2

D

D

D

a

a

a

t

t

t

a

a

a

R

R

R

e

e

e

p

p

p

l

l

l

i

i

i

c

c

c

a

a

a

t

t

t

i

i

i

o

o

o

n

n

n

S

S

S

y

y

y

s

s

s

t

t

t

e

e

e

m

m

m

D

D

D

e

e

e

s

s

s

i

i

i

g

g

g

n

n

n

When designing a system by using NEC Storage ReplicationControl SQL Option, it is necessary to

design Microsoft SQL Server 2000’s database as well as NEC Storage’s data replication relations.

For information on designing the data replication system, refer to the “NEC Storage Manager Data

Replication User’s Manual (Installation and Operation Guide for Windows)”.

3

3

3

.

.

.

3

3

3

A

A

A

p

p

p

p

p

p

l

l

l

i

i

i

c

c

c

a

a

a

t

t

t

i

i

i

o

o

o

n

n

n

t

t

t

o

o

o

B

B

B

a

a

a

c

c

c

k

k

k

u

u

u

p

p

p

S

S

S

y

y

y

s

s

s

t

t

t

e

e

e

m

m

m

The concept of using the snapshot backup created by NEC Storage ReplicationControl SQL Option as a

backup to the master operations is described below along with the restoration model for Microsoft SQL

Server 2000 Books Online.

3

3

3

.

.

.

3

3

3

.

.

.

1

1

1

B

B

B

a

a

a

c

c

c

k

k

k

u

u

u

p

p

p

T

T

T

y

y

y

p

p

p

e

e

e

s

s

s

(1) Snapshot backup

Refers to the type of backup used on the NEC Storage ReplicationControl SQL Option.

Functionally the same as the conventional database’s complete backup and file backup, etc., this

type is capable of roll forwarding by using the transaction log backup. In the same manner as

other backups, the snapshot backup and recovery are traced with MSDB.

(2) Database backup

Since the snapshot backup is used, a complete backup of the database is not made.

(3) Database differential backup

Since the snapshot backup is used, a differential backup of the database is basically not made.

(4) Transaction log backup

The database can be restored to the state before the error occurred by combining the transaction

log backup with the snapshot backup.

In order to apply the transaction log after snapshot restoration, specify “norecovery” with the

“-remod” option.

Perform the system database backup or restoration by using the normal backup method or

with NEC Storage ReplicationControl by suspending the business operations of Microsoft SQL Server

2000.

For information on the timing of performing the system database backup, refer to the Microsoft SQL

Server 2000 Books Online.

Chapter 3 Database System Configuration

17

3

3

3

.

.

.

4

4

4

C

C

C

o

o

o

n

n

n

c

c

c

e

e

e

p

p

p

t

t

t

o

o

o

f

f

f

P

P

P

a

a

a

r

r

r

a

a

a

l

l

l

l

l

l

e

e

e

l

l

l

P

P

P

r

r

r

o

o

o

c

c

c

e

e

e

s

s

s

s

s

s

i

i

i

n

n

n

g

g

g

i

i

i

n

n

n

O

O

O

t

t

t

h

h

h

e

e

e

r

r

r

N

N

N

o

o

o

d

d

d

e

e

e

s

s

s

An explanation on using the snapshot backup created by the NEC Storage ReplicationControl SQL

Option for parallel operations on Microsoft SQL Server of other nodes is offered below.

3

3

3

.

.

.

4

4

4

.

.

.

1

1

1

S

S

S

t

t

t

a

a

a

n

n

n

d

d

d

b

b

b

y

y

y

S

S

S

e

e

e

r

r

r

v

v

v

e

e

e

r

r

r

By the snapshot backup, separated database file can be used as a search database by other servers.

The search server must be used as a standby server. For details, refer to the Microsoft SQL Server 2000

Books Online.

In this case, when performing snapshot restoration, specify “-norestore” and then specify “standby” for

the “-remod” option. The database restored through snapshot restoration can be used as the database for

the standby mode.

3

3

3

.

.

.

4

4

4

.

.

.

2

2

2

L

L

L

o

o

o

g

g

g

D

D

D

i

i

i

s

s

s

t

t

t

r

r

r

i

i

i

b

b

b

u

u

u

t

t

t

i

i

i

o

o

o

n

n

n

The database restored as the search database through snapshot restoration can apply backup of

transaction logs updated with the business server in the same manner as the database for the normal

standard mode.

Through this work, data from the search database can be changed to data at the time when the

transaction log was copied as a backup.

3

3

3

.

.

.

4

4

4

.

.

.

3

3

3

S

S

S

e

e

e

r

r

r

v

v

v

e

e

e

r

r

r

A

A

A

c

c

c

c

c

c

o

o

o

m

m

m

p

p

p

a

a

a

n

n

n

i

i

i

e

e

e

d

d

d

b

b

b

y

y

y

U

U

U

p

p

p

d

d

d

a

a

a

t

t

t

e

e

e

Files from the database once disconnected through snapshot backup are used by other servers.

In this case, attach the files of the disconnected database. They can be used in the same manner as the

ordinary database. It is not possible to apply the backup of the transaction log updated by the business

server.

To reflect the data updated by the business server, MV/RV synchronization and separation are required.

3

3

3

.

.

.

4

4

4

.

.

.

4

4

4

F

F

F

i

i

i

l

l

l

e

e

e

s

s

s

O

O

O

p

p

p

e

e

e

r

r

r

a

a

a

t

t

t

e

e

e

d

d

d

i

i

i

n

n

n

P

P

P

a

a

a

r

r

r

a

a

a

l

l

l

l

l

l

e

e

e

l

l

l

When files from the database once disconnected through snapshot backup are operated in parallel

through another node, the files cannot be used as a disk backup.

To use them as a backup, either copying them onto a tape as a backup or use multiple RVs.

Chapter 3 Database System Configuration

18

3

3

3

.

.

.

5

5

5

O

O

O

p

p

p

e

e

e

r

r

r

a

a

a

t

t

t

i

i

i

o

o

o

n

n

n

A

A

A

u

u

u

t

t

t

o

o

o

m

m

m

a

a

a

t

t

t

i

i

i

z

z

z

a

a

a

t

t

t

i

i

i

o

o

o

n

n

n

The tape backup system, which used data replication, requires a linkage operation between the business

operation side and the backup server side. NetBackup is available the backup software provided with

the linkage function between servers. When using ARCserve and BackupExec, job scheduling software

programs are required.

Chapter 4 Functions of NEC Storage ReplicationControl SQL Option

19

Chapter 4 Functions of NEC Storage

ReplicationControl SQL Option

This chapter explains the its operational outline, command operation methods, display of various states, as well as

some notes on the metafile management of the snapshot backup that is a function of the NEC Storage

ReplicationControl SQL Option operating on the business server.

4

4

4

.

.

.

1

1

1

S

S

S

n

n

n

a

a

a

p

p

p

s

s

s

h

h

h

o

o

o

t

t

t

B

B

B

a

a

a

c

c

c

k

k

k

u

u

u

p

p

p

Snapshot backup refers to a function that performs snapshot backup and restoration without suspending

the database by using the functions provided by Microsoft SQL Server 2000 and NEC Storage series

data replication.

The snapshot backup minimizes or eliminates the need for using the server’s resource for backup

purposes.

The snapshot backup is conducted by the following functions:

• I/O freeze function

Freezes the update I/O of Microsoft SQL Server 2000 to specify the static point of the database

during the snapshot backup.

• Creation of metafile

Refers to the file for storing Microsoft SQL Server 2000’s file configuration and transaction log

state information, etc. The file is created during snapshot backup and the information is used for

snapshot restoration.

• Data Replication operation

Separates or connects MVs and RVs of NEC Storage by using the functions of NEC Storage

ReplicationControl.

Moreover, if the update I/O for the backup target database is attempted during the snapshot backup, the

Microsoft SQL Server 2000 freezes the update I/O for all databases included in the instance in which

the backup target database is located. Ending the snapshot backup will automatically release the

control of the update I/O for all databases and resume the update I/O function.

Chapter 4 Functions of NEC Storage ReplicationControl SQL Option

20

4

4

4

.

.

.

1

1

1

.

.

.

1

1

1

S

S

S

n

n

n

a

a

a

p

p

p

s

s

s

h

h

h

o

o

o

t

t

t

B

B

B

a

a

a

c

c

c

k

k

k

u

u

u

p

p

p

O

O

O

p

p

p

e

e

e

r

r

r

a

a

a

t

t

t

i

i

i

o

o

o

n

n

n

s

s

s

The snapshot backup operation includes:

(1) stopping the update I/O of Microsoft SQL Server 2000;

(2) creating metafile;

(3) flushing MV;

(4) separating MV/RV.

Figure 4-1 Operation to Execute Snapshot Backup

Business Server

Metafile

(1) Stopping the database I/O

(2) Creating metafile

(3) Flushing MV
(4) Separating MV/RV

Backup Server

Master Volume (MV) Replication Volume (RV)

Data file Data file

Log file

Log file

Chapter 4 Functions of NEC Storage ReplicationControl SQL Option

21

4

4

4

.

.

.

1

1

1

.

.

.

2

2

2

S

S

S

n

n

n

a

a

a

p

p

p

s

s

s

h

h

h

o

o

o

t

t

t

R

R

R

e

e

e

s

s

s

t

t

t

o

o

o

r

r

r

e

e

e

O

O

O

p

p

p

e

e

e

r

r

r

a

a

a

t

t

t

i

i

i

o

o

o

n

n

n

s

s

s

The snapshot restore operation includes:

(1) acquiring the MV information from the metafile;

(2) unmounting MV;

(3) restoring from RV to MV;

(4) mounting MV;

(5) restoring database.

Figure 4-2 Operation to Execute Snapshot Restoration

(1) Acquiring the MV information

from the metafile

(2) Unmounting MV
(3) Restoring RV/MV
(4) Mounting MV

(5) Restoring database

Business Server

Metafile

Backup Server

Master Volume (MV) Replication Volume (RV)

Data file Data file

Log file

Log file

Chapter 4 Functions of NEC Storage ReplicationControl SQL Option

22

4

4

4

.

.

.

2

2

2

C

C

C

o

o

o

m

m

m

m

m

m

a

a

a

n

n

n

d

d

d

s

s

s

Commands used on the NEC Storage ReplicationControl SQL Option are described below.

Table 4-1 Lists of the NEC Storage ReplicationControl SQL Option Commands

Command name Operation name Description

iSMsql_snapshotbkup

Snapshot backup Backs up database.

iSMsql_snapshotrst

Snapshot restore Restores database from backup.

* Operation rights are required for the users belonging to Administration group.

When using the NEC Storage ReplicationControl SQL Option’s commands, it is necessary to specify a

configuration so that the NEC Storage ReplicationControl directly issues the replication operation I/O

issuing path to the disk array.

For explanation about commands and operation settings, refer to the “NEC Storage Data Replication

Command Reference”.

4

4

4

.

.

.

2

2

2

.

.

.

1

1

1

S

S

S

n

n

n

a

a

a

p

p

p

s

s

s

h

h

h

o

o

o

t

t

t

B

B

B

a

a

a

c

c

c

k

k

k

u

u

u

p

p

p

C

C

C

o

o

o

m

m

m

m

m

m

a

a

a

n

n

n

d

d

d

Snapshot backup uses the iSMsql_snapshotbkup command.

By instructing Microsoft SQL Server 2000, iSMsql_snapshotbkup command freezes the update I/O,

creates the metafile for the specified path and records the database configuration and the transaction log

state. Thereafter, it separates the MV and the RV where the specified database is stored.

After the separation is completed, the command sends the completion instruction to Microsoft SQL

Server 2000, which in turn creates the history in the MSDB.

The following options can be specified for the iSMsql_snapshotbkup command regarding snapshot

backup operation.

(1) Specifying the database name (-db dbname or –dbfile dbfile_name)

A name recognized by Microsoft SQL Server 2000 can be specified as the database name.

When simultaneously performing snapshot backups on multiple databases, specify multiple

database names in the database operation file.

For details of the database operation file, refer to the “NEC Storage Manager Data Replication

Command Reference”.

(2) Specifying the metafile (-metafile metafile_name or –metafolder

metafolder_name)

For the metafile, a metafile name created during snapshot backup can be specified.

When simultaneously performing snapshot backups on multiple databases, specify the name of the

folder that stores metafiles. Under the specified folder name, multiple metafiles that correspond

to each database on which a snapshot backup has been performed are created. The name of the

Chapter 4 Functions of NEC Storage ReplicationControl SQL Option

23

metafiles is as follows:

Database name_metafile.dat

The metafile can be created for the shared disk, MV or local disk.

However, the data file for the database specified with -db or –dbfile and the volume in which the

log file is stored cannot be specified. This is to identify the database to be restored from the

metafile content during recovery.

•

To create metafile on the shared disk This is used when saving metadata on the backup

server side. It eases metafile saving.

• To create metafile on the MV This is used when the shared disk cannot be used. It

is necessary when separating after performing

snapshot backup.

To use the metafile information when executing

snapshot restoration, it is necessary to restore

metafile before executing the snapshot restoration.

• To create metafile on the local disk This is used when saving metadata on the local disk.

(3) Specifying the pair volume

Specify the MV volume and the RV volume.

•

Specifying the MV (-mv volume -mvflg mv_flg): Specifies the MV volume and volume

type.

• Specifying the RV (-rv volume -rvflg rv_flg): Specifies the RV volume and volume type.

When specifying multiple pair volumes, describe the specification (-file file_name) in the

replication operation file.

For information on the volume type and replication operation file, refer to the “NEC Storage

Manager Data Replication Command Reference”.

When specifying a drive name with regard to a volume consisting of multiple partitions, all the

partitions become included in the operation by specifying the drive name for any of the partitions.

However, this functions only when the option that allows multiple partitions to be specified is

enabled. For information on setting options, refer to the “NEC Storage Manager Data

Replication Command Reference”.

(4) Specifying RV access restriction after snapshot backup (-rvacc)

Access restriction on the RV after snapshot backup can be specified.

• Read Only (-rvacc ro): Access to RV is possible only for reference purposes.

• Read/Write (-rvacc rw): Access to RV is possible for reference and update purposes.

Chapter 4 Functions of NEC Storage ReplicationControl SQL Option

24

Unless well versed in OS and file system operations for Windows, Read Only (-rvacc ro) should

not be specified for the RV access restriction. For details, refer to 3.6 “RV Access Restrictions

Setting” of the “NEC Storage Manager Data Replication User’s Manual (Installation and

Operation Guide for Windows)”.

(5) Specifying waiting for snapshot backup completion (-wait/-nowait)

With snapshot backup, the program can be made to wait for the end of the command after

executing the separation.

• Wait specified (-wait [second]): When the value is specified to “second”, the disk array’s

monitoring time interval becomes the specified time. The

specifiable value is 1 to 30 seconds (integer number). When

the value is omitted, 5 seconds is set.

• No wait (-nowait): The command is ended only after specifying snapshot

backup start. It is not made to wait for separation

completion.

The end of separation is checked by the iSMrc_query

command.

(6) Canceling the MV/RV state check (-nocheck)

Performs snapshot backup without checking the MV/RV state.

Normally, the snapshot backup command is not operated unless synchronization between MV and

RV is completed. Specifying “-nocheck” makes it possible to perform snapshot backup even when

MV-RV synchronization is not completed.

This is specified when the MV-RV synchronization time is unclear but immediate backup is

necessary.

(7) Specifying the time when the RV becomes available (-rvuse)

The snapshot backup function makes it possible to specify the time at which the RV becomes

available after separation has been performed. This specification is applicable when performing

a snapshot backup without checking the state of the MV/RV.

•

Normal separation (-rvuse complete): Allows the RV to be used after separation has

been performed and the differential reflection

(synchronization) of the MV and the RV has

been completed.

• Immediate separation (-rvuse immediate): Makes the immediate use of the RV possible

while the differential reflection

(synchronization) of the MV and the RV is being

performed after separation has been performed.

Chapter 4 Functions of NEC Storage ReplicationControl SQL Option

25

• Using the default setting (-rvuse default): Uses the setting stored in the replication

operation option setting file.

This function can be used only when “NEC Storage DynamicDataReplication Ver2” has been

installed in the disk array. For details about this function, refer to the “NEC Storage Manager

Data Replication User’s Manual (Function Guide)” and “NEC Storage Manager Data Replication

Command Reference”.

(8) Specifying the user ID/password

The user ID/password to be connected to Microsoft SQL Server 2000 can be specified.

When omitted, the user name and password for the Windows login account is used. No entry in

the password field is recognized as “no password”.

•

Specifying from the command line (-uid userid -pass password):

Specifies the user ID/password from the command

line.

• Specifying from the keyboard (-input): When executing the command, interactively enter

a user ID and password by using a keyboard.

“User ID:” Enter a user ID.

“Password:” Enter a password.

Those specifications can be described in the database operation file.

For details of the database operation file, refer to the “NEC Storage Manager Data Replication

Command Reference”.

(9) Specifying the instance name (-server instance_name)

The computer name and the instance name when connecting to a labeled instance can be specified.

They can be specified in the format of computer_name\instance_name.

When omitted, the connection is made to the default instance.

The computer name must be either a local computer name, or a virtual computer name in the

MSCS (Microsoft Cluster Server) environment.

Those specifications can be described in the database operation file.

For details of the database operation file, refer to the “NEC Storage Manager Data Replication

Command Reference”.

The iSMsql_snapshotbkup command is used to output messages to each database on which a snapshot

backup is performed when the snapshot backup operation starts and ends as well as when the

flush/separate operation starts and ends.

Chapter 4 Functions of NEC Storage ReplicationControl SQL Option

26

• Start message

SnapshotBackup Start YYYY/MM/DD hh:mm:ss

DataBase db_name
MV:physical-disk-no ld_name type

Volume_name
Path

RV:physical-disk-no ld_name type

Volume_name
Path

•

End message

SnapshotBackup Normal End YYYY/MM/DD hh:mm:ss

DataBase db_name
MV:physical-disk-no ld_name type

Volume_name
Path

RV:physical-disk-no ld_name type

Volume_name
Path

• Starting flush operation

Flush Start YYYY/MM/DD hh:mm:ss

•

Ending flush operation

Flush Normal End YYYY/MM/DD hh:mm:ss

•

Starting separation operation

Separate Start YYYY/MM/DD hh:mm:ss

•

Ending separation operation

Separate Normal End YYYY/MM/DD hh:mm:ss

Description of message

YYYY/MM/DD hh:mm:ss Start/End time (YY/MM/DD hh:mm:ss)
physical-disk-no PD number
Path Drive name / NTFS folder name
Volume_name MountPoint volume name
ld_name LD name
type OS Type
db_name Database name

•

Message during execution

Separating.....

Only when specified by “-wait” is specified is this output until separation is completed. “.” is

dynamically updated.

Chapter 4 Functions of NEC Storage ReplicationControl SQL Option

27

SnapshotBackup Start YYYY/MM/DD hh:mm:ss

DataBase db_name
MV:physical-disk-no ld_name type

Volume_name
Path

RV:physical-disk-no ld_name type

Volume_name

Path
Flush Start YYYY/MM/DD hh:mm:ss
Flush Normal End YYYY/MM/DD hh:mm:ss
Separate Start YYYY/MM/DD hh:mm:ss

Separating.....

Separate Normal End YYYY/MM/DD hh:mm:ss
SnapshotBackup Normal End YYYY/MM/DD hh:mm:ss

DataBase db_name
MV:physical-disk-no ld_name type

Volume_name

Path

RV:physical-disk-no ld_name type

Volume_name

Path

Execution Conditions

When performing snapshot backup, it is necessary to meet the following conditions.

(1) MVs and RVs targeted for operation should be set as a pair.

(2) The pair targeted for operation should be principally during restoration synchronization or

replication.

(3) The Copy Control State of the pair targeted for operation should be in the foreground copy status.

* To separate the pairs in the background copy state, it is necessary to perform the copy restart

operation to place the pairs in the foreground copy status.

(4) The disk array in which the specified MV and RV are stored should not be in the freeze state.

(5) The MV targeted for operation should be registered in the volume correspondence table.

(6) The volume of MVs and RVs targeted for operation should be a basic volume.

(Specifying a volume using dynamic volume function is not allowed.)

(7) The MV must exist in the disk array under the own host control.

(8) The data file and the log file included in the database should exist in the target MV.

(9) When specifying a database name with the -db option, only one database must exist in the target MV.

(10) When specifying a database name with the -dbfile option, all databases that exist in the target MV

must be specified.

(11) The metafile-specified location should not be the volume where the data file and log file of the

database are stored.

(12) The disk where the metafile is created should have unused space.

Figure 4-3 shows the execution conditions of the snapshot backup ((1) to (12) in the diagram refer to

the numbers above).

Chapter 4 Functions of NEC Storage ReplicationControl SQL Option

28

Figure 4-3 Execution Conditions of Snapshot Backup

Shared disk

Pairs targeted for operation

MV
data

RV

data

(1) Should be set as a pair.
(2) Should not be during restoration execution.
(3) Should be foreground.
(4) Should not be in the freeze status.
(5) Should be registered in the volume correspondence

table.
(6) Should be the basic volume.
(7) MVs should be a disk array under the own-host

control.
(8) The data and log files of the database should be in

MV.
(9) When specifying a database name with the -db

option, only one database must exist in the target MV.
(10) When specifying a database name with the -dbfile

option, all databases that exist in the target MV

MV

log

RV
log

Metafile

(11) The metafile should not be other than the targeted

MV.

(12) Space for creating metafile should be available.

Chapter 4 Functions of NEC Storage ReplicationControl SQL Option

29

Operation Example

An example of snapshot backup operation is shown below.

C:\>iSMsql_snapshotbkup -db snap -metafile c:\snap\snapdat.dat -wait 2

SnapshotBackup Start YYYY/MM/DD hh:mm:ss
DataBase snap
MV: 4 dev001 WN
\\?\Volume{3a78b50b-0f0b-11d5-9c71-00004c7929e8}\
D:
RV: 5 dev002 WN
\\?\Volume{2213cadd-24e9-11d5-bf42-00004c7929e8}\

­ Flush Start YYYY/MM/DD hh:mm:ss
Flush Normal End YYYY/MM/DD hh:mm:ss
Separate Start YYYY/MM/DD hh:mm:ss

Separating.....

Separate Normal End YYYY/MM/DD hh:mm:ss
SnapshotBackup Normal End YYYY/MM/DD hh:mm:ss
DataBase snap

MV: 4 dev001 WN
\\?\Volume{3a78b50b-0f0b-11d5-9c71-00004c7929e8}\
D:

RV: 5 dev002 WN
\\?\Volume{2213cadd-24e9-11d5-bf42-00004c7929e8}\

-

C:\>

Explanation

•

Database “snap” is in the d: drive.

The d: drive’s LD (logical disk) is dev001; and a pair is set with dev002.

Snapshot backup is performed on the dev001 and dev002 pair.

•

Waits for the command completion until separation is completed.

Chapter 4 Functions of NEC Storage ReplicationControl SQL Option

30

4

4

4

.

.

.

2

2

2

.

.

.

2

2

2

S

S

S

n

n

n

a

a

a

p

p

p

s

s

s

h

h

h

o

o

o

t

t

t

R

R

R

e

e

e

s

s

s

t

t

t

o

o

o

r

r

r

e

e

e

C

C

C

o

o

o

m

m

m

m

m

m

a

a

a

n

n

n

d

d

d

Snapshot restore uses the iSMsql_snapshotrst command.

By executing iSMsql_snapshotrst command, the restoration target volume is identified from the

specified metafile to be restored from the RV to the MV.

After restoration is executed, the database must be restored by giving the restoration instruction to

Microsoft SQL Server 2000.

When using an RV as a file system, it is necessary to release the mount of the file system.

With the iSMsql_snapshotrst command, the following options can be specified with regard to the

restoration operation.

(1) Specifying the database name (-db dbname or -dbfile dbfile_name)

A name recognized by Microsoft SQL Server 2000 can be specified as the database name.

When simultaneously performing snapshot backups on multiple databases, specify multiple

database names in the database operation file.

For details of the database operation file, refer to the “NEC Storage Manager Data Replication

Command Reference”.

(2) Specifying the metafile (-metafile metafilename or -metafolder

metafolder_name)

For the metafile, a metafile name incorporated during snapshot restoration can be specified.

The metafile specified during snapshot backup must be specified.

When simultaneously performing snapshot restorations on multiple databases, specify the name of

the folder that stores metafiles.

It is impossible to specify a metafile existing in the disk targeted for backup/restoration.

(3) Specifying the pair volume

Specify the MV volume and the RV volume.

•

Specifying the MV (-mv volume -mvflg mv_flg): Specifies the MV’s volume and volume

type.

• Specifying the RV (-rv volume -rvflg rv_flg): Specifies the RV’s volume and volume

type.

When specifying multiple pair volumes, describe the specification (-file file_name) in the

replication operation file.

For information on the volume type and replication operation file, refer to the “NEC Storage

Manager Data Replication Command Reference”.

When specifying a drive name with regard to a volume consisting of multiple partitions, all the

partitions become included in the operation by specifying the drive name for any of the partitions.

This, however, is limited to when the option allowing multiple partitions to be specified is enabled.

Chapter 4 Functions of NEC Storage ReplicationControl SQL Option

31

For information on setting options, refer to the “NEC Storage Manager Data Replication

Command Reference”.

(4) Specifying the copying range (-cprange)

Normally, only the differential area (diff) between MV and RV is copied. However, this option

can specify explicitly that the full area be copied.

(5) Specifying the Copy Control State (-cpmode)

The Copy Control State during restoration execution and in the synchronous state can be specified

at the same time as snapshot restoration.

•

Synchronous copy (-cpmode sync): Places the Copy Control State in the synchronous

copy mode.

• Semi-synchronous copy (-cpmode semi): Places the Copy Control State in the

semi-synchronous copy mode.

Semi-synchronous copying can be specified for

two differing disk array pairs.

• Background copy (-cpmode bg): Places the Copy Control State in the background

copy state.

(6) Specifying the RV access restriction (-rvacc)

The access-to-RV restriction during snapshot restoration execution and in the snapshot complete

state can be specified.

•

Not Ready (-rvacc nr) Placed in the Not Ready state, thus making it impossible for the host

to operate the volume.

• Read Only (-rvacc ro) Enables the host to only read the volume.

Unless well versed in OS and file system operations for Windows, Read Only (-rvacc ro) should

not be specified for the RV access restriction. For details, refer to 3.6 “RV Access Restrictions

Setting” of the “NEC Storage Manager Data Replication User’s Manual (Installation and

Operation Guide for Windows)”.

(7) Specifying waiting for copy completion (-wait/-nowait)

With snapshot restoration, the program can be made to wait for the end of the command after the

restoration operation until being placed in the synchronous state.

•

Wait specified (-wait [second]): When the value is specified to “second”, the disk array’s

monitoring time interval becomes the specified time. The

specifiable value is 1 to 30 seconds (integer number).

When the value is omitted, 5 seconds is set.

• No wait (-nowait): The command is ended after only specifying snapshot

restoration start.

Chapter 4 Functions of NEC Storage ReplicationControl SQL Option

32

The end of restoration is checked by the iSMrc_query

command.

(8) Specifying the RV operation mode (-mode)

Specify the RV operation mode applicable when restoration is performed.

• RV update restoration (-mode update) Restores the update that has been performed on

the MV while reflecting the update on the RV.

After the restoration has been completed, the

mode switches to the restoration complete state.

•

RV protection restoration (-mode protect) Restores the update that has been performed on

the MV without reflecting the update on the RV.

After the restoration has been completed, the RV

is automatically separated and the mode

switches to the separation complete state.

• Using the default setting (-mode default) Uses the setting stored in the replication

operation option setting file.

This function can be used only when either the “NEC Storage DynamicDataReplication Ver2” or

the “NEC Storage RemoteDataReplication Ver2” is installed in the disk array. For details about

this function, refer to the “NEC Storage Manager Data Replication User’s Manual (Function

Guide)” and “NEC Storage Manager Data Replication Command Reference”.

(9) Specifying the user ID/password

The user ID/password to be connected to Microsoft SQL Server 2000 can be specified.

When omitted, the user name and password for the Windows login account is used. No entry in

the password field is recognized as “no password”.

•

Specifying from the command line (-uid userid -pass password):

Specifies the user ID/password from the command

line.

•

Specifying from the keyboard (-input): When executing the command, interactively enter

a user ID and password by using a keyboard.

“User ID:” Enter a user ID.

“Password:” Enter a password.

Those specifications can be described in the database operation file.

For details of the database operation file, refer to the “NEC Storage Manager Data Replication

Command Reference”.

(10) Specifying the instance name (-server instance_name)

The computer name and the instance name when connecting to a labeled instance can be specified.

Chapter 4 Functions of NEC Storage ReplicationControl SQL Option

33

They can be specified in the format of computer_name\instance_name.

When omitted, the connection is made to the default instance.

The computer name must be either a local computer name, or a virtual computer name in the

MSCS (Microsoft Cluster Server) environment.

Those specifications can be described in the database operation file.

For details of the database operation file, refer to the “NEC Storage Manager Data Replication

Command Reference”.

(11) Specifying restoration mode (-remode)

With snapshot restoration, the kind of database restoration can be specified.

•

Recovering the database immediately after command execution (-remod recovery)

Recovered as the database when snapshot backup was performed.

• Recovering the database by applying the transaction log after command execution (-remod

norecovery)

After executing snapshot restoration, the database is restored by applying

the transaction log at the point of execution transaction log backup. The

database cannot be used until transaction log is applied.

• Recovering the database as the database for search (-remod standby -refile refilename)

Restores the database as the database for search.

The undo file must be specified as well.

Those specifications can be described in the database operation file.

For details of the database operation file, refer to the “NEC Storage Manager Data Replication

Command Reference”.

(12) Specifying restore command execution (-norestore)

Snapshot restore can specify that MV is not unmounted and data is not copied from pair-set RV to

MV (restore).

This is set in case snapshot restoration fails or when the database is restored only as the test/search

database.

(13) Specifying database file transfer (-move os_file_name[,...])

When the database is restored only as the test/search database, this option is used when the

snapshot backup environment and the database file location differ.

Specify all the physical files that are the factors of the database to be restored by separating with a

comma.

Those specifications can be described in the database operation file.

For details of the database operation file, refer to the “NEC Storage Manager Data Replication

Command Reference”.

Chapter 4 Functions of NEC Storage ReplicationControl SQL Option

34

The iSMsql_snapshotrst command is used to output messages to databases on which snapshot

restorations are performed when the snapshot restoration operation starts and ends as well as when the

restoration operation starts and ends.

•

Start message

SnapshotRestore Start YYYY/MM/DD hh:mm:ss

DataBase db_name
MV:physical-disk-no ld_name type

Volume_name
Path

RV:physical-disk-no ld_name type

Volume_name
Path

•

End message

SnapshotRestore Normal End YYYY/MM/DD hh:mm:ss

DataBase db_name
MV:physical-disk-no ld_name type

Volume_name
Path

RV:physical-disk-no ld_name type

Volume_name
Path

•

Restore start message

Restore Start YYYY/MM/DD hh:mm:ss

• Restore end message

Restore Normal End YYYY/MM/DD hh:mm:ss

Description of message

YYYY/MM/DD hh:mm:ss Start/end time (yyyy-mm-dd hh:mm:ss)
physical-disk-no PD number
Path Drive name / NTFS folder name
Volume_name MountPoint volume name
ld_name LD name
type OS Type
db_name Database name

•

Executing message

Restoring.....

Only when “-wait” is specified is this output until restoration is completed. “,” is updated

dynamically.

SnapshotRestore Start YYYY/MM/DD hh:mm:ss

MV:physical-disk-no ld_name type

Volume_name
Path

Chapter 4 Functions of NEC Storage ReplicationControl SQL Option

35

RV:physical-disk-no ld_name type

Volume_name

Path
Restore Start YYYY/MM/DD hh:mm:ss

Restoring.....

Restore Normal End YYYY/MM/DD hh:mm:ss
SnapshotRestore Normal End YYYY/MM/DD hh:mm:ss

MV:physical-disk-no ld_name type

Volume_name

Path

RV:physical-disk-no ld_name type

Volume_name

Path

Execution Conditions

When performing restoration, it is necessary to meet the following conditions.

(1) MVs and RVs targeted for operation are set as a pair.

(2) The main operation of the operation target pair is in the separate status. However, this should not

be during execution of the separation.

(3) With regard to the pair set in the same disk array, the semi-synchronous mode cannot be specified.

When specifying the semi-synchronous mode, it should be for the pair set between disk arrays.

(4) The disk array in which the specified MV and RV are stored should not be in the freeze status.

(5) The operation target MV is registered in the volume correspondence table.

(6) The volume of the operation target MV and RV is a basic volume.

(Specifying a volume using dynamic volume function is not allowed.)

(7) MV must exist in the disk array under its own host’s control.

(8) Other applications should not use the target MV.

(9) The data file and the log file included in the database exist in the target RV.

(10) When specifying a database name with the -db option, only one database must exist in the target

MV.

(11) When specifying a database name with the -dbfile option, all databases that exist in the target MV

must be specified.

(12) A metafile should not exist in the target MV.

(13) The RV must have been unmounted from the host.

Figure 4-4 shows the conditions for executing snapshot restoration ((1) to (13) in the diagram refer to

the numbers above).

Chapter 4 Functions of NEC Storage ReplicationControl SQL Option

36

Figure 4-4 Snapshot Restoration Execution Conditions

Shared disk

Operation target pair

MV
data

RV

data

MV

log

RV
log

Metafile

(1) Set as a pair.
(2) In the separate status.
(3) Semi-synchronization disabled

if for the same disk array.

(4) Should not be in the freeze

status.

(9) The data file and the log file

for the database exist.

(13) The RV must have been

unmounted from the host.

(5) Registered in the volume

correspondence table.
(6) Should be a basic volume.
(7) MV must be a disk array

under its own host’s

control.
(8) Other applications should

not use the target MV.
(10) When specifying a

database name with the -db

option, only one database

must exist in the target

MV.
(11) When specifying a

database name with the

-dbfile option, all

databases that exist in the

target MV must be

specified.
(12) A metafile should not exist

in the target MV.

Chapter 4 Functions of NEC Storage ReplicationControl SQL Option

37

Operation Example

Shows an example of the snapshot restoration operation.

(1) An example of not waiting for the end of command until the restoration is completed.

C:\>iSMsql_snapshotrst -db snap -metafile c:\snap.dat

SnapshotRestore Start YYYY/MM/DD hh:mm:ss
DataBase snap
MV: 4 dev001 WN
\\?\Volume{3a78b50b-0f0b-11d5-9c71-00004c7929e8}\
D:
RV: 5 dev002 WN
\\?\Volume{2213cadd-24e9-11d5-bf42-00004c7929e8}\

­ Restore Start YYYY/MM/DD hh:mm:ss
SnapshotRestore Normal End YYYY/MM/DD hh:mm:ss
DataBase snap
MV: 4 dev001 WN
\\?\Volume{3a78b50b-0f0b-11d5-9c71-00004c7929e8}\
D:
RV: 5 dev002 WN
\\?\Volume{2213cadd-24e9-11d5-bf42-00004c7929e8}\

-

C:\>

Explanation

•

Database “snap” is in the d: drive.

The d: drive’s LD (logical disk) is dev001; and a pair is set with dev002.

Snapshot backup is performed on the dev001 and dev002 pair.

•

Waits for command completion until restoration is completed.

Chapter 4 Functions of NEC Storage ReplicationControl SQL Option

38

(2) An example of waiting for command completion until restoration is completed.

Monitors the processing state in 2-second intervals by specifying -wait 2.

C:\>iSMsql_snapshotrst -db snap -metafile c:\snap.dat -wait 2

SnapshotRestore Start YYYY/MM/DD hh:mm:ss

DataBase snap

MV: 4 dev001 W N
\\?\Volume{3a78b50b-0f0b-11d5-9c71-00004c7929e8}\
D:

RV: 5 dev002 WN
\\?\Volume{2213cadd-24e9-11d5-bf42-00004c7929e8}\

­ Restore Start YYYY/MM/DD hh:mm:ss

Restoring.....

Restore Normal End YYYY/MM/DD hh:mm:ss
SnapshotRestore Normal End YYYY/MM/DD hh:mm:ss

DataBase snap

MV: 4 dev001 W N
\\?\Volume{3a78b50b-0f0b-11d5-9c71-00004c7929e8}\
D:

RV: 5 dev002 WN
\\?\Volume{2213cadd-24e9-11d5-bf42-00004c7929e8}\

-

C:\>

Explanation

•

Database “snap” is in the d: drive.

The d: drive’s LD (logical disk) is dev001; and a pair is set with dev002.

Snapshot backup is performed on the dev001 and dev002 pair.

•

Waits for command completion until restoration is completed.

(3) An example for not performing restoration

C:\>iSMsql_snapshotrst -db snap -metafile c:\snap.dat -norestore

SnapshotRestore Start YYYY/MM/DD hh:mm:ss
DataBase snap
SnapshotRestore Normal End YYYY/MM/DD hh:mm:ss
DataBase snap

C:\>

Explanation

•

The restoration is not performed.

Chapter 4 Functions of NEC Storage ReplicationControl SQL Option

39

4

4

4

.

.

.

3

3

3

M

M

M

e

e

e

t

t

t

a

a

a

f

f

f

i

i

i

l

l

l

e

e

e

H

H

H

a

a

a

n

n

n

d

d

d

l

l

l

i

i

i

n

n

n

g

g

g

The metafile created when executing the snapshot backup command is described below.

One metafile is required for each backup.

The metafile contains the target database’s original file configuration and the transaction log state

information.

The file size is approximately several hundred KB. Its maximum size is approximately 1MB.

The metafile can be created on the shared disk, MV or local disk. This metafile is used when recovering

from backup or starting the standby database on another node. Normally the shared disk is used.

When the metafile is lost, snapshot restoration cannot be executed. Therefore, make sure to save it onto

a highly reliable disk.

There respective uses are described below.

•

Shared disk

Used when saving the metafile on the backup server side. The advantage is the ease of saving

metafile.

A disk on the business server or the backup server can be used as a shared disk.

•

MV

Used when the shared disk format cannot be used due to network reasons such as when using an

RV from a remote distance with RDR. Since metafile information is used during recovery, it is

necessary to restore before recovery. At backup, unmount and separate the metafile MV after

snapshot backup.

•

Local disk

Can be used when saving metafile directly from a local volume to a tape or disk. When using the

snapshot backup as a disk backup, it is sufficient to use the local disk for the metafile.

Restore the database file on the RV created with snapshot backup by using the metafile created at the

time.

Attempting to restore the database file by using a metafile created at a different time may cause an

error.

When performing a snapshot backup, note the following:

(1) Metafile (-metafile) specification

•

Overwritten when the specified file already exists.

• If there is no folder for (or path to) the specified file name, the command fails to create

metafiles which result in an abnormal end.

• If there is a folder with the same name as the specified file name, the command fails to create

metafiles which result in an abnormal end.

(2) Meta-folder (-metafolder) specification

Chapter 4 Functions of NEC Storage ReplicationControl SQL Option

40

• When the specified folder already exists, all files in the folder are deleted and metafiles are

created.

• If there is no folder for (or path to) the specified folder name, the command fails to create

metafiles which result in an abnormal end.

• If there is a file with the same name as the specified file name, the command fails to create

metafiles which result in an abnormal end.

4

4

4

.

.

.

4

4

4

A

A

A

c

c

c

c

c

c

e

e

e

s

s

s

s

s

s

R

R

R

e

e

e

s

s

s

t

t

t

r

r

r

i

i

i

c

c

c

t

t

t

i

i

i

o

o

o

n

n

n

A user belonging to the Administrators group must execute the ReplicationControl command.

Therefore, A user belonging to the Administrator group also must be executed the NEC Storage

ReplicationControl SQL Option.

It is essential that accounts connected to Microsoft SQL Server 2000 must have the right to access all

databases.

Chapter 5 Installation and Setting of NEC Storage ReplicationControl SQL Option

41

Chapter 5 Installation and Setting of NEC

Storage ReplicationControl SQL
Option

This chapter explains the work necessary to install the NEC Storage ReplicationControl SQL Option.

5

5

5

.

.

.

1

1

1

O

O

O

p

p

p

e

e

e

r

r

r

a

a

a

t

t

t

i

i

i

n

n

n

g

g

g

E

E

E

n

n

n

v

v

v

i

i

i

r

r

r

o

o

o

n

n

n

m

m

m

e

e

e

n

n

n

t

t

t

(1) Operating OS

This software is operable on one of the following operating systems.

Microsoft Windows 2000 Advanced Server (SP2 or later)

or Microsoft Windows 2000 Server (SP2 or later)

(2) Unused disk space required

To install the NEC Storage ReplicationControl SQL Option, an unused disk space of at least

approximately 1 MB is required.

(3) Memory capacity required

To use the NEC Storage ReplicationControl SQL Option, a memory of at least approximately

4MB is required.

(4) Linkup software

This software operates in liaison with the following software program:

 NEC Storage ReplicationControl (Ver2.1 or later)

NEC Storage ReplicationControl SQL Option cannot be installed in the environment where the

NEC Storage ReplicationControl (Ver2.1 or later) has not been installed.

This software also operates in liaison with either of the following Microsoft software programs:

 Microsoft SQL Server 2000 Enterprise Edition (SP2 or later)

 Microsoft SQL Server 2000 Standard Edition (SP2 or later)

The NEC Storage ReplicationControl SQL Option can be executed only in the environment where

the Microsoft SQL Server 2000 (SP2 or later) has been installed.

5

5

5

.

.

.

2

2

2

S

S

S

o

o

o

f

f

f

t

t

t

w

w

w

a

a

a

r

r

r

e

e

e

I

I

I

n

n

n

s

s

s

t

t

t

a

a

a

l

l

l

l

l

l

a

a

a

t

t

t

i

i

i

o

o

o

n

n

n

To install NEC Storage ReplicationControl SQL Option, follow the procedure below.

The NEC Storage ReplicationControl SQL Option is connected to the target MV and installed on a

server installed with Microsoft SQL Server 2000. Additionally NEC Storage ReplicationControl

Ver2.1 or later should be preinstalled.

Chapter 5 Installation and Setting of NEC Storage ReplicationControl SQL Option

42

Normally, in the case of backup operations, the software is installed on the business server only; in the

case of parallel operations on a different node, the software is installed on a server operated in parallel

with the business server.

(1) Log on as the Administrator.

(2) Check the [Add/Remove Programs] in [Control Panel] to verify that NEC Storage

ReplicationControl is installed.

If it is not installed, install NEC Storage ReplicationControl first.

(3) Insert the setup CD-ROM for the NEC Storage ReplicationControl SQL Option into the CD-ROM

drive. Then select the following installation program from [Add/Remove Programs] in [Control

Panel].

CD-ROM drive:\iSMSQL\SETUP.EXE

(4) Follow the directions of the installer.

5

5

5

.

.

.

3

3

3

S

S

S

o

o

o

f

f

f

t

t

t

w

w

w

a

a

a

r

r

r

e

e

e

U

U

U

n

n

n

i

i

i

n

n

n

s

s

s

t

t

t

a

a

a

l

l

l

l

l

l

a

a

a

t

t

t

i

i

i

o

o

o

n

n

n

To uninstall NEC Storage ReplicationControl SQL Option, follow the procedure below.

(1) Log on as the Administrator.

(2) Check that the command for the NEC Storage ReplicationControl SQL Option is started.

If it is started, either make the end of processing wait or terminate the command for the NEC

Storage ReplicationControl SQL Option by force.

(3) If the [Event Viewer] is open, close it.

(4) Uninstall the following software by using [Add/Remove Programs] in [Control Panel].

NEC Storage ReplicationControl SQL Option

(5) Follow the directions of the uninstaller.

5

5

5

.

.

.

4

4

4

S

S

S

o

o

o

f

f

f

t

t

t

w

w

w

a

a

a

r

r

r

e

e

e

U

U

U

p

p

p

d

d

d

a

a

a

t

t

t

e

e

e

To update NEC Storage ReplicationControl SQL Option, uninstall existing program and then install

updated program.

5

5

5

.

.

.

5

5

5

S

S

S

e

e

e

t

t

t

t

t

t

i

i

i

n

n

n

g

g

g

o

o

o

f

f

f

N

N

N

E

E

E

C

C

C

S

S

S

t

t

t

o

o

o

r

r

r

a

a

a

g

g

g

e

e

e

R

R

R

e

e

e

p

p

p

l

l

l

i

i

i

c

c

c

a

a

a

t

t

t

i

i

i

o

o

o

n

n

n

C

C

C

o

o

o

n

n

n

t

t

t

r

r

r

o

o

o

l

l

l

S

S

S

Q

Q

Q

L

L

L

O

O

O

p

p

p

t

t

t

i

i

i

o

o

o

n

n

n

When constructing a system to apply the Microsoft SQL Server 2000 Database and the NEC Storage

ReplicationControl SQL Option, be sure to refer to Chapter 3 and the Microsoft SQL Server 2000

Books Online. Then design the database configuration before starting construction. If the configuration

is not appropriate for the NEC Storage ReplicationControl SQL Option, executing this function will end

in error.

Chapter 5 Installation and Setting of NEC Storage ReplicationControl SQL Option

43

5

5

5

.

.

.

5

5

5

.

.

.

1

1

1

R

R

R

e

e

e

p

p

p

l

l

l

i

i

i

c

c

c

a

a

a

t

t

t

i

i

i

o

o

o

n

n

n

V

V

V

o

o

o

l

l

l

u

u

u

m

m

m

e

e

e

P

P

P

r

r

r

e

e

e

p

p

p

a

a

a

r

r

r

a

a

a

t

t

t

i

i

i

o

o

o

n

n

n

The database is designed and constructed as a Replication Volume of the database to which the NEC

Storage ReplicationControl SQL Option is applied. For details, refer to the “NEC Storage Manager

Data Replication User’s Manual (Installation and Operation Guide for Windows)”.

Note that the types and configurations of available volumes are defined.

5

5

5

.

.

.

5

5

5

.

.

.

2

2

2

D

D

D

a

a

a

t

t

t

a

a

a

b

b

b

a

a

a

s

s

s

e

e

e

C

C

C

r

r

r

e

e

e

a

a

a

t

t

t

i

i

i

o

o

o

n

n

n

Other than creating a Replication Volume, the database is constructed in the same way as that for the

usual Microsoft SQL Server 2000. For details, refer to the Microsoft SQL Server 2000 Books Online.

For information on construction, refer to Appendix A “Notes”.

5

5

5

.

.

.

5

5

5

.

.

.

3

3

3

V

V

V

o

o

o

l

l

l

u

u

u

m

m

m

e

e

e

A

A

A

s

s

s

s

s

s

i

i

i

g

g

g

n

n

n

m

m

m

e

e

e

n

n

n

t

t

t

f

f

f

o

o

o

r

r

r

M

M

M

e

e

e

t

t

t

a

a

a

f

f

f

i

i

i

l

l

l

e

e

e

s

s

s

The NEC Storage ReplicationControl SQL Option uses metafiles to control the snapshot.

It is necessary to provide a metafile for each backup. Metafiles are allocated to a different volume from

the volume to which the database is allocated.

In accordance with the description in Section 4.3, the volume for metafiles is provided. Depending on

the allocation of metafiles, the database is constructed as follows.

•

When allocating to a shared disk

Set for a shared disk by setting the network computer. Multiple metafiles can be allocated to a

volume.

It is unnecessary to be targeted by DDR and RDR.

•

When allocating to MV

Used when a shared disk cannot be used for network reasons. Allocate an MV for each database.

This volume is created in the same way as normal volumes other than the database.

•

When allocating to a local disk

When used as a disk backup, a local disk is sufficient for metafiles. It is all right to allocate

multiple metafiles to a volume. For this configuration, the preparation of the volume only assigns

a disk.

5

5

5

.

.

.

6

6

6

S

S

S

e

e

e

t

t

t

t

t

t

i

i

i

n

n

n

g

g

g

o

o

o

f

f

f

M

M

M

i

i

i

c

c

c

r

r

r

o

o

o

s

s

s

o

o

o

f

f

f

t

t

t

S

S

S

Q

Q

Q

L

L

L

S

S

S

e

e

e

r

r

r

v

v

v

e

e

e

r

r

r

2

2

2

0

0

0

0

0

0

0

0

0

When many databases are to be operated simultaneously, it is necessary to change the Microsoft SQL

Server 2000 settings in advance. If the settings are not appropriate, when the NEC Storage

ReplicationControl SQL Option function is executed, an error occurs resulting in an abnormal end.

Chapter 5 Installation and Setting of NEC Storage ReplicationControl SQL Option

44

5

5

5

.

.

.

6

6

6

.

.

.

1

1

1

C

C

C

h

h

h

a

a

a

n

n

n

g

g

g

e

e

e

o

o

o

f

f

f

W

W

W

o

o

o

r

r

r

k

k

k

e

e

e

r

r

r

T

T

T

h

h

h

r

r

r

e

e

e

a

a

a

d

d

d

M

M

M

a

a

a

x

x

x

i

i

i

m

m

m

u

u

u

m

m

m

N

N

N

u

u

u

m

m

m

b

b

b

e

e

e

r

r

r

When the snapshot backup and snapshot restoration have been executed, worker threads are consumed

in the Microsoft SQL Server 2000.

Especially when snapshot backups are simultaneously performed on multiple databases, the number of

worker threads consumed increases in proportion to the number of databases. When the number of

available worker threads has been used up and new worker threads cannot be created, the NEC Storage

ReplicationControl SQL Option results in an abnormal end, displaying the following message:

iSM13689: Failed to snapshot execution. code=3627

Therefore, when snapshot backups are simultaneously performed on many databases, beforehand it is

necessary to make available the necessary maximum number of worker threads.

Indication of the maximum number of the worker threads

= Default 255 + (The number of databases on which snapshot backups are simultaneously

performed × 2)

Although the default number of worker threads is 255, those worker threads are also consumed by other

processes that use the Microsoft SQL Server 2000. Therefore, when processes other than the NEC

Storage ReplicationControl SQL Option also use the Microsoft SQL Server 2000, it is necessary to take

into consideration the number of worker threads consumed by those processes when setting the

maximum number of worker threads.

Change the worker thread maximum number according to the following procedure:

(1) From the Microsoft SQL Server’s menu, start Enterprise Manager.

(2) Select the target instance and display the properties.

(3) Select the “Processor” tag and change the worker thread maximum number controlled by the

processor.

(4) Resume the instance service.

Chapter 6 Operations of NEC Storage ReplicationControl SQL Option

Chapter 6 Operations of NEC Storage

ReplicationControl SQL Option

This chapter describes the basic operational procedure based on using data replications. When designing an actual
operational procedure, adjust the design to the system configuration and the recovery requirements.

6

.

1

T

a

p

e

B

a

c

k

u

p

6

.

1

T

a

p

e

B

a

c

6

.

1

T

a

p

e

B

Describes operations to save from the snapshot backup to the tape medium using the backup server without
suspending operations by using the NEC Storage ReplicationControl SQL Option. Here, the procedure is
operated with MV/RV in the separation state and with MV/RV synchronized immediately before backup.
This procedure has the advantage of being able to use RV as a disk backup.

a

c

k

k

u

u

p

p

45

Chapter 6 Operations of NEC Storage ReplicationControl SQL Option

N

1

.

1

.

6

.

6

6

The procedure for performing snapshot backup is described. The backup target data files are already set in
terms of pairs, with the operations running. Metafiles are placed in a shared disk. The shared disk where
metafiles are placed shall be accessible from both the busin ess server and the backup server.
In this example, the data file and the log file are created in different volumes with the database name as
snap.

Business Server

1

.

1

1

.

1

.

Master Volume (MV) Replication Volume (RV)

a

B

a

B

a

B

Data file

Log file

c

c

snap

d:

e:

c

p

u

k

k

k

p

u

p

u

f:

Metafile

Shared drive

Figure 6-1 Snapshot Backup

Backup Server

Tape

Backup software such as
ARCserve
BackupExec and

etBackup

Data file

Log file

46

Chapter 6 Operations of NEC Storage ReplicationControl SQL Option

Procedure 1. Remove the drive name for the backup targ et disk (Backup Server)

Remove the drive name for the backup target disk on the backup server side by executing the
MOUNTVOL command to prevent new access. When using a service to mon itor the disk state, it is
necessary to stop the service before executing th e MOUNTVOL command.

MOUNTVOL d: /D
MOUNTVOL e: /D

Procedure 2. Execute file system flush of the backup target disk (Backup Server)

Flush the file system of the backup target disk on the backup server side and then write t he
still-unwritten data in the file system buffer to the disk.

iSMrc_flush -mvol \\?\Volume{d9ea193d-9d59-11d6-ab08-806d6172696f}\
iSMrc_flush -mvol \\?\Volume{d9ea193e-9d59-11d6-ab08-806d6172696f}\

Procedure 3. Unmount backup target disk (Backup Server)

Unmount the backup target disk on the backup server side and cancel the associations between the
volume and the file system.

iSMrc_umount -mvol \\?\Volume{d9ea193d-9d59-11d6-ab08-806d6172696f}\
iSMrc_umount -mvol \\?\Volume{d9ea193e-9d59-11d6-ab08-806d6172696f}\

Procedure 4. Issue replication command (Business Server)

Issue the replication command.
MVs and RVs are synchronized.

iSMrc_replicate -mv d: -mvflg drv -wait
iSMrc_replicate -mv e: -mvflg drv -wait

Ordinary operations

Figure 6-2 Operation to Execute Replication

Replication Execution

Data file

MV RV

MV RV

Data file

Log file Log file

47

Chapter 6 Operations of NEC Storage ReplicationControl SQL Option

48

Chapter 6 Operations of NEC Storage ReplicationControl SQL Option

Procedure 5. Issue snapshot backup command (Business Server)

Issue the snapshot backup command. When using a service to mon itor the disk state, it is necessary to
stop the service before executing the snapshot backup. Start the service after executing the snapshot
backup.
MVs and RVs are separated to create metafiles in the shared disk.

iSMsql_snapshotbkup -db snap -metafile f:\snap.dat -wait

Figure 6-3 Operation to Execute Snapshot Backup

Procedure 6. Reconfigure the drive name for the b ackup target disk (Backup Server)

Reconfigure the removed d rive name for the backup target disk on the backup server side by executing
the MOUNTVOL command.

MOUNTVOL d: \\?\Volume{d9ea193d-9d59-11d6-ab08-806d6172696f}\
MOUNTVOL e: \\?\Volume{d9ea193e-9d59-11d6-ab08-806d6172696f}\

Procedure 7 . Mount backup target disk (Backup Server)

Mount the backup target disk of the backup server side. When using a service to monitor the disk state,
start the service after executing the mounting.

iSMrc_mount -drv d:
iSMrc_mount -drv e:

Snapshot Backup Execution

Data file

MV

MV

Metafile

Shared disk

Data file

RV

Log file Log file

RV

49

Chapter 6 Operations of NEC Storage ReplicationControl SQL Option

N

Procedure 8 . Tape backup (Backup Server)

Copy the data files and log files copied in the RV, to a tape as a backup by using the backup software.
Copy the metafiles of the shared disk to a tape.
After the snapshot backup is executed, the backup files o f the transaction log extract ed before
performing the snapshot backup are not used. Deleting backup files of the transaction log is permitted.

Data file

RV

Log file

RV

Metafile

Shared disk

Backup software such as
ARCserve
BackupExec and

etBackup

Tape

Figure 6-4 Tape Backup

50

6

N

6

Business Server

Chapter 6 Operations of NEC Storage ReplicationControl SQL Option

p

u

k

c

a

B

e

s

a

b

a

t

a

D

e

.

.

6

This section describes procedures for simultaneously per forming snapshot backups on multiple databases.
The backup target data files are already set in terms of pairs, with the operations running. Metafiles are
placed in a shared disk. Th e shared disk where metafiles are placed shall be accessible from both the
business server and the backu p server.
In this example, databases are named snap1 and snap2. Data files are created in the same volume, however,
log files are created in different volumes.

2

.

1

2

.

1

.

u

M

u

M

M

u

2

.

1

l

p

i

t

l

l

p

i

t

l

l

p

i

t

l

e

e

a

D

a

D

a

b

a

t

a

b

a

t

e

s

e

s

Tape

B

B

k

c

a

k

c

a

Backup software
such as ARCserve
BackupExec and

etBackup

u

u

p

p

Backup Server

snap1

snap2

Master Volume (MV) Replication Volume (RV)

d:

Log file

e:

Data file

e:

Data file

f:

Log file

g:

Metafile

Shared disk

Log file

Data file

Data file

Log file

51

Chapter 6 Operations of NEC Storage ReplicationControl SQL Option

Figure 6-5 Snapshot Backup

52

Chapter 6 Operations of NEC Storage ReplicationControl SQL Option

Procedure 1. Prepare a database operation file

Prepare a database operation file.
For details of the database operation file, refer to the “NEC Storage Manager Data Replication
Command Reference”.

snap_dbfile.txt

#db:db_name remod:restore_mode
db:snap1 remod:norecovery
db:snap2 remod:norecovery

* This file is an example for when the same file is used for both snapshot backup and snapshot

recovery operations. The abo ve “remod” option specification is ignored when a snap shot
backup is performed, but is effective when a snapshot restoration is performed.

Procedure 2. Remove the drive name for the backup targ et disk (Backup Server)

Remove the drive name for the backup target disk on the backup server side by executing the
MOUNTVOL command to prevent new access. When using a service to mon itor the disk state, it is
necessary to stop the service before executing th e MOUNTVOL command.

MOUNTVOL d: /D
MOUNTVOL e: /D
MOUNTVOL f: /D

Procedure 3. Execute file system flush of the backup target disk (Backup Server)

Flush the file system of the backup target disk on the backup server side and then write t he
still-unwritten data in the file system buffer to the disk.

iSMrc_flush -mvol \\?\Volume{d9ea193d-9d59-11d6-ab08-806d6172696f}\
iSMrc_flush -mvol \\?\Volume{d9ea193e-9d59-11d6-ab08-806d6172696f}\
iSMrc_flush -mvol \\?\Volume{d9ea193c-9d59-11d6-ab08-806d6172696f}\

Procedure 4. Unmount the backup target disk (Backup Ser ver)

Unmount the backup target disk on the backup server side and cancel the associations between the
volume and the file system.

iSMrc_umount -mvol \\?\Volume{d9ea193d-9d59-11d6-ab08-806d6172696f}\
iSMrc_umount -mvol \\?\Volume{d9ea193e-9d59-11d6-ab08-806d6172696f}\
iSMrc_umount -mvol \\?\Volume{d9ea193c-9d59-11d6-ab08-806d6172696f}\

53

Chapter 6 Operations of NEC Storage ReplicationControl SQL Option

Procedure 5. Issue the replication command (Business Server)

Issue the replication command.
MVs and RVs are synchronized.

iSMrc_replicate -mv d: -mvflg drv -wait
iSMrc_replicate -mv e: -mvflg drv -wait
iSMrc_replicate -mv f: -mvflg drv -wait

Executing replication

d:

Log file

Log file

Normal operations

Normal operations

Figure 6-6 Operation to Execute Replication

MV

e:

Data file Data file

e:

Data file

MV

f:

Log file

MV

RV

Data file

RV

Log file

RV

54

Chapter 6 Operations of NEC Storage ReplicationControl SQL Option

55

Chapter 6 Operations of NEC Storage ReplicationControl SQL Option

Procedure 6. Issue the snapshot backup command (B usiness Server)

Issue the snapshot backup command. When using a service to mon i tor the disk state, it is necessary
to stop the service before executing the snapshot backup. Start the service after executing the snapshot
backup.
MVs and RVs are separated to create metafiles in the shared disk.

iSMsql_snapshotbkup –dbfile snap_dbfile.txt – metafolder g:\metafolder –wait

Data file

Executing snapshot backup

d:

Log file

MV RV

e:

e:

Data file

Log file

Data file

Data file

MV

f :

Log file

MV

g:

Metafile

Shared disk

Figure 6-7 Operation to Execute Snapshot Backup

Procedure 7. Reconfigure the drive name for the b ackup target disk (Backup Server)

Reconfigure the removed d rive name for the backup target disk on the backup server side by executing
the MOUNTVOL command.

MOUNTVOL d: \\?\Volume{d9ea193d-9d59-11d6-ab08-806d6172696f}\
MOUNTVOL e: \\?\Volume{d9ea193e-9d59-11d6-ab08-806d6172696f}\

RV

Log file

RV

56

Chapter 6 Operations of NEC Storage ReplicationControl SQL Option

p

N

MOUNTVOL f: \\?\Volume{d9ea193c-9d59-11d6-ab08-806d6172696f}\

Procedure 8. Mount the backup target disk (Backup Server)

Mount the backup target disk on the backup server side. When using a service to monitor the disk
state, start the service after executing the mounting.

iSMrc_mount -drv d:
iSMrc_mount -drv e:
iSMrc_mount -drv f:

Procedure 9 . Tape backup (Backup Server)

Copy the data files and log files copied in the RV, to a tape as a backup by using the backup software.
Copy the metafiles of the shared disk to a tape.
After the snapshot backup has been executed, the backup files of the transaction log extracted before
the snapshot backup is performed are not used. Deleting backup files of the transaction log is
permitted.

Log file

Log file

RV

Data file

Data file

RV

Log file

RV

Metafile

Shared disk

Backup software
such as
ARCserve
BackupExec and

etBackup

Figure 6-8 Tape Backup

Ta

e

57

Chapter 6 Operations of NEC Storage ReplicationControl SQL Option

N

y

o

v

v

v

e

e

e

r

r

r

y

y

f:

Metafile

Shared disk

Tape

Backup software such as
ARCserve
BackupExec and

etBackup

Data file

Log file

Replication Volume (RV)

Business Server

3

.

1

.

6

.

1

.

6

1

.

6

The procedure for performing recovery from the backup obtained through snapshot backup is described here.
It is assumed that errors occurred in MV’s data file and the backup and the metafile previously where
snapshot backup was obtained are stored in the tape.
In this example, the data file and the log file are created in different volumes with the database name as
snap.

If an error occurs in the data file disk but not in the log file disk, a transaction log backup can be created
with Microsoft SQL Server 2000. In this case, recovery until immediately before the error is made possible
by applying the transaction log when the error occurs in the log file disk.
In the event that transaction log backups have been made periodically, recovery shall be possible until the
latest transaction log backup copy is created if an error occurs in the log file disk.
If the transaction log backup file is lost, recovery until the transaction log backup is created becomes
impossible. Save the transaction log backup file in a high-reliable disk.

R

3

R

3

.

R

Master Volume (MV)

o

c

e

o

c

e

c

e

Errors occurred
in the data disk!

d:

Data file

e:

Log file

Figure 6-9 Performing Snapshot Restoration

Backup Server

58

Chapter 6 Operations of NEC Storage ReplicationControl SQL Option

Procedure 1. Create transaction log backup (Business Server)

Create a transaction log backup when errors occur in Microsoft SQL Server 2000’s data disk.

T-SQL : BACKUP LOG snap TO DISK = ‘g:\sql\backups\trbl.dat’ WITH NO_TRUNCATE

Error occurred!

* In the event that errors occur in a disk, maintenance personnel may replace it. In this case, the OS

may be restarted to correctly recognize the replaced disk.

Procedure 2. Detach database (Business Server)

Detach the database where the error occurred.

T-SQL : EXEC sp_detach_db snap

Procedure 3. Initialize backup target disk (Backup Server)

Initialize the RV by using “Disk management” of Windows2000 if the logical volume is recovered due
to a hardware failure or if the file system is incorrect due to a procedural mistake during separation.
If the file system is in the normal state when recovering data due to an application error, etc., mount
the recovery target disk (all the disks of the database) of the backup server side and then associate the
volume with the file system.

iSMrc_mount -drv d:
iSMrc_mount -drv e:

Data file

MV

Figure 6-10 Create Transaction Log Backup

Data file

RV

59

Chapter 6 Operations of NEC Storage ReplicationControl SQL Option

N

Procedure 4. Restore from the tape to the RV (Backup Server)

Restore data from the tape to the RV by using the backup software.

Procedure 5. Remove the drive name for the recovery target disk (Backup Server)

Remove the drive name for the recovery target disk on the backup server side by executing the
MOUNTVOL command to prevent new access. When using a service to monitor the disk state, it is
necessary to stop the service before executing the MOUNTVOL command.

MOUNTVOL d: /D
MOUNTVOL e: /D

Procedure 6. Execute file system flush of the recovery target disk (Backup Server)

Flush the file system of the recovery target disk on the backup server side and then write the
still-unwritten data in the file system buffer to the disk.

iSMrc_flush -mvol \\?\Volume{d9ea193d-9d59-11d6-ab08-806d6172696f}\
iSMrc_flush -mvol \\?\Volume{d9ea193e-9d59-11d6-ab08-806d6172696f}\

Procedure 7. Unmount recovery target disk (Backup Server)

Unmount the recovery target disk of the backup server side and cancel the associations between the
volume and the file system.

iSMrc_umount -mvol \\?\Volume{d9ea193d-9d59-11d6-ab08-806d6172696f}\
iSMrc_umount -mvol \\?\Volume{d9ea193e-9d59-11d6-ab08-806d6172696f}\

Data file

RV

Log file

RV

Metafile

Shared disk

Figure 6-11 Restore from the Tape to the RV

Backup software such as
ARCserve
BackupExec and

etBackup

Tape

60

Chapter 6 Operations of NEC Storage ReplicationControl SQL Option

Procedure 8. Execute snapshot restoration (Business Server)

Execute a snapshot restoration by specifying the -remod norecovery option and the RV protection.
When using a service to monitor the disk state, it is necessary to stop the service before executing the
snapshot restoration. Start the service after executing the snapshot restoration.
When executing a snapshot restoration by specifying the RV protection, the separation is automatically
performed after synchronization has been completed as the result of the restoration. Therefore, it is
not necessary to execute the separation operation.

iSMsql_snapshotrst -db snap -metafile f:\snap.dat -remod norecovery -mode protect

Procedure 9. Reconfigure the drive name for the recovery target disk (Backup Server)

Reconfigure the removed drive name for the recovery target disk on the backup server side by
executing the MOUNTVOL command.

MOUNTVOL d: \\?\Volume{d9ea193d-9d59-11d6-ab08-806d6172696f}\
MOUNTVOL e: \\?\Volume{d9ea193e-9d59-11d6-ab08-806d6172696f}\

Snapshot restoration execution

Data file

MV

Log file

MV

Metafile

Shared disk

Figure 6-12 Execute Snapshot Restoration

Data file

RV

Log file

RV

61

Chapter 6 Operations of NEC Storage ReplicationControl SQL Option

Procedure 10. Apply transaction log (Business Server)

Apply the transaction log with Microsoft SQL Server 2000. The transaction log is applied in the order
of performing backup of the transaction log extracted after snapshot backup.

T-SQL : RESTORE LOG snap FROM DISK = ‘g:\sql\backups\backup01.dat’ WITH
NORECOVERY

·

·

·
T-SQL : RESTORE LOG snap FROM DISK = ‘g:\sql\backups\trbl.dat’ WITH
NORECOVERY

Apply all the transaction logs.
Restore the database.

T-SQL : RESTORE DATABASE snap WITH RECOVERY

Procedure 11. Start normal operati ons (Business Server)

Start normal operations after making sure that Microsoft SQL Server 2000 operates normally.

Procedure 12. Backup extraction (Backup Server)

The program can be made to wait for the completion of automatic separation after synchronization has
been completed as the result of restoration by way of the RV protection specification. After
completing the separation, extract the necessary backup.

iSMrc_wait -rv d: -rvflg drv -cond sep
iSMrc_wait -rv e: -rvflg drv -cond sep

62

6

N

6

Business Server

Chapter 6 Operations of NEC Storage ReplicationControl SQL Option

y

r

e

v

o

c

e

R

e

s

a

b

a

t

a

D

e

.

.

6

The procedure for performing recovery from the backup of multiple databases obtained through a snapshot
backup is described in this section. It is assumed that an error occurred in MV’s data file and the backup
and the metafile previously obtained through a snapshot backup are stored in the tape.
In this example, databases are named snap1 and snap2. Data files exist in the same volume; however, log
files exist in different volumes.

4

.

1

4

.

1

.

u

M

u

M

M

u

4

.

1

l

p

i

t

l

t

l

t

l

e

l

p

i

i

p

e

l

D

D

a

a

a

t

a

t

b

b

a

a

s

s

Tape

e

R

e

e

R

e

Backup software
such as ARCserve
BackupExec and

etBackup

c

c

o

o

v

v

e

e

y

r

y

r

Backup Server

snap1

snap2

Master Volume (MV) Replication Volume (RV)

d:

Log file

e:

Data file

An error
occurred

e:

Data file

f:

Log file

g:

Metafile

Shared disk

Figure 6-13 Performing Snapshot Restoration

Log file

Data file

Data file

Log file

63

Chapter 6 Operations of NEC Storage ReplicationControl SQL Option

64

Chapter 6 Operations of NEC Storage ReplicationControl SQL Option

If an error occurred in the disk in which data files for databases, snap1 and snap2, are allocated, but not in
the log file disk, a transaction log backup can be created with Microsoft SQL Server 2000. In this case,
recovery up until immediately before the error occurred is possible by applying the transaction log after a
snapshot restoration has been performed. In the event that transaction logs have been periodically backed
up, if an error occurred in the log file disk, recovery shall be possible up until the latest transaction log
backup copy had been created.
If the transaction log backup file is lost, recovery up until the transaction log backup copy had been created
is impossible. Save the transaction log backup file in a highly reliable disk.

Procedure 1. Prepare a databas e operation file

Prepare a database operation file.
For details of the database operation file, refer to the “NEC Storage Manager Data Replication
Command Reference”.

snap_dbfile.txt

#db:db_name remod:restore_mode
db:snap1 remod:norecovery
db:snap2 remod:norecovery

Procedure 2. Create a transaction log backu p (Business Server)

Create a transaction log backup when an error occurs in Microsoft SQL Server 2000’s data file disk.

T-SQL : BACKUP LOG snap1 TO DISK = 'h:\sql\backups_snap1\trbl.dat' WITH
NO_TRUNCATE
T-SQL : BACKUP LOG snap2 TO DISK = 'h:\sql\backups_snap2\trbl.dat' WITH
NO_TRUNCATE

* In the event that an error occurs in a disk, maintenance personnel may replace the disk. In this case,

the OS may be restarted to correctly recognize the replaced disk.

Procedure 3. Detach the database (Business Server)

Detach the database where the error occurred.

T-SQL : EXEC sp_detach_db snap1
T-SQL : EXEC sp_detach_db snap2

Procedure 4. Initialize the recovery target disk (Backup Server)

Initialize the RV by using “Disk management” of Windows2000 if the logical volume is recovered due
to a hardware failure or if the file system is incorrect due to a procedural mistake during separation.
If the file system is in the normal state, for example, when data is recovered from an application error,
etc., mount the recovery target disk (all the disks in the database) on the backup server side and then

65

Chapter 6 Operations of NEC Storage ReplicationControl SQL Option

N

associate the volume with the file system.

iSMrc_mount -drv d:
iSMrc_mount -drv e:
iSMrc_mount -drv f:

Procedure 5. Restore data from the tape to the R V (B ackup Server)

Restore data from the tape to the RV by using the backup software.

Log file

RV

Data file

Data file

RV

Tape

Backup software
such as ARCserve
BackupExec and

etBackup

Log file

RV

Metafile

Figure 6-14 Restoring Data from the Tape to the RV

Procedure 6. Remove the drive name for the recovery target disk (Backup Server)

Remove the drive name for the recovery target disk on the backup server side by executing the
MOUNTVOL command to prevent new access. When using a service to monitor the disk state, it is
necessary to stop the service before executing the MOUNTVOL command.

MOUNTVOL d: /D
MOUNTVOL e: /D
MOUNTVOL f: /D

Procedure 7. Execute file system flush of the recovery target disk (Backup Server)

Shared disk

66

Chapter 6 Operations of NEC Storage ReplicationControl SQL Option

Flush the file system of the recovery target disk on the backup server side and then write the
still-unwritten data in the file system buffer to the disk.

iSMrc_flush -mvol \\?\Volume{d9ea193d-9d59-11d6-ab08-806d6172696f}\
iSMrc_flush -mvol \\?\Volume{d9ea193e-9d59-11d6-ab08-806d6172696f}\
iSMrc_flush -mvol \\?\Volume{d9ea193c-9d59-11d6-ab08-806d6172696f}\

Procedure 8. Unmount the recovery target disk (Backup Server)

Unmount the recovery target disk on the backup server side and cancel the associations between the
volume and the file system.

iSMrc_umount -mvol \\?\Volume{d9ea193d-9d59-11d6-ab08-806d6172696f}\
iSMrc_umount -mvol \\?\Volume{d9ea193e-9d59-11d6-ab08-806d6172696f}\
iSMrc_umount -mvol \\?\Volume{d9ea193c-9d59-11d6-ab08-806d6172696f}\

Procedure 9. Execute snapshot restoration (Busin ess Server)

Execute a snapshot restoration by specifying the “remod:norecovery” option and the RV protection.
When using a service to monitor the disk state, it is necessary to stop the service before executing the
snapshot restoration. Start the service after executing the snapshot restoration.
When executing a snapshot restoration by specifying the RV protection, separation is automatically
performed after synchronization has been completed as the result of the restoration. Therefore, it is
not necessary to execute the separation operation.

iSMsql_snapshotrst –dbfile snap_dbfile.txt – metafolder g:\metafolder –mode protect

67

Chapter 6 Operations of NEC Storage ReplicationControl SQL Option

Performing snapshot restoration

d:

Log file

MV

e:

Data file

e:

Data file

MV

f:

MV

Log file

RV

Data file

Data file

RV

Log file Log file

RV

g:

Metafile

Shared disk

Figure 6-15 Operation to Execute Snapshot Restoration

68

Chapter 6 Operations of NEC Storage ReplicationControl SQL Option

Procedure 10. Reconfigure the driv e name for the recovery target disk (Backup Server)

Reconfigure the removed drive name for the recovery target disk on the backup server side by
executing the MOUNTVOL command.

MOUNTVOL d: \\?\Volume{d9ea193d-9d59-11d6-ab08-806d6172696f}\
MOUNTVOL e: \\?\Volume{d9ea193e-9d59-11d6-ab08-806d6172696f}\
MOUNTVOL f: \\?\Volume{d9ea193c-9d59-11d6-ab08-806d6172696f}\

Procedure 11. Apply transaction log (Business Server)

Apply the transaction log with Microsoft SQL Server 2000. The transaction log is applied in the order
of performing backup of the transaction log extracted after snapshot backup.

T-SQL : RESTORE LOG snap1 FROM DISK = 'h:\sql\backups_snap1\backup01.dat'
WITH NORECOVERY
T-SQL : RESTORE LOG snap2 FROM DISK = 'h:\sql\backups_snap2\backup01.dat'
WITH NORECOVERY

·

·

·
T-SQL : RESTORE LOG snap1 FROM DISK = 'h:\sql\backups_snap1\trbl.dat' WITH
NORECOVERY
T-SQL : RESTORE LOG snap2 FROM DISK = 'h:\sql\backups_snap2\trbl.dat' WITH
NORECOVERY

Apply all the transaction logs.
Restore the database.

T-SQL : RESTORE DATABASE snap1 WITH RECOVERY
T-SQL : RESTORE DATABASE snap2 WITH RECOVERY

Procedure 12. Start normal operati ons (Business Server)

Start normal operations after making sure that Microsoft SQL Server 2000 operates normally.

Procedure 13. Backup extraction (Backup Server)

The program can be made to wait for the completion of automatic separation after synchronization has
been completed as the result of restoration by way of the RV protection specification. After
completing the separation, extract the necessary backup.

iSMrc_wait -rv d: -rvflg drv -cond sep
iSMrc_wait -rv e: -rvflg drv -cond sep
iSMrc_wait -rv f: -rvflg drv -cond sep

69

Chapter 6 Operations of NEC Storage ReplicationControl SQL Option

70

Chapter 6 Operations of NEC Storage ReplicationControl SQL Option

6

.

2

D

i

s

k

B

a

c

k

u

p

6

.

2

D

i

s

k

B

a

c

6

.

2

D

i

s

k

B

Multiple RV operations are necessary when using the disk itself as a backup device. Consequently, this
makes the backup server unnecessary, thus making it possible to perform a series of operations with the
business server. Securing data consistency on the operation side is the same as when tape backup is
performed.
The procedure for disk backup operation is described below.

.

6

.

6

.

6

Procedure 1. Prepare three groups of two-replication operation files

1

.

2

.

2

2

For details about how to describe the replication operation file, refer to the “NEC Storage Manager
Data Replication Command Reference”.
disklist0.txt

P

1

P

1

.

P

a

p

e

r

a

p

e

r

a

p

e

r

k

a

c

k

o

i

t

a

r

o

i

t

a

r

o

i

t

a

r

u

u

n

n

n

p

p

#Type:MV Type:RV
0: mvdata 0:rvdata1
0: mvlog 0:rvlog1

snaplist0.txt

#Type:MV Type:RV
0: mvsnap 0:rvsnap1

disklist1.txt

#Type:MV Type:RV
0: mvdata 0:rvdata2
0: mvlog 0:rvlog2

snaplist1.txt

#Type:MV Type:RV
0: mvsnap 0:rvsnap2

disklist2.txt

#Type:MV Type:RV
0: mvdata 0:rvdata3
0: mvlog 0:rvlog3

snaplist2.txt

71

Chapter 6 Operations of NEC Storage ReplicationControl SQL Option

#Type:MV Type:RV
0: mvsnap 0:rvsnap3

72

Chapter 6 Operations of NEC Storage ReplicationControl SQL Option

2

.

2

.

6

.

6

6

The procedure for performing snapshot backup is described below. The backup target data file and log file
have already been paired and are running business operations.
In this example, the data file and the log file are created in different volumes with a database name of
“snap”.

Business Server

2

.

2

2

.

2

.

c

a

B

c

a

B

a

B

Master Volume (MV) Replication Volume (RV)

p

u

c

k

k

k

p

u

p

u

d:

Data file

e:

Log file

f:

Metafile

Figure 6-16 Performing Disk Backup

Data file

Log file

Metafile

73

Chapter 6 Operations of NEC Storage ReplicationControl SQL Option

g

Procedure 1. Execute the replication (Business Server)

Execute replication for the current volume.

iSMrc_replicate -file disklist0.txt -wait
iSMrc_replicate -file snaplist0.txt -wait

Data file

Log file

MV

Metafile

MV

Replication execution

MV

Figure 6-17 Performing Replication

RV

RV

RV

Data file 2

Data file 1

Lo

file 2

Log file 1

Metafile 3

Metafile 2

Metafile 1

Data file 3

Log file 3

74

Chapter 6 Operations of NEC Storage ReplicationControl SQL Option

Procedure 2. Execute snapshot backup (Business Server)

Execute snapshot backup on the current volume.

iSMsql_snapshotbkup -db snap -metafile f:\snap.dat -file disklist0.txt -nowait

Procedure 3. Remove the drive name for the metafile disk (Business Server)

Remove the drive name for the metafile disk by executing the MOUNTVOL command to prevent new
access. When using a service to monitor the disk state, it is necessary to stop the service before
executing the MOUNTVOL command.

MOUNTVOL f: /D

Procedure 4. Unmounting metafile disk (Business Server)

Unmount the metafile disk and cancel association between volume and file system.

iSMrc_umount -mvol \\?\Volume{d9ea193c-9d59-11d6-ab08-806d6172696f}\

Snapshot Backup Execution

Data file

MV

Log file

MV

Metafile

MV

Figure 6-18 Performing Snapshot Backup

Data file

RV

Log file

RV

Metafile

RV

75

Chapter 6 Operations of NEC Storage ReplicationControl SQL Option

Procedure 5. Execute separation on the metafile volume (Business Server)

Issue the separation command to the metafile volume. When using a service to monitor the disk state,
stop the service after executing separation.

iSMrc_separate -file snaplist0.txt

Procedure 6. Reconfigure the drive name for the metafile disk (Business Server)

Reconfigure the removed drive name for th e metafile disk by executing the MOUNTVOL command.

MOUNTVOL f: \\?\Volume{d9ea193c-9d59-11d6-ab08-806d6172696f}\

Procedure 7. Circulate the replication operation file (Business Server)

move disklist2.txt save.txt
move disklist1.txt disklist2.txt
move disklist0.txt disklist1.txt
move save.txt disklist0.txt
move snaplist2.txt save.txt
move snaplist1.txt snaplist2.txt
move snaplist0.txt snaplist1.txt
move save.txt snaplist0.txt

Data file

MV

Log file

MV

Separation execution

Metafile

MV

Figure 6-19 Performing Separation

Data file

RV

Log file

RV

Metafile

RV

76

Chapter 6 Operations of NEC Storage ReplicationControl SQL Option

77

Chapter 6 Operations of NEC Storage ReplicationControl SQL Option

When executing backup hereafter, start it from Procedure 1. disklist0.txt and snaplist0.txt are always in the
current RV.

Backup first time

Backup second time

Backup third time

Connect

Data

(MV)

Data

(MV)

Data

(MV)

Figure 6-20 Circulation of Replication Operation File

Separate

Separate

Separate

Connect

Separate

Separate

Separate

Connect

Data1

Data2

Data3

Data1

Data2

Data3

Data1

Data2

Data3

Use Data1, Data2, and
Data3 alternately.

78

Chapter 6 Operations of NEC Storage ReplicationControl SQL Option

y

3

.

2

.

6

.

2

.

6

2

.

6

If an error occurs on the data file disk but not on the log file disk, a transaction log backup can be made with
Microsoft SQL Server 2000. In this case, recovery up to immediately before the error is now possible by
applying the transaction log after executing snapshot restoration.
In the event that the transaction log has been backed up periodically, recovery up until the transaction log is
created is now possible if an error occurs on the log file disk.
If the transaction log backup file is lost, recovery up until the transaction log backup is created is now
impossible.
Save the transaction log backup file onto a highly reliable disk.
An example of this is that when an error occurs, disklist0.txt and snaplist0.txt are saved as valid data.

Business Server

R

3

R

3

.

R

o

c

e

o

c

e

c

e

Error occurred on the data disk!

Master Volume (MV)

o

v

r

e

r

e

v

r

e

v

d:

Data file

e:

Log file

f:

Metafile

y

y

Data file

Log file

Metafile

Replication Volume (RV)

79

Chapter 6 Operations of NEC Storage ReplicationControl SQL Option

Figure 6-21 Performing Recovery from Disk Backup

80

Chapter 6 Operations of NEC Storage ReplicationControl SQL Option

Procedure 1 Create the transaction log backup (Business Server)

Create a transaction log backup if an error occurs on Microsoft SQL Server 2000’s data disk.

T-SQL : BACKUP LOG snap TO DISK = 'g:\sql\backups\trbl.dat' WITH NO_TRUNCATE

Procedure 2. Detach the database (Business Server)

Detach the database where the error occurred.

T-SQL : EXEC sp_detach_db snap

Procedure 3. Execute metafile disk’s file system flush (Business Server)

Flush the file system of the metafile disk and then write the still-unwritten data in the file system
buffer to the disk.

iSMrc_flush -drv f:

Procedure 4. Unmount the metafile disk (Business Server)

Unmount the metafile disk and cancel the associations between the volume and the file system. When
using a service to monitor the disk state, stop the service before unmounting.

iSMrc_umount -drv f:

Procedure 5. Execute restoration (Business Server)

Restore the latest backup file from the RV to the MV.
When executing a snapshot restoration by specifying the RV protection, the separation is automatically
performed after synchronization has been completed as the result of the restoration. Therefore, it is
not necessary to execute the separation operation.

iSMrc_restore -file snaplist0.txt -mode protect

*1: Save latest backup data to metafile 1.

Metafile

Restoration execution

MV

Figure 6-22 Performing Restoration

RV

Metafile 1

Metafile 3

Metafile 2

*1

81

Chapter 6 Operations of NEC Storage ReplicationControl SQL Option

Procedure 6. Execute snapshot restoration (Business Server)

Execute snapshot restoration from the latest backup RV to the MV. When using a service monitor the
disk state, start the service after executing the snapshot restoration.
When executing a snapshot restoration by specifying the RV protection, the separation is automatically
performed after synchronization has been completed as the result of the restoration. Therefore, it is
not necessary to execute the separation operation.

iSMsql_snapshotrst -db snap -metafile f:\snap.dat -file disklist0.txt –remod norecovery

-mode protect

*1: Save latest backup data to data file1 and log file1.

Procedure 7. Apply the transaction log (Business Server)

Apply the transaction log with Microsoft SQL Server 2000. The transaction log is applied in the
sequence of performing backup of the transaction log extracted after the snapshot backup.

T-SQL : RESTORE LOG snap FROM DISK = ‘g:\sql\backups\backup01.dat’ WITH
NORECOVERY

·

·

·
T-SQL : RESTORE LOG snap FROM DISK = ‘g:\sql\backups\trbl.dat’ WITH

Snapshot restore execution

Data file

MV

Log file

MV

Figure 6-23 Performing Snapshot Restoration

RV

Log file 1

RV

Data file 3

Data file 2

Data file 1

Log file 3

Log file 2

*1

82

Chapter 6 Operations of NEC Storage ReplicationControl SQL Option

NORECOVERY

Apply all the transaction logs.
Restore the database.

T-SQL : RESTORE DATABASE snap WITH RECOVERY

Procedure 8. Start ordinary business operations (Business Server)

Start ordinary business operations after making sure that Microsoft SQL Server 2000 operates
normally.

Procedure 9. Backup extraction (Business Server)

The program can be made to wait for the completion of automatic separation after synchronization has
been completed as the result of restoration by way of the RV protection specification. After
completing the separation, extract the necessary backup.

iSMrc_wait -file disklist0.txt -cond sep
iSMrc_wait -file snaplist0.txt -cond sep

83

Chapter 6 Operations of NEC Storage ReplicationControl SQL Option

6

.

3

P

a

r

a

l

l

e

l

O

p

e

r

a

t

i

o

n

o

n

A

n

A

A

a

a

a

n

n

t

t

t

a

a

a

o

o

o

b

b

b

Business Server

6

.

3

P

a

r

a

l

l

e

l

O

p

e

r

a

t

i

o

n

o

n

6

.

3

P

a

r

a

l

l

e

l

O

p

e

r

a

t

i

o

n

Describes operations to starting Microsoft SQL Server 2000 on the search server and using the snapshot
backup as the database of another node without stopping search work by the NEC Storage
ReplicationControl SQL Option. The standby database is used only for searches. Periodically applying the
transaction log offers the advantage of reflecting the latest data without stopping search work.

b

d

n

a

t

S

s

a

n

o

1

.

3

.

6

.

6

6

Data resulting from snapshot backup can be used as the search database.
Data once restored for reference purposes in Microsoft SQL Server 2000 cannot be used as the backup data.
The backup target data and log files will have already been paired and replication will be being executed and
the business server will be being executed and the business server will be running operations.
In this example, the data file and the log file are created in different volumes with the database name as
“snap”.

1

.

3

1

.

3

.

Master Volume (MV)

p

O

p

O

p

O

snap

d:

Data file

e:

Log file

e

e

e

i

t

a

r

a

r

a

r

Figure 6-24 Running as Standby Database

n

o

i

t

n

o

i

t

Metafile

Shared disk

f:

S

s

a

S

s

a

Replication Volume (RV)

d

n

a

t

d

n

a

t

Used as a search database

snap

d:

Data file

e:

Log file

b

b

o

y

y

y

n

D

D

D

t

h

e

t

h

e

t

h

e

e

s

a

e

s

a

e

s

a

Search Server

r

N

o

d

e

r

N

o

r

N

o

d

d

e

e

84

Chapter 6 Operations of NEC Storage ReplicationControl SQL Option

Procedure 1. Preparation

Set Microsoft SQL Server 2000 so that the search server can b e used as a standby server. For details,
refer to Microsoft SQL Server 2000 Books Online.

Procedure 2. Detaching database (Search Server)

Detach the targeted database

T-SQL : EXEC sp_detach_db snap

Procedure 3. Remove the drive name for the search target disk (Search Server)

Remove the drive name for th e search target disk on the search server side by executing the
MOUNTVOL command to prevent new access. When using a service to monitor the disk state, it is
necessary to stop the service before executing the MOUNTVOL command.

MOUNTVOL d: /D
MOUNTVOL e: /D

Procedure 4. Execute file system flush of the search target disk (Search Server)

Flush the file system of the search target disk and then write the still-unwritten data in the file system
buffer to the disk.

iSMrc_flush -mvol \\?\Volume{d9ea193d-9d59-11d6-ab08-806d6172696f}\
iSMrc_flush -mvol \\?\Volume{d9ea193e-9d59-11d6-ab08-806d6172696f}\

Procedure 5. Unmount the search target disk (Search Server)

Unmount the search target disk of the search server and cancel the associations between the volume
and the file system.

iSMrc_umount -mvol \\?\Volume{d9ea193d-9d59-11d6-ab08-806d6172696f}\
iSMrc_umount -mvol \\?\Volume{d9ea193e-9d59-11d6-ab08-806d6172696f}\

85

Chapter 6 Operations of NEC Storage ReplicationControl SQL Option

Procedure 6. Issue the replication command (Business Server)

Issue the replication command.
MVs and RVs are synchronized.

iSMrc_replicate -mv d: -mvflg drv
iSMrc_replicate -mv e: -mvflg drv

Ordinary business

operations

Procedure 7. Issue the snapshot backup command (Business S erver)

To immediately use the RV, execute backup commands by specifying the -nocheck and -rvuse immediate
options. When using a service to monitor the disk state, it is necessary to stop the service before executing
the snapshot backup. Start the service after executing the snapshot backup.
MVs and RVs are separated creating metafiles in the shared disk.

iSMsql_snapshotbkup -db snap -metafile f:\snap.dat -nocheck -rvuse immediate

Data file

MV

Log file

MV

Replication Execution

Data file

MV

Log file

MV

Figure 6-25 Performing Replication

Snapshot Backup Execution

Data file

Log file

Metafile

Data file

Log file

RV

RV

RV

RV

Shared disk

86

Chapter 6 Operations of NEC Storage ReplicationControl SQL Option

Figure 6-26 Performing Snapshot Backup

Procedure 8. Reconfigure the drive name for the search target disk (Search Server)

Reconfigure the removed drive name for the search target disk on the search server side by executing

D

n

o

i

t

u

b

i

r

t

s

i

r

t

s

i

r

t

s

i

t

u

b

i

t

u

b

i

n

o

i

n

o

i

the MOUNTVOL command.

MOUNTVOL d: \\?\Volume{d9ea193d-9d59-11d6-ab08-806d6172696f}\
MOUNTVOL e: \\?\Volume{d9ea193e-9d59-11d6-ab08-806d6172696f}\

Procedure 9. Mount the search target disk (Search Server)

Mount the target disk on the RV side. When using a service to monitor the disk state, start the service
after executing the mounting.

iSMrc_mount -drv d:
iSMrc_mount -drv e:

Procedure 10. Execute snapshot restoration (Search Server)

Execute snapshot restoration with the search server.
The data copied as a backup through snapshot backup is restored as the standby database in the search
server’s Microsoft SQL Server 2000.

iSMsql_snapshotrst -db snap -metafile f:\snap.dat -norestore -remod standby

-refile g:\db_undo.dat

6

6

6

2

.

3

.

.

3

.

3

.

L

2

L

2

.

L

o

o

o

g

g

g

D

D

By copying the transaction log as a backup using the business server and applying the transaction log
backup to the search server, the contents of the search server’s database can be made to be equivalent to the
transaction log backup status.
For details, refer to the Microsoft SQL Server 2000 Books Online.
Use the file specified with the -refile option during the snapshot restoration operation as an undo file
required for recovery in standby mode.

87

Chapter 6 Operations of NEC Storage ReplicationControl SQL Option

m

o

c

c

A

r

e

v

r

e

S

r

o

f

n

o

r

r

a

a

a

a

a

a

r

t

t

i

t

o

i

t

o

i

t

e

e

e

t

Metafile

Shared dick

f:

n

n

S

r

o

f

Used as a replication database

v

r

e

snap

d:

Data file

e:

Log file

e

c

A

r

c

m

o

Replication Server

m

o

c

c

A

r

e

v

r

e

S

r

o

f

Business Server

3

.

3

.

6

.

6

6

By making RVs of the master database, the database can be separated and used by other servers. RVs are
used to build test environments, etc.

3

.

3

3

.

3

.

Master Volume (MV) Replication Volume (RV)

e

p

O

e

p

O

e

p

O

d

p

U

d

p

U

d

p

U

snap

d:

Data file

e:

Log file

Figure 6-27 Running as a Replication Database

p

p

p

a

a

a

n

n

n

i

d

e

i

d

e

i

y

b

y

b

y

b

d

e

88

Ordinary business

Chapter 6 Operations of NEC Storage ReplicationControl SQL Option

Procedure 1. Detach the database (Replication Server)

Detach the relevant database if the database is run on all the replication servers.

T-SQL : EXEC sp_detach_db snap

Procedure 2. Remove the drive name for the replication target disk (Replicati on Server)

Remove the drive name for the replication target disk on the replication server side by executing the
MOUNTVOL command to prevent new access. When using a service to monitor the disk state, it is
necessary to stop the service before executing the MOUNTVOL command.

MOUNTVOL d: /D
MOUNTVOL e: /D

Procedure 3. Execute file system flush of the replication target disk (Replication Server)

Flush the file system of the replication target disk on the replication server side and then write the
still-unwritten data in the file system buffer to the disk.

iSMrc_flush -mvol \\?\Volume{d9ea193d-9d59-11d6-ab08-806d6172696f}\
iSMrc_flush -mvol \\?\Volume{d9ea193e-9d59-11d6-ab08-806d6172696f}\

Procedure 4. Unmount the replication target disk (Replication Server)

Unmount the replication target disk on the replication server side and cancel the associations between
the volume and the file system.

iSMrc_umount -mvol \\?\Volume{d9ea193d-9d59-11d6-ab08-806d6172696f}\
iSMrc_umount -mvol \\?\Volume{d9ea193e-9d59-11d6-ab08-806d6172696f}\

Procedure 5. Issue the replication command (Business Server)

Issue the replication command.
MVs and RVs are synchronized.

iSMrc_replicate -mv d: -mvflg drv -wait
iSMrc_replicate -mv e: -mvflg drv -wait

Data file

operations

MV

Log file

MV

Replication execution

Data file

RV

Log file

RV

89

Chapter 6 Operations of NEC Storage ReplicationControl SQL Option

Figure 6-28 Performing Replication

90

Chapter 6 Operations of NEC Storage ReplicationControl SQL Option

Procedure 6. Issue the snapshot backup command (Business Server)

Issue the snapshot backup command. When using a service to monitor the disk state, stop the service
before backing up the snapshot. Start the service after executing the snapshot backup.
MVs and RVs are separated creating metafiles in the shared disk.

iSMsql_snapshotbkup -db snap -metafile f:\snap.dat -wait

Procedure 7. Reconfigure the drive name for the re pli cation target disk (Replication Server)

Reconfigure the remo ved drive name for the replication target disk on the replication server side by
executing the MOUNTVOL command.

MOUNTVOL d: \\?\Volume{d9ea193d-9d59-11d6-ab08-806d6172696f}\
MOUNTVOL e: \\?\Volume{d9ea193e-9d59-11d6-ab08-806d6172696f}\

Procedure 8. Mount the replication target disk (Repli cation Server)

Mount the target disk on the RV side. When using a service to monitor the disk state, start the service
after executing the unmounting.

iSMrc_mount -drv d:
iSMrc_mount -drv e:

Procedure 9. Attach the database (Replication Server)

Attach the database with the replication server.

Procedure 10. Reflect the data for the business server

Stopping the business operations of the replication server and then repeating Procedures 1 to 9, the

Snapshot Backup Execution

Data file

MV

Log file

MV

Metafile

Shared disk

Figure 6-29 Performing Snapshot Backup

Data file

Log file

RV

RV

91

Chapter 6 Operations of NEC Storage ReplicationControl SQL Option

data for the business server can be used by the replication server

92

Chapter 7 Measures for Errors

93

Chapter 7 Measures for Errors

This chapter describes measures for errors that occur while operating the NEC Storage ReplicationControl SQL
Option.

7

7

7

.

.

.

1

1

1

E

E

E

r

r

r

r

r

r

o

o

o

r

r

r

D

D

D

e

e

e

t

t

t

e

e

e

c

c

c

t

t

t

i

i

i

o

o

o

n

n

n

M

M

M

e

e

e

t

t

t

h

h

h

o

o

o

d

d

d

When errors occur, the NEC Storage ReplicationControl SQL Option outputs the details of the standard
output, the standard error output, the event log and the operation trace.
The messages described in “NEC Storage Manager Message Handbook” are output to the standard
output, to the standard error output and to the event log. Take appropriate corrective actions in
accordance with the explanation in the messages.
In the operation trace, the messages output to the standard output, to the standard error output and to the
event log are recorded together with detailed internal information.
Operation trace is output to the same file as that of NEC Storage ReplicationControl. The data is
output to iSMrpl.log file in etc\trace folder, within installation folder of NEC Storage
ReplicationControl. Check the contents by using the text editor, etc.

When errors occur, Microsoft SQL Server 2000 outputs the contents of errors to the error log. For
details, refer to Microsoft SQL Server 2000 Books Online.

7

7

7

.

.

.

2

2

2

E

E

E

r

r

r

r

r

r

o

o

o

r

r

r

s

s

s

R

R

R

e

e

e

l

l

l

a

a

a

t

t

t

e

e

e

d

d

d

t

t

t

o

o

o

D

D

D

a

a

a

t

t

t

a

a

a

b

b

b

a

a

a

s

s

s

e

e

e

C

C

C

o

o

o

n

n

n

f

f

f

i

i

i

g

g

g

u

u

u

r

r

r

a

a

a

t

t

t

i

i

i

o

o

o

n

n

n

s

s

s

With the NEC Storage ReplicationControl SQL Option’s error output, if “iSM13689: Failed to snapshot
execution.” and “iSM13690: Failed to sql command execution.” are output without outputting other
error messages immediately before, a certain form of error has occurred at the Microsoft SQL Server

2000.
Take appropriate measures while referring to the error log of Microsoft SQL Server 2000.

In the event that the I/O is high for the disk, the snapshot backup may fail. In this case, if the error log
of Microsoft SQL Server 2000 is referred to, error code 844 or 845 is output.
The snapshot backup must be executed when the operations load is lowered. It is necessary to review
the operation if this error occurs.

Chapter 7 Measures for Errors

94

7

7

7

.

.

.

3

3

3

E

E

E

r

r

r

r

r

r

o

o

o

r

r

r

s

s

s

R

R

R

e

e

e

l

l

l

a

a

a

t

t

t

e

e

e

d

d

d

t

t

t

o

o

o

M

M

M

e

e

e

t

t

t

a

a

a

f

f

f

i

i

i

l

l

l

e

e

e

C

C

C

o

o

o

n

n

n

f

f

f

i

i

i

g

g

g

u

u

u

r

r

r

a

a

a

t

t

t

i

i

i

o

o

o

n

n

n

s

s

s

With the NEC Storage ReplicationControl SQL Option’s error output, if “iSM13693: Metafile is
existing in the same volume as the database.” is output, the metafile setup is incorrect. In this case,
specify the metafile correctly as described in 4.3 “Metafile Handling”.

In the event that “iSM13696: Failed to get database volume from metafile.” is output when the metafile
is in the shared disk of another computer, check if the shared disk can be used with the user name and
the password executing the NEC Storage ReplicationControl SQL Option.
When executing the NEC Storage ReplicationControl SQL Option from NetBackup, check the setup of
the user name and the password that execute the NEC Storage ReplicationControl SQL Option of
NetBackup.

The database file on the RV created with the snapshot backup needs to be restored by using the metafile
created at that time.
An attempt to restore the database file using a metafile created at a different time will lead to an error at
the Microsoft SQL Server 2000 when applying the transaction log.
Likewise, once a file of the database disconnected through snapshot backup is operated in parallel on
another node, the file cannot be used as a disk backup. When applying the transaction log, an error will
occur at the Microsoft SQL Server 2000.