The migration of the internal database to new hardware or to a new Microsoft Windows operating system was no big deal in the past and before the release of Data Protector 8.xx. With the introduction of PostgreSQL as the new internal database this has been changed and several steps are necessary in order to perform a successful migration. The following is a guide that enables you doing a migration to new hardware, or, for example, the move from Windows 2008 R2 to Windows 2012 R2. For a successful migration, some requirements must be met; furthermore the migration is dependent on various conditions. For the listed instructions no guarantee can be given and it is recommended to perform the migration with an HP partner. For the elaborate article I would be glad to receive some donations.<\/p>\n
Prerequisites and conditions:<\/p>\n
omnidbcheck -extended<\/code> shows no errors. For Data Protector version 8.10<\/b> it might be necessary to apply hotfix QCCR2A50694<\/b> first. Successful omnidbcheck:
\n\n\r\nC:\\>omnidbcheck -extended\r\nCheck Level Mode Status\r\n===========================================================\r\nDatabase connection -connection OK\r\nSchema consistency -schema_consistency OK\r\nDatafiles consistency -verify_db_files OK\r\nDatabase consistency -database_consistency OK\r\nMedia consistency -media_consistency OK\r\nSIBF(readability) -sibf OK\r\nDCBF(presence and size) -bf OK\r\nOMNIDC(consistency) -dc OK\r\nDONE!<\/pre>\n<\/blockquote>\n<\/li>\n
- The old “Detail Catalog Binary Files” (pre DP 8.XX) were fully migrated. The command (example)
\"C:\\Program Files\\Omniback\\bin\\perl.exe\" omnimigrate.pl -report_old_catalog<\/code> shows following output:
\n\n\r\nOld Detail Catalog Binary Files size:\r\n\r\nDCBF ( 0 files): 0 MB\r\nOld filename data files: 0 MB\r\nTotal: 0 MB\r\n<\/pre>\n<\/blockquote>\nIf there are still old “Binary Files” in place, you have to migrate the files first. For this purpose, the command (example) \"C:\\Program Files\\OmniBack\\bin\\perl.exe\" omnimigrate.pl -start_catalog_migration<\/code> can be used. If for the “DCBF” 0 files are displayed, but “Old filename data files” are still displayed, this may mean that there were modifications to the old dcbf directories during or after the migration. In this special case you can copy the DCBF files from db40 to the db80 folder and run omnidbutil -remap_dcdir<\/code> and omnidbutil -fixmpos<\/code>.<\/li>\n- The old catalog and the old “Binary Files” must be deleted after the migration from version 6, 7 to version 8 (Attention: see hint DB40). If this step has not yet been performed or if you are uncertain about the status, you can use the command (example)
\"C:\\Program Files\\Omniback\\bin\\perl.exe\" omnimigrate.pl -remove_old_catalog<\/code> to delete the old files. With a successful completion of the command, the file global<\/code> will be adjusted and the support for the old catalog will be removed (SupportOldDCBF=1<\/code>).<\/li>\n- There must not exist any DCBF directory from a previous (pre 8.xx DP) Data Protector version. The check can be done using the GUI – Internal Database. Alternatively, export the IDB with the command
omnidbutil -writedb <Pathname><\/code>. After the export, and the note on to copy directories, no DB40 path must displayed. By the way: the export of IDB to a connected network share is possible since v8.xx. Check export for db40 directories:
\n\n\r\nPlease make a copy of the following Internal Database directories and then press Enter to bring the Internal Database back to a fully operational state:\r\n\r\n \"C:\/Program Files\/OmniBack\/server\/db80\/msg\"\r\n \"C:\/Program Files\/OmniBack\/server\/db80\/meta\"\r\n \"C:\/Program Files\/OmniBack\/server\/db80\/dcbf\/dcbf3\"\r\n \"C:\/Program Files\/OmniBack\/server\/db80\/dcbf\/dcbf0\"\r\n \"C:\/Program Files\/OmniBack\/server\/db80\/dcbf\/dcbf2\"\r\n \"C:\/Program Files\/OmniBack\/server\/db80\/dcbf\/dcbf1\"\r\n \"C:\/Program Files\/OmniBack\/server\/db80\/dcbf\/dcbf4\"\r\n<\/pre>\n<\/blockquote>\nNote: in the example the separation of “Program Files” and “Program Data” has not yet been performed, see also following items.\n<\/li>\n
- Note db40<\/b>: If there are any DCBF files in folder db40 left after migration from pre DP 8.XX to DP 8.XX, it might have different causes. The migration of DCBF files is absolutely necessary before removing the old catalog. To check for old “Binary Files”, save
select medium_name, dcbf_directory, dcbf_version from dp_dcbf_info i, dp_dcbf_directory d where i.dcbf_directory_seq_id = d.dp_numkey order by dcbf_version;<\/code> into file dcbf_version.sql<\/code> and execute the command omnidbutil \u2013run_script dcbf_version.sql \u2013detail<\/code>. The output displays the media ID, folder and DCBF version. A media with -1<\/code> has not been migrated so far and can be migrated with the command omnimm -upgrade_dcbf <mediumID><\/code>. If for the DCBF folders (db40 path – see export IDB) a back-slash, instead of a forward-slash is displayed, you are required to export the IDB (omnidbutil \u2013writedb <Pathname><\/code>). Modify the file dpidb.dat<\/code> and change for the DCBF folders the back-slash into a forward-slash. Save the file and import the modified IDB using the command omnidbutil \u2013readdb <Pathname><\/code>. With the command omnidbutil -remove_dcdir <PathName><\/code> you can remove the old catalog and DCBF directories. The most important part in file dpidb.dat<\/code> should look as follow (example and without separation of “Program Files” and “Programdata”):
\n\n\r\n20cf4d3f-d425-4f01-8823-9b9e9dcfa72c\t1004\tC:\/Program Files\/OmniBack\/server\/db80\/dcbf\/dcbf3\t214748364800\t3\t2147483648\t100000\t44\t6964137984\r\n20cf4d3f-d425-4f01-8823-9b9e9dcfa72c\t1001\tC:\/Program Files\/OmniBack\/server\/db80\/dcbf\/dcbf0\t214748364800\t0\t2147483648\t100000\t48\t9023758336\r\n20cf4d3f-d425-4f01-8823-9b9e9dcfa72c\t1003\tC:\/Program Files\/OmniBack\/server\/db80\/dcbf\/dcbf2\t214748364800\t2\t2147483648\t100000\t39\t6941310976\r\n20cf4d3f-d425-4f01-8823-9b9e9dcfa72c\t1002\tC:\/Program Files\/OmniBack\/server\/db80\/dcbf\/dcbf1\t214748364800\t1\t2147483648\t100000\t40\t6340190208\r\n20cf4d3f-d425-4f01-8823-9b9e9dcfa72c\t1005\tC:\/Program Files\/OmniBack\/server\/db80\/dcbf\/dcbf4\t214748364800\t4\t2147483648\t100000\t63\t7780794368\r\n<\/pre>\n<\/blockquote>\n<\/li>\n
- The separation of “Program Files” and “Programdata” has been done in the past. If this is not the case and you plan to do the separation during the migration on the target hardware or platform, some additional steps are required. In this guide the separation was not done so far, so all steps are documented.<\/li>\n
- The used user names and passwords (Windows) to start the Data Protector services remain the same on the target hardware or platform. If you plan to change this and if you want to use new user and password, please refer to the article \u201eData Protector 8.0 Windows \u2013 change user account for DP services\u201c (link: https:\/\/www.data-protector.org\/wordpress\/2013\/11\/data-protector-8-0-windows-change-user-account-dp-services\/<\/a>).<\/li>\n
- The article does not apply for migrations from pre DP 8.XX versions.<\/li>\n
- On the source system the most current Data Protector version should be installed before the migration is done, as this will ease the migration procedure. This does apply for source systems only when the separation of “Program Files” and “Programdata” has already been done. The reason is a bug in the installation sequence when upgrading from DP 8.0X to 8.10. In this guide the same version of Data Protector is installed on the target and the upgrade will be done on the target system after the migration has been completed.<\/li>\n
- The name of the server and the IP addresses remain the same on the target cell server. If you are required to change that, additional steps might be necessary (export of clients beforehand, import of clients after migration, change cell server name, etc. – this will not be part of this guide).<\/li>\n
- The server name has to start with a leading letter and must not start with a leading number. The reason is a limitation in the included application server (JBOSS\/Tomcat).<\/li>\n
- The internal database has not been restored in the past and there must not exist several DB80 directories (original and restored versions).<\/li>\n
- All names in this guide are examples.<\/li>\n
- After the migration, make sure you immediately start a backup for the server and the internal database. A restore of the IDB with data before the migration might not work, especially when the DCBF directories were changed during the migration. This will be possible only, when additional modification in the exported database is performed.<\/li>\n
- The guide does not apply to MoM environments.<\/li>\n<\/ul>\n
Step by Step:<\/p>\n
\n- Make a backup of the IDB in case any error occurs. Using a Jukebox with some slots makes it easy to do a fast recovery. The media will be formatted and the IDB backup started. In this example the backup was done to e:\\IDBBackup\\01..05 and copied off the server after the IDB backup. In case you do not have sufficient local disk space, use a filelibrary configured to store the data on network share. The definition of the Jukebox and the used drive will be exported into text files. Definition Jukebox:
\n\n\r\nE:\\Program Files\\OmniBack\\bin>omnidownload -library IDBBackup\r\nNAME \"IDBBackup\"\r\nDESCRIPTION \"\"\r\nHOST servername.domain\r\nPOLICY Jukebox\r\nTYPE File\r\nREPOSITORY\r\n \"E:\\IDBBackup\\01\"\r\n \"E:\\IDBBackup\\02\"\r\n \"E:\\IDBBackup\\03\"\r\n \"E:\\IDBBackup\\04\"\r\n \"E:\\IDBBackup\\05\"\r\nMGMTCONSOLEURL \"\"\r\n<\/pre>\n<\/blockquote>\nDefinition drive:<\/p>\n
\n\r\nE:\\Program Files\\OmniBack\\bin>omnidownload -device IDBBackup_Drive01\r\nNAME \"IDBBackup_Drive01\"\r\nDESCRIPTION \"\"\r\nHOST servername.domain\r\nPOLICY Jukebox\r\nTYPE File\r\nPOOL \"IDBBackup\"\r\nLIBRARY \"IDBBackup\"\r\nCONCURRENCY 10\r\nENCRCAPABLE\r\nBUFFERS 16\r\nBLKSIZE 64\r\nRESTOREDEVICEPOOL NO\r\nCOPYDEVICEPOOL NO\r\n<\/pre>\n<\/blockquote>\nIn case of any errors you can use these text files to re-create the Jukebox (see help for command omniupload<\/code>).<\/li>\n- Stop the Data Protector scheduler using the command
omnitrig -stop<\/code><\/li>\n- Export the internal database with the command
omnidbutil \u2013writedb <pathname><\/code> (in this guide Z:\\ExportIDB is used). On request copy the directories DCBF, MSG and META off the server (i.e. Z:\\Migration).<\/li>\n- Stop the Data Protector services using the command
omnisv -stop<\/code><\/li>\n- Copy all Data Protector directories off the server (i.e. to Z:\\Migration). Skip the copy for the directories DCBF, MSG and META, as this has been done in previous step. Comment: when copying the directories, all symbolic links in IDB structure will be copied as whole, so please plan for sufficient disk space on target. Once you copied the directories all relevant Data Protector parts have been backed up, however, this does not apply for any additional services installed on the source system.<\/li>\n
- Install the new box or operating system. Use the same server name, IP addresses, domain, groups, users and passwords. In case of changes, you need to check the configuration files step by step (see below).<\/li>\n
- Install HP Data Protector 8.XX to “D:\\Program Files\\Omniback” and “D:\\Programdata\\Omniback” (example). Use the same version, the same patches or hotfixes as installed on source system.<\/li>\n
- Configure impersonation:
\n\n\r\nC:\\Users\\administrator>omniinetpasswd -inst_srv_user domain\\administrator\r\nUser 'domain\\administrator' is configured to be used by Installation Server.\r\n<\/pre>\n<\/blockquote>\n<\/li>\n
- Stop the Data Protector services using the command
omnisv -stop<\/code><\/li>\n- On demand change the local security policy. This is required, if you plan to start the “Data Protector INET” service using a domain user, instead of the NT Authority\\SYSTEM account. Add the user to the policies “Impersonate a client after authentication” and “Replace a process level token”.<\/li>\n
- Copy back the DCBF, MSG and META directories to the new path. In this guide the path
D:\\Programdata\\OmniBack\\server\\db80<\/code> is used.<\/li>\n- Change the DCBF directories in the file
dpidb.dat<\/code> (see export of IDB). This step is required only for target systems where the Data Protector directories are changed during the migration. Change of DCBF directories from:
\n\n\r\nCOPY dp_catalog_dcbf_directory (db_uuid, seq_id, dcbf_directory, maxsize, fill_sequence, min_freespace, max_dcbf_files, cur_num_of_files, cur_occupied_space) FROM stdin;\r\n20cf4d3f-d425-4f01-8823-9b9e9dcfa72c\t1002\tE:\/Program Files\/OmniBack\/server\/db80\/dcbf\/dcbf1\t214748364800\t1\t2147483648\t100000\t47\t6341406720\r\n20cf4d3f-d425-4f01-8823-9b9e9dcfa72c\t1004\tE:\/Program Files\/OmniBack\/server\/db80\/dcbf\/dcbf3\t214748364800\t3\t2147483648\t100000\t44\t6964137984\r\n20cf4d3f-d425-4f01-8823-9b9e9dcfa72c\t1001\tE:\/Program Files\/OmniBack\/server\/db80\/dcbf\/dcbf0\t214748364800\t0\t2147483648\t100000\t48\t9023758336\r\n20cf4d3f-d425-4f01-8823-9b9e9dcfa72c\t1003\tE:\/Program Files\/OmniBack\/server\/db80\/dcbf\/dcbf2\t214748364800\t2\t2147483648\t100000\t39\t6941310976\r\n20cf4d3f-d425-4f01-8823-9b9e9dcfa72c\t1005\tE:\/Program Files\/OmniBack\/server\/db80\/dcbf\/dcbf4\t214748364800\t4\t2147483648\t100000\t63\t7780794368\r\n<\/pre>\n<\/blockquote>\nChange of DCBF directories to:<\/p>\n
\n\r\nCOPY dp_catalog_dcbf_directory (db_uuid, seq_id, dcbf_directory, maxsize, fill_sequence, min_freespace, max_dcbf_files, cur_num_of_files, cur_occupied_space) FROM stdin;\r\n20cf4d3f-d425-4f01-8823-9b9e9dcfa72c\t1002\tD:\/ProgramData\/OmniBack\/server\/db80\/dcbf\/dcbf1\t214748364800\t1\t2147483648\t100000\t47\t6341406720\r\n20cf4d3f-d425-4f01-8823-9b9e9dcfa72c\t1004\tD:\/ProgramData\/OmniBack\/server\/db80\/dcbf\/dcbf3\t214748364800\t3\t2147483648\t100000\t44\t6964137984\r\n20cf4d3f-d425-4f01-8823-9b9e9dcfa72c\t1001\tD:\/ProgramData\/OmniBack\/server\/db80\/dcbf\/dcbf0\t214748364800\t0\t2147483648\t100000\t48\t9023758336\r\n20cf4d3f-d425-4f01-8823-9b9e9dcfa72c\t1003\tD:\/ProgramData\/OmniBack\/server\/db80\/dcbf\/dcbf2\t214748364800\t2\t2147483648\t100000\t39\t6941310976\r\n20cf4d3f-d425-4f01-8823-9b9e9dcfa72c\t1005\tD:\/ProgramData\/OmniBack\/server\/db80\/dcbf\/dcbf4\t214748364800\t4\t2147483648\t100000\t63\t7780794368\r\n<\/pre>\n<\/blockquote>\n<\/li>\n
- Restore the during the migration copied files in
D:\\Programdata\\OmniBack\\log\\server<\/code>. The most important files are media.log<\/code>, Ob2Event.*<\/code> and the folder auditing<\/code>.<\/li>\n- Modify or restore the configuration files
global<\/code> (example: D:\\ProgramData\\Omniback\\Config\\Server\\Options<\/code>) and omnirc<\/code> (example: D:\\ProgramData\\Omniback<\/code>).<\/li>\n- Modify or restore the files
cell_info<\/code>, lic.dat<\/code> and installation_servers<\/code>. Comment: After the upgrade to DP 8.1X all installed licenses become invalid and must be regenerated using the portal http:\/\/webware.hp.com<\/a>. This requires a current support contract with HP.<\/li>\n- Restore the directories:
BarLists, Barschedules, consolidationlists, copylists, Datalists, dlgroups, dr, Integ, rptgroups, rptschedules, Schedules, users<\/code>. For the files in folder users<\/code> crosscheck the entries before overwriting.<\/li>\n- Modify the files
hpdp-idb-cp.cfg<\/code> and idb.config<\/code> in directory (example) D:\\ProgramData\\Omniback\\Config\\Server\\idb<\/code>. In both files modify the pathes.
\nExample hpdp-idb-cp.cfg:<\/p>\n\n\r\n[databases]\r\nhpdpidb = host=127.0.0.1 port=7112 dbname=hpdpidb\r\n\r\n[pgbouncer]\r\nservice_name=hpdp-idb-cp\r\nlisten_addr = *\r\nlisten_port = 7113\r\nunix_socket_dir = \/tmp\r\nauth_type = md5\r\nadmin_users = hpdp\r\nstats_users = hpdp\r\npool_mode = transaction\r\nserver_reset_query =\r\nignore_startup_parameters = application_name,extra_float_digits\r\nserver_check_query = select 1\r\nserver_check_delay = 10\r\nmax_client_conn = 1200\r\ndefault_pool_size = 50\r\nquery_wait_timeout = 10\r\nlog_connections = 0\r\nlog_disconnections = 0\r\nlog_pooler_errors = 1\r\nlogfile = D:\\ProgramData\\OmniBack\\log\\hpdp-idb-cp.log\r\npidfile = D:\\ProgramData\\OmniBack\\log\\hpdp-idb-cp.pid\r\nauth_file = D:\\ProgramData\\OmniBack\\config\\server\\idb\\ulist\r\n<\/pre>\n<\/blockquote>\nExample idb.config:<\/p>\n
\n\r\nPGHOSTNAME='localhost';\r\nPGIDBNAME='hpdpidb';\r\nPGUSER='hpdpidb_app';\r\nPGPASSWORD='bWhhbnTvZ3Xxbao2Zw==';\r\nPGSUPERUSER='hpdp';\r\nPGSUPERPASSWORD='anpabZl3bnh6dGY3eQ==';\r\nPGMAXOPEN_CONN_NUMBER='5';\r\nPGDATA_PG='D:\\ProgramData\\OmniBack\\server\\db80\\pg';\r\nPGDATA_IDB='D:\\ProgramData\\OmniBack\\server\\db80\\idb';\r\nPGDATA_JCE='D:\\ProgramData\\OmniBack\\server\\db80\\jce';\r\nPGOSUSER='domain\\administrator';\r\nPGPORT='7112';\r\nPGCPPORT='7113';\r\nPGWALPATH='D:\\ProgramData\\OmniBack\\server\\db80\\pg\\pg_xlog_archive';\r\nIDB_SEC_FLAG='11';\r\n<\/pre>\n<\/blockquote>\n<\/li>\n
- On demand and depending on configuration it might be necessary to restore (copy back) additional files and directories. For example, when Exchange is backed up in the Environment, the folder (example)
D:\\ProgramData\\Omniback\\server\\db80\\vssdb\\metadata60<\/code> is required.<\/li>\n- Start the Data Protector services using the command
omnisv -start<\/code>.<\/li>\n- Stop the Data Protector scheduler using the command
omnitrig -stop<\/code>.<\/li>\n- Import the IDB using the command
omnidbutil -readdb <pathname><\/code> (in the guide Z:\\ExportIDB is used).<\/li>\n- Stop the Data Protector services using the command
omnisv -stop<\/code>.<\/li>\n- Start the Data Protector services using the command
omnisv -start<\/code>.<\/li>\n- Check the consistency of the internal database using the command
omnidbcheck -extended<\/code>. No errors must be reported.<\/li>\n- For further checks start some backups and restore some data for backups done before the migration and after the migration.<\/li>\n
- After successful migration the used Jukebox (IDBBackup) and for the Jukebox used directories can be removed. All other directories used during the migration should be kept for at least 7 days.<\/li>\n
- On demand and if not already done on the source system, the upgrade to the most current Data Protector version can be started.<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"
The migration of the internal database to new hardware or to a new Microsoft Windows operating system was no big deal in the past and before the release of Data Protector 8.xx. With the introduction of PostgreSQL as the new internal database this has been changed and several steps are necessary in order to perform […]<\/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-uw","jetpack_sharing_enabled":true,"jetpack-related-posts":[{"id":3262,"url":"https:\/\/www.data-protector.org\/wordpress\/2016\/12\/migrate-dp-9-0x-dp-9-0x-hardware-microsoft-windows\/","url_meta":{"origin":1892,"position":0},"title":"Migrate DP 9.0X to DP 9.0X using new hardware and Microsoft Windows","date":"8. December 2016","format":false,"excerpt":"{:en}I already wrote several articles on how to migrate the internal database to a new hardware, new Data Protector version, or new operating system (see link). With the introduction of PostgreSQL as internal database for Data Protector and compared to previous versions (DP 6 and DP 7), some more steps\u2026","rel":"","context":"In "HowTo"","img":{"alt_text":"writedb","src":"https:\/\/i1.wp.com\/www.data-protector.org\/wordpress\/wp-content\/uploads\/2016\/12\/writedb.png?resize=350%2C200&ssl=1","width":350,"height":200},"classes":[]},{"id":3004,"url":"https:\/\/www.data-protector.org\/wordpress\/2016\/07\/runbook-migrate-data-protector-7-0x-data-protector-9-0x\/","url_meta":{"origin":1892,"position":1},"title":"RUNBOOK \u2013 Migrate Data Protector 7.0x to Data Protector 9.0x","date":"5. July 2016","format":false,"excerpt":"{:en} 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\u2026","rel":"","context":"In "HowTo"","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":1919,"url":"https:\/\/www.data-protector.org\/wordpress\/2014\/03\/omnispeed-2-0-data-protector-8-xx-hp-ux-linux-windows\/","url_meta":{"origin":1892,"position":2},"title":"OMNISPEED 2.0 for Data Protector 8.XX on HP-UX, Linux and Windows","date":"27. March 2014","format":false,"excerpt":"{:en}The new version of OMNISPEED is available. Version 2.0 was especially developed for Data Protector 8.XX environments and supports HP-UX (Itanium) 11.31, Linux (RedHat and SUSE Linux Enterprise Server) and Microsoft Windows (2008 R2, 2012 and 2012 R2) for the Data Protector versions 8.00, 8.01 and 8.1X. The most important\u2026","rel":"","context":"In "SCD"","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":1892,"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":4432,"url":"https:\/\/www.data-protector.org\/wordpress\/2018\/12\/data-protector-10-updated-release-a-10-20-build-115\/","url_meta":{"origin":1892,"position":4},"title":"Data Protector 10 \u2013 Updated Release A.10.20 (Build 115)","date":"10. December 2018","format":false,"excerpt":"{:en}Data Protector\u00a0A.10.20 (Build 115)\u00a0has been released on December 6, 2018. The new version is another full install to simplify the upgrade and installation process.This will continue to be the default for all future Data Protector versions. Data Protector 10.20 does not require any previous version to install the latest version\u2026","rel":"","context":"In "DP A.10.00"","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":2095,"url":"https:\/\/www.data-protector.org\/wordpress\/2014\/08\/add-licenses-data-protector\/","url_meta":{"origin":1892,"position":5},"title":"How to add licenses in Data Protector","date":"25. August 2014","format":false,"excerpt":"{:en}There are different ways to add licenses into Data Protector. Copy and paste the license file generated on the licensing portal (http:\/\/www.webware.hp.com) as ...\/Config\/Server\/cell\/lic.dat Copy and paste of a single or several licenses keys into exisiting lic.dat Copy and paste of a single license key using the Data Protector GUI\u2026","rel":"","context":"In "BASICS"","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]}],"_links":{"self":[{"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/posts\/1892"}],"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=1892"}],"version-history":[{"count":30,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/posts\/1892\/revisions"}],"predecessor-version":[{"id":2813,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/posts\/1892\/revisions\/2813"}],"wp:attachment":[{"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/media?parent=1892"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/categories?post=1892"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/tags?post=1892"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}