Hardware Support and Software Pre-Requisites Data protector 6.2

HP Data Protector software

Introduction

HP Data Protector software simplifies application protection in virtual and physical environments through unified recovery and advanced automation. Global, one-touch backup configuration and a wide range of disk-based recovery options across HP and non-HP arrays, including fully-automated application recovery, help you meet any SLA for up to 70% less total cost of ownership than competitive backup software solutions.

More than 41,000 customers around the world, and nearly half of the Global 500, rely on HP Data Protector software to protect their critical applications and data. Data Protector is a key component of the HP Information Management solution portfolio, which dramatically simplifies the management and governance of information for today's modern enterprise organization.

What's New

Extending the Power of HP - down-to-the-second recovery of application for HP P4000 arrays.

Only HP Data Protector software can recover virtual server applications and data to any point in time - down-to-the-second - from a centralized console without scripting. Data Protector 6.2 extends this functionality to the P4000. Together, Data Protector and P4000 achieve a highly cost-effective enterprise recovery solution ideal for virtual server deployments of applications such as Microsoft SharePoint, Microsoft Exchange and SQL Server.

Data Protector allows backup administrators to select the point in time to which they'd like to recover into the Data Protector console. Data Protector accesses the application transaction log (where all of the application's transactions are recorded before they're processes and/or written to data files) and fills in the data gaps between snapshots. Data Protector then synchronizes the application with the data and restarts the application. This functionality is possible with any Data Protector recovery solution whether from snapshot, disk or tape.

Extending simplified snapshot functionality to non-HP arrays such as EMC CLARiiON and Network Appliance

Data Protector Zero Downtime Backup snapshot support has been extended to non-HP arrays through VSS integration. Global one-touch protection ensures snapshot configurations - as well as all backup methods - are automatically extended to new virtual machines, Microsoft databases, and Oracle databases as they're brought online. One click in the Data Protector console and Data Protector will automatically apply the chosen backup method to new VMs and databases. This level of automation extends to physical environments as well.

Reducing the burden of single item recovery on the backup administrator.

Data Protector Granular Recovery Extension empowers SharePoint and VMware vSphere administrators to recover single items directly from the application administrator's console, without asking for assistance from the backup administrator.

Data Protector allows application administrators to recover single items from Data Protector disk or tape backups - they don't need to know or use Data Protector, nor do they need to contact the backup administrator. For SharePoint environments, GRE allows application administrators to recover single items from ANY 3rd party snapshots.

NEW Data Protector Reporter software - sophisticated operational analysis, SLA compliance reporting across multi-site distributed geographies.

Data Protector software includes robust reporting capabilities, including a notification function which allows customers to forward events to HP or 3rd-party reporting or management tools such as HP Storage Essentials and IBM Tivoli. For customers who require the most advanced reporting capabilities, HP provides Data Protector Reporter software - which delivers enterprise reporting, designed specifically for Data Protector customers. HP Data Protector Reporter software is customer-installable software which delivers centralized, automated reporting to optimize operations and infrastructure - and realize up to 30% savings. It features a powerful reporting engine that drives global, multi-site backup and restore analysis. Data Protector Reporter features 35+ out-of-the-box reports including SLA and performance reporting. The optional current licensed module provides enhanced powerful customized ad-hoc query and analysis flexible reporting. For more information, please download the Data Protector Reporter QuickSpecs on hp.com/go/dataprotector.

Enhanced single-pass disaster recovery functionality - for no additional cost.

Data Protector 6.2 introduces new disaster recovery functionality which is included in the cost of Data Protector. Unlike some backup software solutions that require you to keep a separate image backup from which to initiate recovery, Data Protector provides "single-pass DR" - which enables customers to create a disaster recovery image from any existing full backup. You can restore from physical-to-virtual and virtual-to-physical servers across dissimilar hardware. In addition, once the backup administrator initiates the disaster recovery process, Data Protector automatically re-builds the system and the partitioning. Data Protector 6.2 supports both Linux and Windows operating systems - for specific support please check the compatibility matrix on hp.com/go/dataprotector.

