Only one source can write to one drive therefore for the big data, you would be best to split these partitions out in DP so you have more objects, thus both drives can be used at the same time....
↧
Re: Can data protector write from one source to two tape-drives?
↧
[172:512] virtual machine ´MyVM` Download of disk descriptor file (MyVM.vdk) failed
I have this error, when I start backup VM.
Descriptor error:
I try resotore on directory without problem.
My user have all right the same root vsphere, any idea??
Thanks
↧
↧
Granular recovery to restore error
Hi all ,
I have implemented granular recovery (DP 9.08 and VCENTER 6.0) , backups and GRE restore work well on windows VM
but, By using Granular Recovery and restore on linux VM i see the following error message:
----Details: CannotaccesstonetworkshareontargetVM---
I dont have a network share configured in any VM my restore path is a local filesystem.
It works well in Windows VM but not in Linux VM
Please your help
Thanks.
Cristhian
↧
Re: [172:512] virtual machine ´MyVM` Download of disk descriptor file (MyVM.vdk) failed
Hello
I can imagine two possibilities for this,
1º User doesn't have anough rights.
Datastore -> Allocate space
Datastore -> Browse datastore
Datastore -> Low level file operations
Datastore -> Remove file
Datastore -> Rename datastore
Folder -> Delete folder
Folder -> Rename folder
Global -> Licenses
Host -> Configuration -> Maintenance
Host -> Inventory -> Add standalone host
Network -> Assign network
Resource -> Assign virtual machine to resource
pool
Resource -> Remove resource pool
Resource -> Rename resource pool
Sessions -> Validate session
vApp -> Delete
vApp -> Rename
Virtual machine -> Configuration *
Virtual machine -> Interaction -> Answer question
Virtual machine -> Interaction -> Power Off
Virtual machine -> Interaction -> Power On
Virtual machine -> Inventory -> Create new
Virtual machine -> Inventory -> Register
Virtual machine -> Inventory -> Remove
Virtual machine -> Inventory -> Unregister
Virtual machine -> Provisioning *
Virtual machine -> State -> Create snapshot
Virtual machine -> State -> Remove snapshot
• Web service: Optionally, change the web service
2º Descriptor file is in wrong state or corrupted, Have you treid to download file manually from Vsphere or web console?
Best Regards
↧
Data Protector 9
Hi,
I am trying to import a windows installation server for DP onto my cell manager. The cell manager is an HPUX 11.31 server which also is the unix installation server for DP. This is working.
The windows server (Microsoft Windows Server 2012 R2 Standard - Version 6.3.9600) has had the DP installation server version software installed.
I am now attempting to import the windows server as an installation server on the cell manager but the error I am getting is:
Import Installation Server failed
The installation server information cannot be added/udpated in the Cell Manager configuration file.
The actions that follow are all correct - Check tha the Data Protector services on the Cell Manager computer are running, check that the Data Protector inet server on the remote computer is running and install that host as a Data Protector Installation Server.
Any advice gratefully accepted.
↧
↧
Re: Data Protector 9
hi,
Looks like comunication.
did you check ping , telnet, nslookup and both ways,
ping <client_longname>
ping <client_shortname>
nslookup <client_longname>
nslookup <client_shortname>
nslookup <client_ip>
telnet <client_name> 5555
Regards.
↧
Re: Data Protector Post-Backup Copy Protection
ok. Thanks for the answer!
↧
Re: Bad catalog access for message #0 in set 9004
# omnicheck -patches
Patch level Patch description
===========================================
DPUX_00084/DPLNX_00372 Core Component
DPUX_00085/DPLNX_00373 Cell Manager Component
DPUX_00086/DPLNX_00374 Disk Agent
DPUX_00087/DPLNX_00375 Media Agent
DPUX_00088/DPLNX_00376 User Interface
PHSS_43643/DPLNX_00255(BDL703) English Documentation (Guides, Help)
SSPUX700_019 mmd Site Specific Patch
QCCR2A68666_HF1 rsm Test Binary
Number of patches found: 8.
This does not happen to other gui consoles and only on one/two jobs We have not installed any new patches for some time.
Thanks,
Marcus
↧
Re: Bad catalog access for message #0 in set 9004
Out of support...no assistance
↧
↧
Re: Bad catalog access for message #0 in set 9004
Hello
If it just happen for SQL backup please provide to use list of pacthes installed into SQL client
omnicheck -patches -host "sqlhostname"
From SQL server output for command sql_bar -version
Best Regards
↧
I can't add 2nd Drive in Dataprotector
Hi everyone,
I have :
- One HP MSL2024 0-Drive Tape Library (AK379A)
- 2xDrives HP MSL LTO-5 Ultrium 3000 FC (BL544B)
- and a HP Dataprotector Licenced.
The 1st Drive is correctly detect by the software. But the second drive doesn't show any scsi adress.
Both are connected on a SAN Switch.
When i tape this commande (devbra -devices) i get the following result (attached).
Did anyone get this problem before?
Kindly,
↧
Re: I can't add 2nd Drive in Dataprotector
Hi Gildaram,
From the output we see you're on a Windows host. The library is detected by devbra and one device. What is seen in the Windows Device manager? If the second device is not seen there either then try a rescan and/or a reboot first of all. You first need the device to be visible on the host before Data Protector can see it. If the device is visible on the host, but not in DP then I would suggest to generate devbra debugs and provide them to HPE support.
Koen
↧
Re: DP 9.07 Using COFC - Poor Performance
Hi Aleskol
We have since provisioned FC-VTLs and we are seeing in excess of 200mbps thoughput, however I am curious to find the exact reason as to why we were forced to abandon COFC, so info as follows ...
- DP 9.07
- Storeonce 4900 / Catalyst Stores / Basic config.
- DP Devices created, SAN attached server used as MA.
- Segment, disk buffer and drives size settings - All manor or configuration has been attempted,
- Source side dedupe is not enabled.
Your comment regarding the OMNIRC values is not something that I have come across, so an interested suggestion, howver as menditoned we are now using FC-VTLs (dedupe enabled) and the bakcups are screaming though.
↧
↧
DP9.07 Vmware integration - usersnap found backup failure
We have vmware integration backups running in DP9.06. Vsphere 5.5
backup is set with CBT enabled. When DP does an incremental it reports a warning saying incremental not possible, will do a full as a usersnap is found.
BUT we then get a MAJOR error [172 : 511] incremental/differential backups not supported when CBT is not used
this seems like a bug....
the backup already reports the warning and says it will do a full but then fails.
we have CBT enabled in the configuration of the specification plus also fallback if CBT is not possible.
anyone seen this?
↧
Re: Cannot start "rds" service, system error: [1053]
I have tried the option which you have given moving the file rdm.chi to different location, which i not worked.
↧
Re: DP9.07 Vmware integration - usersnap found backup failure
Please check page 713/714 of the DP Integration Guide (October 2016), this should address your issue.
In case you are using another version of the Guide, search for "User Snapshot".
↧
Re: DP9.07 Vmware integration - usersnap found backup failure
thanks Michael.
Yes I can see this however I'm baffled why DP shows a warning that incremental is not possible so a full is performed, therefore we assume a full will be done.
We then get the MAJOR error and it fails. The spec is also configured to allow fallback if CBT is not possible.
In my view this backup should work and revert to a full without failure if a user snapshot exists.
↧
↧
Re: Cannot start "rds" service, system error: [1053]
can you upload debug.log here so I can check it
↧
Pre-requisitos para instalar clientes Linux no DP.
- a) garanta que o cliente Linux é suportado, consultando HP Data Protector Platform and integration support matrix
1.b) garanta que o cliente Linux já tenha instalados os pacotes:
- xinetd
- rpm
Ambos são pré-requisitos para a correta instalação e funcionamento do Data Protector.
- c) verifique o arquivo /etc/services e comente as entradas:
personal-agent 5555/tcp # Personal Agent
personal-agent 5555/udp # Personal Agent
Elas conflituam com a porta tcp utilizada pelo Data Protector.
- d) Garanta que a porta 5555 não esteja bloqueda no firewall
- e) Garanta as compatibilidades de bibliotecas abaixo:
- d) Have the compatibility package.
# rpm -qa |grep glibc
glibc-devel-2.12-1.192.el6.x86_64
glibc-common-2.12-1.192.el6.x86_64
compat-glibc-headers-2.5-46.2.x86_64
glibc-2.12-1.192.el6.i686
compat-glibc-2.5-46.2.x86_64
glibc-2.12-1.192.el6.x86_64
glibc-headers-2.12-1.192.el6.x86_64
O comando para instalar:
yum install glibc.i686
Have net-tools installed (some net-tools utilities are needed during installation).
- e) Garanta que o file system onde está montado o /tmp não esteja com a flag noexec, caso contrário, uma mensagem de falta de permissões será emitida durante a instalação.
↧
IDB Users
Four database users exist and are available after the installation. They are important for the DP implementation and configuration, but not visible during the day-to-day work. (A configurable IDB service account is needed in DP to access the IDB; the IDB service is run under this account:) One of them, the user hpdp, is mapped to an OS user and must be created on Unix systems before the DP 8.00 installation. On Windows, the same user as for the CRS Account (DP Administrator) is used per default. The other three users are created automatically during IDB installation; the support user has super user capability and is thought for support to look at the IDB. #
(Before the DP installation, the customer has to create an OS user to become the DB super user and provide the name during installation.
- On Windows, the DB super user can be a local or domain account. (By default it is the DP Administrator, which is already provided during installation. No new user needs be created if the DP Administrator is taken. A dialog window allows during the DP installation process to specify another OS user as DB super user if desired.)
- On Linux and HP-UX, the database OS super user must be created prior to the installation. The recommendation on Linux and HP-UX is to name it as hpdp and to create a user group (with the same name) hpdp that the user belongs to.
The other database usernames are predefined in DP 8.00 and must not be changed by the customer.
The database OS super user (for example hpdp on Unix) is allowed to connect to the database without providing a password. For other DB users, the initial passwords are randomly generated during the installation, but can be changed. And these DB users must enter a password to get access to the DB. As a rule, the regular user will not access the IDB, but for very advanced users and support this possibility is opened.)
(Password maintenance:
- Database OS super user: The password can be changed with the OS admin tools. On Windows the customer must additionally adapt the password in the configuration of the Internal Database service hpdp-idb.
- Database users: The password can be changed with the CLI tool omnidbutil: E.g.
Omnidbutil –set_passwd <username> hpdpidb_spt
With this tool is for every user type the (during installation randomly predefined) password changeable/settable. When changing the password of the application user hpdpidb_app, the tool will not only modify the password in the database, but also update the encrypted password in the idb.config file. Also the JBoss AS password for accessing the database is updated.
The support user is super user and can do everything within the data base. With this account a user can log on to the database and perform appropriate queries. (This is to ease the administration for that the hpdb password would not needed to be changed to grant for support access to superuser functionality.)
Remember to restart the IDB service.
Ownership and permissions
The Super user hpdp owns the tablespace hpdpidb, the actual database hpdpidb as well as the database schema hpdpidb_app. (The support user has also super user capabilities!)
The Application user hpdpidb_app has full control within the schema hpdpidb_app, and owns all objects (tables, views, procedures, functions, triggers …) that exist inside this schema.
The Reporting user hpdpidb_rpt is allowed to use schema hpdpidb_app and select data from any object.)
↧