Quantcast
Channel: All Data Protector Practitioners Forum posts
Viewing all 10494 articles
Browse latest View live
↧

Re: GUI very slow in Data Protector 9.06

June 29, 2016, 1:36 pm
$
0
0

Hi mainland,

if you're absolutely sure that neither firewall, virus scanner or write performance to the OmniBack cluster share are the problem you will need to enable -debug 1-331,333-500,t:1000 for INET on the active cluster node and the GUI running on the same node. Demonstrate the issue by in few easy steps such as creation or modification of a backup spec then stop debugging and send the files to HPE support. If you're able to create a on screen video this might help.

Regards,
Sebastian Koehler

↧
Search

Re: GUI very slow in Data Protector 9.06

June 30, 2016, 1:47 am
$
0
0

yes a full understanding on when the GUI is slow and when it isnt? It might be down to certain hosts in the cell list and when they are accessed via the GUI....

As Sebastian says, debugs or screenshots/video might be the only route to understand...

↧
↧

Re: (DP) Support Tip: Removal of Mount Proxies from the VMware GRE Web Client

June 30, 2016, 1:56 am
$
0
0

Just to add up here, vmware gre component is added in 9.07 setup wizzard so it can be easily uninstalled. For older versions csetup.exe can be used eg: 

csetup.exe -quiet REMOVE=vmwaregre_agent

↧

(DP) Support Tip Vmware CBT backup failur, ... unable to utilize CBT .....

June 30, 2016, 5:04 am
$
0
0

Sometimes Data Protector CBT backups of a certain VM fail.

[Normal] From: VEPALIB_VMWARE@rz3602.gewkoelnag.de ""  Time: 06/01/2016 02:17:12 PM
 Virtual Machine 'instp1.re-rz.de': Backing up configuration file instp1.re-rz.de.vmx ...

[Normal] From: VEPALIB_VMWARE@rz3602.gewkoelnag.de ""  Time: 06/01/2016 02:17:14 PM
 Virtual Machine 'instp1.re-rz.de': Creating snapshot ...

[Critical] From: VEPALIB_VMWARE@rz3602.gewkoelnag.de ""  Time: 06/01/2016 02:17:20 PM
 Backup failed because unable to utilize CBT as it was required.
 
 
This might be a Vmware limitation.
In such a case it is always good idea to double check if the prerequisites for CBT are fulfilled.

https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1020128
Changed Block Tracking (CBT) on virtual machines (1020128)
….
For CBT to identify altered disk sectors since the last change ID, these items are required:
• The host must be ESX/ESXi 4.0 or later.
• The virtual machine owning the disks to be tracked must be hardware version 7 or later.
• I/O operations must go through the ESX/ESXi storage stack. So NFS is supported, as is RDM in virtual compatibility mode, but not RDM in physical compatibility mode. VMFS is supported, whether backed by SAN, iSCSI, or local disk.
• CBT must be enabled for the virtual machine (see below).
• Virtual machine storage must not be (persistent or non-persistent) independent disk, meaning unaffected by snapshots.

↧

DP 9.04 - VMware integration - recommended number of backup hosts

June 30, 2016, 8:45 am
$
0
0

I am looking at moving my client from Veeam to DP/VMware integration. DP v9.04 plus we'll upgrade to v9.06/07

Veeam has a recommended number of backup streams per backup proxy however DP doesnt seem to have that.

For HOTADD and SAN mode, how many backup streams should we recommend per backup host? This client environment will potentially be big so we need to size the proxies to cope with it. Whether this is virtual and/or physical backup hosts.

thanks

↧
↧

DP 9.00 build 88 - Virtual Machine 'VM_BK_Client': Could not backup disk scsi0:0

June 30, 2016, 10:48 am
$
0
0

Hello ,

I'm getting an error on data protector 9  "Virtual Machine 'VM_BK_Client': Could not backup disk scsi0:0" while trying to backup virtual machine.

about environment:

DP 9.00 build 88 - physical linux server - On this server cell manager, VEPA agent , media agents are installed.

i have MSL 6480, StoreOnce 6500 -

I want to perform backup of virutal machine in SAN mode - ofcourse virtual agent has been installed on physical server.

Clients are imported using admin account from vcenter [Standard integration] to cell manager.

Datastore lun's are presented to Backup host [Physical server] and vcenter and Data protector servers are able to resolve the names.

client backup destination is StoreOnce 6500 - Catalyst store

when i performed backup i got the error written in the subject of this post.

Can anyone suggest what is wrong or something i am missing in the configuration ?

Many thanks,

 

logs::

