If I have a backup job set to use tape drive 1 and it is set to run an incremental, if I point this backup job to use tape drive 2 for instance, will it run it as incremental still or will it run as a full?

Environment：

DP 9.03               

Cell Manager:              WINDOW 2008               

Oracle server OS:         AIX 6               

Oracle version:              11g               

 Checking steps and solution:

             ---- check OCI Library file：…./lib64/libclntsh.a, exist

             ---- this OCI file should be loaded by DP file：util_orarest_64.exe

             ---- set PATH=/usr/omni/bin/

             ---- install TM “QCIM2A63008_TM1.tar”

Hi,

I'm planning for my customer DP upgrade from 7.03 to 9.04.

He has old windows 2000 systems with DP6.11 disk agent. Cannot move to new o.s. because an application constrains.

Anyone has tried if DP9 is working with Disk Agent 6.11 ?

thanks in advance

Davide

Virtual machine with vcenter onboard gets its virtual disk unexpectedly unmounted while data protector is performing some backup operations. Windows server goes to BSOD and vm cannot start - operating system not found. Now this is happening almost every day. Help please!

DataProtector - A.07.00 build version 105

VCentr - 5.5

2015-11-10T21:38:02.259Z| vcpu-0| I120: LSI:Event notification sent for SAS device scsi0:0...

2015-11-10T21:38:02.262Z| vcpu-0| I120: Destroying virtual dev for scsi0:0 vscsi=8850

2015-11-10T21:38:02.262Z| vcpu-0| I120: VMMon_VSCSIStopVports: No such target on adapter

2015-11-10T21:38:02.303Z| vcpu-0| I120: scsi0:0: numIOs = 0 numMergedIOs = 0 numSplitIOs = 0 ( 0.0%)

2015-11-10T21:38:02.303Z| vcpu-0| I120: Closing disk scsi0:0

2015-11-10T21:38:02.306Z| vcpu-0| I120: DISKLIB-CBT   : Shutting down change tracking for untracked fid 610996176.

2015-11-10T21:38:02.306Z| vcpu-0| I120: DISKLIB-CBT   : Successfully disconnected CBT node.

2015-11-10T21:38:02.524Z| vcpu-0| I120: DISKLIB-VMFS  : "/vmfs/volumes/4e172714-a5a16bbd-eedf-002264997d72/vcs/vcs-flat.vmdk" : closed.

2015-11-10T21:38:02.525Z| vcpu-0| A115: ConfigDB: Setting scsi0:0.present = "false"

2015-11-10T21:38:04.727Z| mks| I120: SVGA disabling SVGA

2015-11-10T21:38:04.741Z| svga| I120: WinBSOD: ( 1) `A problem has been detected and Windows has been shut down to prevent damage    '

2015-11-10T21:38:04.741Z| svga| I120: WinBSOD: ( 2) `to your computer. '

2015-11-10T21:38:04.741Z| svga| I120: WinBSOD: ( 5) `A process or thread crucial to system operation has unexpectedly exited or been '

2015-11-10T21:38:04.741Z| svga| I120: WinBSOD: ( 6) `terminated. '

2015-11-10T21:38:04.742Z| svga| I120: WinBSOD: ( 8) `If this is the first time you've seen this Stop error screen, '

2015-11-10T21:38:04.742Z| svga| I120: WinBSOD: ( 9) `restart your computer. If this screen appears again, follow '

2015-11-10T21:38:04.742Z| svga| I120: WinBSOD: (10) `these steps: '

2015-11-10T21:38:04.742Z| svga| I120: WinBSOD: (12) `Check to make sure any new hardware or software is properly installed.          '

2015-11-10T21:38:04.742Z| svga| I120: WinBSOD: (13) `If this is a new installation, ask your hardware or software manufacturer       '

2015-11-10T21:38:04.742Z| svga| I120: WinBSOD: (14) `for any Windows updates you might need. '

2015-11-10T21:38:04.742Z| svga| I120: WinBSOD: (16) `If problems continue, disable or remove any newly installed hardware            '

2015-11-10T21:38:04.742Z| svga| I120: WinBSOD: (17) `or software. Disable BIOS memory options such as caching or shadowing.          '

