Trying to find out for sure if DP 8.1x versions support SLES 12 on z/Linux platforms as the latest guide only states below but not sure if that covers exactly z./Linux systems for S390X Architecture.

 Linux (32-bit): RHEL 4 5.x, 6.0, 6.1, 6.2, 6.3, 6.4

SLES 10, 11

 Linux (64-bit): RHEL 4 5.x (Itanium, x64)

RHEL 4 6.x, 7.x (x64)

SLES 9, 10, 11 (Itanium, x64)

SLES 12 (x64)

↧

Moving volume to another server.

March 30, 2016, 3:07 pm

≫ Next: storeonce error with source side deuplication enabled

≪ Previous: DP 8.1x support of z/Linux

I still have a UNIX rp3440-4 server that I am using Data Protector 6.20 because I can not install the current version of DP. So, I am doing backups to Disk onto a 1TB volume that is attached to a Windows 2003 server that is going away. I want to move the volume to a windows 2008 server but don't know how to go about doing that.

Current server is a Windows 2003 server and the volume is mapped as the G: drive. I am doing Filesystem backups to a volume on my SAN.

The new server is a Windows 2008 server and I am going to be mounting the same volume as the O: drive.

I tried to move a different server this morning as a test but failed. I couldn't change the backup job to get it to point to the new server so I decided to delete the backup job and recreate it. To do that I had to export all of the media. Once I created the new backup job I couldn't find any way to import the media back into the pool.

Is there something that I am missing because the server that has the volumes connected to is going to be removed next week.

↧

storeonce error with source side deuplication enabled

March 31, 2016, 6:37 am

≫ Next: (DP) Support Tip: Remote installation for Linux agent system fails

≪ Previous: Moving volume to another server.

Hi I have problem with storeonce 4500 device, everything working fine but my source side dedup backup job not working and give me error

[Normal] From: BSM@dataprotector.domain.local "TEST_SS" Time: 3/30/2016 6:14:15 PM
   Backup session 2016/03/30-19 started.

[Normal] From: BMA@xxx02.domain.local "CATALYST_BA_ETH_SS [GW 1496:1:298090846938045720]" Time: 3/30/2016 6:14:17 PM
   STARTING Media Agent "CATALYST_BA_ETH_SS [GW 1496:1:298090846938045720]"

[Normal] From: BMA@xxx02.domain.local "CATALYST_BA_ETH_SS [GW 1496:0:298090846938045720]" Time: 3/30/2016 6:14:17 PM
   STARTING Media Agent "CATALYST_BA_ETH_SS [GW 1496:0:298090846938045720]"

[Normal] From: BMA@xxx02.domain.local "CATALYST_BA_ETH_SS [GW 1496:0:298090846938045720]" Time: 3/30/2016 6:14:18 PM
   Loading medium from slot \\d2d.ba\CTL_BA\6bb1916e_56fbfb5a_069c_00bd to device CATALYST_BA_ETH_SS [GW 1496:0:298090846938045720]

[Normal] From: BMA@xxx02.domain.local "CATALYST_BA_ETH_SS [GW 1496:1:298090846938045720]" Time: 3/30/2016 6:14:18 PM
   Loading medium from slot \\d2d.ba\CTL_BA\6bb1916e_56fbfb5a_069c_00be to device CATALYST_BA_ETH_SS [GW 1496:1:298090846938045720]

[Normal] From: VBDA@xxx02.domain.local "xxx02.domain.local [\\?\Volume{6249d17d-eeac-48df-86fa-090b4d2f726f}\]" Time: 3/30/2016 6:14:20 PM
   STARTING Disk Agent for xxx02.domain.local:\\?\Volume{6249d17d-eeac-48df-86fa-090b4d2f726f}\ "xxx02.domain.local [\\?\Volume{6249d17d-eeac-48df-86fa-090b4d2f726f}\]".

[Normal] From: VBDA@xxx02.domain.local "xxx02.domain.local [/CONFIGURATION]" Time: 3/30/2016 6:14:21 PM
   STARTING Disk Agent for xxx02.domain.local:/CONFIGURATION "xxx02.domain.local [/CONFIGURATION]".

