cancel
Showing results for 
Search instead for 
Did you mean: 

MSDP conversion failed during upgrade 2.6.1 on NBU Appliance

Zamantatari
Level 2
Partner Accredited

We have 5220 appliance with version 2.5.4 upgrading to 2.6.1 the software part upgraded successfully.

But upgrades has failed in the last section of the MSDP conversion after running 3 hours.  There is a partition created by the upgrade utility for MSDP Catalog, and the size of this is calculated by the upgrade utility.  it created size aroung 215GB the final stage of conversion fails with an out of space condition. 

/dev/vx/dsk/nbuapp/pdcatvol  217G  217G     0 100% /msdp/cat     100% used.Smiley Sad

What do I do now to resume the MSDP conversion to complete the upgrade after expanding the newly created partition (from the web-interface of the appliance or CLISH)

Which scirpts help me to complete my last part on the appliance.

Need experts opinion. THANKS

1 ACCEPTED SOLUTION

Accepted Solutions

Zamantatari
Level 2
Partner Accredited

 

SOLUTION :   This is know issue when you upgrading appliance 5220 from version 2.5.x to 2.6.x   but first verify that MSDP catalog partition 100% used from CLISH

Manage> Storage > Disk Partitions 

You will see MSDP catalog partition 100% used.

Now perform the below steps.

Go to the maintainance shell if it is locked run the below script after the passowrd.

/opt/Symantec/scspagent/IPS/sisipsoverride.sh

then elevate to maintainance shell and follow the below steps.

#  rm -rf /msdp/data/dp1/pdvol/databases/crdbdump

#  rm -rf /msdp/data/dp1/pdvol/databases/crdbrecover

#  rm -rf /msdp/data/dp1/pdvol/databases/pddb-convert3

#  rm -rf /msdp/cat/databases/crdbdump

#  rm -rf /msdp/cat/databases/crdbrecover

#  rm -rf /msdp/cat/databases/pddb-convert3

 

#  cp /msdp/data/dp1/pdvol/tmp/convert3/.cnf /msdp/data/dp1/pdvol/data

#  /usr/openv/pdde/pdconfigure/scripts/installers/PDDE_convert.sh -y --storagepath=/msdp/data/dp1/pdvol --newdbpath=/msdp/cat

Note: Under /log check the timestamp of Directory named patch_log_2.6.1_xxxxxxxxxx  to run below command

# source /log/patch_log_2.6.1_<digits>/common.sh

#  protect_dedupe_catalog

#  /usr/openv/pdde/pdcr/bin/stconv --cleanup

Good Luck.

 

View solution in original post

2 REPLIES 2

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

IMHO you need assistance from Veritas Support.

Please log a call without delay.

Zamantatari
Level 2
Partner Accredited

 

SOLUTION :   This is know issue when you upgrading appliance 5220 from version 2.5.x to 2.6.x   but first verify that MSDP catalog partition 100% used from CLISH

Manage> Storage > Disk Partitions 

You will see MSDP catalog partition 100% used.

Now perform the below steps.

Go to the maintainance shell if it is locked run the below script after the passowrd.

/opt/Symantec/scspagent/IPS/sisipsoverride.sh

then elevate to maintainance shell and follow the below steps.

#  rm -rf /msdp/data/dp1/pdvol/databases/crdbdump

#  rm -rf /msdp/data/dp1/pdvol/databases/crdbrecover

#  rm -rf /msdp/data/dp1/pdvol/databases/pddb-convert3

#  rm -rf /msdp/cat/databases/crdbdump

#  rm -rf /msdp/cat/databases/crdbrecover

#  rm -rf /msdp/cat/databases/pddb-convert3

 

#  cp /msdp/data/dp1/pdvol/tmp/convert3/.cnf /msdp/data/dp1/pdvol/data

#  /usr/openv/pdde/pdconfigure/scripts/installers/PDDE_convert.sh -y --storagepath=/msdp/data/dp1/pdvol --newdbpath=/msdp/cat

Note: Under /log check the timestamp of Directory named patch_log_2.6.1_xxxxxxxxxx  to run below command

# source /log/patch_log_2.6.1_<digits>/common.sh

#  protect_dedupe_catalog

#  /usr/openv/pdde/pdcr/bin/stconv --cleanup

Good Luck.