2015-11-10T21:38:04.742Z| svga| I120: WinBSOD: (18) `If you need to use Safe Mode to remove or disable components, restart '

2015-11-10T21:38:04.743Z| svga| I120: WinBSOD: (19) `your computer, press F8 to select Advanced Startup Options, and then            '

2015-11-10T21:38:04.743Z| svga| I120: WinBSOD: (20) `select Safe Mode. '

2015-11-10T21:38:04.743Z| svga| I120: WinBSOD: (22) `Technical information: '

2015-11-10T21:38:04.743Z| svga| I120: WinBSOD: (24) `*** STOP: 0x000000F4 (0x0000000000000003,0xFFFFFA80C2AC7910,0xFFFFFA80C2AC7BF0,0'

2015-11-10T21:38:04.743Z| svga| I120: WinBSOD: (25) `xFFFFF80001BD3460) '

2015-11-10T21:38:04.743Z| svga| I120: WinBSOD: (29) `Collecting data for crash dump ... '

2015-11-10T21:38:04.744Z| svga| I120: WinBSOD: (30) `Initializing disk for crash dump ... '

2015-11-10T21:38:04.860Z| vcpu-0| I120: CPU reset: soft (mode 2)

2015-11-10T21:38:04.860Z| vcpu-2| I120: CPU reset: soft (mode 1)

2015-11-10T21:38:04.861Z| vcpu-1| I120: CPU reset: soft (mode 1)

Hi everyone,

Data Protector
Product version A.09.00
Internal build version 104

Data Protector Inet service is running as local system on target server
Backup was working with integrated authentication

Hostname of SQL Server: smdc76070.sub.domain.be
Windows Server 2012
Instance name of SQL Server: SCSEC0
Before upgrade:
SQL Server 2012 SP2 with CU2 (11.0.5548)
After upgrade:
SQL Server 2012 SP2 with CU8 (11.0.5634)

Since upgrade of SQL Server the backups (full & transactional) are failing.

Contents of debug.log on target server:

18/11/2015 14:15:15 OB2BAR_SQLBAR.10204.5116 ["/integ/sql_7/sql7_common.cpp $Rev: 41801 $ $Date:: 2014-03-26 06:59:59":4043] A.09.00 b88
[SQL_GetSQLServerVersion] Version number smaller than 2000. Version: 0.0
cmd:"C:\Program Files\OmniBack\bin\sql_bar.exe" -nodirect -dev_n:1 -appsrv:smdc76070.sub.domain.be backupall -n:1 trans
Function trace (currentLevel=0):
Level 0: SQL_GetSQLServerVersion()

18/11/2015 14:15:15 OB2BAR_SQLBAR.10204.5116 ["/lib/cmn/win32nls.c $Rev: 39729 $ $Date:: 2013-10-28 13:34:00":275] A.09.00 b88
Bad catalog access for message #0 in set 9004

18/11/2015 14:15:15 OB2BAR_SQLBAR.10204.5116 ["/lib/cmn/win32nls.c $Rev: 39729 $ $Date:: 2013-10-28 13:34:00":287] A.09.00 b88
FormatMessage() failed with 1813, message #0 in set 9004

18/11/2015 14:15:15 OB2BAR_SQLBAR.10204.5116 ["/integ/sql_7/sql7_common.cpp $Rev: 41801 $ $Date:: 2014-03-26 06:59:59":4043] A.09.00 b88
[SQL_GetSQLServerVersion] Version number smaller than 2000. Version: 0.0
cmd:"C:\Program Files\OmniBack\bin\sql_bar.exe" -nodirect -dev_n:1 -appsrv:smdc76070.sub.domain.be backupall -n:1 trans
Function trace (currentLevel=1):
Level 1: SQL_GetSQLServerVersion()
Level 0: SQL_Backup()

18/11/2015 14:15:16 OB2BAR_SQLBAR.10204.5116 ["/lib/cmn/win32nls.c $Rev: 39729 $ $Date:: 2013-10-28 13:34:00":275] A.09.00 b88
Bad catalog access for message #0 in set 9004

18/11/2015 14:15:16 OB2BAR_SQLBAR.10204.5116 ["/lib/cmn/win32nls.c $Rev: 39729 $ $Date:: 2013-10-28 13:34:00":287] A.09.00 b88
FormatMessage() failed with 1813, message #0 in set 9004

