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

Re: IDB backup failed - Cannot read DBSM message

August 26, 2016, 1:08 am
$
0
0

Software support for Data Protector A.08.00 is no longer available and this looks like a release-specific issue that needs fix. This issue was not fixed on this release so there is no hot fix available. You should consider a upgrade to A.09.07_110.

The DBSM ends abnormally during the IDB backup session
https://softwaresupport.hpe.com/group/softwaresupport/search-result/-/facetsearch/document/KM01699450

Please use the Accept Solution button next to my post and assign a KUDO (thumbs up icon) if this works for you.

Regards,
Sebastian Koehler

↧
Search

Re: DP and StoreOnce Catalyst -> Replication still running after abort in DP

August 26, 2016, 1:21 am
$
0
0

Hi pirx4711,

from what I can see this issue should be resolved since A.09.02. You're at A.09.04 plus various fixes. That makes the actual behavior a bit unpredictable depending on what fixes are used. In any case aborting a replication job will take time. The communication to the StoreOnce systems is async and it takes time until such an abort command is properly handled. I can try the abort on one of my cells if you like. But we're running A.09.07 at the moment.

When user abort is initiated during the replication, the "Abort" command is not send to Catalyst API of D2D box
https://softwaresupport.hpe.com/group/softwaresupport/search-result/-/facetsearch/document/LID/QCCR2A53792

One addtion, if CSM crashes during a replication session, there is no way to stop the process from Data Protector (only from StoreOnce).

I can only recommend using a proper time filter (few hours) during setup phase to limit the amount of object selected and use a single source and target store only. It makes absolutely no sense to test with "all objects that have been an active protection and a copy count less than 1". Also a replication is never useless, because it transports data that can be used by later attempts to speed up the transfer. What do you mean when you say "not working and gives me errors"?

Please use the Accept Solution button next to my post and assign a KUDO (thumbs up icon) if this works for you.

Regards,
Sebastian Koehler

↧
↧

(DP) Support Tip: Replication session ends without any messages

August 26, 2016, 1:27 am
$
0
0

[Error Message]

Replication session sometimes fails without any errors as follows .

[Normal] From: CSM@hostname "CP"  Time: 2016/03/16 9:42:43
 Replication session 2016/03/16-13 started.

[Normal] From: CSM@hostname "CP"  Time: 2016/03/16 9:42:47

 Replication statistics:
  
  Session Queuing Time (hours)         0.00
  ----------------------------------------
  Completed Objects ............       0  
::


[Cause]

When 2 backup sessions start at the same time and each datalists have the same object name , the 2 objects become Original/Copy relation unexpectedly .
Object copies (replication) for those 2 objects will fail without any error message because any target to be copied is not found.


[Workaround / Fix]

By design, DP recognizes objects with the same point in time as pairs of original/copy .
Please consider not to set the same object name and not to schedule them at the same time .

↧

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

August 26, 2016, 2:07 am
$
0
0

Hi mainland,

I can confirm that this issue is resolved in A.09.07_110 and the omnirc parameter is no longer needed. There was a race condition in VMware's VDDK 6.0.1 included in A.09.06. Now with the new patch the recent VDDK 6.0.2 is used.

Please use the Accept Solution button next to my post and assign a KUDO (thumbs up icon) if this works for you.

Regards,
Sebastian Koehler

↧

Re: Error :Unknown SSL protocol error in connection to host:7116 on HPDP 9

August 26, 2016, 2:14 am
$
0
0

Hi 

Thank you for the reply

Do i need to apply all the 9.07_110 patches??

dp patch.PNG

 

↧
↧

Re: Error :Unknown SSL protocol error in connection to host:7116 on HPDP 9

August 26, 2016, 2:32 am
$
0
0

Start with the A.09.07 patch bundle. Then all of them in numeric ascending sequence. Don't forget to upgrade the Cell Manager from GUI afterwards (clients context => Upgrade).

Please use the Accept Solution button next to my post and assign a KUDO (thumbs up icon) if this works for you.

Regards,
Sebastian Koehler

↧

