Thanks Andre
Regards
Jose
Regards
Jose
↧
Re: Upgrade DP 8
↧
Re: Upgrade DP 8
Thanks Bob.
Data Protector is in a hpux 11.31 MC/SG cluster. So I have to upgrade each of the nodes, then import the virtual server, correct ? The package must be down ?
What version of DP 8 should I install ? 8, 8.1 ...
What are the issues when upgrading DP 7 to DP 8 ?
Best Regards
Jose
↧
↧
Re: Upgrade DP 8
Data Protector is in a hpux 11.31 MC/SG cluster. So I have to upgrade each of the nodes, then import the virtual server, correct ? The package must be down ?
Yes
=================
What version of DP 8 should I install ?
I highly recommend against installing DP 8.1, and recomend 8.0 only if you immediately install patch bundle 8.01
==================
What are the issues when upgrading DP 7 to DP 8 ?
Therer were lots of issues with the IDB found during the upgrade. These have mostly been fixed with the 8.01 patch, but, I don't think that they are totally fixed yet
↧
Re: Upgrade DP 8
Thank you very much for your help.
I will proceed with this post soon.
Regards
Jose
I will proceed with this post soon.
Regards
Jose
↧
Migrate DB and configuration, DP6 to DP7
Good morning,
My name is Raul, I´m new to the forum and I have a doubt with importing a database.
I have currently running a DP 6.0 and I have to install a new DP 7.0 on a new HP-UX cluster, the problem is i don´t know if I can migrate the database and settings of dp6 to dp7. Is that possible?
How could I?
Thanks
↧
↧
Re: Migrate DB and configuration, DP6 to DP7
Per the Installation and Licensing GUide for DP 7
Chapter 4
There is no direct upgrade path from DP 6.0. On your original cell manager, you would have to stop DP, and make a copy of
/etc/opt/omni/server Configuration Files
You would have to install DP 7 on your new server, then, you should be able to just put this directory back into place
The IDB is more problematical. I would recommend that you do a 'writedb/readdb' prior to the Upgrade to compress the IDB, then back it up to Tape. Upgrade to DP 7, install the patch bundles, Import the tape, and restore the IDB
However, your version of DP is so old, I can't guarantee that this method will work. Perhaps doing a 'readdb' after moving over to the new DP would also work.
↧
Re: OV Omniback/Data Protector
Hi,
any firewall between?
Best regards
Daniel
↧
Re: OV Omniback/Data Protector
Hi,
Environment is:
DP 7.03
DB2 9.5 Integration on MS Cluster, Windows 2008 R2
DP agent installed in cluster aware mode.
Backup job for Archived Log is configured for virtual server.
DB2 archive, according to db2diag.log are successfully archived, but in:
c:\ProgramData\OmniBack\log\debug.log on node where is db, is logged:
21.3.2014 13:49:34 OB2BAR_DB2ARCH.1488.16924 ["/integ/db2/db2arch/main.c $Rev: 38587 $ $Date:: 2013-08-15 13:44:31":470] A.07.00 b105
[main] BU_GetConfig(backupserver.domain, node.domain, DB2, DB2, config) failed with error [8] CS API has already been initialized.
and there is no started Archived_log Backup job in Data Protector.
If we install DP in non cluster aware mode, Archived_logs are backup successfully
Thanks & Regards,
Tom
↧
Re: 65:99 Import failed with possible cause: thsi media already has valid copy in DB
Hello All,
Any help on this issue of importing media for my NDMP backup. Case logged with HP software support for almost 2 weeks without any resolution. Just checking the community if any one can help me on this.
Please let me know if needed any logs.
Appreciate any helps in advance.
Best Regards,
↧
↧
Re: OV Omniback/Data Protector
Hi,
so, it sounds, it is not supported or it is a bug when using the cluster mode.
I recommend to open a case to get this verified.
Best regards
Daniel
↧
Re: OV Omniback/Data Protector
Hi,
Yes, looks like.
But, maybe,.. some user somewhere,..?
Regards,
Tom
↧
DP 6.21 Disaster Recovery Cell Manager unable to add clients from production environment
I am required to retrospectively restore a Windows 2008 Server that is backed up currently backed in a DP 6.21 cell in a production active directory domain. The restored servers are to be separate from the production servers in a standalone setting due to an Exchange 2007 recovery of year old database. If this doesn't work no sweat will recover to existing Exchange Server recovery set. Would be good though to have this in case need to do DR in future.
The backups I take include the autodr agent and options to copy full dr to disk is included. The srd files all exist as well.
I have created a new cell manager with 6.21 installed and close to live environment except is in a workgroup. I have copied the IDB from the live setup by doing a omnidbutil process as below:
1. Stop DP services on production & DR DP.
2. Copy datafiles, msg, meta, dcbf from db40 and write on DR DP at same location.
3. Start DP Services
4. run omnidbutil -change_cell_name
All good so far and I can see the original clients in the restore tab and all the tapes and events etc in the recovery cell manager. I have added the tape drive in the cell manager and have so far successfully been able to restore data from tape to the cell manager as a test.
I cannot see the clients though under clients tab nor under the restore > restore tasks > disaster recovery.
What do I need to do to see these clients? I cannot add the clients over the network due to this being a standolone recovery environment.
↧
Re: DP 6.21 Disaster Recovery Cell Manager unable to add clients from production environment
Hi,
I understand that you want to separate your tests from production, however, I think it's not necessary. Create a ISO image for the box you want to recover in your productive environment. You can use VM or physical machine as target. Start the ISO in the target. If network connection cannot be established, manually assign an IP using netsh. Make sure you do not apply the original network configuration used for the restore (setting in DR GUI wizard). After the restore has been done, make sure you "disconnect" network for the virtual or physical machine, reboot and assign different IP once the system is up. Now, rename the machine, import it into DP and restore the Exchange database.
Keep in mind, this info is very shorten, you need more steps, but keep this as idea how to proceed.
Best regards
Daniel
↧
↧
Re: OV Omniback/Data Protector
Hi,
something from another forum, and related to TSM backup:
-----------
backup db2 on ms cluster (active/active) hello,
if you want to backup db2 on microsoft cluster, you have to
work with "proxynode" and "proxyagent" relationship
grant proxynode target=proxytarget agent=clusternodeA
grant proxynode target=proxytarget agent=clusternodeB
every db2 database which can failover to another clusternode has to be
updated like
db2 update db cfg for sample using vendoropt "'-asnodename=proxytarget'"
db2 update db cfg for sample using LOGARCHMETH1 TSM:DB2 logarchopt1 "’-
asnodename=proxytarget’"
clusternodeA = DSMI_CONFIG on node A
ClusternodeB = DSMI_CONFIG ion node B
you can read more on SC12-4282-02
------------
maybe something similar has to be done related to Data Protector?
Regards,
Tom
↧
Re: Como Migrar Data Protector 6.20 en un servidor w2k3 x32 a un servidor con w2k8 x64
De Momento Llevo ESTOS Pasos
Procedimiento de migración de
realizar la migración de la siguiente manera:
1. Instale un cliente de Data Protector en el sistema Windows de 64 bits o de 64 bits
del sistema de Windows Server 2008 que se convertirá en su nuevo Gerente de la célula. Para
obtener más información, consulte "Instalación de clientes de Windows" en la página 90.
2. Importe el sistema celular del viejo celular del gerente.
3. En el viejo Cell Manager, agregue el nombre de host del nuevo Gerente de la célula a la
lista de hosts de confianza en los clientes asegurados. Desde el directorio
Data_Protector_home \ bin, ejecute:
perl-winomnimigrate.pl prepare_clients New_CM_Name
New_CM_Name es el nombre del cliente de la nueva Gerente Móvil desde el anterior
paso. Para más detalles sobre winomnimigrate.pl, consulte el Data Protector HP Command
Line Interface Reference.
Para obtener más información acerca de hosts de confianza y asegurar clientes de Data Protector,
consulte "Protección de los clientes" en la página 221 y "confía host" en la página 234.
4. Copia de seguridad del BID. Asegúrese de que el medio utilizado más adelante se puede acceder en el
nuevo sistema Cell Manager. Ver el índice de la Ayuda en línea: "copia de seguridad del BID".
5. Restaurar el BID en una ubicación temporal en el nuevo Director de la célula. Dependiendo
de la opción que elija para la copia de seguridad del BID, es posible que tenga que configurar la
dispositivo e importar el catálogo de los medios apropiados. Una vez que la copia de seguridad del BID
objeto está en el BID, puede restaurar el BID con el fin de mover las configuración de
datos al nuevo sistema. Ver el índice de la Ayuda en línea: "BID restaurar".
6. Desinstale el cliente de Data Protector del nuevo Gerente de la célula. Consulte "Desinstalación
de un cliente de Data Protector "en la página 238.
7. Instalar Data Protector Cell Manager en el nuevo Director de la célula. Consulte "Instalación
del Administrador de Data Protector celular (CM) y el servidor (s) instalación (IS) "en la página 44.
HE Instalado EL DP EN UNA UBICACION SIMILAR MANAGER CELULAR A LA QUE TENIA EL ANTIGUO
ANTIGUO DIRECTOR CELL (D: \ Omniback)
NUEVO GERENTE DE CELULAR (D: \ Omniback)
8. Si ha cambiado el puerto predeterminado de Data Protector Inet en el antiguo Director de celda, configure
el mismo puerto Inet en el nuevo Director de la célula. Consulte "Cambio de la Data Protector
número de puerto por defecto "en la página 382.
A partir del 9 me pierdo
9. Mover el BID restaurada (que reside en una ubicación temporal en el nuevo celular
Manager) y los datos de configuración en la misma ubicación en el nuevo Director de la célula
ya que estaba en el antiguo Director de la célula. No reinicie los servicios de Data Protector.
Ver el índice de la Ayuda en línea: "BID restaurar".
Restauro las Carpetas del BID del antiguo gerente dell En Una Carpeta porción EJEMPLO "d: \ copiaidb"
Lo cellmanager El nuevo él Instalado en "d: \ Omniback"
Me dados, Mueve el BID (config, registro DB40 y) a la ruta del nuevo gerente de la célula. ¿ESTO significa Que Debo replace AEE Carpetas en el gestor de celular nuevo?. Sin Detener los Servicios de Data Protector en el Servidor nuevo gerente celular x64 estafa W2K8 él MOVIDO Las Carpetas. Ahora CUANDO Intento Para entrar en restauración bid me da des Problema de Comunicación.
Era Buff, me comentaron Que sencillo pero sí me complica porción recuerditos.
Gracias a quien pueda aconsejarme algoritmo.
Un saludo,
Federico.
↧
online backup error
the error for the oracle
RMAN-03009: failure of backup command on dev_0 channel at 03/25/2014 10:08:00
ORA-19506: failed to create sequential file, name="mdaonline<mda_368:843127677:1>.dbf", parms=""
ORA-27028: skgfqcre: sbtbackup returned error
ORA-19511: Error received from media manager layer, error text:
Vendor specific error: OB2_StartObjectBackup() failed ERR(-17)
also check the attach file
Thanks in Advance
↧
Re: DP 6.21 Disaster Recovery Cell Manager unable to add clients from production environment
Thanks Daniel for your quick reply.
I realised where I made a mistake and now can see the clients so that part is all good. I just have to fiddle with the recovery, still persisting with the separate env for now.
I am going the track of copying a virtual domain controller in so that takes care of the domain accounts and domain etc.
Now to create the automated recovery.iso. I didn't have WAIK installed on the live environment so that will be happening at first chance now!
Will update on progress. Thanks
↧
↧
Re: OV Omniback/Data Protector
And for Informix, documentation says:
Integrating Informix Server and Data Protector
Configuring the Integration
6 Chapter 1
If you intend to use the Data Protector CLI, set the Data Protector
environment variable OB2BARHOSTNAME to the virtual server name as
follows:
Windows: set OB2BARHOSTNAME=<virtual_server_name>
UNIX: export OB2BARHOSTNAME=<virtual_server_name>
but for DB2 Integration, only:
In Client, select the DB2 Server system. In a cluster environment,
select the virtual server.
Regards,
Tom
↧
HP DP 8.0 on Enterprise Linux 5.9
Hi Folks ,
We are planning to install HP DP 8.0 on OEL 5.9 .
According to 8.0 support matix , OEL 5.9 is not compatible with HP DP 8.0 , but RHEL 5.9 is supported.
As per my knowledege RHEL+ oracle logos & oracle packages = OEL.
I am sure it will work also on 5.9 but HP support guys are saying its not supported.
Pls eloborate to overcome this issue.
***** WE CANT CHANGE OS due to some dependency*****
↧
Data Protector 6.10 backups interfering with Microsoft SQL Full and Differential backups
Hello --
We are running release 6.10 on an HP-UX cell manager. A typical backup involves going to a D2D, image, or VLS, incremental, library. After the initial backup is complete, a copy to LTO tape is subsequently done.
One of the client systems is a Microsoft Windows 2012 Standard x86_64 server that is running Microsoft SQL 2008R2 on it. The Full and Incremental backups that are done for the server includes the /CONFIGURATION and operating system, C:\, drive. Among the files that are included in these backups are the log files for the database server. These are not the .trn files that are affiliated with the database, rather these are the ones associated with the SQL Server application.
The database server does native Full, Differential, and Transaction log backups to another local drive. Weekly snapshots of the drive are done to two LeftHand systems, and are not included in the Data Protector backups.
I have been getting reports the database Differential backups periodically fail. I looked further into the issue, and according to colleagues that I have spoken to, it appears that Data Protector is using VSS handles. When I rescheduled the Data Protector full backup on a different night than the SQL Server Full backups, the SQL Differential backups completed successfully.
My questions are the following:
1. Am I correct in saying that Data Protector uses VSS handles during its backups?
2. If the above is true, what step(s) can I take to have Data Protector be able to do its backups without interfering with
the SQL Server jobs?
Thanks.
↧