18/11/2015 14:15:20 OB2BAR_SQLBAR.10204.5116 ["/integ/sql_7/sql7_common.cpp $Rev: 41801 $ $Date:: 2014-03-26 06:59:59":1724] A.09.00 b88
[SQL7_InitVDI] pDB->pVDISet->Create failed. Err code: 0x80770007, ?15 [152:8530]

18/11/2015 14:15:20 OB2BAR_SQLBAR.10204.5116 ["/integ/sql_7/sql7_backup.cpp $Rev: 41801 $ $Date:: 2014-03-26 06:59:59":577] A.09.00 b88
[SQL7_BackupDB] Getting exit code failed. Err: 6 , '[6] The handle is invalid. '
cmd:"C:\Program Files\OmniBack\bin\sql_bar.exe" -nodirect -dev_n:1 -appsrv:smdc76070.sub.domain.be backupall -n:1 trans
Function trace (currentLevel=3):
Level 3: SQL7_BackupDB()
Level 2: SQL7_BackupDatabases()
Level 1: SQL7_Backup()
Level 0: SQL_Backup()

18/11/2015 14:15:23 OB2BAR_SQLBAR.10204.5116 ["/lib/cmn/win32io.c $Rev: 42935 $ $Date:: 2014-06-06 11:59:21":162] A.09.00 b88
OB2_SysErrnoToString: for -13, from (system) failed with 317

18/11/2015 14:15:23 OB2BAR_SQLBAR.10204.5116 ["/integ/sql_7/sql7_backup.cpp $Rev: 41801 $ $Date:: 2014-03-26 06:59:59":683] A.09.00 b88
[SQL7_BackupDatabases] pCurDB->pVDISet->SignalAbort() failed. Err code: -2139684852, ?15 [152:8530]
cmd:"C:\Program Files\OmniBack\bin\sql_bar.exe" -nodirect -dev_n:1 -appsrv:smdc76070.sub.domain.be backupall -n:1 trans
Function trace (currentLevel=2):
Level 2: SQL7_BackupDatabases()
Level 1: SQL7_Backup()
Level 0: SQL_Backup()

18/11/2015 14:15:24 OB2BAR_SQLBAR.10204.5116 ["/integ/sql_7/sql7_common.cpp $Rev: 41801 $ $Date:: 2014-03-26 06:59:59":1724] A.09.00 b88
[SQL7_InitVDI] pDB->pVDISet->Create failed. Err code: 0x80770007, ?15 [152:8530]

18/11/2015 14:15:25 OB2BAR_SQLBAR.10204.5116 ["/integ/sql_7/sql7_backup.cpp $Rev: 41801 $ $Date:: 2014-03-26 06:59:59":577] A.09.00 b88
[SQL7_BackupDB] Getting exit code failed. Err: 6 , '[6] The handle is invalid. '
cmd:"C:\Program Files\OmniBack\bin\sql_bar.exe" -nodirect -dev_n:1 -appsrv:smdc76070.sub.domain.be backupall -n:1 trans
Function trace (currentLevel=3):
Level 3: SQL7_BackupDB()
Level 2: SQL7_BackupDatabases()
Level 1: SQL7_Backup()
Level 0: SQL_Backup()

18/11/2015 14:15:27 OB2BAR_SQLBAR.10204.5116 ["/lib/cmn/win32io.c $Rev: 42935 $ $Date:: 2014-06-06 11:59:21":162] A.09.00 b88
OB2_SysErrnoToString: for -13, from (system) failed with 317

18/11/2015 14:15:27 OB2BAR_SQLBAR.10204.5116 ["/integ/sql_7/sql7_backup.cpp $Rev: 41801 $ $Date:: 2014-03-26 06:59:59":683] A.09.00 b88
[SQL7_BackupDatabases] pCurDB->pVDISet->SignalAbort() failed. Err code: -2139684852, ?15 [152:8530]
cmd:"C:\Program Files\OmniBack\bin\sql_bar.exe" -nodirect -dev_n:1 -appsrv:smdc76070.sub.domain.be backupall -n:1 trans
Function trace (currentLevel=2):
Level 2: SQL7_BackupDatabases()
Level 1: SQL7_Backup()
Level 0: SQL_Backup()

