[Error Message]
Remote installation for Linux agent system fails with following error messages .

  [Warning] <hostname>  Could not use secure shell protocol, instead using rexec and rcp commands...
  :
  [Warning] <hostname>  Invalid username or bad password (root)

[Cause/Workaround /Fix]
Most of Linux systems don't allow to use both of ssh and rexec as default .
Please refer to a guide in HP Data Protector 9.00 Installation Guide as follows .

Chapter 3: Installing Data Protector clients
 - Remote installation
   - Remote installation using secure shell

Hi All,

After some advice if possible. We have rebuilt our Data Protector 8.10 environment (Windows Server 2012) in a DR test, after the re-install we had an issue with the certificate expiry being too far in the future (sometime in 2038), after googling for a while, I found an article stating the fix was to run 'Omnigencert.pl' and lower the cert expiration date.

I created the new cert using the util and set the expiry for 1000 days. I restarted the DP services 'omnisv -stop' then 'omnisv -start'. All services started fine - but thats as much luck as we have!

- When opening the gui, it detects the new cert, we click OK but then DP cannot connect to the host.
- When going to the web URL (Https://HOSTNAME:7116) I cannot connect to the site.
- When running Omni commands (e.g. Omnimm -List_media_info 'TAPENAME') we get the correct information is returned.

We have tried repairing the install, checked the ports are not in use, i've even asked it nicely... but no luck as of yet.

Do any of you DP Boffins have any ideas, we could try ?

Many Thanks in advance

Jamie Bennett

You should make sure that your IDB backups is always 100% good, because if this is not good could cause problems in the IDB like archive logs are not cleared and the IDB is growing a lot.

For any error on the IDB backup, please create a case to investigate what the issue is.

SQL Server provides an API called Virtual Backup Device Interface (VDI) that enables independent software vendors to integrate SQL Server into their products for providing support for backup and restore operations, this is different than the SQL Server Native Backups which can take backups using BACKUP DATABASE T-SQL command.

When configuring Data Protector with MS SQL the  user must be a sysadmin. More information can be found in Microsoft Documentation:

 https://support.microsoft.com/en-us/kb/2926557

- SQL Server VDI backup and restore operations require Sysadmin privileges

The VDI connection requires the Sysadmin permission because the connection itself is capable of executing more than simple backup operations and involves shared resources between the client and server. 

The following .omnir variable can be implemented to traverse cross (nested) filesystems with specifiying a single object in the backup specification:

   OB2_ALLOW_REMOTE_MOUNT_POINT=1

This functionality is is only implemented on UNIX disk agents.

hello sorry for de english

i have been reviewing and tapes can store up to 3 TB, but i could not find a way to make so you

thank you

Guys

We have trying to upgrade from 6.20 to DP 9.00

Cellmanager os: HPUX 11.31

bash-4.1# /opt/omni/sbin/omnisv status

    ProcName  Status  [PID]

===============================

    rds     : Active  [24391]

    crs     : Active  [24395]

    mmd     : Active  [24393]

    kms     : Active  [24394]

    omnitrig: Active

    uiproxy : Active  [24397]

    Sending of traps disabled.

===============================

Status: All Data Protector relevant processes/services up and running.

#########

bash-4.1# /opt/omni/sbin/omnidbcheck -dc

Medium ID:                             Mpos[Bin/Db]  Offset Details Results

===============================================================================

0a9c0034:560c76e8:3445:0001

0a9c0034:54cd97a0:20c2:0001

0a9c0034:54a34171:378a:0001

0a9c0034:551c3740:0a0f:0001

0a9c0034:56634696:11e5:0001

0a9c0034:5542c644:0478:0001

0a9c0034:551c5c88:2034:0001

0a9c0034:5542c447:0385:0001

0a9c0034:56318a90:5a52:0001

0a9c0034:5483c117:22b3:0001

0a9c0034:569ee4bd:5607:0001

0a9c0034:560dd31c:16f6:0001

0a9c0034:5515be65:5e54:0001

0a9c0034:56d48e15:22b0:0001

0a9c0034:564aba7d:6c59:0001

0a9c0034:561dd53e:4c0e:0001

0a9c0034:52c1f330:4d54:0001

0a9c0034:54cd6894:048e:0001

0a9c0034:556ba8a5:2cde:0001

0a9c0034:52535841:68fc:0001

0a9c0034:55cc9fe4:119a:0001

0a9c0034:528d8649:3e6b:0001

0a9c0034:54497569:31b6:0001

0a9c0034:50b6920e:21c6:0001

0a9c0034:54a33f75:3666:0001

0a9c0034:559321bf:1e5d:0001

0a9c0034:55b3f0ab:5fb8:0001

0a9c0034:56100111:7164:0001

0a9c0034:551b35cf:5c0c:0001

0a9c0034:54a34074:3696:0001

0a9c0034:55d12677:6137:0001

0a9c0034:5542c557:0411:0001

0a9c0034:560ec919:31c6:0001

0a9c0034:551c2ee8:04c6:0001

0a9c0034:545c8156:5901:0001

0a9c0034:55cd3380:665b:0001

0a9c0034:560dd42c:17ac:0001

0a9c0034:50fd9420:3deb:0001

0a9c0034:55932493:1fdf:0001

0a9c0034:547bb466:4cd7:0001

0a9c0034:53506c6e:4895:0001

0a9c0034:556ba99c:2d85:0001

0a9c0034:560ec07b:2ca5:0001

0a9c0034:5500b7c8:7085:0001

0a9c0034:542a2998:401f:0001

0a9c0034:537d397e:3a13:0001

0a9c0034:54654090:6c90:0001

0a9c0034:5467ad10:03cd:0001

0a9c0034:537941ff:6b05:0001

0a9c0034:55c9954c:366b:0001

0a9c0034:56baaba3:45b7:0001

0a9c0034:54cec11c:57d5:0001

0a9c0034:528527c6:0a48:0001

0a9c0034:56d4df80:5193:0001

0a9c0034:52c31413:07a8:0001

0a9c0034:54f1f913:4707:0001

0a9c0034:52c1d10c:38c6:0001

0a9c0034:55d3bba0:0c2a:0001

0a9c0034:55ff90d8:0231:0001

0a9c0034:56f1d369:2543:0001

0a9c0034:56bab8d5:4d7d:0001

0a9c0034:5411d37f:6443:0001

0a9c0034:56f877e2:59c1:0001

0a9c0034:55bab3d7:093b:0001

0a9c0034:56130f1c:65e2:0001

0a9c0034:547bb56d:4db7:0001

0a9c0034:54f1fb1b:483c:0001

0a9c0034:545c0567:101b:0001

0a9c0034:542b947c:2996:0001

0a9c0034:55d27403:387c:0001

0a9c0034:55931f1d:1cce:0001

0a9c0034:5610020b:71b7:0001

0a9c0034:55bab639:0aa6:0001

0a9c0034:55bab735:0b3d:0001

0a9c0034:56a8f2e0:1f28:0001

0a9c0034:55d3bc5c:0cc0:0001

0a9c0034:55d510e9:5b5c:0001

0a9c0034:55d51414:5d55:0001

0a9c0034:560dd69f:196f:0001

0a9c0034:55d665e1:3613:0001

0a9c0034:55d8a9ff:286e:0001

0a9c0034:5610138a:085b:0001

0a9c0034:55e4efa0:02bb:0001

0a9c0034:55e4f100:0364:0001

0a9c0034:55e4f233:0412:0001

0a9c0034:560c74c5:331b:0001

0a9c0034:560cca7a:65d7:0001

0a9c0034:560c7537:3357:0001

0a9c0034:560c75f3:33fd:0001

0a9c0034:565bb971:4a05:0001

0a9c0034:5611bdae:1620:0001

0a9c0034:56130e13:6548:0001

0a9c0034:5635019f:163b:0001

0a9c0034:56350261:1692:0001

0a9c0034:5635032b:16e2:0001

0a9c0034:55d27738:3a93:0001

0a9c0034:565ce495:0f2a:0001

0a9c0034:565ce560:0f7b:0001

0a9c0034:565ce636:0fe1:0001

0a9c0034:5685cfaf:2489:0001

0a9c0034:5685d071:24d8:0001

0a9c0034:5685d15c:259f:0001

0a9c0034:5685d244:25f9:0001

0a9c0034:5685d3be:26ce:0001

0a9c0034:56aea17c:30e7:0001

0a9c0034:56aea265:31bc:0001

0a9c0034:56aea34d:3209:0001

0a9c0034:56d4e103:531e:0001

0a9c0034:56d4e289:53c7:0001

0a9c0034:56f68ff5:2855:0001

0a9c0034:56f99657:1865:0001

Check finished : 0 errors reported.

DONE!

########

bash-4.1# /opt/omni/sbin/omnidbcheck

Check Level             Mode            Status

==================================================

Core                    -core           OK

Filenames               -filenames      OK

DCBF(presence and size) -bf             OK

DONE!

########

bash-4.1# kcusage shmmax
Tunable Usage / Setting
=============================================
shmmax 2472411136 / 2684354560
bash-4.1#

##############

bash-4.1# cd /dp

bash-4.1# ll

total 28

dr-xr-xr-x   1 root       root          2048 Jun 11  2014 DOCS

dr-xr-xr-x   1 root       root          2048 Jun 17  2014 LICENSE

dr-xr-xr-x   1 root       root          2048 Jun  9  2014 LOCAL_INSTALL

-r--r--r--   1 root       root          5599 Jun 25  2014 Readme.txt

dr-xr-xr-x   1 root       root          2048 Jun 18  2014 hpux

bash-4.1# cd Lo

bash: cd: Lo: No such file or directory

bash-4.1# cd LOCAL_INSTALL/

bash-4.1# ll

total 214

-r-xr-xr-x   1 root       root        109184 Jun  9  2014 omnisetup.sh

bash-4.1# /opt/omni/sbin/omnisv status

    ProcName  Status  [PID]

===============================

    rds     : Active  [9547]

    crs     : Active  [9551]

    mmd     : Active  [9549]

    kms     : Active  [9550]

    omnitrig: Active

    uiproxy : Active  [9553]

    Sending of traps disabled.

===============================

Status: All Data Protector relevant processes/services up and running.

bash-4.1# /opt/omni/sbin/omnisv stop

HP Data Protector services successfully stopped.

bash-4.1# /opt/omni/sbin/omnisv start

HP Data Protector services successfully started.

bash-4.1# /opt/omni/sbin/omnisv status

    ProcName  Status  [PID]

===============================

    rds     : Active  [14541]

    crs     : Active  [14545]

    mmd     : Active  [14543]

    kms     : Active  [14544]

    omnitrig: Active

    uiproxy : Active  [14556]

    Sending of traps disabled.

===============================

Status: All Data Protector relevant processes/services up and running.

bash-4.1# ll

total 214

-r-xr-xr-x   1 root       root        109184 Jun  9  2014 omnisetup.sh

bash-4.1# ./omnisetup.sh

  The omnisetup.sh script did not complete the last time it was run.

  Cell Manager still has to be installed

  Installation Server still has to be installed

  The omnisetup.sh script can now resume the installation session

  or it can ignore the saved state and start a new session.

  If you choose to ignore, the script will erase the saved state

  and will process only the command line options.

  Do you want the setup to resume the installation? (Y/n)

n

  Ignoring saved state...

  Data Protector version A.06.20 found

  Cell Manager detected...

  Installation Server detected...

  Client detected, installed components:  da ma cc docs

  Passed:   The user account "hpdp" will be used for the IDB service.

  Passed:   Port number "7112" will be used for the "hpdp-idb" service.

  Passed:   Port number "7113" will be used for the "hpdp-idb-cp" service.

  Passed:   Port number "7116" will be used for the "hpdp-as" service.

  Passed:   Port number "9999" will be used for the "hpdp-as" service.

  Passed:   The kernel parameter value: SHMMAX = 2684354560.

            The minimum required parameter value is "2684354560".

  Passed:   There are "8557428736" bytes of available system memory.

            8 GB of system memory are recommended.

            4 GB of system memory are required.

  Passed:   Data Protector installation requires 2764800 kilobytes of free

            storage space on the "/opt" filesystem.

            The filesystem "/opt" has 44276904 kilobytes of free space.

  Passed:   Data Protector installation requires 1356800 kilobytes of free

            storage space on the "/var" filesystem.

            The filesystem "/var" has 100468848 kilobytes of free space.

  Passed:   Data Protector installation requires 6144 kilobytes of free

            storage space on the "/" filesystem.

            The filesystem "/" has 54287336 kilobytes of free space.

  Exporting Data Protector IDB

  RDS service running.

Exporting HP Data Protector Internal Database.

This may take a few minutes.

**********************  DEFAULT ERROR REPORT  *******************************

[Critical] From: OMNIDBUTIL@obl-backup ""  Time: 04/06/16 11:36:18

[12:1165] Internal Database network communication error.

*****************************************************************************

Done!

  Exporting DONE!

Installing Data Protector A.09.00 Cell Manager and Installation Server...

=======  04/06/16 11:37:33 GMT  BEGIN swinstall SESSION

         (non-interactive) (jobid=OBL-BACKUP-0039)

       * Session started for user "root@OBL-BACKUP".

       * Beginning Selection

       * Target connection succeeded for "OBL-BACKUP:/".

       * "OBL-BACKUP:/dp/hpux/DP_DEPOT":  Cannot open the logfile on

         this target or source.  Possibly the media is read-only or

         there is a permission problem.  Check the daemon logfile and

         "/var/tmp/swagent.log" on this host for more information.

       * Source:                 /dp/hpux/DP_DEPOT

       * Targets:                OBL-BACKUP:/

       * Software selections:

           + B6960MA,r=A.09.00,a=HP-UX_B.11.11_32/64,v=HP

             DATA-PROTECTOR.OMNI-AUTODR-P,r=A.09.00,a=HP-UX_B.11.11_32/64,v=HP,fr=A.09.00,fa=HP-UX_B.11.11_32/64

             DATA-PROTECTOR.OMNI-CC,r=A.09.00,a=HP-UX_B.11.11_32/64,v=HP,fr=A.09.00,fa=HP-UX_B.11.31_IA

             DATA-PROTECTOR.OMNI-CC-P,r=A.09.00,a=HP-UX_B.11.11_32/64,v=HP,fr=A.09.00,fa=HP-UX_B.11.11_32/64

             DATA-PROTECTOR.OMNI-CF-P,r=A.09.00,a=HP-UX_B.11.11_32/64,v=HP,fr=A.09.00,fa=HP-UX_B.11.11_32/64

             DATA-PROTECTOR.OMNI-CHS-LS-P,r=A.09.00,a=HP-UX_B.11.11_32/64,v=HP,fr=A.09.00,fa=HP-UX_B.11.11_32/64

             DATA-PROTECTOR.OMNI-CORE,r=A.09.00,a=HP-UX_B.11.11_32/64,v=HP,fr=A.09.00,fa=HP-UX_B.11.23_IA

             DATA-PROTECTOR.OMNI-CORE-IS,r=A.09.00,a=HP-UX_B.11.11_32/64,v=HP,fr=A.09.00,fa=HP-UX_B.11.23_IA

             DATA-PROTECTOR.OMNI-CS,r=A.09.00,a=HP-UX_B.11.11_32/64,v=HP,fr=A.09.00,fa=HP-UX_B.11.31_IA

             DATA-PROTECTOR.OMNI-DA,r=A.09.00,a=HP-UX_B.11.11_32/64,v=HP,fr=A.09.00,fa=HP-UX_B.11.31_IA

             DATA-PROTECTOR.OMNI-DA-P,r=A.09.00,a=HP-UX_B.11.11_32/64,v=HP,fr=A.09.00,fa=HP-UX_B.11.11_32/64

             DATA-PROTECTOR.OMNI-DB2-P,r=A.09.00,a=HP-UX_B.11.11_32/64,v=HP,fr=A.09.00,fa=HP-UX_B.11.11_32/64

             DATA-PROTECTOR.OMNI-DOCS,r=A.09.00,a=HP-UX_B.11.11_32/64,v=HP,fr=A.09.00,fa=HP-UX_B.11.11_32/64

             DATA-PROTECTOR.OMNI-DOCS-P,r=A.09.00,a=HP-UX_B.11.11_32/64,v=HP,fr=A.09.00,fa=HP-UX_B.11.11_32/64

             DATA-PROTECTOR.OMNI-EMC-P,r=A.09.00,a=HP-UX_B.11.11_32/64,v=HP,fr=A.09.00,fa=HP-UX_B.11.11_32/64

             DATA-PROTECTOR.OMNI-FRA-LS-P,r=A.09.00,a=HP-UX_B.11.11_32/64,v=HP,fr=A.09.00,fa=HP-UX_B.11.11_32/64

             DATA-PROTECTOR.OMNI-INF-P,r=A.09.00,a=HP-UX_B.11.11_32/64,v=HP,fr=A.09.00,fa=HP-UX_B.11.11_32/64

             DATA-PROTECTOR.OMNI-INTEG-P,r=A.09.00,a=HP-UX_B.11.11_32/64,v=HP,fr=A.09.00,fa=HP-UX_B.11.11_32/64

             DATA-PROTECTOR.OMNI-JCE-DISPATCHER,r=A.09.00,a=HP-UX_B.11.11_32/64,v=HP,fr=A.09.00,fa=HP-UX_B.11.31_IA

             DATA-PROTECTOR.OMNI-JCE-SERVICEREGISTRY,r=A.09.00,a=HP-UX_B.11.11_32/64,v=HP,fr=A.09.00,fa=HP-UX_B.11.31_IA

             DATA-PROTECTOR.OMNI-JPN-LS-P,r=A.09.00,a=HP-UX_B.11.11_32/64,v=HP,fr=A.09.00,fa=HP-UX_B.11.11_32/64

             DATA-PROTECTOR.OMNI-LOTUS-P,r=A.09.00,a=HP-UX_B.11.11_32/64,v=HP,fr=A.09.00,fa=HP-UX_B.11.11_32/64

             DATA-PROTECTOR.OMNI-MA,r=A.09.00,a=HP-UX_B.11.11_32/64,v=HP,fr=A.09.00,fa=HP-UX_B.11.31_IA

             DATA-PROTECTOR.OMNI-MA-P,r=A.09.00,a=HP-UX_B.11.11_32/64,v=HP,fr=A.09.00,fa=HP-UX_B.11.11_32/64

             DATA-PROTECTOR.OMNI-NDMP-P,r=A.09.00,a=HP-UX_B.11.11_32/64,v=HP,fr=A.09.00,fa=HP-UX_B.11.11_32/64

             DATA-PROTECTOR.OMNI-OR8-P,r=A.09.00,a=HP-UX_B.11.11_32/64,v=HP,fr=A.09.00,fa=HP-UX_B.11.11_32/64

             DATA-PROTECTOR.OMNI-SAP-P,r=A.09.00,a=HP-UX_B.11.11_32/64,v=HP,fr=A.09.00,fa=HP-UX_B.11.11_32/64

             DATA-PROTECTOR.OMNI-SAPDB-P,r=A.09.00,a=HP-UX_B.11.11_32/64,v=HP,fr=A.09.00,fa=HP-UX_B.11.11_32/64

             DATA-PROTECTOR.OMNI-SAPHANA-P,r=A.09.00,a=HP-UX_B.11.11_32/64,v=HP,fr=A.09.00,fa=HP-UX_B.11.11_32/64

             DATA-PROTECTOR.OMNI-SMISA-P,r=A.09.00,a=HP-UX_B.11.11_32/64,v=HP,fr=A.09.00,fa=HP-UX_B.11.11_32/64

             DATA-PROTECTOR.OMNI-SODA-P,r=A.09.00,a=HP-UX_B.11.11_32/64,v=HP,fr=A.09.00,fa=HP-UX_B.11.11_32/64

             DATA-PROTECTOR.OMNI-SSEA-P,r=A.09.00,a=HP-UX_B.11.11_32/64,v=HP,fr=A.09.00,fa=HP-UX_B.11.11_32/64

             DATA-PROTECTOR.OMNI-SYB-P,r=A.09.00,a=HP-UX_B.11.11_32/64,v=HP,fr=A.09.00,fa=HP-UX_B.11.11_32/64

             DATA-PROTECTOR.OMNI-TS-AS,r=A.09.00,a=HP-UX_B.11.11_32/64,v=HP,fr=A.09.00,fa=HP-UX_B.11.31_IA

             DATA-PROTECTOR.OMNI-TS-CF-P,r=A.09.00,a=HP-UX_B.11.11_32/64,v=HP,fr=A.09.00,fa=HP-UX_B.11.11_32/64

             DATA-PROTECTOR.OMNI-TS-CORE,r=A.09.00,a=HP-UX_B.11.11_32/64,v=HP,fr=A.09.00,fa=HP-UX_B.11.23_IA

             DATA-PROTECTOR.OMNI-TS-CS,r=A.09.00,a=HP-UX_B.11.11_32/64,v=HP,fr=A.09.00,fa=HP-UX_B.11.31_IA

             DATA-PROTECTOR.OMNI-TS-JRE,r=A.09.00,a=HP-UX_B.11.11_32/64,v=HP,fr=A.09.00,fa=HP-UX_B.11.31_IA

             DATA-PROTECTOR.OMNI-TS-PEGASUS-P,r=A.09.00,a=HP-UX_B.11.11_32/64,v=HP,fr=A.09.00,fa=HP-UX_B.11.11_32/64

             DATA-PROTECTOR.OMNI-VEPA-P,r=A.09.00,a=HP-UX_B.11.11_32/64,v=HP,fr=A.09.00,fa=HP-UX_B.11.11_32/64

             DATA-PROTECTOR.OMNI-VMW-P,r=A.09.00,a=HP-UX_B.11.11_32/64,v=HP,fr=A.09.00,fa=HP-UX_B.11.11_32/64

             DATA-PROTECTOR.OMNI-VMWAREGRE-AGENT-P,r=A.09.00,a=HP-UX_B.11.11_32/64,v=HP,fr=A.09.00,fa=HP-UX_B.11.11_32/64

             DATA-PROTECTOR.OMNI-WS,r=A.09.00,a=HP-UX_B.11.11_32/64,v=HP,fr=A.09.00,fa=HP-UX_B.11.31_IA

       * A "+" indicates an automatic selection due to dependency or

         the automatic selection of a patch or reference bundle.

       * Selection succeeded.

       * Beginning Analysis and Execution

       * Session selections have been saved in the file

         "/.sw/sessions/swinstall.last".

       * "OBL-BACKUP:/":  There will be no attempt to mount filesystems

         that appear in the filesystem table.

#################

##########################

bash-4.1# /opt/omni/sbin/omnidbcheck -extended

Check Level             Mode            Status

==================================================

Core                    -core           OK

Filenames               -filenames      OK

DCBF(presence and size) -bf             OK

SIBF(readability)       -sibf           OK

OMNIDC(consistency)     -dc             OK

DONE!

#########################

Any idea ??

Gentlemen, I am facing a problem that already took me a few hours of work ... When trying to install the DP on a client, the below error appears:

[12: 1625] Import host failed.
System error: [110] Connection timed out

Even installing via  "./omnisetup.sh -server -install da" then the matter in CellManager, the same error occurs.

Someone might think that might be? The port 5555 is communicating

Client is RedHat 7

I  try to restore data from hp Ux to Aix system through D.P and i 'm taking the below messages

[Warning] From: VRDA@aixdb "/SNAP/ktest"  Time: 7/4/2016 10:50:40 πμ
    Cross filesystem/platform restore of ACLs is not supported. ACLs will not be restored.

[Minor] From: VRDA@aixdb "/SNAP/ktest"  Time: 7/4/2016 10:50:40 πμ
    Record with ACL's is not from the AIX filesystem !

Does anyone know what this warnings means ?

=== Cell Manager:

RHEL 6.7

DP 9.04 with SSPLNX900_004

=== Mount Proxy (VEAgent backup server)

RHEL 7.2

DP 9.04

All VMware LUNs have been presented to the mount proxy

All VMs configured for SAN transport.

Yet a test backup of a VM uses NBDSSL transport.

in some instances it is necessary to capture CRS and/or MMD debugs.

one of the simplest ways to get the CRS and MMD threads is to run omnisv in debugs mode

ex:

omnisv -start -debug 0-200 dbg.txt

this will write debugs including CRS/MMD to the default location which is to the Omniback/tmp location

you can use all of the debug varaibles here as well

change location

omnisv -start -debug 0-200 C:\temp\dbg.txt

circular

omnisv -start -–debug 1-200,C:30000  CircularDBG.txt  

The complete debugging command is as follows :

-debug 1-99[,C:n][,T:s][,U] XYZ [host]

where:

1-99 is the debug range. Specify the range 1-99 unless instructed otherwise. Specify optional parameters as a part of the range parameter, separated by commas:

C:n limits the size of debug files to n kilobytes. The minimum value is 4 (4 kB) and the default value is 1024 (1 MB).

T:s is the timestamp resolution, where the default value is 1, 1000 means the resolution is one millisecond and 0 means timestamps are turned off.

On some platforms (for example, on Novell NetWare), millisecond resolution is not available.

U is the Unicode flag. If it is specified, the debug files on Windows are written in the Unicode format.

XYZ is the debug postfix, for example DBG_01.txt.

host is a list of clients where debugging is turned on.

Hey, I am new on this forum. I want information for data matching issues.

The option in Data Protector Transportation mode: SAN is not exclusive (the backup will continue), if SAN transport method fails then we will use the remaining transport methods available that Vmware API VixDiskLib_ConnectEx() passes to Data Protector.

If all the transport methods are available then it will choose the one that you selected in the Backup specification, otherwise it will continue through all the list of available methods using the following list defined by VixDiskLib_ConnectEx(): san:hotadd:nbdssl:nbd

Hello everyone,

Does Data Protector 9.04 support vSphere 6.0.0 U2?

Which the highest version of vSphere is supported by DP 9.04?

I really appreciate your prompt help.

Thank you and Best regards.

Anh Nguyen

Problem

Because of minor inconsistencies between StoreOnce Software (SOS) and other parts of DP, in the 3rd party libraries used for networking,
after upgrading to DP 9.03, or 9.04 there can be SOS server problems...
- Some command line commands on the SOS server fail with "The daemon is stopped."
- Backup sessions to the SOS will fail with "StoreOnce error: StoreOnce device offline, network error occurred or secure communication failed while contacting the StoreOnce device" when contacting "sos" B2D device!"
- Restore sessions from SOS will fail with "Restore of object hostname.domain.com:/object named "ObjectName" may be incomplete because some medium is missing."

This happens even though the SOS service is up and running.

Solution, when this problem is encountered after DP 9.03, 9.04 or 9.05 patch installation...

Solution 1 - Turn off SSL for the SOS server.

1. - Put OB2_STOREONCESOFTWARE_SSL_ENABLE=0 in the SOS omnirc file.
2. - Stop and Start the StoreOnceSoftware service.

Solution 2 - Reload all certificates throughout the cell.

1. - Run command omnicc -encryption -disable -all
2. - Run command omnicc -encryption -enable -all
3. - Stop and Start the StoreOnceSoftware service.
This forces DP to create new certificates and then StoreOnceSoftware can be used successfully.

Solution 3 - Reload the certificates for the components using SOS.

Replace the certificates on the SOS server itself, the Cell Manager and each client (Gateway)
that connects directly to the SOS.

You can use the certificates HP DP provide (hpdpcert2048_cert.pem and hpdpcert2048_key.pem).
Alternatively you re-create your own new certificates (hpdpcert2048_cert.pem and hpdpcert2048_key.pem)
with a key length of 2048 and sign them with the existing hpdpcert.pem

You can replace the certificates using the following steps

1. - Copy the new certificate files
hpdpcert2048_cert.pem
hpdpcert2048_key.pem
to Cell Manager directory
Windows: \ProgramData\Omniback\Config\Server\certificates
Unix: /etc/opt/omni/server/certificates

2. - Run commands from the CM
omnicc -encryption -enable <hostname> -cert hpdpcert2048_cert.pem -key hpdpcert2048_key.pem -trust hpdpcert.pem
replacing the <hostname> with hostname of affected hosts.

3. - Stop and Start the StoreOnceSoftware service.

NOTE: If something goes wrong during the certificate import or if something is wrong
with certificates themselves, the CM will be unable to communicate with the clients.
In this case it would be necessary to log on to each affected client and replace
the certificates manually.
If you're using your own certificates, we recommend testing them on one or two clients first.

Hello every one,

After upgrade Data protector from 9.0 to 9. 5 and upgrade all cleint successfully. I faced problem that the Backup of Exchange Server not working as schedule and when I make manually Data Protector shows error that " Configured User dpservice is not a member of MS Exchange built-in gruop 'Organization Management'"

Thanks for help.....

I read something that gave me the impression that in the GUI, DP will eventually be unable to show all of the backup specifications once some file reaches 80k.  I think that’s what it said.  Is that true?  If so, what file is it?  We have maybe 10% of our environment moved over and we’d like to see what impact we’ve made on that 80k so far so we can gauge when we might go over that threshold.

Thanks,

Randy

Hello!

I have a problem to backup VMS with VAgent behind Firewall.

My Cellmanager is in local Zone (Name: IT-CELLMANAGER)

My Mediamanager is in local Zone (Name: IT-MEDIAMANAGER)

My Backuphost (EXT-BACKUPHOST) for vmware is behind Firewall. Also the VCenter-Appliance (EXT-VCENTER).

All Ports I need are allowed:

• 5555, 445 between all Servers with DP-Agent.
• Ports definde in omnirc between all Servers with DP-Agent
• 443 between IT-CELLMANAGER and EXT-VCENTER
• 443 between EXT-BACKUPHOST and EXT-VCENTER

I have importet the SM-VCENTER in DP as Vcenter-Server.

I have created  a job and can read all the VMs from VCenter-Server.

But running the job I get following error:

[Normal] From: VEPALIB_VMWARE@EXT-Backuphost "/Datacenter" Time: 13.04.2016 10:25:44

Resolving objects for backup on vCenter EXT-VCENTER' ...

[Major] From: VEPALIB_VMWARE@EXT-Backuphost "/Datacenter" Time: 13.04.2016 10:25:48

Backup failed.

It seems that the listning is not possible.

What I have forgotten in firewall? Or is their another problem?

rg.

Hansi

Netapp NDMP backups and restores of data volumes with a “/” at the end of the name worked fine in the past.
An example would be a data volume named "/vol/Dataset_CIFS_FS/".
Now after upgrade to DP 9.05 we observe some problems during restore tests.

- With DP 9.05 restore behavior changed
    - Using name  "/vol/Dataset_CIFS_FS/" we  observed that Restore GUI does not present any files for selection.
      Same for all those data volume backups that contain a "/" at the end of the data volume name.
      Using such name with DP 9.05 we are only able to restore the whole data volume but not single files as
      in the past.
 
    - DP 9.05 tests with name "/vol/Dataset_CIFS_FS" (omitting /) show:
      If doing same backup/restore with this data volume name all works fine.
 
So be careful with your data volume name.  
A solution for future backups could be to not use a "/" in the data volume name.

Hello everyone,

I'm new with HP data protector.

i have backed-up my data to a tape, but when i insert that one to the tape library to restore, it shows up unknown

Any quick way to turn the unknown tape to good?