Migrate Data Protector 7.0x to Data Protector 9.0x In section installation source it was recommended to use a patched installation source for the upgrade. This method must not be used for upgrades from Data Protector version en 8.13 and newer, as it will cause serious damages in the internal database (no ! available"possible#. $or versions older 8.13 it is too recommended not to use a patched installation source due to missing tests b% engineering. In this case, please install Data Protector &.' rst followed b% installation of current patch bundle. ne e!ception to use a patched installation source is when doing a new installation ()green eld approach* + i.e. indows -'1- - /luster /ell 0erver#, es there are no depenencies for upgrading internal database.
Data Protector 7.0 was introduced on 16.04.2012 and meanwhile superseded b two ma!or releases. "n #0.06.2016 the time has come and the support $or Data Protector 7.0x ends. %hus& it is time $or all undecided customer to upgrade to the current 'ersion ( Data Protector 9.06. ) big step& as with the upgrade the internal database will change. Man customers ha'e been postponed this step due to uncertainties with the upgrade. *ewlett Pac+ard Pac+ard ,nterprise alread released in the past two ad'isories and explained how the upgrade to the new internal database can be per$ormed -please re$er to http//h2064.www2.hpe http//h2064.www2.hpe.com/hpsc/doc/publi .com/hpsc/doc/public/displadocd3c04#0769 c/displadocd3c04#0769 and and http//h2066.www2.hpe.com/hpsc/doc/publi http//h2066.www2.hpe .com/hpsc/doc/public/displadocd3c049#7621 c/displadocd3c049#7621. . *owe'er& the change to the new 'ersion also o5ers opportunities& the bac+up and reco'er strateg -e.g. bac+up to *P, tore"nce might be reconsidered& reconsidered& as the current 'ersion o5ers a lot o$ new $eatures compared to Data Protector 7.0x. ome selected $eatures •
#P) emote 8op support
•
)utomated pause and resume o$ bac+up !obs
•
)ccelerated Mware bac+up through #P) snapshot management
•
8ached Mware single item reco'er direct $rom *P, #P) snapshot or mart 8ache
•
Mware Power "n and :i'e Migrate $rom *P, #P) snapshot or mart 8ache
•
tore"nce 8atalst o'er ;iber 8hannel and ;ederated 8atalst support
•
Data Domain appliance to appliance replication management
•
)utomated eplication nchroni
"n the web there are man instructions& but no step=b=step documentation $or upgrading to latest 'ersion. %here$ore& this article deals with the upgrade o$ Data Protector 7.0x to Data Protector 9.06 and o5ers all re>uired steps as a runboo+. Some notes before you can start: •
•
•
•
•
•
%his step=b=step documentation is 'alid $or 8ell Manager nstallation on ?indows 200@ or ?indows 2012. t is assumed that the path 8AProgram ;ilesA"mniBac+ and 8AProgramDataA"mniBac+ is used. %his runboo+ can also be used $or :inux or de'iating installation paths. ?hen migrating -this is a separate and subse>uent process the D8B; Cles are con'erted into a new $ormat. %he new D8B; $ormat is approximatel 1. times to 2 times larger than the old $ormat& it is there$ore enough $ree dis+ space re>uired. )ll existing Data Protector licenses should be regenerated in ad'ance using the new licensing portal https//menterpriselicense.hpe.com & old ",E# licenses can no longer be used in current Data Protector 'ersions. "$ course ou can onl be migrate licenses& $or which there is a maintenance contract. hould the upgrade $ail despite these detailed instructions& there is alwas a rollbac+ to Data Protector 7.0x possible. But ou need to ha'e our DP 7.0 installation sources and the most recentl installed patch bundle a'ailable. t is recommended to mo'e all used and appendable media into a separate pool so that mixing o$ to be migrated and new media is a'oided. %he 8atalog Migration o$ D8B; Cles is a downstream process and can either be per$ormed directl a$ter the upgrade or a$ter a $ew wee+s. $ possible plan $or no acti'it on the 8ell er'er during the catalog migration.
•
•
•
•
t is recommended to test the upgrade using a 'irtual machine. Fsing the exported Data Protector 7 database it can be easil imported into the test en'ironment. ?ith Data Protector 9.0x name resolution is top most priorit to a'oid problems during or a$ter the migration. t is there$ore re>uired that the 8ell Manager is alwas been resol'ed -;GDH& short and re'erse. B upgrading to the latest 'ersion earlier operating sstem 'ersions ma stop wor+ing& as e.g. ?indows 200# is no longer supported. n such a case and i$ the client is running as a 'irtual machine& the client can be bac+ed up with the Mware or *per= integration in the $uture. %he $ollowing steps are onl one possible path $or migration& there are se'eral was to upgrade. %hus the success is not guaranteed& because a success$ul upgrade also depends on the existing en'ironment. %his runboo+ were howe'er alread carried out during man success$ul migrations and thus the instructions should be appropriate $or our en'ironment too.
Preparation: •
8hec+ing the consistenc o$ the internal database. %here must be no errors appear. $ errors are seen ou need to address them be$ore the upgrade to DP 9.0x can be continued. %o chec+ the DB use the command o
omnidbchec+ =extended
8leaning o$ the old internal database
•
o
8lose Data Protector IF
o
omnidbutil =clear
o
omnidb =strip
o
omnidbutil =purge =sessions 90 -or correspondingl higher& lower 'alue
o
omnidbutil =purge =dcb$ =$orce
o
omnitrig =stop
o
omnistat -no bac+up !ob must run
o
omnidbutil =purge =Clenames =$orce
"pen Data Protector IF
o
•
Monitor =J 8urrent essions
elect the purge session
?atch progress and wait $or the end o$ the process
During the purge o$ Clenames no bac+ups can run& scheduled !obs are >ueued and will onl be executed i$ the purge has been completed. n larger en'ironments& it ma be necessar to cancel the purge process and continue at a later time. %o stop the purge use the command omnidbutil =purgeKstop . )lternati'el& the purge can also be per$ormed selecti'el $or indi'idual clients. 8reate directories $or the migration
•
o
m+dir 8AmigrationAmmdb
o
m+dir 8AmigrationAcdb
o
m+dir 8AmigrationAother
o
m+dir 8AmigrationAprogram ClesAomnibac+
o
m+dir 8AmigrationAprogram dataAomnibac+
De$rag the internal database using export and import
•
o
t must not run an bac+ups& chec+ with the command omnistat
o
omnidbutil =writedb =mmdb 8AmigrationAmmdb =cdb 8AmigrationAcdb
o
)t the end o$ the export ou are prompted to cop some special directories. Eou need to cop them be$ore the database is re=enabled. %hese are usuall the D8B; and MI directories& but there might be other directories re>uired to cop. ;or sa$et the $ollowing directories are copied
robocop L8AProgramDataA"mniBac+ADB40AD8B;L 8AmigrationAotherAD8B; . /e /r1 /w1
8oping ma be necessar $or $urther D8B; directories. n this case& the cop operation is continued in line.
robocop L8AProgramDataA"mniBac+ADB40AmsgL 8AmigrationAotherAmsg . /e
/r1 /w1 robocop L8AProgramDataA"mniBac+ADB40AmetaL 8AmigrationAotherAmeta
. /e /r1 /w1 robocop L8AProgramDataA"mniBac+ADB40A'ssdbL 8AmigrationAotherA'ssdb .
/e /r1 /w1 o
How the exported database can be imported again& the $ollowing command is used omnidbutil =readdb =mmdb 8AmigrationAmmdb =cdb 8Amigration cdb
o
•
•
$ the command omnidbinit =$orce was used prior importing the database the D8B;& MI and M,%) directories need to be copied bac+ into the old location& because the original $olders are deleted when the database is initiali
;or sa$et& the omnidbchec+ =extended is per$ormed again& it must not show an errors. $ necessar& temporar Cles in 8AProgramDataA"mniBac+Atmp and 8AProgramDataA"mniBac+Alog can be remo'ed. But please be beware not all log Cles can be deleted. ;iles as the media.log must be retained& because it might be re>uired in case o$ reco'ering data. %he media.log pro'ides in$ormation when and in what order a media was used during a bac+up. 8op/bac+up the entire Data Protector installation
•
o
omnis' =stop
o
robocop L8AProgram ;ilesA"mniBac+L 8AmigrationAprogramClesAomnibac+ . /e /r1 /w1 /purge
o
robocop 8AProgramDataA"mniBac+ 8AmigrationAprogramdataAomnibac+ . /e /r1 /w1 /purge
o
omnis' =start
Installation sources:
•
t is highl recommended to use a patched installation source $or the installation. %o this end& the $ollowing steps are carried out on a temporar ?indows ser'er on which no Data Protector installation exists. o
o
•
Per$orm the Data Protector 9.0 installation as an administrator -run as admin and select the installation o$ the installation ser'er. Ho an other components apart $rom the installation ser'er will be installed. nstall additional patch bundle and patches a$ter the installation has been completed. Please re$er to https//www.data=protector.org/wordpress/2016/04/hpe= data=protector=patch=bundle=9=06=$eatures/ and https//www.data= protector.org/wordpress/201#/06/basics=installation=order=patches/
%he so updated installation can be used as an installation source $or the upgrade o$ the 8ell Manager. %o this end& all the $olders o$ the depot $rom the temporar installation ser'er are copied to the Data Protector 8ell Manager 7.0x -e.g. to 8AmigrationAinstall . "nce done& the temporar installation ser'er can be uninstalled.
Upgrade: •
•
•
%he upgrade is carried out with the patched installation sources and setup.exe is executed as an administrator -run as admin. t is recommended to lea'e all the proposed de$aults during installation and thus per$orm the upgrade. During the upgrade parts o$ the old database are exported and prepared $or import into the new database. %his process ma ta+e some time depending on the si
;ollowing this part the installation o$ Data Protector 9.0x is continued normall.
•
•
•
)$ter the upgrade it is recommended to re'iew and ad!ust the conCguration Cles global and omnirc. n addition& the bac+up speciCcation o$ the 8ell Manager should be chec+ed. During the upgrade to DP 9.06 the existing speciCcation has been di'ided into an DB and a Clesstem speciCcation.
After the upgrade: •
•
)$ter the upgrade the D8B; directories should be migrated to the new $ormat. n principle there are two options the immediate migration o$ all D8B; Cles or migration o$ the D8B; Cles $or long=term bac+ups onl. %he second wa is the pre$erred method& as ou wait $or the expiration o$ the short=term protection o$ the old media and thus these D8B; Cles will not ha'e to be migrated. )$ter $our to six wee+s ou migrate onl media with long=term protection. e>uired steps $or both was
•
o
o
"pen administrati'e command line and change into the director 8AProgram ;ilesA"mniBac+Abin un the command perl omnimigrate.pl =startKcatalogKmigration
o
o
o
%he D8B; migration is 'er time consuming& howe'er& runs in the bac+ground and does not ha'e to be acti'el monitored. )$ter the D8B; migration is done chec+ that all the media ha'e been migrated. ;or this purpose& the command perl omnimigrate.pl =reportKoldKcatalog is used. )s a result LD8B; -0 ClesL is expected. hould still Cles are displaed& the $ollowing steps must not be executed. $ new bac+ups ha'e alread run during D8B; migration& it ma happen that D8B; 2.0 Cles were created in the DB40AD8B; directories. %he Cles $ound in DB40AD8B; are mo'ed
o
to 8AProgramDataA"mniBac+Aser'erADB@0AD8B;Adcb$1=4 . %he Cles can be distributed& in principle it is not necessar to maintain a certain order. o
%o adapt the change the command omnidbutil =remapKdcdir is executed a$ter mo'ing the D8B; Cles. %he old D8B; directories will be remo'ed& the $ollowing commands are
o
used
o
o
o
omnidbutil =remo'eKdcdir L8AProgramDataA"mniBac+ADB40AD8B;L
omnidbutil =remo'eKdcdir L8AProgramDataA"mniBac+ADB40Adcb$1L
omnidbutil =remo'eKdcdir L8AProgramDataA"mniBac+ADB40Adcb$2L
omnidbutil =remo'eKdcdir L8AProgramDataA"mniBac+ADB40Adcb$#L
omnidbutil =remo'eKdcdir L8AProgramDataA"mniBac+ADB40Adcb$4L
Depending on the si
o
Rollback:
How the DB40 path can be deleted ( 8AProgramDataA"mniBac+ADB40
•
•
•
•
•
$ the upgrade $ails& ou can rollbac+ at an time& assuming that no migration o$ Cles D8B; Cles began. %he $ailed Data Protector 9.0x installation needs to be remo'ed and installation o$ Data Protector 7.0x and patches to be done. %he command omnidbutil =readdb =mmdb 8AmigrationAmmdb =cdb 8AmigrationAcdb will be used to re=import the old database. )dditional directories as D8B;& MI and M,%)& need to be copied bac+ to the DB40 path. %he conCguration $rom the pre'iousl sa'ed Data Protecor installation -8AmigrationAomnibac+Aprogramdata needs to be copied to 8AProgramDataA"mniBac+AconCgAser'er so that the initial state is restored.