18/11/2015 14:15:28 OB2BAR_SQLBAR.10204.5116 ["/integ/sql_7/sql7_common.cpp $Rev: 41801 $ $Date:: 2014-03-26 06:59:59":1724] A.09.00 b88
[SQL7_InitVDI] pDB->pVDISet->Create failed. Err code: 0x80770007, ?15 [152:8530]

18/11/2015 14:15:29 OB2BAR_SQLBAR.10204.5116 ["/integ/sql_7/sql7_backup.cpp $Rev: 41801 $ $Date:: 2014-03-26 06:59:59":577] A.09.00 b88
[SQL7_BackupDB] Getting exit code failed. Err: 6 , '[6] The handle is invalid. '
cmd:"C:\Program Files\OmniBack\bin\sql_bar.exe" -nodirect -dev_n:1 -appsrv:smdc76070.sub.domain.be backupall -n:1 trans
Function trace (currentLevel=3):
Level 3: SQL7_BackupDB()
Level 2: SQL7_BackupDatabases()
Level 1: SQL7_Backup()
Level 0: SQL_Backup()

18/11/2015 14:15:31 OB2BAR_SQLBAR.10204.5116 ["/lib/cmn/win32io.c $Rev: 42935 $ $Date:: 2014-06-06 11:59:21":162] A.09.00 b88
OB2_SysErrnoToString: for -13, from (system) failed with 317

18/11/2015 14:15:31 OB2BAR_SQLBAR.10204.5116 ["/integ/sql_7/sql7_backup.cpp $Rev: 41801 $ $Date:: 2014-03-26 06:59:59":683] A.09.00 b88
[SQL7_BackupDatabases] pCurDB->pVDISet->SignalAbort() failed. Err code: -2139684852, ?15 [152:8530]
cmd:"C:\Program Files\OmniBack\bin\sql_bar.exe" -nodirect -dev_n:1 -appsrv:smdc76070.sub.domain.be backupall -n:1 trans
Function trace (currentLevel=2):
Level 2: SQL7_BackupDatabases()
Level 1: SQL7_Backup()
Level 0: SQL_Backup()

18/11/2015 14:15:32 OB2BAR_SQLBAR.10204.5116 ["/integ/sql_7/sql7_common.cpp $Rev: 41801 $ $Date:: 2014-03-26 06:59:59":1724] A.09.00 b88
[SQL7_InitVDI] pDB->pVDISet->Create failed. Err code: 0x80770007, ?15 [152:8530]

18/11/2015 14:15:33 OB2BAR_SQLBAR.10204.5116 ["/integ/sql_7/sql7_backup.cpp $Rev: 41801 $ $Date:: 2014-03-26 06:59:59":577] A.09.00 b88
[SQL7_BackupDB] Getting exit code failed. Err: 6 , '[6] The handle is invalid. '
cmd:"C:\Program Files\OmniBack\bin\sql_bar.exe" -nodirect -dev_n:1 -appsrv:smdc76070.sub.domain.be backupall -n:1 trans
Function trace (currentLevel=3):
Level 3: SQL7_BackupDB()
Level 2: SQL7_BackupDatabases()
Level 1: SQL7_Backup()
Level 0: SQL_Backup()

18/11/2015 14:15:36 OB2BAR_SQLBAR.10204.5116 ["/lib/cmn/win32io.c $Rev: 42935 $ $Date:: 2014-06-06 11:59:21":162] A.09.00 b88
OB2_SysErrnoToString: for -13, from (system) failed with 317

18/11/2015 14:15:36 OB2BAR_SQLBAR.10204.5116 ["/integ/sql_7/sql7_backup.cpp $Rev: 41801 $ $Date:: 2014-03-26 06:59:59":683] A.09.00 b88
[SQL7_BackupDatabases] pCurDB->pVDISet->SignalAbort() failed. Err code: -2139684852, ?15 [152:8530]
cmd:"C:\Program Files\OmniBack\bin\sql_bar.exe" -nodirect -dev_n:1 -appsrv:smdc76070.sub.domain.be backupall -n:1 trans
Function trace (currentLevel=2):
Level 2: SQL7_BackupDatabases()
Level 1: SQL7_Backup()
Level 0: SQL_Backup()

At the same time, in application log:

SQLVDI: Loc=IdentifySQLServer. Desc=MSSQLSERVER. ErrorCode=(1060)The specified service does not exist as an installed service.
. Process=10204. Thread=5116. Client. Instance=. VD=.

