Data Protector - Passion for Data Protection

data-protector.org

Author Archives: danielbraun

EADR for Cell Server – DP 8.1X on Windows 2012 R2

Posted on by 17 Comments

With Data Protector 8.XX the process to create disaster recovery images has been changed. Since the new version, the backup of the internal database is separated from the filesystem backup of the cell server. Hence, the “makeiso.cmd” (see https://www.data-protector.org/wordpress/2011/03/recover-cell-server-with-enhanced-automated-disaster-recovery/) is no longer working. With the separation it is necessary to provide 2 session id’s for the command omniiso; a session id from the filesystem backup and a session id from the IDB backup. As a preparation for a disaster and to automate the creation of the recovery image new batch files were created. Please see the guide below and how to implement the new scripts. The guide is valid for Data Protector version 8.10 and 8.11 only and was tested with Windows 2012 R2. For Data Protector version 8.0X the scripts will not work, as the option -anyobj is not available for the omniiso command. However, with some modifications it will be possible to run the scripts as scheduled task.

[wpdm_file id=23]

Requirements and implementation:

  • On cell server the correct version of the WAIK/ADK is installed. When Windows 2012 R2 is used, the version “ADK for Windows 8.1” is required.
  • The batch files (see download link) are copied into the Data Protector “bin” Folder (i.e: D:\Program Files\Omniback\bin).
  • The backup of the filesystems for the cell server is done using the Options “Copy Recovery Set to disk” (Filesystem Options – Advanced – Tab Other) and “Detect NTFS hardlinks”, “Backup share Information for directories” and “Use Shadow Copy” (Filesystem Options – Advanced – Tab WinFS Options).
  • The backup of the filesystems for the cell server is done using a separate backup specification (no other client) and as Post-exec script the batch file EADR_CS_FSBackup_Post.cmd (to be executed on cell server) will be inserted (Backup Specification Options – General – Post-exec).
  • The backup of the internal database from the cell server is created with no schedule (will be started by the filesystem backup) and as Post-exec script the batch file EADR_CS_IDBBackup_Post.cmd (to be executed on cell server) will be inserted (Backup Specification Options – General – Post-exec).
  • In file “EADR_CS_FSBackup_Post.cmd” the following changes must be made: variables OMNIHOME, OMNIDATA and IDBBACKUP (name of the IDB backup specification) must be modified, depending on existing environment.
  • In file “EADR_CS_IDBBackup_Post.cmd” at least the following changes must be made: variables OMNIHOME, OMNIDATA, CELLSERVER, WAIKPATH and NETWORKSHARE must be modified, depending on existing environment.
  • The batch files are already prepared with variables, so see the values as example.

Example Session Messages filesystem backup:

[Normal] From: BSM@server.domain "CS_Backup_FS"  Time: 04.04.2014 11:01:57
	Starting to execute "EADR_CS_FSBackup_Post.cmd"...


Starting EADR preparation and IDB backup

Script Environment: host='SERVER' user='DOMAIN\user' 
                    script='D:\Program Files\OmniBack\bin\EADR_CS_FSBackup_Post.cmd' 
                    path='D:\Program Files\OmniBack\bin\' 
Backup successfully started.
Session Key: R-2014/04/04-23
[Normal] From: BSM@server.domain "CS_Backup_FS"  Time: 04.04.2014 11:01:57
	The exec script "EADR_CS_FSBackup_Post.cmd" has completed.

Example Session Messages IDB backup:

[Normal] From: BSM@server.domain "CS_Backup_IDB"  Time: 04.04.2014 12:09:50
	Starting to execute "EADR_CS_IDBBackup_Post.cmd"...


Starting the EADR preparation process

Script Environment: host='SERVER' user='DOMAIN\user' 
                    script='D:\Program Files\OmniBack\bin\EADR_CS_IDBBackup_Post.cmd' 
                    path='D:\Program Files\OmniBack\bin\' 
Creating the ISO image ...
[Normal] From: omniiso@server.domain "omniiso"  Time: 04.04.2014 12:09:55
	Creating the Disaster Recovery ISO image file. This may take a few minutes...

[Normal] From: omniiso@server.domain "omniiso"  Time: 04.04.2014 12:09:55
	Initializing MiniOS directory structure.

[Normal] From: omniiso@server.domain "omniiso"  Time: 04.04.2014 12:09:55
	Mounting MiniOS image.

[Normal] From: omniiso@server.domain "omniiso"  Time: 04.04.2014 12:10:00
	Inserting Recovery Info file into the MiniOS image file.

[Normal] From: omniiso@server.domain "omniiso"  Time: 04.04.2014 12:10:00
	Inserting hardware information file into the MiniOS image file.

[Normal] From: omniiso@server.domain "omniiso"  Time: 04.04.2014 12:10:00
	Inserting network information file into the MiniOS image file.

[Normal] From: omniiso@server.domain "omniiso"  Time: 04.04.2014 12:10:00
	Inserting ASR BCD file into the MiniOS image file.

[Normal] From: omniiso@server.domain "omniiso"  Time: 04.04.2014 12:10:00
	Copying MiniOS system files to the image file.

[Normal] From: omniiso@server.domain "omniiso"  Time: 04.04.2014 12:10:00
	Copying DRM binaries to the image file.

[Normal] From: omniiso@server.domain "omniiso"  Time: 04.04.2014 12:10:00
	Copying DRM configuration directory to the image file.

[Normal] From: omniiso@server.domain "omniiso"  Time: 04.04.2014 12:10:00
	Copying backup application depot directory to the image file.

[Normal] From: omniiso@server.domain "omniiso"  Time: 04.04.2014 12:10:00
	Storing phase 0 log file into the Recovery Set archive.

[Normal] From: omniiso@server.domain "omniiso"  Time: 04.04.2014 12:10:00
	Configuring vendor specific system images.

[Normal] From: omniiso@server.domain "omniiso"  Time: 04.04.2014 12:10:00
	Creating the MiniOS image startup file.

[Normal] From: omniiso@server.domain "omniiso"  Time: 04.04.2014 12:10:00
	Installing additional MiniOS packages.

[Normal] From: omniiso@server.domain "omniiso"  Time: 04.04.2014 12:10:17
	Installing additional MiniOS packages.

[Normal] From: omniiso@server.domain "omniiso"  Time: 04.04.2014 12:11:04
	Installing additional MiniOS packages.

[Normal] From: omniiso@server.domain "omniiso"  Time: 04.04.2014 12:11:09
	Installing additional MiniOS packages.

[Normal] From: omniiso@server.domain "omniiso"  Time: 04.04.2014 12:11:15
	Installing additional MiniOS packages.

[Normal] From: omniiso@server.domain "omniiso"  Time: 04.04.2014 12:11:20
	Installing additional MiniOS packages.

[Normal] From: omniiso@server.domain "omniiso"  Time: 04.04.2014 12:11:25
	Installing additional MiniOS packages.

[Normal] From: omniiso@server.domain "omniiso"  Time: 04.04.2014 12:11:32
	Installing additional MiniOS packages.

[Normal] From: omniiso@server.domain "omniiso"  Time: 04.04.2014 12:11:39
	Cleaning up MiniOS image, preparing it for usage.

[Normal] From: omniiso@server.domain "omniiso"  Time: 04.04.2014 12:11:39
	Injecting driver files into the MiniOS image.

[Normal] From: omniiso@server.domain "omniiso"  Time: 04.04.2014 12:11:56
	Initializing MiniOS scratch space.

[Normal] From: omniiso@server.domain "omniiso"  Time: 04.04.2014 12:11:57
	Dismounting/Committing MiniOS image.

[Normal] From: omniiso@server.domain "omniiso"  Time: 04.04.2014 12:12:18
	Writing CD-ROM ISO image to the target location.

[Normal] From: omniiso@server.domain "omniiso"  Time: 04.04.2014 12:12:18
	Successfully created the Disaster Recovery ISO image.

Saving information about used media ...
Copying generated ISO file and information about used media to network share ...
        1 file(s) copied.
        1 file(s) copied.
        1 file(s) copied.
Finished
[Normal] From: BSM@server.domain "CS_Backup_IDB"  Time: 04.04.2014 12:12:26
	The exec script "EADR_CS_IDBBackup_Post.cmd" has completed.

Solution: DP 8.11 Patch Bundle and VE Integration

Posted on by 10 Comments

When using the Data Protector VE integration to backup virtual machines and after the installation of patch bundle 8.11 it might happen, that the backup of the virtual machines is not working. The problem occurs on German localized vCenter Servers only, as the root path for the datacenter is reported as “Datencenter”. The solution is to install a hotfix. Log a support case and ask for QCCR2A52103 if you have the same session messages as shown below. A workaround is to open the “Managed Object Browser” on your vCenter server (https://localhost/mob), select “content” and change the group-d1 property from “rootFolder ManagedObjectReference:Folder group-d1 (Datencenter)” to “rootFolder ManagedObjectReference:Folder group-d1 (Datacenters)“.

[Normal] From: BSM@server.doamin "VEPA_TEST"  Time: 03.04.2014 17:05:29
	Backup session 2014/04/03-40 started.

[Normal] From: BSM@server.doamin "VEPA_TEST"  Time: 03.04.2014 17:05:29
	OB2BAR application on "server.doamin" successfully started.

[Normal] From: VEPALIB_VMWARE@server.doamin "/Datacenter"  Time: 03.04.2014 17:05:30
	Resolving objects for backup on vCenter 'server1.doamin' ... 

[Major] From: VEPALIB_VMWARE@server.doamin "/Datacenter"  Time: 03.04.2014 17:05:37
	Backup failed.

[Normal] From: BSM@server.doamin "VEPA_TEST"  Time: 03.04.2014 17:06:14
	OB2BAR application on "server.doamin" disconnected.

Reviewed: Persistent Binding Windows 2012

Posted on by 4 Comments

In a previous article (see https://www.data-protector.org/wordpress/2013/05/persistent-binding-hp-lto-tape-drives-windows/) I reported about “tape persistence” for Windows.
In general there is noch change to adopt this for Windows 2012 and the registry keys are the same. However, a requirement is to activate “Target Persistent Binding” for the Fibre Channel HBA. In case of a QLogic adapter you may use the tool “QConvergeConsole” (SANSurfer) for the configuration. For Emulex (HBAAnywhere) the configuration is nearly the same. After configuration and activation on the HBA, adding the registry keys and a final reboot, the tape drives and the changer can be used “persistent”. Comment: all tested with HP libraries/drives.

Example:

qlogic

Registry:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\hplto]
"AutoRun"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Tape]
"Persistence"=dword:00000001
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\MChgr]
"Persistence"=dword:00000001