[Normal] From: VBDA@xxx02.domain.local "xxx02.domain.local [\\?\Volume{6249d17d-eeac-48df-86fa-090b4d2f726f}\]" Time: 3/30/2016 6:14:29 PM
   VSS option was specified. Attempting to create snapshot.

[Normal] From: VBDA@xxx02.domain.local "xxx02.domain.local [\\?\Volume{6249d17d-eeac-48df-86fa-090b4d2f726f}\]" Time: 3/30/2016 6:14:33 PM
   Clearing archive flags is not applicable with Volume Shadow Copy backup.

[Critical] From: VBDA@xxx02.domain.local "xxx02.domain.local [\\?\Volume{6249d17d-eeac-48df-86fa-090b4d2f726f}\]" Time: 3/30/2016 6:14:34 PM
   Unexpected close reading NET message => aborting.

[Critical] From: VBDA@xxx02.domain.local "xxx02.domain.local [\\?\Volume{6249d17d-eeac-48df-86fa-090b4d2f726f}\]" Time: 3/30/2016 6:14:34 PM
   Connection to Media Agent broken => aborting.

[Normal] From: VBDA@xxx02.domain.local "xxx02.domain.local [\\?\Volume{6249d17d-eeac-48df-86fa-090b4d2f726f}\]" Time: 3/30/2016 6:14:34 PM
   Filesystem Statistics:

       Directories ........         4
       Regular files ......         4
       ------------------------------
       Objects Total ......         3
       Total Size .........   2.99 MB

[Major] From: BMA@xxx02.domain.local "CATALYST_BA_ETH_SS [GW 1496:1:298090846938045720]" Time: 3/30/2016 6:14:34 PM
[90:51]     \\d2d.ba\CTL_BA\6bb1916e_56fbfb5a_069c_00be
   Cannot write to device (StoreOnce error: The requested bandwidth mode is not allowed by the data transfer policy)

[Normal] From: VBDA@xxx02.domain.local "xxx02.domain.local [\\?\Volume{6249d17d-eeac-48df-86fa-090b4d2f726f}\]" Time: 3/30/2016 6:14:36 PM
   ABORTED Disk Agent for xxx02.domain.local:\\?\Volume{6249d17d-eeac-48df-86fa-090b4d2f726f}\ "xxx02.domain.local [\\?\Volume{6249d17d-eeac-48df-86fa-090b4d2f726f}\]".

[Normal] From: BMA@xxx02.domain.local "CATALYST_BA_ETH_SS [GW 1496:1:298090846938045720]" Time: 3/30/2016 6:14:39 PM
   Unloading medium to slot \\d2d.ba\CTL_BA\6bb1916e_56fbfb5a_069c_00be from device CATALYST_BA_ETH_SS [GW 1496:1:298090846938045720]

[Normal] From: BMA@xxx02.domain.local "CATALYST_BA_ETH_SS [GW 1496:1:298090846938045720]" Time: 3/30/2016 6:14:39 PM
   ABORTED Media Agent "CATALYST_BA_ETH_SS [GW 1496:1:298090846938045720]"

[Normal] From: BMA@xxx02.domain.local "CATALYST_BA_ETH_SS [GW 1496:2:298090846938045720]" Time: 3/30/2016 6:14:39 PM
   STARTING Media Agent "CATALYST_BA_ETH_SS [GW 1496:2:298090846938045720]"

[Normal] From: BMA@xxx02.domain.local "CATALYST_BA_ETH_SS [GW 1496:2:298090846938045720]" Time: 3/30/2016 6:14:40 PM
   Loading medium from slot \\d2d.ba\CTL_BA\6bb1916e_56fbfb70_069c_00c1 to device CATALYST_BA_ETH_SS [GW 1496:2:298090846938045720]

[Normal] From: VBDA@xxx02.domain.local "xxx02.domain.local [/C]" Time: 3/30/2016 6:14:42 PM
   STARTING Disk Agent for xxx02.domain.local:/C "xxx02.domain.local [/C]".

