Pular para o conteúdo principal

Redirecionar Restore do Oracle no Netbackup

Vamos supor que você precise fazer um restore do seu banco Oracle que está no servidor "SRV1" mas não quer fazer no mesmo servidor de origem. Você tenta fazer um alternate client restore com todos os passos que manda o figurino e acaba recebendo uma mensagem parecida com esta.

Backup file not found in NetBackup catalog INF - Recovery Manager complete

O que está acontecendo é que, por default, o Netbackup não permite que se façam restores de bases de dados em clientes alternativos, ou seja, a base copiada do cliente SRV1 somente deverá ser restaurada no cliente SRV1.

O RMAN mostrará um log bastante parecido com este:

channel d1: starting datafile backupset restore
channel d1: specifying datafile(s) to restore from backup set
restoring datafile 00001 to /data1/oracle/oradata/CCRF/system01.dbf
restoring datafile 00002 to /data1/oracle/oradata/CCRF/undotbs01.dbf
restoring datafile 00003 to /data1/oracle/oradata/CCRF/indx01.dbf
restoring datafile 00004 to /data1/oracle/oradata/CCRF/tools01.dbf
restoring datafile 00005 to /data4/oracle/oradata/CCRF/perfstat01.dbf
restoring datafile 00006 to /data1/oracle/oradata/CCRF/DATA.dbf
restoring datafile 00007 to /data1/oracle/oradata/CCRF/NDX.dbf
released channel: d1
RMAN-00571: ==============================================
RMAN-00569: ========= ERROR MESSAGE STACK FOLLOWS ============
RMAN-00571: ==============================================
RMAN-03002: failure of restore command at 01/21/2007 01:10:20
ORA-19507: failed to retrieve sequential file, handle="bk_u3ij106l3_s114_p1_t638589603-CCRF", parms=""
ORA-27029: skgfrtrv: sbtrestore returned error
ORA-19511: Error received from media manager layer, error text:
Failed to process backup file

No log do Bprd você verá que o Netbackup estará apresentando um erro dizendo que não existe um arquivo liberando o restore alternado.

<2> db_valid_client: no alternate names to check in /usr/openv/netbackup/db/altnames - No such file or directory (2)


Para resolver este problema simplesmente crie um arquivo chamado No.Restrictions (Case sensitive) dentro da pasta /usr/openv/netbackup/db/altnames/ .
O comando que pode ser utilizado para facilmente criar este arquivo é o touch

touch /usr/openv/netbackup/db/altnames/No.Restrictions

Caso você esteja utilizando o Netbackup for Windows altere o nome do caminho para o Path de instalação do Netbackup correspondente ao Windows.

c:\Program Files\Veritas\Netbackup\db\altnames\No.Restrictions


Agradeço a contribuição deste post ao colega Felipe e ao suporte da Symantec que nos disponibilizou esta informação detalhada.

Comentários

Anônimo disse…
Pô Brother, esse Felipe manja muuuito. ;-)

Abraços

Felipe

Postagens mais visitadas deste blog

Netbackup Status Code

Veritas Status Codes and Messages Retirado de http://www.mwalters.com/CLIC/Configs/Veritas_Status_Codes.htm Status Codes Status Code: 0 Message: the requested operation was successfully completed Explanation: There were no problems detected with the requested operation. Recommended Action: None, unless this was a database backup performed through a database extension product (for example, NetBackup for Oracle or NetBackup for SQL Server). In those instances, code 0 means the backup script that started the backup ran without error. However, you must check other status as explained in the related NetBackup manual to see if the database was successfully backed up. Status Code: 1 Message: the requested operation was partially successful Explanation: A problem that may require corrective action was detected during the requested operation. Recommended Action: Check the All Log Entries report and also the progress log (if there is one). Some of the problems that can show up under Status Code ...