olano Absent Member.
Absent Member.
1017 views

DP6.20 VEIA, a virtual machine as backup host

Hi All,

 

    We want to use the new integration VEIA of DP 6.20 to backup VMWare VMs. Because we don't have any dedicated physical machine, a virtual machie will be used a backup host.

     So I have two questions about this:

    1. For my understanding, if a virual machine is used  the backup host , the transportation mode would be LAN mode. Is that correct?Then how about the data flow would be? Does the backup host need enough space to hold the virtual machines to be backed up?

    2. Where will the media agent be installed ?  For the documentstion, it need be installed on the backup host. Is that correct? In our situation, the backup host is a virtual machine. I can't understand  how  the media agent on a VM  can  control the media?

 

    Can anyone help on this?

   Thanks!

 

Lan

  

0 Likes
1 Reply
Highlighted
Absent Member.. Wessam Ehab Absent Member..
Absent Member..

Re: DP6.20 VEIA, a virtual machine as backup host

it is possible to connect your backup device to SAN and configure it for use with Data Protector

Just read the below, it is all from the Online Help.

 

Preparing Backup Devices

Preparation of a backup device consists of connecting the device to the system or in an SAN environment to the SAN and knowing which of the (working) associated device files (SCSI address) is to be used.

Prerequisite

A Media Agent (the General Media Agent or the NDMP Media Agent) must be installed on each system that has a backup device connected or in an SAN environment on systems controlling backup devices on the SAN.

Steps

    1. Connect the backup device to a computer system or in an SAN environment to the SAN.
    2. Continue the preparation:

On Windows

Specify SCSI address syntax for a device connected to the Windows system.

On UNIX

Find or create the device filename for a device connected to the UNIX system.

  1. In case you plan that several devices will be using the same media, you have to ensure that the writing density and the block size settings are identical.
  2. Boot the system to have the device become known to the system.
  3. For some backup devices, additional steps have to be performed.

After preparing the backup device, configure it for use with Data Protector. Prepare the media that you want to use with your backups.


 

In the SAN Environment Step

Check that the same robotics device filename exists on all systems that need to access the shared library. Ignore this if you plan to use indirect library access.

On HP-UX and Solaris

On HP-UX and Solaris, the requirement of the device file identity is accomplished via hard or soft links, if necessary.

On Windows

On Windows clients, use the libtab text file to override default SCSI device identification and reassign robotics control devices to the logical drives defined on another host.

The libtab file should be created on the Media Agent client in the Data Protector home directory, as a text file with the following syntax (spaces in logical drive name are allowed):

<hostname> <control_device_file> <device_name>

for example

tavaja.hermes scsi2:0:4:0 DLT_1


 

In the direct backup environment Steps

    1. Check that the same robotics device filename exists on all systems that need to access the shared library. Ignore this if you plan to use indirect library access.

The requirement of the device file identity is accomplished via hard or soft links, if necessary. The other possibility is to use the libtab text file to override default SCSI device identification and reassign robotics control devices to the logical drives defined on another host.

The libtab file should be created on the Media Agent client in the Data Protector home directory, as a text file with the following syntax (spaces in logical drive name are allowed):

<hostname> <control_device_file> <device_name>

for example

tavaja.hermes scsi2:0:4:0 DLT_1

  1. To configure a device for direct backup, the WWN and LUN numbers for the device must be obtained. This can be done using the FC bridge administrative tool. The two numbers must be obtained as a 16 character hexadecimal string format, respectively. If the FC bridge administrative tool provide the LUN for the device as a 2 character hexadecimal string, this string must be entered as the second byte in the 16 character hexadecimal string.
  2. Check if the device file for the XCopy engine exists on the Media Agent client (backup system).

 

File devices

Turn off the compression option for the file you want to use as a device. You can do this through Windows Explorer:

Step

Right-click the file, click Properties, and deselect the Compress feature under Attributes.


 

Magazine Step

Create a media pool with magazine support before you configure a magazine device. The device must have support for magazines (for example, HP 12000e).


 

SCSI library, Jukebox, External Control Step

Decide which slots in the library you want to use with Data Protector. You will need to specify them when configuring a library.


 

Windows robotics drivers

On Windows, robotics drivers are automatically loaded for enabled tape libraries. To use the library robotics with Data Protector on a Windows system, disable the respective Windows driver.

Steps

  1. In the Control Panel, double-click Administrative Tools.
  2. Double-click Computer Management and then click Device Manager.
  3. Expand Medium Changers.
  4. Right-click the medium changer, for example 4mm DDS Medium Changer, and then select Disable.
  5. Restart the system to apply the changes. The robotics is now ready to be configured with Data Protector.

 

Hope This Helps 🙂

Wesam

Regards,
Wesam
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.