[Normal] From: BSM@ backup_Host_cell_manager "Windows_Cluster"  Time: 6/30/2016 6:18:23 PM
 Backup session 2016/06/30-16 started.

[Normal] From: BSM@ backup_Host_cell_manager "Windows_Cluster"  Time: 6/30/2016 6:18:24 PM
 OB2BAR application on " backup_Host_cell_manager" successfully started.

Warning: program compiled against libxml 208 using older 207
[Normal] From: VEPALIB_VMWARE@ backup_Host_cell_manager ""  Time: 06/30/2016 06:18:25 PM
 Resolving objects for backup on vCenter "Vcenter_server"...

[Normal] From: VEPALIB_VMWARE@ backup_Host_cell_manager ""  Time: 06/30/2016 06:18:28 PM
 Virtual Machine 'VM_BK_Client': Usersnap found.  But only Main VM will be backed up ...

[Normal] From: VEPALIB_VMWARE@ backup_Host_cell_manager ""  Time: 06/30/2016 06:18:28 PM
 Add Virtual Machine to the backup ...
  Name: VM_BK_Client
  Path: /datacenter/VM_BK_Client
  InstanceUUID: 503f56a7-c9ef-c955-90de-b6f4e84725d5

[Normal] From: VEPALIB_VMWARE@ backup_Host_cell_manager ""  Time: 06/30/2016 06:18:30 PM
 Virtual Machine 'VM_BK_Client': Locking vMotion ...

[Normal] From: VEPALIB_VMWARE@ backup_Host_cell_manager ""  Time: 06/30/2016 06:18:32 PM
 Creating folder /var/opt/omni/tmp/d2337af7-8b20-49ff-a5c0-ab5f96472933 ...

[Normal] From: VEPALIB_VMWARE@ backup_Host_cell_manager ""  Time: 06/30/2016 06:18:32 PM
 Virtual Machine 'VM_BK_Client': Backing up configuration file VM_BK_Client.vmx ...

[Normal] From: VEPALIB_VMWARE@ backup_Host_cell_manager ""  Time: 06/30/2016 06:18:33 PM
 Virtual Machine 'VM_BK_Client': Creating snapshot ...

[Major] From: VEPALIB_VMWARE@ backup_Host_cell_manager ""  Time: 06/30/2016 06:19:54 PM
 Virtual Machine 'VM_BK_Client': Could not backup disk scsi0:0 ...

[Major] From: VEPALIB_VMWARE@ backup_Host_cell_manager ""  Time: 06/30/2016 06:19:54 PM
[172:285]  Virtual Machine 'VM_BK_Client': No disk backed up ...

[Critical] From: VEPALIB_VMWARE@ backup_Host_cell_manager ""  Time: 06/30/2016 06:19:54 PM
 Backup of object failed.
  Name: VM_BK_Client
  Path: VM_BK_Client
  InstanceUUID: 503f56a7-c9ef-c955-90de-b6f4e84725d5

[Normal] From: VEPALIB_VMWARE@ backup_Host_cell_manager ""  Time: 06/30/2016 06:19:55 PM
 Virtual Machine 'VM_BK_Client': Removing snapshot ...

[Normal] From: VEPALIB_VMWARE@ backup_Host_cell_manager ""  Time: 06/30/2016 06:19:57 PM
 Virtual Machine 'VM_BK_Client': Unlocking vMotion ...

[Normal] From: BSM@ backup_Host_cell_manager "Windows_Cluster"  Time: 6/30/2016 6:20:12 PM
 OB2BAR application on " backup_Host_cell_manager" disconnected.

[Normal] From: BSM@ backup_Host_cell_manager "Windows_Cluster"  Time: 6/30/2016 6:20:43 PM

 Backup Statistics:
         
  Session Queuing Time (hours)         0.00       
  -------------------------------------------     
  Completed Disk Agents ........          0         
  Failed Disk Agents ...........          0         
  Aborted Disk Agents ..........          0         
  -------------------------------------------     
  Disk Agents Total  ...........          0         
  ===========================================     
  Completed Media Agents .......          0         
  Failed Media Agents ..........          0         
  Aborted Media Agents .........          0         
  -------------------------------------------     
  Media Agents Total  ..........          0         
  ===========================================     
  Throttled Gateways ...........          0         
  Gateways Total ...............          2         
  ===========================================     
  Overall Deduplication Ratio ..          -           
  ===========================================     
  Mbytes Total .................       0 MB       
  Used Media Total .............          0         
  Disk Agent Errors Total ......          0   


============================================================================
                      Session completed with errors!
============================================================================

DPX

 

 

 

 

↧

