Existing set customer of database uses a raw device, due to the large amount of data in the database. The customer plans to replace the old storage with new storage devices. In the process of environmental inspection lvcb engineers found the following: #getlvcb -TA sjklv Intrapolicy = copies = 0 interpolicy = lvid =
lvname = label = machine id = number Ips = 0 relocatable = strict = stripe width = 0 stripe size in exponent = 0 type = upperbound = 0
fs = time created = time modified =
As the vg is too large, the expansion of vg is impossible. As the service window is very short, and customers do not want to avoid the risk of large adjustments of the whole original environment, what is the recommended approach?

Question

Existing set customer of database uses a raw device, due to the large amount of data in the database. The customer plans to replace the old storage with new storage devices. In the process of environmental inspection lvcb engineers found the following: #getlvcb -TA sjklv Intrapolicy = copies = 0 interpolicy = lvid =

lvname = label = machine id = number Ips = 0 relocatable = strict = stripe width = 0 stripe size in exponent = 0 type = upperbound = 0

fs = time created = time modified =

As the vg is too large, the expansion of vg is impossible. As the service window is very short, and customers do not want to avoid the risk of large adjustments of the whole original environment, what is the recommended approach?

Tomas Ojeda · Accepted Answer

Use migratepv for data migration

Tomas Ojeda · Answer

Based on lvcb offset reconstruction nude equipment, and the database level 0 backup import

Tomas Ojeda · Answer

Use the dd command for data migration

Tomas Ojeda · Answer

Use the cplv command for data migration

Question list

List of questions

Question 1

(0)

Question 2

(0)

Question 3

(0)

Question 4

(0)

Question 5

(0)

Question 6

(0)

Question 7

(0)

Question 8

(0)

Question 9

(0)

Question 10

(0)

Related questions

Question 128 - H13-629 discussion

Suggested answer: D

0 comments