Re: DP and StoreOnce Catalyst -> Replication still running after abort in DP

August 26, 2016, 3:38 am
$
0
0

Hi,

errors like the ones below. Replication starts and after a couple of minutes I get "Can not open device" messages. Later on the NETIO errors. This does not only happen with scheduled copies with larger amounts of data, it alos happens with smaller afterbackup replications that would only transfer smaller orcale logs.

AFAIK this is an error that comes from the target SO (BMA). Similar jobs are working for a 4500 -> 6500 replication. Already tried to lower the number of outgoing connection on the SO4500.

 

[Major] From: BMA@sdet2033.xxx.yy "DE_SDES0227_ORALOG01_SDET2033 [GW 8848:19:2815601691639843188]"  Time: 17.08.2016 15:04:20
[90:54]     \\sdes0227.de.xxx.yy\DE_SDES0227_ORALOG01\12b87de3_57b460c6_2e1c_0171
      Cannot open device (StoreOnce error: The object is not ready)

[Major] From: BMA@sdet2028.xxx.yy "DE_SDES0227_ORALOG01_SDET2028 [GW 8848:19:2815626980407280244]"  Time: 17.08.2016 15:04:21
[90:54]     \\sdes0227.de.xxx.yy\DE_SDES0227_ORALOG01\12b87de3_57b460c8_2e1c_0172
      Cannot open device (StoreOnce error: The object is not ready)

[Critical] From: CMA@sdet2033.xxx.yy "DE_SDES0213_ORALOG01_SDET2033 [GW 8848:38:2815601691639843188]"  Time: 17.08.2016 15:05:32
[90:17]     Cannot start NETIO process ([0] The operation completed successfully. ) => aborting

[Critical] From: CMA@sdet2033.xxx.yy "DE_SDES0213_ORALOG01_SDET2033 [GW 8848:39:2815601691639843188]"  Time: 17.08.2016 15:05:34
[90:17]     Cannot start NETIO process ([0] The operation completed successfully. ) => aborting

[Critical] From: CMA@sdet2033.xxx.yy "DE_SDES0213_ORALOG01_SDET2033 [GW 8848:39:2815601691639843188]"  Time: 17.08.2016 15:05:40
[90:17]     Cannot start NETIO process ([0] The operation completed successfully. ) => aborting

[Critical] From: CMA@sdet2033.xxx.yy "DE_SDES0213_ORALOG01_SDET2033 [GW 8848:38:2815601691639843188]"  Time: 17.08.2016 15:05:39
[90:17]     Cannot start NETIO process ([0] The operation completed successfully. ) => aborting

[Critical] From: CMA@sdet2033.xxx.yy "DE_SDES0213_ORALOG01_SDET2033 [GW 8848:39:2815601691639843188]"  Time: 17.08.2016 15:05:46
[90:17]     Cannot start NETIO process ([0] The operation completed successfully. ) => aborting

[Critical] From: CMA@sdet2033.xxx.yy "DE_SDES0213_ORALOG01_SDET2033 [GW 8848:38:2815601691639843188]"  Time: 17.08.2016 15:05:45
[90:17]     Cannot start NETIO process ([0] The operation completed successfully. ) => aborting

[Critical] From: CMA@sdet2033.xxx.yy "DE_SDES0213_ORALOG01_SDET2033 [GW 8848:39:2815601691639843188]"  Time: 17.08.2016 15:05:52
[90:17]     Cannot start NETIO process ([0] The operation completed successfully. ) => aborting
…
…
...
[Critical] From: CMA@sdet2033.xxx.yy "DE_SDES0213_ORALOG01_SDET2033 [GW 8848:39:2815601691639843188]"  Time: 18.08.2016 02:27:17
[90:17]     Cannot start NETIO process ([0] The operation completed successfully. ) => aborting

[Critical] From: CMA@sdet2033.xxx.yy "DE_SDES0213_ORALOG01_SDET2033 [GW 8848:38:2815601691639843188]"  Time: 18.08.2016 02:27:15
[90:17]     Cannot start NETIO process ([0] The operation completed successfully. ) => aborting
↧