In addition, Data Protector DR functionality is especially useful in remote and branch office environments. Data Protector is fully replication aware, and provides a single management console from which to oversee deduplication-enabled replication between local or geographically distributed sites. When Data Protector performs a backup in the remote office, the backup with the DR image can be replicated to the central data center, In the event of an outage, the DR image can be prepared and delivered to the ROBO site via FTP site or by shipping a USB drive for fast recovery.

IPv6 and NDMP

Data Protector 6.2 is fully IPv6 compliant. Data Protector IPv6 support is backward compatible for IPv4 environments. In addition, Data Protector 6.2 also provides NDMP snapmirror to tape support, which provides efficient backup of large files.

Hardware Support and Software Pre-Requisites Hardware Support Broad coverage of HP-UX, Windows, Solaris, Tru64, OpenVMS, NetWare, Linux, AIX, and other operating environments HP XP/EVA, and EMC Symmetrix disk array support for ZDB/IR Backup to disk supports any storage that the server's operating system supports HP Tape libraries, StorageTek, ADIC, IBM etc. For detailed information on HP Data Protector support matrices please visit: http://www.hp.com/go/dataprotector Software Pre-Requisites Cell Manager Requirements The Data Protector Session Manager does not support the IDB on a file system that is mounted as NFS type. On Systems Running HP-UX (PA-RISC) - 11.11, 11.23, 11.31 and HP-UX (IA64) - 11.23, 11.31 The Cell Manager must meet the following minimum requirements: The Soft File Limit per Process on the Cell Manager should be at least 1024. 256 MB RAM (512 MB recommended) For each parallel backup session 40 MB of RAM are required and 5 - 8 MB per data segment size. For example, if you want to run 60 parallel backup sessions 3 GB of RAM plus 512 MB for data segments are needed. 240 MB of disk space + approximately 2% of planned data to be backed up (for use by the IDB). It is recommended to modify the kernel parameters as follows: Set maxdsiz (Max Data Segment Size) or maxdsiz_64 (for 64-bit systems) to at least 134217728 bytes (128 MB). Set semmnu (Number of Semaphore Undo Structures) to at least 256. After committing these changes, recompile the kernel and reboot the machine. On Systems Running Solaris 8/9/10 The Cell Manager must meet the following minimum requirements: 256 MB of RAM (512 MB recommended) For each parallel backup session 40 MB of RAM are required and 5-8 MB per data segment size. This means that, for example, if you want to run 60 parallel backup sessions 3 GB of RAM plus 512 MB of data segments are needed. 300 - 425 MB of disk space + approximately 2% of planned data to be backed up (for use by the IDB) The following values of kernel parameters are recommended: SEMMNI (maximum number of semaphore sets in the entire system) = 100 and SEMMNS (maximum semaphores on the system) = 256. A system restart is necessary for kernel changes to take effect. The requirements for viewing online Help on the Data Protector Cell Manager are the same as on Data Protector clients. For Java GUI Client, Java Runtime Environment (JRE) 1.5.0_06 or newer (for example, 1.5.0_07) is required. On Systems Running Windows XP The Cell Manager must meet the following minimum requirements: 256 MB RAM (512 MB recommended). For each parallel backup session 40 MB of RAM are required. For example, if you want to run 60 parallel backup sessions 3 GB of RAM are needed. Windows 2000, Service Pack 3 or later Windows XP Professional, Service Pack 1 must be installed 190 MB of disk space + approximately 2% of planned data to be backed up (for use by the IDB) 2 + 5MB of disk space needed on system drive For viewing online help on the Data Protector Cell Manager, Microsoft Internet Explorer 6.0 or newer is required. For Java GUI Client, Java Runtime Environment (JRE) 1.5.0. or newer (for example, 1.5.0_07) is required. On Systems Running Windows Server 2003 (32-bit) and Windows 2003/2008 & 2008-R2 (64-bit x86_64) The Cell Manager must meet the following minimum requirements: 256 MB RAM (512 MB recommended). Each parallel backup session requires 40 MB of RAM. For example, 60 parallel backup sessions requires 3 GB of RAM. 190 MB of disk space + approximately 2% of planned data to be backed up (for use by the IDB) 2 + 5MB of disk space needed on system drive On Windows Server 2008 systems, the firewall must also be configured to accept "Remote Service Administration" (NP) connections (port 445). On Windows Server 2008 systems, administrative privileges are required to install Data Protector A.06.2. For viewing online Help on the Data Protector Cell Manager, Microsoft Internet Explorer 6.0 or newer version is required. For the Java GUI Client on Windows Server 2003 systems, Java Runtime Environment (JRE) 1.5.0_06 or newer update (for example, 1.5.0_07) is required. For the Java GUI Client on Windows Server 2008 systems, BEAJRockit 5.0 1.5.0_06 or newer update (for example, 1.5.0_07) is required. On Linux Systems The Cell Manager must meet the following minimum requirements: 256 MB RAM (512 MB recommended). For each parallel backup session 40 MB of RAM are required and 5 - 8 MB per data segment size. This means that, for example, if you want to run 60 parallel backup sessions 3 GB of RAM plus 512 MB for data segments are needed. 300 - 425 MB of disk space + approximately 2% of planned data to be backed up (for use by the IDB). If the version of libstdc++ on the system is not 5 (for example libstdc++.so.6 instead of libstdc++.so.5) you need to install the compatibility package compat-2004 or compat-libstdc++. To install the Java GUI Server on Red Hat Enterprise Linux 4.0, the libstdc++-4.0.2-8.fc4.x86_64.rpm package is required. If yours system does not already contain a 64-bit version of libstdc++. so. 5 then you must install it with libstdc++-3.3.3-7.x86_64.rpm. To run the Java GUI Server on SuSE Linux Enterprise Server 9 (64-bit), the package compat-libstdc++-lsb-4 .0.2_20050901-0.4. x86_64 . rpm is required. Requirements for viewing online Help on the Data Protector Cell Manager are the same as on Data Protector clients. For Java GUI Client, Java Runtime Environment (JRE) 1.5.0_06 or newer (for example, 1.5.0_07) is required. Operating Systems supported by HP AutoPass The following Windows operating systems are supported by HP AutoPass: Windows 2000 Windows XP Windows Server 2003 (32-bit) Windows Vista (32-bit) Windows Server 2008 (32-bit) The following HP-UX operating systems are supported by HP AutoPass: HP-UX 11.00, HP-UX 11.11 (PA-RISC) HP-UX 11.23, HP-UX 11.31 (PA-RISC, Itanium) Solaris and Linux operating systems are not supported.