Data Protector 8 – Patch Bundle 8.11

Posted on by 2 Comments

On 2014/03/28 HP released patch bundle 8.11 for Linux, HP-UX and Windows. The update will fix 59 problems and will add 18 enhancements, including the EMC Data Domain Boost device interface type. It is recommended to read the full description of the bundle.

If you own a valid support contract you can download the patches from http://support.openview.hp.com/selfsolve/patches. For login you need the HP Passport account.

Download the patch bundle as usual, you will need your Passport account.

– Windows – DPWINBDL_00811 – Patch Bundle

– Linux – DPLNXBDL_00811 – Patch Bundle

– HP-UX – DPUXBDL_00811 – Patch Bundle

OMNISPEED 2.0 for Data Protector 8.XX on HP-UX, Linux and Windows

Posted on by 2 Comments

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 change is a direct connection to the internal database, therefore the tool must run on the cell server directly. Other changes include the increased runtime of 48 hours, to run the script for X times and the calculation for B2D devices (StoreOnce Gateways – Software/Hardware). The tool supports the international versions of Data Protector; this includes English, French, Japanese and tradtional Chinese, no matter which reginal settings are used. However, the output is in English. Because of the direct connection to the internal database, the runtime is faster. This allows an decreased value for the measurements; it is set to three, instead of five seconds.