Re: Error :Unknown SSL protocol error in connection to host:7116 on HPDP 9

August 26, 2016, 5:06 am
$
0
0

Thank you for the update.

Will try and let you know the result

↧
Search

Re: HP DP GUI painfully, painfully slow

August 26, 2016, 5:26 am
$
0
0

I don't recall the details but I do remember following the docs.  Nothing bizarre stands out in my mind.  THAT being said there are still a lot of legacy files that are still around (and that HP really could not help me remove).  The db40 and the underlying dbcf_# files are still ebing touched. 

 

Vince

↧
↧

Re: HP DP GUI painfully, painfully slow

August 26, 2016, 5:31 am
$
0
0

Please share perl omnimigrate.pl -report_old_catalog to check if the DCBF migration is through or not. I guess SupportOldDCBF=1 is still in your global option file causing lookups to pass db40. Doing this is usually 3 times slower on each DCBF lookup.

Regards,
Sebastian Koehler

↧

Re: HP DP GUI painfully, painfully slow

August 26, 2016, 5:40 am
$
0
0

I could have sworn HP had me run the migration.  We don't have ANY backups from 2 years ago in our DP environment.

(root@sapbck)# ./omnimigrate.pl -report_old_catalog
Old Detail Catalog Binary Files size:
DCBF (   0 files):                     0 MB
Old filename data files:           2780 MB
Total:                             2780 MB

Here are all the things set in my .omnirc

OB2OSTTIMEOUT=7200
OB2TAPEALERT=0
OB2SHMEM_IPCGLOBAL=1

OB2INETTIMEOUT=240
OB2IPCKEEPALIVE=1

# SSH was disabled before 3/24/15
OB2_SSH_ENABLED=1

# OB2CHANGERELEMENTPARSER=0
OB2CHANGERELEMENTPARSER=1

# change debug file location
OB2DBGDIR=/omniback/debug

# Added per HP Support 5/5/16
OB2MADETECTDRIVESWAP=1

# Added 8/24 per HP forum
OB2IPCREVERSELOOKUP=0
OB2_DNSTIMEOUT=2

↧

Re: HP DP GUI painfully, painfully slow

August 26, 2016, 5:48 am
$
0
0

Based on that output you're ready to get rid of the old db40 structure. Please check those items:

  1. Is SupportOldDCBF=1 still in /etc/opt/omni/server/options/global?
  2. Are there still actively used DCBF directories listed in omnidbutil -list_dcdirs (below db40)

Regards,
Sebastian Koehler

↧

Re: HP DP GUI painfully, painfully slow

August 26, 2016, 5:53 am
$
0
0

Apparently it is in there twice:

SupportOldDCBF=0
# Data Protector A.09.00
# This value was automatically copied from previous version.
# This variable is no longer in use.
SupportOldDCBF=1
# Data Protector A.09.00
# This value was automatically copied from previous version.
# This variable is no longer in use.

(root@sapbck)# omnidbutil -list_dcdirs
Configured DC directories:

 Allocation Sequence
 |        Maximum Usage in MB
 |        |        Maximum Number of Files in Directory
 |        |        |        Minimum Free Space [MB]
 |        |        |        |        Directory
 |        |        |        |        |
===========================================================================
 0        4096     10000    100      /var/opt/omni/server/db40/dcbf
 0        204800   100000   2048     /omniback/var_opt_omni/server/db80/dcbf/dcbf0
 2        204800   100000   2048     /omniback/var_opt_omni/server/db80/dcbf/dcbf2
 2        4096     10000    100      /var/opt/omni/server/db40/dbcf_2
 1        204800   100000   2048     /omniback/var_opt_omni/server/db80/dcbf/dcbf1
 1        4096     10000    100      /var/opt/omni/server/db40/dbcf_1
 3        204800   100000   2048     /omniback/var_opt_omni/server/db80/dcbf/dcbf3
 4        204800   100000   2048     /omniback/var_opt_omni/server/db80/dcbf/dcbf4

DONE!

↧
↧

