Tape mistakenly deleted

[360Highlander]

Using NetBackup 4.5GA

a Tape was mistakenly deleted using the dt.bat command. Is there anyway to restore the information on the tape? Can information from the catalog tape be written back to Veritas before it runs again? Please help, I'm feeling awful!

 

[Stumpr]

Has the tape been written to since you deleted it? If not then no problem. Simply import the tape. The import process will rebuild the catalog information. If the tape has been written to after you deleted it then ...well sorry.

Bob Stump
Incorrigible punster -- Do not incorrige

 

[Stumpr]

If the tape has not been written to yet then take immediate measures to ensure that it will not be written to before you do the import process.

Did you vault? then that copy could be used for restores.

Bob Stump
Incorrigible punster -- Do not incorrige

 

[360Highlander]

The tape has not been written to since this happened. How do I go about importing the tape? I am unsure about vault as well. Thanks.

 

[Stumpr]

Excellent. Don't worry. Your OK.

The import can be done via the GUI
sysadmin guide:
Chapter 4, “Using Catalog for Catalog Backups and Verifying, Duplicating, and Importing Images,” explains how to manage and back up the NetBackup internal catalogs. Catalog is also used to search for specific backup images in order to verify, duplicate, or import backup images.

Use this as your guide and start with the GUI at the catalog icon. There are 2 phases for the import.

The following will look sloppy as it is a cut/paste from the admin guide:
Importing Backup Images
NetBackup can import backups that have expired, or are from another NetBackup server.
During an import operation, NetBackup recreates NetBackup catalog entries for the
backups that are on the imported volume. This option is useful for moving volumes from
one site to another and for recreating NetBackup catalog entries for expired backups.
The expiration date for the imported items is the current date plus the retention period.
For example, if a backup is imported November 14, 2001 and its retention period is one
week, the new expiration date is November 21, 2001.
Notes About Importing Backup Images
? You cannot import images generated for clients in Apollo wbak policies.
? NetBackup does not direct backups to imported volumes.
? To import from a volume that has the same media ID as an existing volume (for
example A00001) on this server, first duplicate the existing volume to another media
ID (for example, B00001). Then, remove information about the existing media ID that
is causing the problem (in this example, A00001) from the NetBackup catalog by
running the following command:
/usr/openv/NetBackup/admincmd/bin/bpexpdate -d 0 -ev media ID
Next, delete the existing media ID that is causing the problem (in this example,
A00001) from Media Manager on this server. Finally, add the volume you are
importing (the other A00001) to Media Manager on this server. The Media Manager
System Administrator’s Guide contains instructions for deleting and adding volumes.
To avoid this problem in the future, use unique prefix characters for media IDs on all
servers.
? You cannot import a backup if an unexpired copy of it already exists on the server
where you are trying to import it.
? You cannot import data from disk-image.
? To initiate an import – Phase I
The result of initiating an import is to create a list of expired images from which you can
select images to import. However, no importing occurs at this stage.
1. Add the media IDs that have the backups to Media Manager on the server where you
are going to import the backups.
2. In the NetBackup Administration Console, expand NetBackup Management >
Catalog.
3. Select Actions > Initiate Import. A dialog appears titled
Step 1: Read Catalog from Media.
- The Master Server field indicates the master server to
which you are importing the images.
- In the Media Host field, specify the name of the host
that contains the volume you are going to import.
- In the Media ID (to import) field, type the Media ID of the volume that contains
the backups you are importing.
- If you’re importing Backup Exec images, check Password, then enter the
password.
Click OK. The Confirm Initiate Import dialog
appears.
4. Click OK to start the process of reading the catalog
information from the source volume.
5. Click on the Catalog Results tab to see NetBackup look at each image on the tape and
determine whether or not it has expired and can be imported. The job also displays in
Activity Monitor as an Import type. Select the import job log just created to view the
job results.
Note Since it is necessary to mount and read the tape at this phase, reading the catalog
and building the list can take some time to complete.
Chapter 4, Using Catalog for Catalog Backups and Verifying, Duplicating, and Importing Images 211
Viewing Job Results
? To import backup images – Phase II
1. In the NetBackup Administration Console, expand NetBackup Management >
Catalog.
2. Set up the search criteria to find imported images by setting the search action to
Import.
3. Select the image(s) you wish to import and Select
Actions > Import. The Confirm Import dialog
appears.
4. To view the log, click the Results tab, then select the
import job log just created.
Note When importing backups that have fragments on more than one tape, do not start
the import until you have read the catalog for all the tapes containing fragments.
Otherwise, the import will fail with a message similar to: Import of backupid
failed, fragments are not consecutive.

Bob Stump
Incorrigible punster -- Do not incorrige

 

[360Highlander]

regarding this note
-------
Note When importing backups that have fragments on more than one tape, do not start
the import until you have read the catalog for all the tapes containing fragments.
Otherwise, the import will fail with a message similar to: Import of backupid
failed, fragments are not consecutive.
--------