Error 1935.An error occurred during the installation

Error 1935.An error occurred during the installation of assembly 'Microsoft.VC80.ATL,



If you receive a 1935 error when you try to install software, the Windows file system transaction log has become corrupted. The transaction log is used by the Windows file system to recover when a file error occurs. It can also happen if there is an error with the installation of .netframework.
Step 1: To correct this install error, you need to clear the log.

a. Open an Administrator command prompt: Right-click Start > All Programs > Accessories > Command Prompt and select "Run as Administrator" and click "Allow" for the elevation prompt
b. In the command prompt, type the command below:
fsutil resource setautoreset true C:\
c. This assumes that C: is the drive in which Vista is installed. If it is installed on another drive like D:, please change the drive letter appropriately.
d. Reboot the system.
e. Install the software and check.
Step 2: Check if you are able to install in clean boot.
“How to perform Clean Boot” http://support.microsoft.com/kb/929135

Note: Please ensure that the computer is set to start as usual by following the step 7 from the article.
Step 3: Repair .net framework and check.
Repair the Microsoft .NET Framework installation
To do this, follow these steps:
a. Click Start, click Control Panel, and then click Add or Remove Programs.
b. In the Currently installed programs list, click Microsoft .NET Framework, and then click Change/Remove.
c. Click Repair, and then click Next.
Diana
Microsoft Answers Support Engineer
Visit our Microsoft Answers Feedback Forum and let us know what you think.