Re: HP DP GUI painfully, painfully slow

August 26, 2016, 6:20 am
$
0
0

Please make sure no sessions are running and do the following.

  1. Run omnidbutil -remap_dcdir. If no error is returned, move all DCBFs from /var/opt/omni/server/db40/dcbf, /var/opt/omni/server/db40/dbcf_1 and /var/opt/omni/server/db40/dbcf_2 to any of the other DCBF folders (e.g. /omniback/var_opt_omni/server/db80/dcbf/dcbf0) and run omnidbutil -remap_dcdir again.
  2. Then run omnidbutil -remove_dcdir /var/opt/omni/server/db40/dcbf, omnidbutil -remove_dcdir /var/opt/omni/server/db40/dcbf_1 and omnidbutil -remove_dcdir /var/opt/omni/server/db40/dcbf_2.
  3. Remove both instances of SupportOldDCBF from global file and restart the services (omnisv stop, omnisv start).
  4. Then it is save to remove the old catalog using perl omnimigrate.pl -remove_old_catalog. The directory structure /var/opt/omni/server/db40 can be removed afterwards.

Please use the Accept Solution button next to my post and assign a KUDO (thumbs up icon) if this works for you.

Regards,
Sebastian Koehler

↧

Re: unable to restore... AES256 encryption

August 26, 2016, 6:21 am
$
0
0

If that was set in the Filesystem Option or the Object Property, wouldn't aes256 show up in the backup spec?

For example, my backup spec currently looks like:

# grep -i aes256 All_Physical_Clients_Inc
# echo $?
1

And here's what it looks like after I set AES256 on one system:

# grep -i aes256 All_Physical_Clients_Inc
-encode "aes256"
# echo $?
0

So, is there some place that aes256 could be set such that its presence wouldn't be required in a backup spec?

 

 

↧
Search

Re: unable to restore... AES256 encryption

August 26, 2016, 6:25 am
$
0
0

The second option is that encryption was enabled on the backup device (LTO4 and later) and an offline restore is performed. In this case the encryption key must be supplied. An offline restore happens when client with the MiniOS (EADR recovery image) is not able to ask the Cell Manager for the encryption key via the network. Is this the case? Maybe due to your temporary address assigned.

Regards,
Sebastian Koehler

↧

Re: Error :Unknown SSL protocol error in connection to host:7116 on HPDP 9

August 26, 2016, 6:50 am
$
0
0

hi,

I have installed the required patches succesfully.

However still i am getting the same issue.Kindly let me know how to fix this

↧
↧

Re: unable to restore... AES256 encryption

August 26, 2016, 6:52 am
$
0
0

All my drives are LTO-5 or LTO-6. 

When I use omnidownload to look at their settings, I see 'ENCRYPT' in the output. But I don't see any way to change that using the GUI.

I did perform an offline restore. But when I changed the network settings, ping worked fine both to and from the test system. It should have had no problems communicating with the cell manager. However, I'll try a restore without changing the networking, though I think the test host would have problems communicating with the cell manager, because linux tends to check if an IP is in use before bringing the network interface up.

Thanks for your help, Sebastian.

↧

Re: Error :Unknown SSL protocol error in connection to host:7116 on HPDP 9

August 26, 2016, 7:01 am
↧

Re: unable to restore... AES256 encryption

August 26, 2016, 7:36 am
$
0
0

You are looking for this option in GUI. Device & Media => Device Properties.

2016-08-26_16h33_34.png

When I say "Offline Restore" I mean it from an EADR perspective. Here is a section from DisasterRecovery.pdf.

Note that Data Protector first tries to perform an online restore. If the online restore fails for
any reason (for example, the Cell Manager or network service is not available or firewall is
preventing access to the Cell Manager) Data Protector tries to perform remote offline recovery. If
the remote offline restore fails (for example, because the Media Agent host accepts requests only
from the Cell Manager), Data Protector performs a local offline restore.

Please use the Accept Solution button next to my post and assign a KUDO (thumbs up icon) if this works for you.

Regards,
Sebastian Koehler

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