will this fix be included in 9.09?
also is 9.09 out today??
will this fix be included in 9.09?
also is 9.09 out today??
This is a limitation for Windows OS.
From Installation Guide: Installing Windows Clients:
Limitations
Due to the security restrictions imposed by the Windows operating system, Installation Server can be used to remotely install clients only in the same domain.
So both IS and client have to be in the same domain.
What you should do is to install the client locally and Import it.
If you have many clients in the external domain you may want to install IS role on one of the clients and to import it as second Win IS and to add the rest of the clients using this IS.
Regards
And looking at the error messages you have provided wrong credentials so this is something different.
Hi All,
Backups which triggered by the below is failing remaining all are running fine.
kindly help me how to fix the issue.
[Normal] From: BSM@clesap01.imgworld.org "GRC-Online2" Time: 3/31/2017 8:51:07 AM
Backup session 2017/03/31-22 started.
[Normal] From: BSM@clesap01.imgworld.org "GRC-Online2" Time: 3/31/2017 8:51:08 AM
OB2BAR application on "clegrcdev1.imgworld.org" successfully started.
[Warning] From: INET_thread_omnisap.exe@clegrcdev1.imgworld.org "clegrcdev1.imgworld.org" Time: 3/31/2017 8:51:17 AM
No data for user drcadm@SAP_DRC_LocalAdmin in Inet's impersonation configuration.
BR0051I BRBACKUP 7.00 (32)
BR0055I Start of database backup: bevmrpbr.anf 2017-03-31 08.51.27
BR0484I BRBACKUP log file: D:\oracle\DRC\sapbackup\bevmrpbr.anf
BR0477I Oracle pfile D:\oracle\DRC\102\database\initDRC.ora created from spfile D:\oracle\DRC\102\database\spfileDRC.ora
BR0280I BRBACKUP time stamp: 2017-03-31 08.51.29
BR0319I Control file copy created: D:\oracle\DRC\sapbackup\CNTRLDRC.DBF 32325632
BR0280I BRBACKUP time stamp: 2017-03-31 08.51.29
BR0057I Backup of database: DRC
BR0058I BRBACKUP action ID: bevmrpbr
BR0059I BRBACKUP function ID: anf
BR0110I Backup mode: ALL
BR0077I Database file for backup: D:\oracle\DRC\sapbackup\CNTRLDRC.DBF
BR0061I 22 files found for backup, total size 176250.992 MB
BR0143I Backup type: online
BR0130I Backup device type: util_file
BR0109I Files will be saved by backup utility
BR0126I Unattended mode active - no operator confirmation required
BR0280I BRBACKUP time stamp: 2017-03-31 08.51.29
BR0315I 'Alter database begin backup' successful
BR0280I BRBACKUP time stamp: 2017-03-31 08.51.29
BR0229I Calling backup utility with function 'backup'...
BR0278I Command output of 'D:\usr\sap\DRC\SYS\exe\uc\NTAMD64\backint.exe -u DRC -f backup -i D:\oracle\DRC\sapbackup\.bevmrpbr.lst -t file -c':
[Normal] From: OB2BAR_BACKINT@clegrcdev1.imgworld.org "DRC" Time: 3/31/2017 8:51:39 AM
Backint is started with the following parameters:
D:\usr\sap\DRC\SYS\exe\uc\NTAMD64\backint.exe -u DRC -f backup -i D:\oracle\DRC\sapbackup\.bevmrpbr.lst -t file -c.
[Normal] From: BMA@clesap01.imgworld.org "HP:Ultrium 3-SCSI_2_clesap01" Time: 3/31/2017 8:52:18 AM
STARTING Media Agent "HP:Ultrium 3-SCSI_2_clesap01"
[Normal] From: BMA@clesap01.imgworld.org "HP:Ultrium 3-SCSI_2_clesap01" Time: 3/31/2017 8:52:18 AM
Detected a replaced drive at "2";
previous serial number: "", new "HU10716AF4".
[Normal] From: BMA@clesap01.imgworld.org "HP:Ultrium 3-SCSI_2_clesap01" Time: 3/31/2017 8:52:18 AM
By: UMA@clesap01.imgworld.org@/dev/rchgr/autoch2
Loading medium from slot 53 to device /dev/rtape/tape10_BESTn
[Warning] From: BMA@clesap01.imgworld.org "HP:Ultrium 3-SCSI_2_clesap01" Time: 3/31/2017 9:00:16 AM
The device "HP:Ultrium 3-SCSI_2_clesap01" could not be opened("Device could not be accessed")
[Normal] From: BMA@clesap01.imgworld.org "HP:Ultrium 3-SCSI_2_clesap01" Time: 3/31/2017 9:00:16 AM
Starting the device path discovery process.
[Normal] From: BMA@clesap01.imgworld.org "HP:Ultrium 3-SCSI_2_clesap01" Time: 3/31/2017 9:00:24 AM
A new path(s) "/dev/rtape/tape10_BESTn" found for device "HP:Ultrium 3-SCSI_2_clesap01" and stored.
[Normal] From: BMA@clesap01.imgworld.org "HP:Ultrium 3-SCSI_2_clesap01" Time: 3/31/2017 9:00:24 AM
Device path discovery process finished.
[Major] From: BMA@clesap01.imgworld.org "HP:Ultrium 3-SCSI_2_clesap01" Time: 3/31/2017 9:07:14 AM
[90:54] /dev/rtape/tape10_BESTn
Cannot open device ([6] No such device or address)
[Normal] From: BMA@clesap01.imgworld.org "HP:Ultrium 3-SCSI_2_clesap01" Time: 3/31/2017 9:07:14 AM
By: UMA@clesap01.imgworld.org@/dev/rchgr/autoch2
Unloading medium to slot 53 from device /dev/rtape/tape10_BESTn
[Normal] From: BMA@clesap01.imgworld.org "HP:Ultrium 3-SCSI_2_clesap01" Time: 3/31/2017 9:07:34 AM
ABORTED Media Agent "HP:Ultrium 3-SCSI_2_clesap01"
in our enviranment we have 4 drives wnen backup is triggered by using drive 2 those backups are failing with below error
kindly help me to salve the issue
installing Data Protector on a Linux Server the following error may be reported
Following steps should correct issue:
List locales available on system
# localectl list-locales | grep en_US
en_US
en_US.iso88591
en_US.iso885915
en_US.utf8
Select and set proper UTF8 locale
# localectl set-locale LANG=en_US.utf8
Alternatively you could use the following manual steps:
Run DP CM installation from DP 9.00 MR depot with applied SSPLNX900_005
After initdb failed in script "/opt/omni/sbin/IDBsetup.sh" replace line 560:
su - ${PGOSUSER} -c "LD_LIBRARY_PATH=${PGHOME}/lib:$LD_LIBRARY_PATH ${PGHOME}/bin/initdb -E utf8 -A md5 --pwfile ${TOMNI}/pgpass.$$ -D ${PGDATA_PG} -U ${PGSUPERUSER}" 1>&2
with:
su - ${PGOSUSER} -c "LD_LIBRARY_PATH=${PGHOME}/lib:$LD_LIBRARY_PATH ${PGHOME}/bin/initdb -E utf8 --locale=C -A md5 --pwfile ${TOMNI}/pgpass.$$ -D ${PGDATA_PG} -U ${PGSUPERUSER}" 1>&2
and run script "/opt/omni/sbin/IDBsetup.sh"
Update "/etc/opt/omni/client/omni_info" with cs component:
# /opt/omni/bin/omnicc -put_component_str cs client/omni_format client/omni_info A.09.00
Re-import the Cell Manager host and Installation Server to the cell:
# omnicc -import_host <cm_hostname>
# omnicc -import_is <cm_hostname>
Hi KloppYNWA69,
The 9.09 patch bundle is available now, but according to the release notes QCCR2A73053 is not included. I cross my fingers for A.09.09_115.
Please use the Accept Solution button next to my post and assign a KUDO (thumbs up icon) if this works for you.
Regards,
Sebastian Koehler
There are 2 methods for restoring the internal database.
What is the difference between the two and which is best for restore?
Online
in a disaster recovery scenario the Online restore would require the reinstallation of the Data Protector Cell Manager software and a reimport of the latest Internal Database backup. This would require locating the media through the Media.log or Obrindex.dat file*, importing the media and running the restore and recovery through the GUI in the restore context.
Offline
Same DR scenario, this does require reinstalling the DP Software and then locating the original Obrindex.dat file*, copying it to the new install location and running a few commands to export the variables to a text file and then to read them in exceuting the restore and recovery.
Which is best?
There a few considerations. With the online you can pick and choose files for restore, choose an alternative location for restore - say if you wanted to find a single file for restore or some Config data. on a full IDB restore the downside is that the IDB will need to be restored to an alternative location, for example C:\ProgramData\Omniback\Server\db80_new\. this is because the process takes place with the services up and running. With the Offline restore the process will restore the IDB back to the original location. While there is no functional downside to the new location in regards to the online restore it does leave the installation in a changed state.
Conclusion. The choice is yours. There are good points ot both but i would recommend testing eacjh of these so that when the time comes and you need to recover the Database or installation as quickly as possible you are familar with the necessary steps.
* OBrindex.dat and Media.log. with either method its important that you have a copy of the Obrindex.dat file or the Media.log. I would recommend making sure you have a backup plan on securing these files to a safe location.
Search the blogs for "Obrindex.dat" there is another article covering this file, how to secure a backup copy and how to recover the IDB with it using the CLI.
> [Normal] From: BMA@clesap01.imgworld.org "HP:Ultrium 3-SCSI_2_clesap01" Time: 3/31/2017 8:52:18 AM
> Detected a replaced drive at "2";
> previous serial number: "", new "HU10716AF4".
Did you replace a tape drive recently? I don't know this software but the backup environment that I use, utilizes a table of the tape drives with the device files and their serial numbers. If a tape drive is replaced, you have to update the device file and/or the serial number.
Also the errors here indicate that there was a change in the tape device files.
> [Normal] From: BMA@clesap01.imgworld.org "HP:Ultrium 3-SCSI_2_clesap01" Time: 3/31/2017 9:00:24 AM
> A new path(s) "/dev/rtape/tape10_BESTn" found for device "HP:Ultrium 3-SCSI_2_clesap01" and stored.
> [Normal] From: BMA@clesap01.imgworld.org "HP:Ultrium 3-SCSI_2_clesap01" Time: 3/31/2017 9:00:24 AM
> Device path discovery process finished.
> [Major] From: BMA@clesap01.imgworld.org "HP:Ultrium 3-SCSI_2_clesap01" Time: 3/31/2017 9:07:14 AM
> [90:54] /dev/rtape/tape10_BESTn
> Cannot open device ([6] No such device or address)
First check the tape drive device files in the OS (it looks like HP-UX) and then check the configuration area for the tape drives in your backup environment.
I think you use the commvault backup system. Look at this URL http://documentation.commvault.com/commvault/v10/article?p=features/hardware_specific_issues/hardware_changes.htm#Replace_a_Drive_with_the_Same_Drive_Type
and scroll down to the section "Replace a Drive with the Same Drive Type". You need to update the serial number for the replaced tape drive.
I need help with a problem that I can not solve, I'm having errors in virtual disks, is there any way to solve them? attached image I have searched for some type of solution but I can not find anything, I can indicate a solution to this problem
Thanks it works for me
Hello, hopefully this is an easy question for someone to answer.
We are running DP 9.05 and we have a backup specification for an Exchange DAG with three databases selected for backup. However, it seems that DP is skipping one of the selected databases during the job and makes no mention of errors or such. It's as if it doesn't exist.
I'm not really sure where to start in troubleshooting this and would greatly appreciate any guidance any of you may have. Thanks.
-Sean
> how can i just remove this aborted session & 6thbackup
Hi all,
We use HP DP 9.07 (RedHat 6.8). The last week scheduled copy job failed wit error
[Critical] From: CSM@srv0050 "copy_job" Time: 04/03/2017 08:00:02 AM
Internal error: DbaXXXX functions.
If I run the job directly, it completes without error.
I checked internal dB - it's OK.
Do you have any idea what is wrong?
Thanks a lot
Oracle backup failure post upgrading to DP 9.08_113
Backup fails with below error. any suggestion to fix this issue. it is urgent.
[Major] From: OB2BAR_SBT_CHANNEL@vfilvhycagldb1.xxxx.com "HYCPRD" Time: 4/2/2017 4:34:19 PM
Cannot start DBSM (Time out occurred.)
[Major] From: OB2BAR_SBT_CHANNEL@vfilvhycagldb1.xxxx.com "HYCPRD" Time: 4/2/2017 4:36:19 PM
Cannot start DBSM (Time out occurred.)
RMAN-03009: failure of backup command on dev_2 channel at 04/02/2017 16:36:23
ORA-19509: failed to delete sequential file, handle="HYCPRD-DD<HYCPRD_23867:940264248:1:2>.df", parms="SBT_LIBRARY=/opt/omni/lib/libob2oracle8_64bit.so,ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=HYCPRD,OB2BARLIST=HYCPRD-DD)"
ORA-27027: sbtremove2 returned error
ORA-19511: Error received from media manager layer, error text:
Vendor specific error: OB2_StartQueries() failed ERR(0)
ORA-19513: failed to identify sequential file
RMAN-12018: channel dev_2 disabled, job failed on it will be run on another channel
RMAN-08044: channel dev_1: finished piece 1 at 02-APR-17
RMAN-08530: piece handle=HYCPRD-DD<HYCPRD_23866:940264248:1:3>.df tag=TAG20170402T163045 comment=API Version 2.0,MMS Version 65.9.0.113
RMAN-08540: channel dev_1: backup set complete, elapsed time: 00:06:30
RMAN-08048: channel dev_1: starting incremental level 0 datafile backup set
RMAN-08010: channel dev_1: specifying datafile(s) in backup set
RMAN-08522: input datafile file number=00002 name=/u01/oradata/HYCPRD/sysaux01.dbf
RMAN-08038: channel dev_1: starting piece 1 at 02-APR-17
Hello Expert,
CM= Windows 2012 R2, DP=9.08.113 build
clinet= WIndows 2008 R2, DP=9.08_113 build, Exchnage 2010
Trying to restore single mail uisng GRE but getting error as soon I select Database and click next it gives error as An error occurred while retrieving the backup versions available for restore.
Able to restore sucessfully from mbx1 but not from mbx2. Host is added in the userlist with SYSTEM NT AUTHORITY host fqdn.
Debug.log
017-04-03 12:28:24,198 - 5420 - (:0)
Begin : GetAllBackupVersionsForDatabaseImport
2017-04-03 12:28:47,774 - 8592 - (:0)
Begin : Ping
2017-04-03 12:28:48,008 - 8592 - (:0)
End : Ping
2017-04-03 12:29:44,647 - 5420 - ("trunk/ExchangeGre/src/WebSite/EchangeWCFClient/ExchangeWSAdapter.cs $Rev: 1444 $ $Date:: 2015-10-20 07:40:53":0) 09.00.20088
GetAllBackupVersionsForDatabaseImport Failed . ErrorDetail =
2017-04-03 12:29:44,647 - 5420 - (:0)
End : GetAllBackupVersionsForDatabaseImport
2017-04-03 12:29:44,647 - 5420 - ("trunk/ExchangeGre/src/GUI/MmcGui/src/Wizards/ImportWizard/UserControls/ImportBackupWizard_BackupVersionSelectScreen.cs $Rev: 1444 $ $Date:: 2015-10-20 07:40:53":0) 09.00.20088
Error getting backup versions for mailbox/database = 4GB-A, GreReturnCode = GRE_OBJECTSNOTFOUND,
m_errorDetail = No detail
might be worth trying to reconfigure the GRE component on the mailbox host it fails on.
Maybe go into IIS and make sure it all looks ok, then make sure .NET is version 4. Compare all this with the other host.
Does it fail with all databases?
Already tried reinstalling mbx2 client but still GRE fails.
IIS looks fine and similar on both servers. .NET version is there.
Yes it fails for all database with same error.
Hi,
Few more details like DP version, patch details OS details will help to understand the issue better.
Does this backup ever work or it's a new specification?