Data Protector Not a Valid Mount Point on Network Share

June 30, 2016, 12:08 pm
$
0
0

Hello all,

   We're using Data Protector A.06.11, I'm running into a problem with one of my backups this week.  I have a job where it is backing up four Network Shares using one cell manager.  For some reason over this past weekend one of the shares started receiving the "Not a valid mount point" error 81:52 (The filesystem mount point specified by the user is not a real mount point on the system running the VBDA agent) and aborted. The other 3 shares backed up just fine with no problems. The only thing that happened is that my boss totally re-arranged files and folders within this one share (deleted some, moved them out, renamed a few, and created new ones) which I'm sure is the cause of the problem. I've tried recreating the job but still receive the same error. The Actions says to " Verify the configuration of the backup object and the table of mounted filesystems on the host running the VBDA agent" - how or where do you do this at. Where is the VBDA agent? The cell manager is on a Windows 2003 system but the network share is a CIF and does not contain a real OS. Any ideas as to how to correct this?

↧

(DP) Support Tip Vmware CBT backup failure, ... unable to utilize CBT .....

July 1, 2016, 3:48 am
$
0
0

Sometimes Data Protector CBT backups of a certain VM fail.

[Normal] From: VEPALIB_VMWARE@rz3602.gewkoelnag.de ""  Time: 06/01/2016 02:17:12 PM
 Virtual Machine 'instp1.re-rz.de': Backing up configuration file instp1.re-rz.de.vmx ...

[Normal] From: VEPALIB_VMWARE@rz3602.gewkoelnag.de ""  Time: 06/01/2016 02:17:14 PM
 Virtual Machine 'instp1.re-rz.de': Creating snapshot ...

[Critical] From: VEPALIB_VMWARE@rz3602.gewkoelnag.de ""  Time: 06/01/2016 02:17:20 PM
 Backup failed because unable to utilize CBT as it was required.
 
 
This might be a Vmware limitation.
In such a case it is always a good idea to double check if the prerequisites for CBT are fulfilled.

https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1020128
Changed Block Tracking (CBT) on virtual machines (1020128)
….
For CBT to identify altered disk sectors since the last change ID, these items are required:
• The host must be ESX/ESXi 4.0 or later.
• The virtual machine owning the disks to be tracked must be hardware version 7 or later.
• I/O operations must go through the ESX/ESXi storage stack. So NFS is supported, as is RDM in virtual compatibility mode, but not RDM in physical compatibility mode. VMFS is supported, whether backed by SAN, iSCSI, or local disk.
• CBT must be enabled for the virtual machine (see below).
• Virtual machine storage must not be (persistent or non-persistent) independent disk, meaning unaffected by snapshots.

↧
Search

Re: The session does not end, last post Completed Media Agent

June 30, 2016, 10:03 pm
$
0
0

Thanks sebastian, I introduced the line you comment and today backups have completed successfully

regards

↧
↧

Re: DP 9.00 build 88 - Virtual Machine 'VM_BK_Client': Could not backup disk scsi0:0

June 30, 2016, 11:36 pm
$
0
0

Hi dpx,

build 88 is the very first Data Protector A.09.00 release (included on the original media kit released back in 2014). Please update the Cell including the VEPA backup proxy to version A.09.06_108. It contains so many fixes that will most probably resolve the issue.

Regards,
Sebastian Koehler

↧

Re: DP 9.04 - VMware integration - recommended number of backup hosts

June 30, 2016, 11:47 pm
$
0
0

Hi KloppYNWA69,

performance requirements for SAN transport and HOTADD are similar. I usually recommend a single core (vCPU) per parallel stream. Depending on the other agents running (Media Agent) you will should have 16 GB RAM. So this is very similar to what they do with Veeam. Monitoring the system when the backup is running to see if it works prpperly.

Regards,
Sebastian Koehler

↧

Re: Data Protector Not a Valid Mount Point on Network Share

July 1, 2016, 2:42 am
$
0
0

Hi Ron,

for Network Share backups the VBDA process is executed on a Windows client that reads the data from the CIFS share.

It is mandatory to run the Data Protector INET service on this client as a named user that is able to connect to the share and read the data (instead of LOCAL SYSTEM). Here is a screenshot of the Map Network Share dialog. The Client system entry here is the Windows where VBDA is executed.

2016-07-01_11h29_13.png

Please connect to the Windows client as the Data Protector INET service user and try to open the share as specified in the backup spec. Does this work?

Regards,
Sebastian Koehler

↧

Converting Cell Manager from HP UX

July 1, 2016, 6:18 am
$
0
0