I have removed the backup from Data Protector, removed Data Protector agents from target server and reinstalled them. Now, when I want to add the backup again, I get this error:
Integration cannot be configured. 12:8019. Description: *RETVAL*8010

In debug.log:

19/11/2015 11:29:17 OB2BAR_SQLBAR.6292.5592 ["/integ/sql_7/sql7_common.cpp $Rev: 41801 $ $Date:: 2014-03-26 06:59:59":4043] A.09.00 b88
[SQL_GetSQLServerVersion] Version number smaller than 2000. Version: 0.0
cmd:"C:\Program Files\OmniBack\bin\sql_bar.exe" econfig -dbuser: -password: -appsrv:smdc76070.sub.domain.be -instance:SCSEC0 -port:1433 -inet \\.\pipe\586b86cd-39f5-4ff3-8885-1df262ccb81c
Function trace (currentLevel=2):
Level 2: SQL_GetSQLServerVersion()
Level 1: SQL7_CheckConfig()
Level 0: SQL_Config()

19/11/2015 11:29:17 OB2BAR_SQLBAR.6292.5592 ["/lib/cmn/win32nls.c $Rev: 39729 $ $Date:: 2013-10-28 13:34:00":275] A.09.00 b88
Bad catalog access for message #0 in set 9004

19/11/2015 11:29:17 OB2BAR_SQLBAR.6292.5592 ["/lib/cmn/win32nls.c $Rev: 39729 $ $Date:: 2013-10-28 13:34:00":287] A.09.00 b88
FormatMessage() failed with 1813, message #0 in set 9004

Running sql_bar.exe chkconf -instance:SCSEC0 gives:

PS C:\Program Files\OmniBack\bin> .\sql_bar.exe chkconf -instance:SCSEC0
[Critical] From: OB2BAR_SQLBAR@smdc76070.sub.domain.be "SCSEC0" Time: 19/11/2015 13:13:28
OB2BAR_SQLBAR: Bad catalog access for message #0 in set 9004

*RETVAL*8010

Does anyone know what is wrong?
Should I not have upgraded to CU8 because Data Protector is not compatible yet? Where can I find the support matrix of SQL Server for Data Protector 9?

Thank you for your help!

A StoreOnce hardware appliance has 3 possible store types: Catalyst, VTL (Virtual Tape Library) and NAS (Network Attached Storage).

The Data Protector device configured for a Catalyst store won’t allow any concurrency. When configuring a device for any of the 2 other types (LTO for VTL or file for NAS), the default concurrency will be used.

For reasons of deduplication efficiency, it is highly recommended to have no concurrency. However, in case of VTL or NAS, DP is not detecting that the target is deduplicating and default concurrency settings of 4 and 3 respectively will be used. As no concurrency is desired in this case, the concurrency for each device should be set to 1 manually in the DP configuration.

DPTIPS: Generating a new SSL certificate in DP 9

http://community.hpe.com/t5/Technical-Support-Services/DPTIPS-Generating-a-new-SSL-certificate-in-DP-9/ba-p/6811583

First of all, it is important to understand that the name of a slot of a Catalyst device in Data Protector is equal to the name of the corresponding item on the store. Typically it looks like this: 3ef5dcb2_5645d8f4_11d4_0001. Please note the difference with the “Medium ID” which is looking similar but which is using colons rather than underscores, e.g. 3ef5dcb2:5645d8f5:11d4:0002. Also note the numbers for the slot ID and the Medium ID are looking similar, but are typically slightly different.

Now, when a medium is missing in the IDB, but the related item is still available on the store, it is possible to import the medium (either through the GUI or CLI). However, a slot is needed first. In some situations, the (empty) slot may still be there. The first slot in this picture is an example:

This slot could be imported through GUI or CLI.

If the slot is, for whatever reason, not available then it needs to be created before the import can be executed. Use the following command for the slot creation:

omnimm -add_slots <DP device name> <SlotID>

“DP device name” is the StoreOnce device in DP or the library name. “SlotID” is the item name on the store. The following command can be used to list the items on the store:

omnib2dinfo -list_objects -b2ddevice <DP device name>

Hi All

I just wanted to clarify something and ask for your assistance.

Single Windows Cell Manager, with Tape library attached.

