Friday, 30 June 2017

A new version of the software has been released: HPE Data Protector 10.00

What's new in Data Protector v10:

  • New web-based graphical user interface (GUI) (Better late than never!)
  • Dashboard, new scheduler
  • New secure communication model
  • Oracle OS authentication

Tuesday, 4 April 2017

New patch HPE data protector 9.09


Data Protector 9.09 for Windows
https://softwaresupport.hpe.com/group/softwaresupport/search-result/-/facetsearch/document/KM02763755#Special Installation Instructions

Data Protector 9.09 for HP-UX
https://softwaresupport.hpe.com/group/softwaresupport/search-result/-/facetsearch/document/KM02763821


Data Protector 9.09 for Linux
https://softwaresupport.hpe.com/group/softwaresupport/search-result/-/facetsearch/document/KM02763695

What's new?

The following key features are introduced in Data Protector 9.09:
·         Windows Mount Proxy support (for GRE, PowerOn and liveMigrate from StoreOnce Catalyst)
·         Firewall-friendly Data Protector
·         Now compatible with DDOS 6.0 and DDBoost 3.3 
·         Dynamic update of VMs in a backup specification
·         NetApp ONTAP 9.0x C-mode supports
·         Telemetry service


Wednesday, 9 November 2016

HPE DP: Now DP support backup 1C:Enterprise with postgresql databases

At 9.07 version data protector adds the ability to make online backup of postgresql. Now you can backup all configuration 1C:Enterprise 8 (1С:Предприятия 8) platform with Oracle Database, IBM DB2, PostgreSQL, SQL Server.

HPE DP: Solve problem when postgres transactions fail with the "out of shared memory"

This is caused by default setting for postgreSQL parameter "max_locks_per_transaction" - default is 64. Need to increase the value to 1024 in postgresql.conf ( takes up about 30 MB of shared memory) and restart dp services. It's recomendation for 9.07 version of data protector.

From PostgreSQL 9.1.24 Documentation max_locks_per_transaction (integer) 

 The shared lock table tracks locks on max_locks_per_transaction * (max_connections + max_prepared_transactions) objects (e.g., tables); hence, no more than this many distinct objects can be locked at any one time. This parameter controls the average number of object locks allocated for each transaction; individual transactions can lock more objects as long as the locks of all transactions fit in the lock table. This is not the number of rows that can be locked; that value is unlimited. The default, 64, has historically proven sufficient, but you might need to raise this value if you have clients that touch many different tables in a single transaction. This parameter can only be set at server start.

HPE DP: Update support Matrices for DP 9.0

Update support matrices for DP 9.0:
https://softwaresupport.hpe.com/group/softwaresupport/search-result/-/facetsearch/document/KM01029738