For more information, please refer to the help. I look forward to further suggestions and hope you will enjoy the tool.

[wpdm_file id=22]

*******************************************************************************
*                                                                             *
* OMNISPEED v 2.00 - Average Speed of DP Sessions                             *
*                                                                             *
* CoPyRiGhT (c) 2014  Data-Protector.org - Daniel Braun                       *
*                                                                             *
*******************************************************************************
Starting script on: rx2600 - 27.03.2014, 17:17:18

Usage:
omnispeed.exe [options]

OPTIONS:
  --separated           output will be separated by ';'
  --continous, -c       script runs in loop mode until CTRL-C is
                        pressed. When no session is running, the script
                        stops automatically. The script will wait for three
                        seconds between each loop and stops after 57600
                        loops = 48 h.
  --sessionid, -s       get speed from completed session or more
                        details from current session.
  --number,    -n       number of cycles before exit. The script will wait
                        for three seconds between each loop and stops after
                        57600 loops = 48 h. Script can be stopped using CTRL-C.
  --debug,     -d       debug mode, output is written to omnispeeddebug.log.
  --exitcodes, -e       prints out the exit codes used in script.
  --version,   -v       displays the script version.
  --help,      -h       prints this help.

Omnispeed must run on cell server, remote execution not allowed.
Cause: Some commands are available on cell server only. In addition
the SQL commands must be executed locally.
Hint: On Windows cell server psexec can be used for remote execution.
Example psexec: psexec.exe \\servername -u domain\user -h cmd.exe
        After the password has been entered, omnispeed can be started.

Mail bug reports and suggestions to daniel-braun(at)data-protector.org.