If I wanted to migrate out the tape library to a Linux server and make this an Installation server would I require an additional Unix Linux drive license? or would this work under the 1 drive license that comes with the starter pack?

So I just need to know if we need to buy a new license to perfor this change?

Many thanks.

Hi All 

Does anyone know if there is an official end of life / version document anywhere?

I'm just trying to get an idea as to when some of the legacy (6.1/6.11/7.00) DP installs become unsupported.

Thanks

HI All

Using DP v9.xx we are backing up a Windows 2012 R2 File server with Deduped data drives.

We are backup up this server with a typical DP filesystem backup, and also a Third party VM replication tool. The VM replication tool appears to back up significantly less changes each backup than the DP Filesystem backup.

We think this may be linked to the deduped data drives?

Are there any specific options we need to enable or be aware of to effciently backup the deduped data drives.

Many thanks

Hello,

I'm having a very hard time to get GRE running. I read the manual "Granular Recovery Extension User Guide for Microsoft SharePoint Server, Exchange and VMware", but from my point of view it's hard to follow the steps. And there is nothing in it at all about the configuration for vCenter Appliance (VCSA).

- DP 9.04 Windows Cell Manager VM with VMware Integration installed - Host A

- DP 9.04 Windows Media Agent (DL580G7, we need this for library/tape connection), with installed GRE Extension Host B

- VMware 6.0U1 VCSA vCenter - Host C

In the DP GUI I've checked the box "Advanced GRE Web Plug-in" on the VCSA Login page.  In the Web Client I already see a new "HP Data Protector" tab with some options. But it only displays "Loading" in the main window. My User in vCenter has full admin rights in DP. It also asks for a Cell Manger and chooses the right one by default. But after that I can not do anything.

I'm really confused about what I've to add to which client. Especially the firwall rules and the settings for encryped control communication (which we are using).

On each client with the VMware GRE agent installed, implement the following:
a.
Create a new file called config in the following path:Windows systems: Data_Protector_program_data\Config\Server\ and set encoding to UCS-2 Little Endian. UNIX systems: /etc/opt/omni/server and create an ordinary (ascii) file.
b.
For each vCenter Server system add an entry one after another in the config file. For example:<vcenter1.company.com>={ encryption={ exception=1; }; }; <vcenter2.company.com>={ encryption={ exception=1; }; };
Here <vcenter.company.com> is the host where the plug-in is installed, and uses the VMware GRE agent.

I've installed the GRE Agent (Extension?) on the Media Agent, there is no directoryData_Protector_program_data\Config\Server\ only Data_Protector_program_data\Config\Client

Can please someone post a step by step guide on how to setup VMware GRE with DP 9.04 and VMware VCSA?

Some of the general store meta data of a StoreOnce software store can be found in the following location:

<Store_Root>\StoreOncelibrary\dvol_0000000X\committed\storemgr\store.d\store_0X

Where X is the store ID.

One of the files seen there when the store is running is “s.dirty”. After stopping the store normally, the file is gone. If the store is not started and the s.dirty file is out there then something went wrong. The store was not stopped in a normal/clean way. Maybe the server crashed, there has been a power failure, the service/daemon was killed or something like that.

What’s important to understand now is that this s.dirty file has a function. It’s a flag which is checked during startup of the store and it will trigger additional checks during startup when the file is there. This is exactly why (startup) errors may be seen when the file is there and the errors may be gone when the s.dirty file has been deleted. However, it is absolutely a bad idea to delete the file! Removing the file to get rid of the errors means just ignoring the problems. Better is to start with the file in place, which will trigger the additional checks and recovery procedures. Note that several retries may be needed to rectify the situation. It’s not because the store is still not started after the first try that it will not work after a couple of retries. Just keep on trying until the store is started rather than trying to start it after deleting the file.

You may notice that your Internal database backups are increasing in the time they take to run or find that a particular operation such as a backup or restore is taking longer than it used to by a significant margin.

The issue may be tied to an issue within the Internal Database that is not being seen through the session reports or debug.log but may be reported in the PG_logs

check the pg_log directory

Win \ProgramData\OmniBack\server\db80\pg\pg_log\

Unix: /var/opt/omni/server/db80/pg/pg_log

(not to be confused with the PG_xlog!)

Here you’ll see logs generated to common IO operations. The level to which these logs are generated are located in the PostGresql.conf file but we discourage changing this unless directed by support due to the

