Sie sind auf Seite 1von 4

Symantec TechNote 303966

Configuration issue with NetBackup RealTime Protection 4.5 and alternate client backup
This document describes a known issue in NetBackup RealTime Protection 4.5. It explains how to correctly configure NetBackup RealTime Protection for a Snapshot Client off-host alternate client backup. Note: The issue described in this document will be fixed in a later version of NetBackup RealTime Protection. This document applies only to NetBackup RealTime Protection 4.5.

5/23/08

2 Configuration issue with NetBackup RealTime Protection 4.5 and alternate client backup Backup or restore fails when using NetBackup RealTime Protection and alternate client backup

Symantec Corporation 5/23/08

Backup or restore fails when using NetBackup RealTime Protection and alternate client backup
NetBackup RealTime Protection 4.5 contains a limitation that requires additional configuration steps to perform an alternate client backup of RealTime application assets. If these steps have not been followed, the RealTime server may not be able to make a TimeImage accessible to the alternate client. The first indication of the problem depends on the type of backup that was performed. Either the backup fails, or you are unable to browse folders and files to restore.

Backup fails
An alternate client backup of a NetBackup RealTime application may fail with status code 156. This failure may happen if the backup was a snapshot-based backup to a storage unit (with or without a retained snapshot for Instant Recovery). A message similar to the following may appear in the NetBackup bpfis log on the alternate client. (Note the text shown here in bold.)
14:38:59.002 [16772] <2> onlfi_vfms_logf: INF create_timeimage: host [s1.snappy.com] not found on appliance 14:38:59.003 [16772] <32> onlfi_fim_split: FTL - VfMS error 11; see following messages: 14:38:59.003 [16772] <32> onlfi_fim_split: FTL - Fatal method error was reported 14:38:59.003 [16772] <32> onlfi_fim_split: FTL vfm_freeze_commit: method: CDP, type: FIM, function: CDP_freeze_commit 14:38:59.003 [16772] <32> onlfi_fim_split: FTL - VfMS method error 6; see follow ing message: 14:38:59.003 [16772] <32> onlfi_fim_split: FTL CDP_freeze_commit: create timeimage failed with status 48

The bpfis log is in the following directory on the NetBackup alternate client: Operating system
Solaris Windows

Location of bpfis log folder


/usr/openv/netbackup/logs/bpfis install_path\NetBackup\logs\bpfis

http://entsupport.symantec.com/docs/303966

Symantec TechNote

Symantec Corporation 5/23/08

Configuration issue with NetBackup RealTime Protection 4.5 and alternate client backup How to update a RealTime application for alternate client backup

Restore fails
If the backup was a Snapshot only backup (for Instant Recovery), the backup succeeds but the attempt to restore fails. The contents of the folder that you are trying to browse do not appear. A message similar to the following may appear in the NetBackup bppfi log on the alternate client. (Note the text shown here in bold.)
14:32:40.089 [18728] <4> create_timeimage: host [s1.snappy.com] not found on appliance 14:32:40.089 [18728] <4> mount_frag: create timeimage failed with status 48

The bppfi log is in the following directory on the NetBackup alternate client Operating system
Solaris Windows

Location of bppfi log folder


/usr/openv/netbackup/logs/bppfi install_path\NetBackup\logs\bppfi

How to update a RealTime application for alternate client backup


In brief, the steps for updating a RealTime application to be used with an alternate client backup are the following. A detailed procedure follows this list.

Add the alternate client to the RealTime Recovery Manager application definition. Apply RealTime protection to the application. Although the attempt to apply protection may appear to fail, the RealTime server is correctly updated. Remove the alternate client from the application definition. RealTime protection is automatically reapplied. At this point, the RealTime server can make the TimeImage accessible to the alternate client.

Note: Use the following procedure once for each alternate client. This procedure need not be performed if the host acting as the alternate client has already been configured as a primary client for another RealTime snapshot backup policy. To update a RealTime application for alternate client backup It is assumed that you have already defined a RealTime application and have added the primary client (application host) and its assets to the application.

Symantec TechNote

http://entsupport.symantec.com/docs/303966

4 Configuration issue with NetBackup RealTime Protection 4.5 and alternate client backup How to update a RealTime application for alternate client backup

Symantec Corporation 5/23/08

Enter the RealTime Recovery Manager shell in the manager mode:


rmsh --manager=host1

Note: host1 is an example name that corresponds to the RealTime Recovery Manager virtual Hostname entry on the RealTime server network worksheet. See the Veritas NetBackup RealTime Protection Installation Guide for the RealTime server network worksheet. (The guide is included in the NetBackup RealTime installation media). 2 Enter the following commands:
manager@host1> update application app1 application<app1>@host1> add application host alt_client_name application<app1>@host1> commit

where app1 is an example name of the RealTime application to be changed. 3 If protection has not already been applied to the application, apply it:
manager@host1> apply protection app1 MyConfigName MyServiceName CDP

where MyConfigName is the name of the protection configuration, MyServiceName is the name of the protection service, and CDP is the protection method. Note: the apply protection command may return a message similar to the following:
Failed to apply protection; We'll retry automatically with next update

Ignore this message and continue with the next step. 4 Remove the alternate client from the application definition:
manager@host1> update application app1 application<app1>@host1> remove application host alt_client_name application<app1>@host1> commit

The RealTime protection is automatically updated and applied. 5 Verify that protection has been successfully applied:
manager@host1> show application app1

The Change state field reads APPLIED. NetBackup alternate client backups can now be performed for the assets defined in this application. For more information on configuring backup for NetBackup RealTime Protection, refer to the Veritas NetBackup 6.5.2 Documentation Updates document:
http://entsupport.symantec.com/docs/302438

Detailed instructions for defining RealTime applications and applying protection are available in the following guide (included in the NetBackup RealTime installation media): Veritas NetBackup RealTime Protection Administrators Guide

http://entsupport.symantec.com/docs/303966

Symantec TechNote