Naming convention for disks, sub-disks and understanding volumes layout for different versions of NetBackup and PureDisk appliances as presented in vxprint output
| Article:TECH182732 | | | Created: 2012-03-01 | | | Updated: 2012-05-29 | | | Article URL http://www.symantec.com/docs/TECH182732 |
| NOTE: If you are experiencing this particular known issue, we recommend that you Subscribe to receive email notification each time this article is updated. Subscribers will be the first to learn about any releases, status changes, workarounds or decisions made. |
Problem
The purpose of this technote is to show different naming convention for disk, sub-disks adopted for different versions of NetBackup and PureDisk appliance and to discuss the disk volumes created for these versions.
Environment
All hardware models and versions of NetBackup and PureDisk appliances.
Cause
Different naming convention and different volume layout causing confusion for customers, partners, field engineers, consultants and the support engineers.
Solution
Details are discussed below, but in summary disk names are different between pre-2.0 versions and post-2.0 versions of NetBackup appliances, disk names are kept same in all PureDisk appliance versions, and there is a difference in the names and number of disk volumes created for pre-2.0.2 and post-2.0.2 versions.
NetBackup 5200 and 5220 appliances:
Example 1:
5200 Appliance Version is 2.0.2
=========================
# vxprint
Disk group: nbuapp
TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0
dg nbuapp nbuapp - - - - - -
dm disk_1 disk_1 - 70277240304 - - - -
v advol fsgen ENABLED 21082160 - ACTIVE - -
pl advol-01 advol ENABLED 21082160 - ACTIVE - -
sd disk_1-02 advol-01 ENABLED 2097152 0 - - -
sd disk_1-06 advol-01 ENABLED 18985008 2097152 - - -
v catvol fsgen ENABLED 2097152 - ACTIVE - -
pl catvol-01 catvol ENABLED 2097152 - ACTIVE - -
sd disk_1-03 catvol-01 ENABLED 64 0 - - -
sd disk_1-07 catvol-01 ENABLED 2095120 64 - - -
sd disk_1-08 catvol-01 ENABLED 1968 2095184 - - -
v pdvol fsgen ENABLED 70254060992 - ACTIVE - -
pl pdvol-01 pdvol ENABLED 70254060992 - ACTIVE - -
sd disk_1-01 pdvol-01 ENABLED 56221792256 0 - - -
sd disk_1-04 pdvol-01 ENABLED 7728399296 56221792256 - - -
sd disk_1-05 pdvol-01 ENABLED 6303869440 63950191552 - - -
Example 2:
5200 appliance with a version prior to 2.0
==========================================
# vxprint
Disk group: nbuapp
TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0
dg nbuapp nbuapp - - - - - -
dm sdb disk_1 - 9755774656 - - - -
v advol fsgen ENABLED 2097152 - ACTIVE - -
pl advol-01 advol ENABLED 2097152 - ACTIVE - -
sd sdb-01 advol-01 ENABLED 2097152 0 - - -
v pdsnapvol fsgen ENABLED 64 - ACTIVE - -
pl pdsnapvol-01 pdsnapvol ENABLED 64 - ACTIVE - -
sd sdb-02 pdsnapvol-01 ENABLED 64 0 - - -
v pdvol fsgen ENABLED 9753677440 - ACTIVE - -
pl pdvol-01 pdvol ENABLED 9753677440 - ACTIVE - -
sd sdb-03 pdvol-01 ENABLED 7804619648 0 - - -
sd sdb-04 pdvol-01 ENABLED 1949057792 7804619648 - - -
Notes:
=====
As shown above, disk naming convention was different, it was sdb in pre-2,0 versions instead of disk_1, disk_2 etc in post-2.0 versions of NetBackup appliances.
Also note that the catvol is not in pre-2.0.2 versions, for these versions catalog is kept in the advol.
With the introduction of AdvancedDisk feature in version 2.0.2, catvol (Catalog volume) and advol (AdvancedDisk volume) are created separately.
After upgrading the same appliance (presented in Example 2 above) to version 2.0.2, vxprint output now looks as shown below, note that catvol is now a separate vol.
# vxprint
Disk group: nbuapp
TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0
dg nbuapp nbuapp - - - - - -
dm disk_1 disk_1 - 9755774656 - - - -
v advol fsgen ENABLED 2097152 - ACTIVE - -
pl advol-01 advol ENABLED 2097152 - ACTIVE - -
sd disk_1-01 advol-01 ENABLED 2097152 0 - - -
v catvol fsgen ENABLED 2097152 - ACTIVE - -
pl catvol-01 catvol ENABLED 2097152 - ACTIVE - -
sd disk_1-02 catvol-01 ENABLED 2097152 0 - - -
v pdvol fsgen ENABLED 9751580352 - ACTIVE - -
pl pdvol-01 pdvol ENABLED 9751580352 - ACTIVE - -
sd disk_1-03 pdvol-01 ENABLED 7804619648 0 - - -
sd disk_1-04 pdvol-01 ENABLED 1946960704 7804619648 - - -
Example 3:
5220 appliance with Storage Shelf (version 2.0)
====================================
vxprint output
===========
Disk group: nbuapp
TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0
dg nbuapp nbuapp - - - - - -
dm disk_1 disk_1 - 9755774656 - - - -
dm disk_2 disk_2 - 76171777984 - - - -
v advol fsgen ENABLED 9755774592 - ACTIVE - -
pl advol-01 advol ENABLED 9755774592 - ACTIVE - -
sd disk_1-01 advol-01 ENABLED 1951154944 0 - - -
sd disk_1-03 advol-01 ENABLED 7804619648 1951154944 - - -
v pdsnapvol fsgen ENABLED 64 - ACTIVE - -
pl pdsnapvol-01 pdsnapvol ENABLED 64 - ACTIVE - -
sd disk_1-02 pdsnapvol-01 ENABLED 64 0 - - -
v pdvol fsgen ENABLED 76171777984 - ACTIVE - -
pl pdvol-01 pdvol ENABLED 76171777984 - ACTIVE - -
sd disk_2-01 pdvol-01 ENABLED 76171777984 0 - - -
Notes:
As a Storage Shelf is attached to this 5220 Base Unit, now there are two disks, disk_1 and disk_2, but note that catvol is not present in this configuration as this vol is added only from version 2.0.2.
Example 4:
5220 appliance with Storage Shelf (version 2.0.2)
======================================
# vxprint
Disk group: nbuapp
TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0
dg nbuapp nbuapp - - - - - -
dm disk_1 disk_1 - 9755774656 - - - -
dm disk_2 disk_2 - 76171777984 - - - -
v advol fsgen ENABLED 1560281088 - ACTIVE - -
pl advol-01 advol ENABLED 1560281088 - ACTIVE - -
sd disk_1-02 advol-01 ENABLED 1560281088 0 - - -
v catvol fsgen ENABLED 1951154176 - ACTIVE - -
pl catvol-01 catvol ENABLED 1951154176 - ACTIVE - -
sd disk_1-01 catvol-01 ENABLED 2097152 0 - - -
sd disk_1-03 catvol-01 ENABLED 1949057024 2097152 - - -
v pdvol fsgen ENABLED 6243221504 - ACTIVE - -
pl pdvol-01 pdvol ENABLED 6243221504 - ACTIVE - -
sd disk_1-04 pdvol-01 ENABLED 6243221504 0 - - -
Notes:
catvol is configured and displayed as this is an appliance of version 2.0.2.
When a Storage Shelf is configured with a NetBackup 5200 appliance running any version older than 2.0.2, and 'Expand' command is used, the size of the catalog volume increases from it's current default size of 1TB to 4.5TB. In version 2.0.2 and later, 'Expand' command is replaced with 'Add' and 'Resize' commands.
Note that the ability to reduce the size of the catalog volume is not supported in version 2.0 when the appliance has a Storage Shelf attached, and it's role is Master server appliance. This support of reducing the size of the catalog volume is included only from version 2.0.2.
PureDisk appliances:
================
> applianceversion
Appliance version is 1.4.2
# vxprint
Disk group: PDDG
TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0
dg PDDG PDDG - - - - - -
dm sdb sdb - 41863568 - - - -
v Storage fsgen ENABLED 41863168 - ACTIVE - -
pl Storage-01 Storage ENABLED 41863168 - ACTIVE - -
sd sdb-01 Storage-01 ENABLED 41863168 0 - - -
> applianceversion
Appliance version is 1.4.1.1
# vxprint
Disk group: PDDG
TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0
dg PDDG PDDG - - - - - -
dm sdb sdb - 70277306352 - - - -
v Storage fsgen ENABLED 70277304320 - ACTIVE - -
pl Storage-01 Storage ENABLED 70277304320 - ACTIVE - -
sd sdb-01 Storage-01 ENABLED 70277304320 0 - - -
Notes:
As you see the disk names are kept same in different versions of PureDisk appliances.
|
|
Related Articles
Article URL http://www.symantec.com/docs/TECH182732
Terms of use for this information are found in Legal Notices
Thank you.