[Critical] From: VBDA@xxx02.domain.local "xxx02.domain.local [/CONFIGURATION]" Time: 3/30/2016 6:14:48 PM
   Unexpected close reading NET message => aborting.

[Critical] From: VBDA@xxx02.domain.local "xxx02.domain.local [/CONFIGURATION]" Time: 3/30/2016 6:14:48 PM
   Connection to Media Agent broken => aborting.

[Normal] From: VBDA@xxx02.domain.local "xxx02.domain.local [/CONFIGURATION]" Time: 3/30/2016 6:14:48 PM
   Filesystem Statistics:

       Directories ........         0
       Regular files ......         0
       ------------------------------
       Objects Total ......         0
       Total Size .........   3.00 MB

[Major] From: BMA@xxx02.domain.local "CATALYST_BA_ETH_SS [GW 1496:0:298090846938045720]" Time: 3/30/2016 6:14:48 PM
[90:51]     \\d2d.ba\CTL_BA\6bb1916e_56fbfb5a_069c_00bd
   Cannot write to device (StoreOnce error: The requested bandwidth mode is not allowed by the data transfer policy)

[Normal] From: VBDA@xxx02.domain.local "xxx02.domain.local [/CONFIGURATION]" Time: 3/30/2016 6:14:50 PM
   ABORTED Disk Agent for xxx02.domain.local:/CONFIGURATION "xxx02.domain.local [/CONFIGURATION]".

[Normal] From: BMA@xxx02.domain.local "CATALYST_BA_ETH_SS [GW 1496:0:298090846938045720]" Time: 3/30/2016 6:14:53 PM
   Unloading medium to slot \\d2d.ba\CTL_BA\6bb1916e_56fbfb5a_069c_00bd from device CATALYST_BA_ETH_SS [GW 1496:0:298090846938045720]

[Normal] From: BMA@xxx02.domain.local "CATALYST_BA_ETH_SS [GW 1496:0:298090846938045720]" Time: 3/30/2016 6:14:53 PM
   ABORTED Media Agent "CATALYST_BA_ETH_SS [GW 1496:0:298090846938045720]"

[Normal] From: VBDA@xxx02.domain.local "xxx02.domain.local [/C]" Time: 3/30/2016 6:14:56 PM
   VSS Writer 'Task Scheduler Writer':Component 'TasksStore' successfully added in the snapshot.

[Normal] From: VBDA@xxx02.domain.local "xxx02.domain.local [/C]" Time: 3/30/2016 6:14:56 PM
   VSS Writer 'VSS Metadata Store Writer':Component 'WriterMetadataStore' successfully added in the snapshot.

[Normal] From: VBDA@xxx02.domain.local "xxx02.domain.local [/C]" Time: 3/30/2016 6:14:56 PM
   VSS Writer 'Performance Counters Writer':Component 'PerformanceCounters' successfully added in the snapshot.

[Normal] From: VBDA@xxx02.domain.local "xxx02.domain.local [/C]" Time: 3/30/2016 6:14:56 PM
   VSS Writer 'System Writer':Component 'System Files' successfully added in the snapshot.

[Normal] From: VBDA@xxx02.domain.local "xxx02.domain.local [/C]" Time: 3/30/2016 6:14:56 PM
   VSS Writer 'System Writer':Component 'Win32 Services Files' successfully added in the snapshot.

[Normal] From: VBDA@xxx02.domain.local "xxx02.domain.local [/C]" Time: 3/30/2016 6:14:56 PM
   VSS Writer 'Registry Writer':Component 'Registry' successfully added in the snapshot.

[Normal] From: VBDA@xxx02.domain.local "xxx02.domain.local [/C]" Time: 3/30/2016 6:14:56 PM
   VSS Writer 'COM+ REGDB Writer':Component 'COM+ REGDB' successfully added in the snapshot.

[Normal] From: VBDA@xxx02.domain.local "xxx02.domain.local [/C]" Time: 3/30/2016 6:14:56 PM
   VSS Writer 'WMI Writer':Component 'WMI' successfully added in the snapshot.

