- \n
- 3PAR Remote Copy support<\/li>\n
- Automated pause and resume of backup jobs<\/li>\n
- Accelerated VMware backup through 3PAR snapshot management<\/li>\n
- Cached VMware single item recovery direct from HPE 3PAR snapshot or Smart Cache<\/li>\n
- VMware Power On and Live Migrate from HPE 3PAR snapshot or Smart Cache<\/li>\n
- StoreOnce Catalyst over Fiber Channel and Federated Catalyst support<\/li>\n
- Data Domain appliance to appliance replication management<\/li>\n
- Automated Replication Synchronization – synchronize metadata of replicated objects between Cell Manager<\/li>\n<\/ul>\n
On the web there are many instructions, but no step-by-step documentation for upgrading to latest version. Therefore, this article deals with the upgrade of Data Protector 7.0x to Data Protector 9.06 and offers all required steps as a runbook.<\/p>\n
Some notes before you can start:<\/b><\/p>\n
- \n
- This step-by-step documentation is valid for Cell Manager Installation on Windows 2008 or Windows 2012. It is assumed that the path
C:\\Program Files\\OmniBack<\/code> andC:\\ProgramData\\OmniBack<\/code> is used. This runbook can also be used for Linux or deviating installation paths.\n<\/li>\n- When migrating (this is a separate and subsequent process) the DCBF files are converted into a new format. The new DCBF format is approximately 1.5 times to 2 times larger than the old format, it is therefore enough free disk space required.<\/li>\n
- All existing Data Protector licenses should be regenerated in advance using the new licensing portal https:\/\/myenterpriselicense.hpe.com<\/a>, old OVKEY3 licenses can no longer be used in current Data Protector versions. Of course you can only be migrate licenses, for which there is a maintenance contract.<\/li>\n
- Should the upgrade fail despite these detailed instructions, there is always a rollback to Data Protector 7.0x possible. But you need to have your DP 7.0 installation sources and the most recently installed patch bundle available.<\/li>\n
- It is recommended to move all used and appendable media into a separate pool so that mixing of to be migrated and new media is avoided.<\/li>\n
- The Catalog Migration of DCBF files is a downstream process and can either be performed directly after the upgrade or after a few weeks. If possible plan for no activity on the Cell Server during the catalog migration.<\/li>\n
- It is recommended to test the upgrade using a virtual machine. Using the exported Data Protector 7 database it can be easily imported into the test environment.<\/li>\n
- With Data Protector 9.0x name resolution is top most priority to avoid problems during or after the migration. It is therefore required that the Cell Manager is always been resolved (FQDN, short and reverse).<\/li>\n
- By upgrading to the latest version earlier operating system versions may stop working, as e.g. Windows 2003 is no longer supported. In such a case and if the client is running as a virtual machine, the client can be backed up with the VMware or Hyper-V integration in the future.<\/li>\n
- The following steps are only one possible path for migration, there are several ways to upgrade. Thus the success is not guaranteed, because a successful upgrade also depends on the existing environment. This runbook were however already carried out during many successful migrations and thus the instructions should be appropriate for your environment too.<\/li>\n<\/ul>\n
Preparation:<\/b><\/p>\n
- \n
- Checking the consistency of the internal database. There must be no errors appear. If errors are seen you need to address them before the upgrade to DP 9.0x can be continued. To check the IDB use the command:\n
- \n
omnidbcheck -extended<\/code><\/li>\n<\/ul>\n<\/li>\n- Cleaning of the old internal database:\n
- \n
- Close Data Protector GUI<\/li>\n
omnidbutil -clear<\/code><\/li>\nomnidb -strip<\/code><\/li>\nomnidbutil -purge -sessions 90<\/code> (or correspondingly higher, lower value)<\/li>\nomnidbutil -purge -dcbf -force<\/code><\/li>\nomnitrig -stop<\/code><\/li>\nomnistat<\/code> (no backup job must run)<\/li>\nomnidbutil -purge -filenames -force<\/code><\/li>\n- Open Data Protector GUI\n
- \n
- Monitor -> Current Sessions<\/li>\n
- Select the purge session<\/li>\n
- Watch progress and wait for the end of the process<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n
- During the purge of filenames no backups can run, scheduled jobs are queued and will only be executed if the purge has been completed. In larger environments, it may be necessary to cancel the purge process and continue at a later time. To stop the purge use the command
omnidbutil -purge_stop<\/code>. Alternatively, the purge can also be performed selectively for individual clients.<\/li>\n- Create directories for the migration:\n
- \n
mkdir C:\\migration\\mmdb<\/code><\/li>\nmkdir C:\\migration\\cdb<\/code><\/li>\nmkdir C:\\migration\\other<\/code><\/li>\nmkdir C:\\migration\\program files\\omniback<\/code><\/li>\nmkdir C:\\migration\\program data\\omniback<\/code><\/li>\n<\/ul>\n<\/li>\n- Defrag the internal database using export and import\n
- \n
- It must not run any backups, check with the command
omnistat<\/code><\/li>\nomnidbutil -writedb -mmdb C:\\migration\\mmdb -cdb C:\\migration\\cdb<\/code><\/li>\n- At the end of the export you are prompted to copy some special directories. You need to copy them before the database is re-enabled. These are usually the DCBF and MSG directories, but there might be other directories required to copy. For safety the following directories are copied:\n
- \n
robocopy \"C:\\ProgramData\\OmniBack\\DB40\\DCBF\" C:\\migration\\other\\DCBF *.* \/e \/r:1 \/w:1<\/code><\/li>\n- Copying may be necessary for further DCBF directories. In this case, the copy operation is continued in line.<\/li>\n
robocopy \"C:\\ProgramData\\OmniBack\\DB40\\msg\" C:\\migration\\other\\msg *.* \/e \/r:1 \/w:1<\/code><\/li>\nrobocopy \"C:\\ProgramData\\OmniBack\\DB40\\meta\" C:\\migration\\other\\meta *.* \/e \/r:1 \/w:1<\/code><\/li>\nrobocopy \"C:\\ProgramData\\OmniBack\\DB40\\vssdb\" C:\\migration\\other\\vssdb *.* \/e \/r:1 \/w:1<\/code><\/li>\n<\/ul>\n<\/li>\n- Now the exported database can be imported again, the following command is used:\n
- \n
omnidbutil -readdb -mmdb C:\\migration\\mmdb -cdb C:\\migration cdb<\/code><\/li>\n<\/ul>\n<\/li>\n- If the command
omnidbinit -force<\/code> was used prior importing the database the DCBF, MSG and META directories need to be copied back into the old location, because the original folders are deleted when the database is initialized. For this, however, the Data Protector services must be stopped. If necessary, additional DCBF directories for the internal database must be created beforehand.<\/li>\n<\/ul>\n<\/li>\n- For safety, the
omnidbcheck -extended<\/code> is performed again, it must not show any errors.<\/li>\n- If necessary, temporary files in
C:\\ProgramData\\OmniBack\\tmp<\/code> andC:\\ProgramData\\OmniBack\\log<\/code> can be removed. But please be beware: not all log files can be deleted. Files as the media.log must be retained, because it might be required in case of recovering data. The media.log provides information when and in what order a media was used during a backup.<\/li>\n- Copy\/backup the entire Data Protector installation:\n
- \n
omnisv -stop<\/code><\/li>\nrobocopy \"C:\\Program Files\\OmniBack\" C:\\migration\\programfiles\\omniback *.* \/e \/r:1 \/w:1 \/purge<\/code><\/li>\nrobocopy C:\\ProgramData\\OmniBack C:\\migration\\programdata\\omniback *.* \/e \/r:1 \/w:1 \/purge<\/code><\/li>\nomnisv -start<\/code><\/li>\n<\/ul>\n- \n<\/ul>\n<\/li>\n<\/ul>\n
- It is highly recommended to use a patched installation source for the installation. To this end, the following steps are carried out on a temporary Windows server on which no Data Protector installation exists.\n
- \n
- Perform the Data Protector 9.0 installation as an administrator (run as admin) and select the installation of the installation server. No any other components apart from the installation server will be installed.<\/li>\n
- Install additional patch bundle and patches after the installation has been completed. Please refer to https:\/\/www.data-protector.org\/wordpress\/2016\/04\/hpe-data-protector-patch-bundle-9-06-features\/<\/a> and https:\/\/www.data-protector.org\/wordpress\/2013\/06\/basics-installation-order-patches\/<\/a><\/li>\n<\/ul>\n<\/li>\n
- The so updated installation can be used as an installation source for the upgrade of the Cell Manager. To this end, all the folders of the depot from the temporary installation server are copied to the Data Protector Cell Manager 7.0x (e.g. to
C:\\migration\\install<\/code>). Once done, the temporary installation server can be uninstalled.<\/li>\n<\/ul>\nUpgrade:<\/b><\/p>\n
- \n
- The upgrade is carried out with the patched installation sources and setup.exe is executed as an administrator (run as admin).<\/li>\n
- It is recommended to leave all the proposed defaults during installation and thus perform the upgrade.<\/li>\n
- During the upgrade parts of the old database are exported and prepared for import into the new database. This process may take some time depending on the size of the environment; the process should not be interrupted.<\/li>\n
![](\"https:\/\/www.data-protector.org\/wordpress\/wp-content\/uploads\/2016\/05\/runbook_1.png\"\/)
<\/p>\n - Following this part the installation of Data Protector 9.0x is continued normally.<\/li>\n
- After the upgrade it is recommended to review and adjust the configuration files
global<\/code> andomnirc<\/code>.<\/li>\n- In addition, the backup specification of the Cell Manager should be checked. During the upgrade to DP 9.06 the existing specification has been divided into an IDB and a filesystem specification.<\/li>\n<\/ul>\n
After the upgrade:<\/b><\/p>\n
- \n
- After the upgrade the DCBF directories should be migrated to the new format. In principle there are two options: the immediate migration of all DCBF files or migration of the DCBF files for long-term backups only.<\/li>\n
- The second way is the preferred method, as you wait for the expiration of the short-term protection of the old media and thus these DCBF files will not have to be migrated. After four to six weeks you migrate only media with long-term protection.<\/li>\n
- Required steps for both ways:\n
- \n
- Open administrative command line and change into the directory
C:\\Program Files\\OmniBack\\bin<\/code><\/li>\n- Run the command:
perl omnimigrate.pl -start_catalog_migration<\/code><\/li>\n- The DCBF migration is very time consuming, however, runs in the background and does not have to be actively monitored.<\/li>\n
- After the DCBF migration is done check that all the media have been migrated. For this purpose, the command
perl omnimigrate.pl -report_old_catalog<\/code> is used. As a result\"DCBF (0 files)\"<\/code> is expected. Should still files are displayed, the following steps must not be executed.<\/li>\n- If new backups have already run during DCBF migration, it may happen that DCBF 2.0 files were created in the
DB40\\DCBF*<\/code> directories.<\/li>\n- The files found in
DB40\\DCBF*<\/code> are moved toC:\\ProgramData\\OmniBack\\server\\DB80\\DCBF\\dcbf1-4<\/code>. The files can be distributed, in principle it is not necessary to maintain a certain order.<\/li>\n- To adapt the change the command
omnidbutil -remap_dcdir<\/code> is executed after moving the DCBF files.<\/li>\n- The old DCBF directories will be removed, the following commands are used:\n
- \n
omnidbutil -remove_dcdir \"C:\\ProgramData\\OmniBack\\DB40\\DCBF\"<\/code><\/li>\nomnidbutil -remove_dcdir \"C:\\ProgramData\\OmniBack\\DB40\\dcbf1\"<\/code><\/li>\nomnidbutil -remove_dcdir \"C:\\ProgramData\\OmniBack\\DB40\\dcbf2\"<\/code><\/li>\nomnidbutil -remove_dcdir \"C:\\ProgramData\\OmniBack\\DB40\\dcbf3\"<\/code><\/li>\nomnidbutil -remove_dcdir \"C:\\ProgramData\\OmniBack\\DB40\\dcbf4\"<\/code><\/li>\n<\/ul>\n<\/li>\n- Depending on the size of the environment less or more DCBF directories may be present and must be removed accordingly.<\/li>\n
- With the command
perl omnimigrate.pl -remove_old_catalog<\/code> the old catalog is removed.<\/li>\n- In the file
C:\\ProgramData\\OmniBack\\Config\\server\\options\\global<\/code> the variableSupportOldDCBF=0<\/code> should be set, but it can also be removed (default after upgrade is 1).<\/li>\n- Now the DB40 path can be deleted –
C:\\ProgramData\\OmniBack\\DB40<\/code><\/li>\n<\/ul>\n<\/li>\n<\/ul>\nRollback:<\/b><\/p>\n
- \n
- If the upgrade fails, you can rollback at any time, assuming that no migration of files DCBF files began.<\/li>\n
- The failed Data Protector 9.0x installation needs to be removed and installation of Data Protector 7.0x and patches to be done.<\/li>\n
- The command
omnidbutil -readdb -mmdb C:\\migration\\mmdb -cdb C:\\migration\\cdb<\/code> will be used to re-import the old database.<\/li>\n- Additional directories as DCBF, MSG and META, need to be copied back to the DB40 path.<\/li>\n
- The configuration from the previously saved Data Protecor installation (
C:\\migration\\omniback\\programdata<\/code>) needs to be copied toC:\\ProgramData\\OmniBack\\config\\server<\/code> so that the initial state is restored.<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"Update 2016\/0705: 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 versionen 8.13 and newer, as it will cause serious damages in the internal database (no fix available\/possible). For versions older 8.13 it is too recommended not […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_mi_skip_tracking":false,"spay_email":""},"categories":[11],"tags":[],"translation":{"provider":"WPGlobus","version":"2.8.8","language":"en","enabled_languages":["en","de"],"languages":{"en":{"title":true,"content":true,"excerpt":false},"de":{"title":false,"content":true,"excerpt":false}}},"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/p28cjj-Ms","jetpack_sharing_enabled":true,"jetpack-related-posts":[{"id":474,"url":"https:\/\/www.data-protector.org\/wordpress\/2011\/04\/data-protector-6-2-installation\/","url_meta":{"origin":3004,"position":0},"title":"Data Protector 6.2 Installation","date":"13. April 2011","format":false,"excerpt":"{:en}For all already waiting for... the new version of HP Data Protector (6.2) will be installed as follows on a Windows 2008 box... Screens were manipulated to show all available options. UAC may appear prior installation, depending on the configured settings Welcome Screen When pressing Advanced you can define settings\u2026","rel":"","context":"In "HowTo"","img":{"alt_text":"DP62_Install","src":"https:\/\/i0.wp.com\/www.data-protector.org\/wordpress\/wp-content\/uploads\/2011\/04\/DP62_01.png?resize=350%2C200&ssl=1","width":350,"height":200},"classes":[]},{"id":1412,"url":"https:\/\/www.data-protector.org\/wordpress\/2013\/06\/basics-installation-order-patches\/","url_meta":{"origin":3004,"position":1},"title":"Installation order of Patches","date":"3. June 2013","format":false,"excerpt":"{:de}Immer wieder stellt sich die Frage in welcher Reihenfolge die Patches f\u00fcr Data Protector installiert werden. Zwischen den einzelnen Patches ergeben sich Abh\u00e4ngigkeiten, welche man in den Beschreibungsdateien zum Patch nachlesen kann; diese m\u00fcssen bei der Installation eingehalten werden. Generell gilt folgende Reihenfolge f\u00fcr die Installation: sofern vorhanden: Patchbundle, Core,\u2026","rel":"","context":"In "History"","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":114,"url":"https:\/\/www.data-protector.org\/wordpress\/2010\/07\/614039-no-more-space-in-any-of-the-detail-catalog-directories\/","url_meta":{"origin":3004,"position":2},"title":"[61:4039] No more space in any of the Detail Catalog directories","date":"7. July 2010","format":false,"excerpt":"{:en}The error [61:4039] could occur when the limit of the detail catalog is reached. In Data Protector 6.11 the size limit for a DCBF directory was increased up to 16 GB, in former versions the limit was set to 4 GB. For my customers I usually add at least addidtional\u2026","rel":"","context":"In "HowTo"","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":694,"url":"https:\/\/www.data-protector.org\/wordpress\/2011\/07\/data-protector-migration-unix-to-other-os\/","url_meta":{"origin":3004,"position":3},"title":"Data Protector Migration Unix to other OS","date":"29. July 2011","format":false,"excerpt":"{:de}Ich kenne nicht viele gute Gr\u00fcnde warum man eine Data Protector Installation von HP-UX auf ein anderes Betriebssystem wechseln sollte,\u00a0dennoch gibt es viele Kunden die diesen Schritt gehen wollen und zum Beispiel auf Windows oder Linux wechseln;\u00a0meist noch verbunden mit einem Upgrade auf eine aktuelle Version von Data Protector.\u00a0Und hier\u2026","rel":"","context":"In "HowTo"","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":4379,"url":"https:\/\/www.data-protector.org\/wordpress\/2018\/10\/data-protector-upgrade-paths\/","url_meta":{"origin":3004,"position":4},"title":"Data Protector Upgrade Paths","date":"29. October 2018","format":false,"excerpt":"{:en} Lately, we've been receiving more requests for potential Data Protector upgrade paths. This post includes a simple overview to guide you including intermediate steps necessary to upgrade to the latest version of the software. To reduce the amount of manual effort to a minimum you should always use the\u2026","rel":"","context":"In "History"","img":{"alt_text":"DP_Upgrade_Paths","src":"https:\/\/i0.wp.com\/www.data-protector.org\/wordpress\/wp-content\/uploads\/2018\/10\/DP_upgrade_paths_10-20.jpg?resize=350%2C200&ssl=1","width":350,"height":200},"classes":[]},{"id":3589,"url":"https:\/\/www.data-protector.org\/wordpress\/2017\/05\/data-protector-9-gr-patches-9-09-build-115\/","url_meta":{"origin":3004,"position":5},"title":"Data Protector 9 \u2013 GR Patches 9.09 (Build 115)","date":"31. May 2017","format":false,"excerpt":"{:en}The General Release Patches\u00a0A.09.09 (Build 115) for Data Protector 9 has been released on May 31, 2017. The 115 GR Patches must be installed on top of the A.09.09 Patch Bundle. It is recommended to install all the GR Patches as a group regardless if the updated components are used\u2026","rel":"","context":"In "DP A.09.00"","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]}],"_links":{"self":[{"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/posts\/3004"}],"collection":[{"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/comments?post=3004"}],"version-history":[{"count":14,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/posts\/3004\/revisions"}],"predecessor-version":[{"id":3140,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/posts\/3004\/revisions\/3140"}],"wp:attachment":[{"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/media?parent=3004"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/categories?post=3004"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/tags?post=3004"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
- Run the command:
- Open administrative command line and change into the directory
- In addition, the backup specification of the Cell Manager should be checked. During the upgrade to DP 9.06 the existing specification has been divided into an IDB and a filesystem specification.<\/li>\n<\/ul>\n
- The so updated installation can be used as an installation source for the upgrade of the Cell Manager. To this end, all the folders of the depot from the temporary installation server are copied to the Data Protector Cell Manager 7.0x (e.g. to
Installation sources:<\/b><\/p>\n
- \n
- If the command
- Create directories for the migration:\n
- Cleaning of the old internal database:\n
- This step-by-step documentation is valid for Cell Manager Installation on Windows 2008 or Windows 2012. It is assumed that the path