Configure IP address on RHEL 5 (GUI & Text mode)

Configure IP address on RHEL 5

 First Method – GUI

Issue the command below to bring up the GUI interface.

#system-config-network

Click on the desire NIC card profile and click on edit button at the top.

 

Select the "Statically set IP address" and key in your desire IP address.

 

Click on the "Activate" button

 

Click on the "Yes" button

Click  the "OK" button

Once done, issue the command below to for changes to take  immediate effect.

#service network restart

Or

#/etc/init.d/network restart

Second Method – Text Based GUI

Issue the command below to bring up the Text-Based-GUI.

#system-config-network-tui

Choose which NIC card you want to edit and hit the "Enter" key

 

Key in all the desire details and once you are done, hit the OK button.

 

Always restart the network service for changes to take immediate effect. Issue the command below to restart the network service.

#service network restart

Third Method – Editing Script File

The location of the script file is at

#/etc/sysconfig/network-script/ifcfg-eth0

Issue the command below to edit the script file.

#vi /etc/sysconfig/network-script/ifcfg-eth0

After you had edit the file, issue the command below to save the file

:wq!

Restart the network services for changes to take immediate effect

#service network restart

How to add/modify IP Address in Redhat Enterprise Linux

Adding the IP Address in Redhat Enterprise Linux can be done by using the netconfig tool or by editing the network-scripts or by using the ifconfig command. While this procedure is tested on Redhat Enterprise Linux, I'm sure it should work on CentOS, Fedora and older Redhat versions.

Set IP Address using Netconfig

Netconfig is a utility in Redhat Enterprise Linux which allows you to add/modify the IP Address the system, the Netmask, default gateways and the Name Servers.

Launch Netconfig,

rhel5# /usr/bin/netconfig

This launches a window as follows:

For static IP uncheck the "Use Dynamic IP configuration(BOOTP/DHCP)"

Now, enter the IP Address, netmask, Default Gateway & Primary Name Server.

Once done, restart the networking service

rhel5# service network restart

or to just reread the interface config files

rhel5# service network reload

This should set the IP Address.

Manually edit Interface configuration files

You can also manually edit the interface configuration files and add/modify the IP Address.

The Network interface configuration files are found in the directory

/etc/sysconfig/network-scripts/

Let's say there are 2 interfaces eth0 & eth1. The files to edit will be

ifcfg-eth0 – For interface eth0

ifcfg-eth1 – For interface eth1

To add the IP Address for interface eth0, edit ifcfg-eth0

rhel5# cd /etc/sysconfig/network-scripts

rhel5# vi ifcfg-eth0

Enter the following Parameters

DEVICE=eth0
BOOTPROTO=static
BROADCAST=192.168.1.255
HWADDR=00:0F:1F:2F:3F:4F
IPADDR=192.168.1.10
NETMASK=255.255.255.0
NETWORK=192.168.1.0
ONBOOT=yes
TYPE=Ethernet

Where

DEVICE indicates the interface
BOOTPROTO indicates if it is static IP or uses DHCP/BOOTP

The above sets the IP Address, Broadcast address, Network, Netmask etc.

Once done, save the file and restart the network service for the changes to take effect.

rhel5# service network restart

or to just reread the interface config files

rhel5# service network reload

Using ifconfig

This is dynamic and the change take effect instantly.

rhel5# ifconfig eth0 192.168.1.10 netmask 255.255.255.0 gw 192.168.1.1 up

This sets the IP Address, Netmask and the default gateway on the interface