[Normal] From: VBDA@xxx02.domain.local "xxx02.domain.local [/C]" Time: 3/30/2016 6:14:56 PM
   VSS option was specified. Attempting to create snapshot.

[Normal] From: VBDA@xxx02.domain.local "xxx02.domain.local [/C]" Time: 3/30/2016 6:15:01 PM
   Clearing archive flags is not applicable with Volume Shadow Copy backup.

[Critical] From: VBDA@xxx02.domain.local "xxx02.domain.local [/C]" Time: 3/30/2016 6:16:04 PM
   Unexpected close reading NET message => aborting.

[Critical] From: VBDA@xxx02.domain.local "xxx02.domain.local [/C]" Time: 3/30/2016 6:16:04 PM
   Connection to Media Agent broken => aborting.

[Normal] From: VBDA@xxx02.domain.local "xxx02.domain.local [/C]" Time: 3/30/2016 6:16:04 PM
   Filesystem Statistics:

       Directories ........     27828
       Regular files ......    138006
       ------------------------------
       Objects Total ......        26
       Total Size .........   2.73 MB

[Major] From: BMA@xxx02.domain.local "CATALYST_BA_ETH_SS [GW 1496:2:298090846938045720]" Time: 3/30/2016 6:16:04 PM
[90:51]     \\d2d.ba\CTL_BA\6bb1916e_56fbfb70_069c_00c1
   Cannot write to device (StoreOnce error: The requested bandwidth mode is not allowed by the data transfer policy)

[Normal] From: VBDA@xxx02.domain.local "xxx02.domain.local [/C]" Time: 3/30/2016 6:16:06 PM
   ABORTED Disk Agent for xxx02.domain.local:/C "xxx02.domain.local [/C]".

[Normal] From: BMA@xxx02.domain.local "CATALYST_BA_ETH_SS [GW 1496:2:298090846938045720]" Time: 3/30/2016 6:16:08 PM
   Unloading medium to slot \\d2d.ba\CTL_BA\6bb1916e_56fbfb70_069c_00c1 from device CATALYST_BA_ETH_SS [GW 1496:2:298090846938045720]

[Normal] From: BMA@xxx02.domain.local "CATALYST_BA_ETH_SS [GW 1496:2:298090846938045720]" Time: 3/30/2016 6:16:08 PM
   ABORTED Media Agent "CATALYST_BA_ETH_SS [GW 1496:2:298090846938045720]"

[Critical] From: BSM@dataprotector.domain.local "TEST_SS" Time: 3/30/2016 6:16:08 PM
   None of the Disk Agents completed successfully.
   Session has failed.

[Normal] From: BSM@dataprotector.domain.local "TEST_SS" Time: 3/30/2016 6:16:08 PM

   Backup Statistics:

       Session Queuing Time (hours)         0.00
       -------------------------------------------
       Completed Disk Agents ........          0
       Failed Disk Agents ...........          3
       Aborted Disk Agents ..........          0
       -------------------------------------------
       Disk Agents Total ...........          3
       ===========================================
       Completed Media Agents .......          0
       Failed Media Agents ..........          3
       Aborted Media Agents .........          0
       -------------------------------------------
       Media Agents Total ..........          3
       ===========================================
       Throttled Gateways ...........          0
       Gateways Total ...............          1
       ===========================================
       Overall Deduplication Ratio ..          -
       ===========================================
       Mbytes Total .................       0 MB
       Used Media Total .............          3
       Disk Agent Errors Total ......          6

============================================================================
                      Session failed!
============================================================================

↧

(DP) Support Tip: Remote installation for Linux agent system fails

March 31, 2016, 7:33 am

≫ Next: Cannot access Data Protector 8.10 after omnigencert.pl

≪ Previous: storeonce error with source side deuplication enabled

