Hi Team,
1) Could you explain me the difference between DP7 vs DP8 vs DP9 and changes that took place?
2) what are the services that run at the time of backup configured and client?
Please, guys, I would like to reply to the 2 queries asap.
Hi Team,
1) Could you explain me the difference between DP7 vs DP8 vs DP9 and changes that took place?
2) what are the services that run at the time of backup configured and client?
Please, guys, I would like to reply to the 2 queries asap.
Hi everyone,
we are using DP9.00 with a deduplicated store (stored on an another server).
On the gateway we can see that 1TB of data is used for a 16,5 deduplicated ratio.
When i do a "storeoncesoftware --list_stores" on the server, i've the same informations.
BUT, the size of the "StoreOnceLibrary" is 3.2TB ...
What can i do ? How can i "purge" this database ?
Any advices would be welcome ;)
Regards,
AP
To answer "1", the main difference, I'd say...
DP 7.0 used a different internal database (IDB) to the later DP versions (8.0, 8.1 and 9.0).
Since DP 8.0 we use Postgres for the IDB.
8.1 and 9.0, because of the new IDB, is more powerful/scalable than 7.0.
The Postgres DB needs more disk space than the DP IDB needed.
Approx 3 - 4 times more disk space for storing the records of the same backups.
DP 7.0 and 8.0 go out of support middle of next year (2016).
DP 8.1 is due to go out of support in 2017.
There is no date yet for when 9.0 goes out of support.
There will be 100s, possibly 1000s of other smaller differences.
Basically 9.0 is the newest, it most supports up to date applications/operating systems.
Hello
Please open support case, we will provide to you an script for to clean and shyncronize SOS information and IDB information.
Best Regards
Hello All
From DP 8.13 and DP 9.03 we have insteresting util_cmd option for to check, set or delete omnirc variable remotely to clients from cell server.
This is usefull in cases like you need to add teh same omnirc variable in several servers.
util_cmd -getomnirc <hostname> <name>
util_cmd -setomnirc <hostname> <name> <value>
util_cmd -delomnirc <hostname> <name>
Best Regards
Hello
Everybody know how much frequebtly from support we request debugs :) , in some cases files created are very big. Well for to avoid this from DP 9.03 is possible create debugs directly compressed in gz format it will help avoiding very big files.
Problem:
A debug log file is created for each thread of a DP process selected for tracing (per module selection). Each debug log file contains execution traces for the thread of configurable detail level. Consequently, collecting logs over an extended period consumes a lot of disk space.
Solution:
Enable in-line compression in gzip format for debug logs.
Best Regards
Hello,
AlesKol, Thank you for your answer.
SOS version will be upgraded together with the upgrade of DP environment.
I opened a support case and we resolved the issue with some help of HPE community.
Suggested solutions were: to move the store; to use this is read-only mode and create a new store; to assing more space to the store. As I did not have spare >10TB LUNs that was not possible.
HPE community posts offered some help:
I did not have a s.bad_integrity file, but had s.dirty file which indicates the store did not close correctly, and a recovery process took place.
I deleted the s.dirty file and then wasable to start the StoreOnceSoftware daemon. At first, the store did not start, but after a while I was able to start it manually and then executed omnimm -delete_unprotected_media command which recovered some space.
Now I am able to successfully start and stop my SOS store.
Best Regars,
Kaspars
Possibly there are media on the Store that are unknown to the DP IDB.
As "JBasilio" says if you contact DP support there is a script they can provide (syncStoreAndIDB.pl).
If there are such media/objects (on the Store, but unknown to the DP IDB)
the script can either delete them, or import them.
Hello,
This is my first DP installation and just finished installing it on a linux server. I've aware that there has been 4 patches released latest one 9.04. Sorry to ask but couldnt find any info about this. For just a fresh installation like this do we need to apply all the previous patches to bring it inline like install 9.01, 9.02, 9.03.. or just applying 9.04 contains all previous patches embedded ?
Thanks!
mula-E
hello,
incremental backup run with following errors on many db's. backup scheduled to run at night.
but when I run same backup on the morning it run successfully.
Please help ASAP.
RMAN-03009: failure of backup command on dev_2 channel at 11/05/2015 05:03:32
[Major] From: OB2BAR_SBT_CHANNEL@gervworap010.corp.zim.com "AFSYS" Time: 11/4/2015 11:03:24 PM
Cannot start DBSM ([12:1602] Cannot access the Cell Manager system. (inet is not responding)
The Cell Manager host is not reachable or is not up and running
or has no Data Protector software installed and configured on it.
System error: [10049] Address already in use
ORA-19509: failed to delete sequential file, handle="DB_AFSYS-Full<AFSYS_16191:894949213:1>.DBf", parms="SBT_LIBRARY=C:/PROGRA~1/OmniBack/bin/orasbt.dll,ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=AFSYS,OB2BARLIST=DB_AFSYS-Full)"
ORA-27027: sbtremove2 returned error
ORA-19511: Error received from media manager layer, error text:
Vendor specific error: OB2_StartQueries() failed ERR(0)
ORA-19513: failed to identify sequential file
RMAN-12018: channel dev_2 disabled, job failed on it will be run on another channel
Hi,
The new Advanced GRE plugin for VMware was designed to run outside of the vCenter so it can be used with new Virtual Center appliances from VMware.
These VCSA appliances usually have iptables running and blocking incoming connections. So it is required to stop iptables or open the required ports (15000-15999) as explained in the GRE guide:
Make sure the VMware Granular Recovery Extension Agent (vmwaregre-agent.exe) is in the list of Windows/Linux Firewall exceptions, on both the mount proxy system and the vCenter Server systems.
Note: Only inbound firewall rules are automatically created during the installation of the Granular Recovery Extension for VMware vSphere. You need to manually create any outbound firewall rule. This is required for communication between the extension's components and the vCenter Server. For the required port ranges, see the HP Data Protector Installation Guide: "firewall support"
The port ranges for the Advanced GRE Web-plugin are between 15000 and 15999.
If the connection to these ports is not allowed, the plugin will fail to connect to the VCSA and you will get an error when trying to save the GRE settings.
Regards,
Juanjo
Hello
All general releases patches are superseded, it means that 9.02superseded 9.01 and moreover....you can upgrade from 9.0 to 9.04 whitout issues.
Best Regards
Hello ,
From new version of DP 9.04 you can see that for the first time DP supported online backup for MySQL 5,5 and superr.
Please see ref. --> Plat. Support Integr. Matrix. dor DP 9.03/9.04
Thas is good news for MySQL guys..
BR
Emil
Hello,
This error seems that you have blocked Inet service, please check that, kill all services of Data Protector on the host or restart the host: gervworap010.corp.zim.com, and try again start the backup.
Check the firewall rules or network overhead in time of the backup!
Please, provie as:
Cell Manager: version of DP and patch level?
Disk Agent: version and patch level?
BR
Emil
Hi JBasilio!
Many thanks for the clarification, understood.
BR,
Mula_E
Hi,
It is funny to post this as I myself work in Hewlett Packard Enterprise itself however I guess I am still looking for an expert from HP on Oracle integration with Oracle RMAN in order to seamlessly manage Oracle DB backups.
I have successfully integrated RMAN governed DB backups with Backup tools like EMC Networker and Symantec Netbackup.
When I started exploring RMAN integrated Oracle DB backups management with HP Data Protector as backup tool, I was looking for a way through the integration to see if RMAN can solely manage, retain and purge Oracle DB backups based on its Retention Policy defined, say 30 days as retention period. So when I fire a command at RMAN CLI like DELETE OBSOLETE; RMAN could convey to DP Cell Manager that any backup for the specific Oracle DB older than 30 days must be physically deleted at this very time which inturn triggers this through Media Agent Clients and qualified backups get deleted, Cell Manager updates its catalog and confrms back to RMAN that requested backups are deleted. Subsequently RMAN updates its own Catalog and marks those OBSOLETE backups as deleted and comes out clean. And I call this perfect output of an end to end integration.
Above is the way things work perfectly when I successfully implemented RMAN integration with NETWORKER and NETBACKUP backup tools. Retention period in these backup tools are set very high as 20 years just to make sure backup tool in itself never qualify Oracle DB backups for purging. RMAN retention period for the Oracle DB is set to, say 30 days, value provided by business and confirmed by application team who is managing application running on the spefic Oracle DB. With this perfect integration in place, RMAN beautifully manages what backup pieces are to be retained and what is to be purged on a frequent basis. Everything is implemented through CRON jobs, completely outside backup tool console.
Since HP DP is also a certified backup tool through a cooperative program called Oracle Backup Solutions Program:
http://www.oracle.com/technetwork/database/features/availability/bsp-088814.html
I expected same RMAN controlled management when it came to HP Data Protector. I have been struggling, even with HP DP Support guys to see how, if at all, is this possible ???
I guess this can be fully answered by someone from HP DP development team who know MML library codes and features and functionalities incorporated into it.
Please help.
Thanks and regards,
Vineet Ranjan (Vineet.Ranjan@hpe.com)
+61 405 396 959
Hey there,
is it posibble to execute a post-exec-script even if a backup fails? But just for a few specific backups, global would be bad.
Reason is that our VMWare backup failed so it gets automatically aborted . We fixed the error but we want to be on the safe side.
Thanks!
Hi,
I updated backup configuration and now I don't got the warnings. Now the messages are:
[Normal] From: BSM@svrdp.phmj.es "" Time: 06/11/2015 13:11:46
Backup session 2015/11/06-8 started.
[Normal] From: BMA@xsm07101.phmj.es "VD1_XSM07101" Time: 06/11/2015 13:11:47
STARTING Media Agent "VD1_XSM07101"
[Normal] From: BMA@xsm07101.phmj.es "VD1_XSM07101" Time: 06/11/2015 13:11:48
Loading medium from slot p:\jukebox\file003 to device VD1_XSM07101
[Normal] From: BMA@xsm07101.phmj.es "VD1_XSM07101" Time: 06/11/2015 13:11:48
Unloading medium to slot p:\jukebox\file003 from device VD1_XSM07101
[Normal] From: BMA@xsm07101.phmj.es "VD1_XSM07101" Time: 06/11/2015 13:11:48
ABORTED Media Agent "VD1_XSM07101"
[Major] From: BSM@svrdp.phmj.es "" Time: 06/11/2015 13:11:49
Backup device unavailable. Trying to promote any pending mirror to original.
[Critical] From: BSM@svrdp.phmj.es "" Time: 06/11/2015 13:12:25
None of the Disk Agents completed successfully.
Session has failed.
[Normal] From: BSM@svrdp.phmj.es "" Time: 06/11/2015 13:12:25
Backup Statistics:
Session Queuing Time (hours) 0,00
-------------------------------------------
Completed Disk Agents ........ 0
Failed Disk Agents ........... 1
Aborted Disk Agents .......... 0
-------------------------------------------
Disk Agents Total ........... 1
===========================================
Completed Media Agents ....... 0
Failed Media Agents .......... 1
Aborted Media Agents ......... 0
-------------------------------------------
Media Agents Total .......... 1
===========================================
Mbytes Total ................. 0 MB
Used Media Total ............. 0
Disk Agent Errors Total ...... 0
Sorry, I post messages about other backup but the problem is exactly the same
Hiii,
We have Oracle 10g integrated with HP DP 7.0, Oracle is installed on HP-UX superdome server 11.31 also DP CM is windows 2008. we are using EML103e library altrium 4 drive.while taking RMAN backup through HP DP it throws following error mentioned below.
RMAN-06206: Crosschecked 666 objects
RMAN-20242: specification does not match any archive log in the recovery catalog
RMAN-03090: Starting backup at 08-NOV-15
RMAN-03033: current log archived
RMAN-08031: released channel: dev_0
RMAN-08031: released channel: dev_1
RMAN-08031: released channel: dev_2
RMAN-08031: released channel: dev_3
RMAN-08031: released channel: dev_4
RMAN-08031: released channel: dev_5
RMAN-08031: released channel: dev_6
RMAN-08031: released channel: dev_7
RMAN-08031: released channel: dev_8
RMAN-08031: released channel: dev_9
RMAN-08031: released channel: dev_10
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 11/08/2015 09:16:00
RMAN-06726: could not locate archivelog /oltp1_arch1/abc/arch/log_7628d0a0_1_9383_765657634.arc
Recovery Manager complete.
[Major] From: ob2rman@xyz "abc" Time: 11/08/15 09:16:02
External utility reported error.
whereas from database end it shows below given error
Media id a0425f0a:560bb647:02a4:0001 for Oracle abc_Saturday_1st week<abc_44806:895176094:1>.dbf not stored as total length exceeds 65 characters.
can anyone help me to know what exactly these error messages mean and will it be any issue while restoring such backup?
Thanks & regards
Amit