Potential log growth with detrimental results that may occur.

In a healthy database the PG_logs (one of which is created at the start/stop of PostGres database) will contain very little information and at a glance would be only a few KB’s large.

Ex:

2015-10-06 08:42:24 EDT LOG: database system was shut down at 2015-10-06 08:32:47 EDT

2015-10-06 08:42:24 EDT LOG: database system is ready to accept connections

2015-10-06 08:42:24 EDT LOG: autovacuum launcher started

2015-10-06 08:42:24 EDT FATAL: the database system is starting up

HOWEVER, under conditions where there may be some database inconsistencies or other irregularity the PG_log may get very large and this would be indicative of a problem in the database that would need support intervention.

In general these types of inconsistencies are known to support and a script can be delivered to fix the issue. Some other issues that cause excessive log growth have been addressed in latest patches.

So, to recap. Small PG_logs are ok but large PG_logs may be indicative of an issue needing investigation. Open a case and support will provide further assistance.

When attempting to produce a remote copy of a backed up object from one site's local B2D store to another at a different site, Data Protector 9.03 is not allowing the device option "Use replication" to be checked.  It throws up an error box saying the destination device does not support replication.

Is there some component I'm missing here?  The originating site has a StoreOnce software store that is working correctly and the destination also has a StoreOnce software store but object copies always rehydrate and spend way too long.

Hello Expert,

I have genrated DP Sessions report from DP GUI Reporting options.

I  first run this report on 30th October 2015 and it listed and give me the session report for the time period April-MAy 2015.

When I run the same reporting today again between same time period (Apr-May 2015)  it don't show many sessions what it was showing last time.

NO chnages in IDB. Can anyone help me how its possible and how to find if any changes in IDB is done or what this the cause for this.

Appreciate any support.

Regards,

Hello,

i have (accidentley) migrated a DP 6.11 system to version 9.0 without migrating it to version 7.0 first.

now i have the DP 9 with all the jobs, but no media pools and no prvious sessions db.

my 6.11 db was backed  up prior to the upgrade, so the question is:

 Is it possible to import the DB of DP 6.11 into the DP 9.0 ? , if so, then how to do it?

thank you in advance.

# service tomcat status
Tomcat service (pid 3236) is running...

# service tomcat stop
Stopping tomcat service...                           [  OK  ]

# service tomcat status
Tomcat service is stopped

# service tomcat start
Starting tomcat service...                           [  OK  ]

# service tomcat status
Tomcat service (pid 3319) is running...


A more verbose way:

# /opt/apache-tomcat/bin/shutdown.sh
Using CATALINA_BASE:   /opt/apache-tomcat
Using CATALINA_HOME:   /opt/apache-tomcat
Using CATALINA_TMPDIR: /opt/apache-tomcat/temp
Using JRE_HOME:        /usr
Using CLASSPATH:       /opt/apache-tomcat/bin/bootstrap.jar:/opt/apache-tomcat/bin/tomcat-juli.jar

# /opt/apache-tomcat/bin/startup.sh
Using CATALINA_BASE:   /opt/apache-tomcat
Using CATALINA_HOME:   /opt/apache-tomcat
Using CATALINA_TMPDIR: /opt/apache-tomcat/temp
Using JRE_HOME:        /usr
Using CLASSPATH:       /opt/apache-tomcat/bin/bootstrap.jar:/opt/apache-tomcat/bin/tomcat-juli.jar
Tomcat started.

DPTIPS: Critical Update for DP 9 .04 Users

http://community.hpe.com/t5/Technical-Support-Services/DPTIPS-Critical-Update-for-DP-9-04-Users/ba-p/6813680

Hi Folks,

We installed the version of DP9 in our company.
I am setting up new backup jobs and everything is ok.

The problem is in my SAP ARCHIVE LOG backup, when I don't have redolog files, the backup starts and got the following message :
BR0013W In offline redolog files found for processing .

After this message from BRBACKUP, Data Protector generates my backup as failed.

"None of the Disk Agents completed successfully .
Session has failed."

With I have redolog for backup, the session starts and finish with sucesses.

In the previous version of the DP (7.0), the backup was completed successfully even when redolog files are empty.

How my backup status completed with successfully even when I do not have redolog files ?

Thank You.