Does this mean I need to do the Phase I part of import on all of the tapes for example, that particular back up was written to tapes 41, 5, and 163. Tape 5 was the one deleted. I already imported 5, but received the following.

-----
INF - Skipping backup id 360nas1_1108314583, there is no fragment 1.
INF - Found no images matching the selection criteria that were ready for phase 2 import.
-----
So I'm guessing I need to import the other two tapes as well? Thanks.

 

[Stumpr]

yes

Bob Stump
Incorrigible punster -- Do not incorrige

 

[360Highlander]

ok, here is the error message I am getting when I start Phase II.
--------
"G:\Program Files\VERITAS\NetBackup\bin\admincmd\bpimport.exe" -Bidfile "G:\Program Files\VERITAS\NetBackup\temp\20050216130550.bid" -L "G:\Program Files\VERITAS\NetBackup\Logs\NBimport\Import2-0008.log" -M 360tempserv -l

Import phase 2 started Wed Feb 16 2005 13:05:51
13:05:55 INF - Importing policy 360nas1_vol1_m, schedule Full (360nas1_1108314583), media id AS163S, created on 02/13/2005 11:09:43.
13:05:55 INF - Importing by reading INDEX file information only, full list not available.
13:05:59 INF - Import of policy 360nas1_vol1_m, schedule Full (360nas1_1108314583) failed, the image was not created with TIR information.

13:05:59 INF - Status = no images were successfully processed.
--------
Thanks

 

[Stumpr]

Please read this techtip
Import phase 2 of a flashbackup image fails with "the image was not created with TIR information

http://seer.support.veritas.com/docs/252283.htm

Bob Stump
Incorrigible punster -- Do not incorrige

 

[360Highlander]

After waiting about 24 hours for this process to finish. It failed. Here is the log.
--------
"G:\Program Files\VERITAS\NetBackup\bin\admincmd\bpimport.exe" -Bidfile "G:\Program Files\VERITAS\NetBackup\temp\20050216130550.bid" -L "G:\Program Files\VERITAS\NetBackup\Logs\NBimport\Import2-0008.log" -M 360tempserv -l

Import phase 2 started Wed Feb 16 2005 13:05:51
13:05:55 INF - Importing policy 360nas1_vol1_m, schedule Full (360nas1_1108314583), media id AS163S, created on 02/13/2005 11:09:43.
13:05:55 INF - Importing by reading INDEX file information only, full list not available.
13:05:59 INF - Import of policy 360nas1_vol1_m, schedule Full (360nas1_1108314583) failed, the image was not created with TIR information.

13:05:59 INF - Status = no images were successfully processed.
--------

Despite the failure tape AS005S now has information on it. Does this mean I'm ok?

 

[360Highlander]

I didn't realize I'd pasted the wrong information

----------
"G:\Program Files\VERITAS\NetBackup\bin\admincmd\bpimport.exe" -Bidfile "G:\Program Files\VERITAS\NetBackup\temp\20050216132742.bid" -L "G:\Program Files\VERITAS\NetBackup\Logs\NBimport\Import2-0010.log" -M 360tempserv -l

Import phase 2 started Wed Feb 16 2005 13:27:43
13:27:46 INF - Importing policy 360nas1_vol1_m, schedule Full (360nas1_1108314583), media id AS163S, created on 02/13/2005 11:09:43.
13:27:46 INF - Importing by reading INDEX file information only, full list not available.
13:27:52 INF - Waiting for mount of media id AS163S on server 360tempserv.
13:28:47 INF - Waiting for positioning of media id AS163S on server 360tempserv.
13:32:24 INF - Beginning import on server 360tempserv of client 360nas1.
15:06:32 INF - Waiting for mount of media id AS005S on server 360tempserv.
15:07:18 INF - Waiting for positioning of media id AS005S on server 360tempserv.
15:07:19 INF - Continuing import on server 360tempserv of client 360nas1.
05:43:56 INF - Waiting for mount of media id AS041S on server 360tempserv.
05:45:07 INF - Waiting for positioning of media id AS041S on server 360tempserv.
05:45:09 INF - Continuing import on server 360tempserv of client 360nas1.
11:22:12 INF - Reading image file information from media id AS041S.
11:42:41 INF - Import of policy 360nas1_vol1_m, schedule Full (360nas1_1108314583) failed, network read failed.

11:42:41 INF - Status = no images were successfully processed.
--------
I ask the same question.
Despite the failure, tape AS005S now (with qt.bat command) shows that there is information on the tape. Does this mean I'm ok or do I need to take other steps to minimize the damage?

 

[Stumpr]

failed, network read failed.

This appears to be a timeout situation. The information may not be complete. Try adjusting the timeout parameters in the client and server properties and rerun the import.

Bob Stump
Incorrigible punster -- Do not incorrige