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

Upgrade 6.2 > 8.10 failure

January 29, 2014, 6:02 am
$
0
0

Hi all,

 

i'messing around with the upgrade from 6.21 to 8.1.

 

When i run through the install Gui the upgrade fails with "Installation terminated due to error(s) on exporting old database.

 

In the logfile omnimigrate_.....log everything looks good, until i see the following lines at the end:

 

 

[....]
StartServices()

	Sys()

			C:\OmniBack\bin/omnisv -start 

		OpenFileForWriting()

					 file=C:\OmniBack\tmp\tmp_omnimigrate_vjmXD_cmd_stdout
					 file=C:/OmniBack/tmp/tmp_omnimigrate_vjmXD_cmd_stdout
		OpenFileForWriting time = 0 s

		OpenFileForWriting()

					 file=C:\OmniBack\tmp\tmp_omnimigrate_kNS1E_cmd_stderr
					 file=C:/OmniBack/tmp/tmp_omnimigrate_kNS1E_cmd_stderr
		OpenFileForWriting time = 0 s

				 stdOut=C:/OmniBack/tmp/tmp_omnimigrate_vjmXD_cmd_stdout
				 stdErr=C:/OmniBack/tmp/tmp_omnimigrate_kNS1E_cmd_stderr
				 C:\OmniBack\bin/omnisv -start  1>"C:/OmniBack/tmp/tmp_omnimigrate_vjmXD_cmd_stdout" 2>"C:/OmniBack/tmp/tmp_omnimigrate_kNS1E_cmd_stderr"
		ReadStdErr()

			TryToOpenFileForReading()

						 file=C:/OmniBack/tmp/tmp_omnimigrate_kNS1E_cmd_stderr
						 encoding=
			TryToOpenFileForReading time = 0 s

		ReadStdErr time = 0 s

		ReadStdOut()

			TryToOpenFileForReading()

						 file=C:/OmniBack/tmp/tmp_omnimigrate_vjmXD_cmd_stdout
						 encoding=
			TryToOpenFileForReading time = 0 s

					 Cannot start "crs" service, system error:
					[1053] The service did not respond to the start or control request in a timely fashion. 
		ReadStdOut time = 0 s

	Sys time = 26 s

	Die()

			msg='C:\OmniBack\bin/omnisv -start ' returns:
			Cannot start "crs" service, system error: [1053] The service did not respond to the start or control request in a timely fashion. 

			err=SYS_FAILED

 

So there is a problem with starting the services in time, which is strange, because i never had issues with this (but i never stop/start them with the omnisv command).

 

Server is W2008R2 Std. running on VMware, VM with 4 CPUs, 4GB, low cpu and disk load on Hardware. Antivirus disabled for install.

 

What can i do about this?

 

thanks & cheers

stefan

 

↧
Search

Re: Data Protector 8.1 Linux: How to start GUI?

January 29, 2014, 6:51 am
$
0
0

Jason,

 

There is no xomni anynmore.  You have to install a Windows client and use that.

 

Further to this, you may have some firewall issues - come back to me here if you do and I will point you in the right direction.

 

Are you on Redhat or SUSE?

 

Regards

Mark

 

↧
↧

Re: Windows 2012 compatibilty with HP DP 6.20 ??

January 29, 2014, 6:51 am
↧

Re: Upgrade 6.2 > 8.10 failure

January 29, 2014, 7:04 am
$
0
0

There is a site-specific patch (SSP) that seems to address problems with 'omnimigrate', SSPNT800_004

 

"omnimigrate.pl script is changed in order to properly export existing Data Protector IDB. "

I am not sure if this script would be valid for 8.1, I don't see why not.  However, there are all kinds of other problems associated with 8.1, and for that reason, irf possible, I recommend that if you are going to upgrade, you only go to 8.0 or even 7.03

 

If you decide to go to 8.0, there are a few more SSPs that fix problems that were discovered after the release

 

You can open a case with the response center, either by phone, or through the SSO web site (preferable)

 

    http://support.openview.hp.com/casemanager/incident-index

 

Click on 'Submit a Service Request'.  Once you have a case open, request that a FTP site be created and that a copy of SSPNT800_004 be sent to the site.  This will include a 'test' file with installation instructions, and how to run the script

↧

Re: Data Protector 8.1 Linux: How to start GUI?

January 29, 2014, 7:08 am
$
0
0

If you are trying to run the Java GUI from your Linux cell manager, the 'xomni' command no longer exists, because support for the Java GUI has gone away.  You will need to use the Windows GUI

 

The system running the Windows GUI should be in the same domain as your cell manager, if not, you would need to create some firewall rules, and set a range of ports in the 'omnirc' file, but, lets jump off that bridge if we come to it

↧
↧

StoreOnceSoftware service in a cluster

January 29, 2014, 7:09 am
$
0
0

Hi,

 

