For a Disaster Recovery of you cell server it is recommended to save information about your libraries and devices. In article Recover Cell Server I already informed about obrindex.dat. I wrote a small tool to save the configuration of your libraries and devices to text files. In addition a batch is generated which allows the import of the libraries and devices into Data Protector. The files are generated in a subfolder of the log folder of Data Protector. UPDATE: Version 1.02 fixes a problem with too short or too long device names, it now can run on Windows 2003, Windows 2008 and Windows 2008 R2. The Perl script will be distributed as source, to run the script a 32Bit Perl (i.e. ActiveState Perl) is required (as the Data Protector Perl modules are written in 32Bit); see the download link for the Perl version below. UPDATE: An additional batch will be
Please find below all available downloads from this blog. BRICK – Backup Related Information Collector and Keeper – Version 2.0 https://www.data-protector.org/wordpress/?s=BRICK EADR for Cell Server – DP 9.06 on Windows 2012 R2 https://www.data-protector.org/wordpress/2016/05/prepare-and-execute-eadr-cell-server-on-windows-2012-r2-data-protector-9-06/ Data Protector Best Practice Guide https://www.data-protector.org/wordpress/?s=best+practice+guide BRICK – Backup Related Information Collector and Keeper – Version 1.20 (Pre 1.10 versions removed) https://www.data-protector.org/wordpress/?s=BRICK OMNILISTFREEDEVS – lists free devices www.data-protector.org/wordpress/?s=OMNILISTFREEDEVS OMNISPEED v2.00 HP-UX / Linux / Windows https://www.data-protector.org/wordpress/2014/03/omnispeed-2-0-data-protector-8-xx-hp-ux-linux-windows/ EADR for Cell Server – DP 8.1X on Windows 2012 R2 https://www.data-protector.org/wordpress/2014/04/eadr-cell-server-dp-8-1x-windows-2012-r2 OMNISPEED – average speed and current speed of running and completed sessions https://www.data-protector.org/wordpress/?s=OMNISPEED+average+speed+and+current+speed Simple Media Vaulting / Off-Site Tape Vaulting https://www.data-protector.org/wordpress/?s=Simple+Media+Vaulting Data Protector 6.2 Scheduler https://www.data-protector.org/wordpress/?s=Data+Protector+6.2+Scheduler Data Protector Migration Unix to other OS https://www.data-protector.org/wordpress/?s=Data+Protector+Migration+Unix+to+other+OS Recover Cell Server with Enhanced Automated Disaster Recovery https://www.data-protector.org/wordpress/?s=Recover+Cell+Server+with+Enhanced+Automated+Disaster+Recovery SaveDevices – omnidownload https://www.data-protector.org/wordpress/?s=SaveDevices+-+omnidownload SaveINSEvent4624 – Something Completely Different https://www.data-protector.org/wordpress/?s=SaveINSEvent4624+-+Something+Completely+Different omnircsync.pl https://www.data-protector.org/wordpress/?=somnircsync.pl Please note: the count of downloads is based on analysis since June 2012.
In previous posts it is documented how to recover a server using Enhanced Automated Disaster Recovery Option. Tis applies to the Cell Server too, as this server might be the most important server in a case of a disaster. For the cell server there are several options available to do a fast recovery. The following steps apply to cell server for all supported operating systems and the steps are only 1 possible way for recovery. The most important information when a recovery of the cell server is required will be the information on which media is the backup of the internal database. With 2 settings you make sure the information is available when needed (if copied off the cell server per scheduled task). First you have to edit the file rdmserver.ini and to enable the parameter archiving=1. In this case DP will write the information regarding the backup of IDB
Are there many good reasons to change from Data Protector on Unix to a different operating system? I do not know many… However, there are customers required to do this step and to migrate to Windows or Linux; often combined with a upgrade to the current version of Data Protector. And here the story starts: there is no path for migration available. The reason is simple, the DCBF folders are not compatible between Unix and Windows nor is there a chance to do an export and import of the internal database. The DCBF folders on HP-UX are stored in big-endian format and on Linux in little-endian format and there is no tool for translation available. What the difference is can be search at your favorite search engine. The article is somehow larger than usual, you’ll need 30 minutes to work through, the article is addressed to experts. At the end of this article you’ll find the link to the export and import