[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

↧

Cannot access Data Protector 8.10 after omnigencert.pl

March 31, 2016, 7:51 am

≫ Next: (DP) Support Tip: make sure IDB backups always is 100% good

≪ Previous: (DP) Support Tip: Remote installation for Linux agent system fails

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

↧

(DP) Support Tip: make sure IDB backups always is 100% good

March 31, 2016, 9:38 am

≫ Next: (DP) Support Tip: Data Protector and MS SQL account permissions

≪ Previous: Cannot access Data Protector 8.10 after omnigencert.pl

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.

↧

(DP) Support Tip: Data Protector and MS SQL account permissions

April 3, 2016, 9:15 pm

≫ Next: (DP) Support Tip: Disk Agent Traversing Cross (nested) Mount Points

≪ Previous: (DP) Support Tip: make sure IDB backups always is 100% good

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.

↧

(DP) Support Tip: Disk Agent Traversing Cross (nested) Mount Points

April 4, 2016, 3:06 pm

≫ Next: software compression

≪ Previous: (DP) Support Tip: Data Protector and MS SQL account permissions

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.

Enabling it, it will also backup NFS mounted mountpoints filesytems.

↧

software compression

April 5, 2016, 10:28 am

≫ Next: DataProtector Upgrade from 6.20 to 9.00

≪ Previous: (DP) Support Tip: Disk Agent Traversing Cross (nested) Mount Points

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

↧

DataProtector Upgrade from 6.20 to 9.00

April 5, 2016, 10:48 pm

≫ Next: Install or import client in the DP

≪ Previous: software compression

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)

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 ??

↧

Install or import client in the DP

April 6, 2016, 6:04 am

≫ Next: Data protector 9 message on Aix system

≪ Previous: DataProtector Upgrade from 6.20 to 9.00

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

↧

Data protector 9 message on Aix system

April 7, 2016, 1:13 am

≫ Next: VMWARE backup is running using the NBD mode even when we mention as SAN mode in VMware configuration

≪ Previous: Install or import client in the DP

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 ?

↧

VMWARE backup is running using the NBD mode even when we mention as SAN mode in VMware configuration

April 7, 2016, 8:42 am

≫ Next: (DP) Support Tip: setting CRS debugs via omnisv

≪ Previous: Data protector 9 message on Aix system

=== 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.

↧

(DP) Support Tip: setting CRS debugs via omnisv

April 8, 2016, 5:36 am

≫ Next: data matching issues

≪ Previous: VMWARE backup is running using the NBD mode even when we mention as SAN mode in VMware configuration

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.

↧

data matching issues

April 8, 2016, 11:44 pm

≫ Next: DP 8.1x support of z/Linux

≪ Previous: (DP) Support Tip: setting CRS debugs via omnisv

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

↧

DP 8.1x support of z/Linux

March 30, 2016, 1:02 pm

≫ Next: Moving volume to another server.

≪ Previous: data matching issues

Trying to find out for sure if DP 8.1x versions support SLES 12 on z/Linux platforms as the latest guide only states below but not sure if that covers exactly z./Linux systems for S390X Architecture.

 Linux (32-bit): RHEL 4 5.x, 6.0, 6.1, 6.2, 6.3, 6.4

SLES 10, 11

 Linux (64-bit): RHEL 4 5.x (Itanium, x64)

RHEL 4 6.x, 7.x (x64)

SLES 9, 10, 11 (Itanium, x64)

SLES 12 (x64)

↧

Moving volume to another server.

March 30, 2016, 3:07 pm

≫ Next: storeonce error with source side deuplication enabled

≪ Previous: DP 8.1x support of z/Linux

Current server is a Windows 2003 server and the volume is mapped as the G: drive. I am doing Filesystem backups to a volume on my SAN.

The new server is a Windows 2008 server and I am going to be mounting the same volume as the O: drive.

Is there something that I am missing because the server that has the volumes connected to is going to be removed next week.

↧

storeonce error with source side deuplication enabled

March 31, 2016, 6:37 am

≫ Next: (DP) Support Tip: Remote installation for Linux agent system fails

≪ Previous: Moving volume to another server.

Hi I have problem with storeonce 4500 device, everything working fine but my source side dedup backup job not working and give me error

↧