I've a HP Data Protector 8.00 Cell Manager installed on a Windows 2008 R2 two nodes cluster with shared storage.

This same cluster hosts the HP DP BackupToDisk store with server side deduplication activated.

 

Everything is working properly except one thing :

 

when hp DP services (AS, CRS, IDB, IDB_CP) fail over from one node to the other everything is working except that the StoreOnceSoftware service does not start on the other node.

 

Indeed this service is not part of the clustered resources. I tried to add it but it can't be brought online.

 

So I've to manually start StoreOnceSoftware service when the other HP DP services fail over from one node to the other.

 

Is there a way to make this service work properly in cluster mode ?

 

Thanks.

↧

Re: StoreOnceSoftware service in a cluster

January 29, 2014, 8:19 am
$
0
0

I checked our StoreOnce Integration Guide, and the only reference to Clusters I found was this:

 

"Deduplication is not supported on clusters."

 

StoreOnce is not part of Data Protector, so, I think that you may want to open a case with the StoreOnce support group, and ask them this question

↧

Re: Data Protector 8.1 Linux: How to start GUI?

January 29, 2014, 11:39 am
$
0
0

RHEL 5.5, no firewall problem, just don't expect HP dropped the xomni GUI

↧
Search

Exchange backup failed

January 29, 2014, 8:54 pm
$
0
0

Helllo All ,

 

The same problem with me daily my exchange backup is going to failed please help me on this topic

 

Error MSG. 61:1002   inactivity timeout of 7200 seconds. The agent on host will be shutdown

↧
↧

Error backup Exchange DP VSS API 3

January 30, 2014, 7:34 am
$
0
0

Hello

 

I've a problem on my job to backup exchange server.

I'm on version 8.10 (before I was on version 8.00 and it worked).

 

I've the message

Error 3 returned from DP VSS API

 

On all client Firewall is off. On each client in omnirc.tmpl I add 

DPCOM_SWITCHUSER_TIMEOUT=600
DPCOM_CONNECT_TIMEOUT=600
OB2IPCKEEPALIVE=1

 

But the problem is still present.

 

I haven't got allow-hosts in C:\ProgramData\OmniBack\Config\client on my client and I check  for Show hidden files,folders, and drives

 

I have not ideas what I've to do.

 

Thank you

 

I can't restart servers

↧

Re: HP Data Protector

January 30, 2014, 7:36 am
$
0
0

Where do I add the command for increasing the wait time for backups.

 

Not enough licenses "Direct attached tape drive for Windows / NetWare / Linux".

Session is waiting for some of devices to get free

 

The command you listed was SMWaitForDevice

 

Any help would be appreciated.

 

Thank You

↧

Re: Exchange backup failed

January 30, 2014, 8:11 am
$
0
0

Without seeing a complete session report, I can only look at the symptom you presented. Sometimes, for example, there is a previous error, where the end result was a timeout

 

However, my main approach for a few years in dealing with Timeout issues is to Implement KeepAlive.  I woud do this on both the Exchange server, and on the Media Agent you are backing up to

 

I wrote a Support Tip on how to do this:

 

http://h30499.www3.hp.com/t5/Data-Protector-Support-and-News/Data-Protector-Support-Tip-Windows-Only-Using-KeepAlive-to/m-p/6202561#M141140

 

This tip was for Windows only, but, I also wrote tips for implementing KeepAlive on both HPUX and Linux if your media agent is running on one of those.  When you enter the board, do a search for 'KeepAlive'

↧

Re: Error backup Exchange DP VSS API 3

January 30, 2014, 8:39 am
$
0
0

First, although it is not directly related, any changes made to 'omnirc.tmpl' will have no effect.  This is a template file.  The lines you referenced should be in a file 'omnirc' and it shouold have no filename extension.

 

Also, whenever you make a change to a 'omnirc' running on Windows, you have to stop and restart the DP INET service after saving the file

 

Here is what I found on your error, although most of these are for DP 6.2 and 7.0x

 

===========

 

In one case, this was caused by having a firewall turned on, where the debugs would show

 

[  5] [MARK 3] in IpcConnectToProcessBase
    Code is:3012  SystemErr: [10061] Connection refused <--------------!!!

 

Turning off the firewall, which was on the Network, in tyhis case HP Sec Blade firewall was enabled.  Alos, if oyu have a local firewall enabled, it can cause this problem

 

I don't know if this is going to be your solution, since this started happening after upgrading to 8.1, but it is a known source for this problem.  There 5 cases where a firewall was shown to cause the problem

 

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

 

There were a couple of 'vssbar' fixes made, but, these were for DP 6.21, so probably not of much help

 

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

 

If all the possible firewalls are turned off, you will need to open a case with the response center.  You will need to run INET debugs, and collect the debugs from the Cell Manager, and the client where this is failing

↧
↧

Re: HP Data Protector