I think the answer is no, but since we are now running 9.06, is it possible to migrate the Database from HP UX 11.31 to Redhat?

Thanks,

Tommy

↧
↧

Re: Converting Cell Manager from HP UX

July 1, 2016, 7:09 am
↧

（DP）Support tips Migrate CM

July 3, 2016, 8:22 pm
$
0
0

1)    Make the safety OFFLINE copy of db80 and confg dirs for disaster recovery purpose

In old cell:

             - omnistat (confirm no backup running)

            - omnisv –stop (stop DP services)

            - copy the “db80” and “config” folder

 

2)    On the old cell, execute writedb of both CDB and MMDB

 

---start DP service:   #omnisv –start

---check IDB and confirm works:   #omnidbcheck –extended  (will take 3-6 hours)

---write IDB to txt files:       omnidbutil –writedb \database (will take 4-8 hours)

             

3)    At the end of the writedb, copy the directories proposed by the writedb

 

Should be： <DP dir>\db80\dcbf

And:                 <DP dir>\db80\msg

 

 

4)    Copy the CONFIG directory (with datalists, barlists, schedules, etc ...)

 

5)    Write down (from omnidbutil –extendinfo) any IDB extension files

 

check and note down the number of existing extensions (fnames/fn/dcbf)

                    ---In  D:\ProgramData\OmniBack\db80\datafiles\Cdb

                    ---omnidbutil –extendinfo > IDB.txt

 

6)    Stop the DP, uninstall the DP from old location (If old and new are two  hosts, please ignore this step)

 

7)    Install the DP to the new disk / location

 

---Installed the DP agent and latest DP patches   

 

8)    Extend the IDB files, based on the info from step #5

 

In GUI—Internal database---usage---<right click> Database tablespace Extension—Add Database tablespace Extension files

 

9)    Execute the readdb on the new IDB from the original files

 

     --omnidbutil –readdb \database

 

10)  Copy the dirs proposed by #3 to their new locations

                           <DP dir>\db80\dcbf

And:                 <DP dir>\db80\msg

 

11）Open GUI, testing everything works

 copy the complete <DP_DATA_DIR>\config\server\idb\ dir from before overwrite 

not only idb.config

 12)  Copy CONFIG folder content to the new location

13）copy back <DP_DATA_DIR>\config\server\idb\ dir in step12

14) restart DP services

15) omnidbutil -show_cell_name

16) omnidbutil -change cell_name <new name>

 

↧
Search

(DP) Support Tip: Hyperv VM "State"

July 4, 2016, 4:53 am
$
0
0

It is important to NOTE, that during an initial backup configuration, that all vm's on a single hyperv node or all vm's participating in a multi-node cluster are in a NON-CRITICAL state as reported by the hosting hyperv node.  During the browse, if a return value of critical is reported against any vm on a given hyperv node, this will crash the DP agent

↧

Procedure to change new ip address in Cell Managers by ISP migration

July 4, 2016, 8:11 pm
$
0
0

We need to change IP Address of our Cell Managers and nodes because we are changing the ISP. This change is imminent. However, we want a procedure that should have to change Databases in Cell Managers, stop services, change re-hosts with new ip address."

↧
↧

GRE plugin integration with vCenter 5.5 and DataProtector 9.06

July 5, 2016, 2:50 am
$
0
0

Hello all,

I'm facing some errors regarding this topic... I planned to migrate my infrastructure from vCenter / vSphere 5.1 to 5.5.

I'm licensed with the VMware GRE plugin, It works well with the 5.1 infrastructure

I already prepared the 5.5 servers, I integrated the server to DataProtector in order to validate that the GRE is working, but the problem is the following :

When I use the vSphere Web Client, if I go to the "HP DataProtector" tab, I have this error : Http Error - 500 
{"message":"Unexpected error :There was a problem while sending query to service https://myservername.mydomain:7116/dp-gui/grePlugin/GetMountProxies.jsp?newMachineTypeParam=ESX. Check that this agent is accessible."}

The server is reachable, it works properly... When I try to access the URL directly from my browser, I have a 404 error....

Maybe there is a little trick... I don't know, please help me =(

↧

Re: GRE plugin integration with vCenter 5.5 and DataProtector 9.06

July 5, 2016, 3:55 am
$
0
0

check your IE version. IE might need upgrading....

↧

Re: GRE plugin integration with vCenter 5.5 and DataProtector 9.06

July 5, 2016, 4:41 am
$
0
0

I have the same problem using IE11 or Google Chrome

I see that the tab is named "HP Data Protector"... On the 9.06 version, it's "HPE Data Protector" if I'm right, no ?

↧
Viewing all 10494 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>