Volume Manager Configuration
114 NetBackup ServerFree Agent System Administrator’s Guide
Disk Group Cloning Example:
In the above example, NetBackup removes the VxVM disk group clone_dg_1_clone
after the backup has completed. If a major system interruption occurs (such as a crash or
unexpected reboot), NetBackup may not be able to remove the clone. In that case, you
must use the bpdgclone command with the -c option to remove the clone, and then
resynchronize the mirror disk with the primary disk. Refer to “Removing a VxVM Volume
Clone” on page 132 for assistance.
When Secondary Disks are Split and Synched
This situation is described for your information only. A backup occurring in this
circumstance should complete normally, in spite of the Volume Manager error described
as follows.
When the secondary (mirror) device is split from its primary, Volume Manager will see
the secondary disk as separate device. But when the secondary disk is then re-synched to
its primary disk (provided Volume Manager had seen it before), the synched secondary
disk is no longer visible and VxVM issues an I/O error. In addition, if DMP is enabled, the
secondary disks are marked as disabled. The next time the secondary is split, it will
reappear in Volume Manager, only to disappear when the disk is again synched to its
primary.
V
x
V
M
d
i
s
k
g
r
o
u
p
d
g
_
1
o
n
p
r
i
m
a
r
y
_
d
i
s
k
1
.
vol01 on
primary_disk1
vol01 on
mirror_disk1
N
e
t
B
a
c
k
u
p
c
r
e
a
t
e
s
a
t
e
m
p
o
r
a
r
y
V
x
V
M
d
i
s
k
g
r
o
u
p
(
c
l
o
n
e
)
c
l
o
n
e
_
d
g
_
1
_
c
l
o
n
e
o
n
m
i
r
r
o
r
_
d
i
s
k
1
.
Client data is in:
- file system /fs_1
- configured over VxVM volume /dev/vx/rdsk/dg_1/vol01
Kommentare zu diesen Handbüchern