January 30, 2014, 8:47 am
$
0
0

The pace where you would increase teh device time out is located at

 

Windows 2003

   Program FIles -> Omniback -> Config -> Server -> Options -> global

Windows 2008

   ProgramData -> Omniback -> Config -> Server -> Options -> global

 

UNIX

   /etc/opt/omni/server/options/global

 

Open the file in an editor, and find the line:

 

# SmWaitForDevice=WaitForInMinutes

# default: 60 minutes

 

Make a copy of the line, then, on one line remove the # sign and the 'space' that follows, and set the value to what you want to use, so, for example

 

SmWaitForDevice=120

# SmWaitForDevice=WaitForInMinutes

 

and save the file.  This will increase the timeout for devices to 2 hours.  At your earliest opportunity, stop and restart Data Protector

↧

Re: HP DataProtector NDMP session failed when backing up Netapp volume

January 30, 2014, 8:53 am
$
0
0

I am having the exact same problem after (I think) upgrading to 7.03.  Have you found a solution to this?  I am going to try and downgrade back to 7.01.

 

↧
Search

Re: Data protector Reporting

January 30, 2014, 9:27 am
$
0
0

I will work on this and update you...

↧

Re: BRICK - new Version 1.10 Linux/Windows, different browser, DP 8.1

January 30, 2014, 10:52 am
$
0
0

I have recently downloaded and ran several brick reports and it is fantastic.  I am new to DP so this is helping out a lot with documenting etc.  

↧
↧

Problem creating job MSSQL DP 6.11

January 30, 2014, 11:25 am
$
0
0

Hi,

 

Successfully installed the DataProtector agent on a windows server 2008 R2, but when trying to create a job in DataProtector to select this server it does not display the application database, the field is blank. Is it something in the MSSQL server configuration? I believe it is no problem in DataProtector.

 

Anyone had any similar experience or have some knowledge about it. I appreciate the help.

 

Regards,

↧

Re: Problem creating job MSSQL DP 6.11

January 30, 2014, 12:23 pm
$
0
0

This is typical of not having a path to the SQL bin directory as one of the environment variables on the SQL server.  It occurs mostly on Exchange, but, I have also see this with SQL

 

Here is what the Exchange integration Guide says about the 'path'

 

The

<Exchange_home>\bin directory must be added to the Windows

Path

environment variable before any operation is performed.

To add this directory, proceed as follows:

1. In the Microsoft Windows Explorer, right-click My Computer and  click Properties.

2. In the Properties dialog box, click Advanced and then Environment Variables.

3. In the Environment Variables dialog box, select Path in the System Variables list and click Edit.

4. Add

         <Exchange_home>\bin

in the Variable Value text box and click OK.

 

One easy way to check this is, on the SQL server, type teh command

 

         path

 

to see if there is a path to the 'bin' directory

 

 

↧

"Cannot open exchanger control device" error

January 31, 2014, 6:04 am
$
0
0

Being new to the data protector hardware and software it seems that I am running into every problem that is out there. The other night we were doing some upgrades to our core network switches and one of the Unix servers that is used by the dp. I wanted to be sure that the dp was not going to have any issues.

 

We had a backup that was still running that I cancelled using the GUI and to be on the safe side I did a "omnisv stop" on the windows server that runs the dp. After the upgrades I started the dp again and now one of the dp's does not want to respond.

 

When I try and do a scan I get the following two messages and nothing else. The agent is being invoked on the Unix box and that is where everything stops.

 

 

 

[Normal] From: MSM@lew-dpbackup.mydomain.com "HP:Ultrium 5-SCSI_1_lewsd1"  Time: 1/31/2014 7:36:25 AM

      Media session 2014/01/31-3 started.

 

[Normal] From: MMA@mydomain.com "HP:Ultrium 5-SCSI_1_lewsd1"  Time: 1/31/2014 7:36:25 AM

      STARTING Media Agent "HP:Ultrium 5-SCSI_1_lewsd1"

 

 

This morning when I logged on to the dp I got the following messages.

 

 

[Critical] From: UMA@mydomain.com "HP:1x8 G2 AUTOLDR_lewsd1"  Time: 1/31/2014 1:55:16 AM

[90:59]     mydomain.com : /dev/rchgr/autoch2

      Cannot open exchanger control device ([6] No such device or address)

 

[Critical] From: BSM@lew-dpbackup.mydomain.com "Weekly All Systems Full-Incr1"  Time: 1/31/2014 1:55:17 AM

      None of the Disk Agents completed successfully.

      Session has failed.

 

 

 

I have rebooted the device, checked for stuck tapes and have done all the commands seen below but I am still not able to get a simple barcode scan of a tape done. Any ideas on this one?

 

omnisv stop

omnisv start

omnidbutil -show_locked_devs

omnidbutil -clear

 

ps -ef | grep omni

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