If it's a totally new NB installation it will obviously have no record of that media & as such will treat it as a new tape.

Was it just 'normal' data on the tape originally? If used for catalog backups during testing it may need re-labelling before NB will be able to write normal backup data to it.

Yes, just checked. I finally work out my procedure for the backup. After I use A0000 as my first tape, and change to a second blank tape. I can't label a second tape. It always comes with a "pending for reoursce required".

But If I "down" and "up" the tape drive, the recorded label in tape drive will be disappear, and I insert a new tape, and did a manul backup, it works and the NB will lable that tape as A00001, and so on for A00003.

It did the same procedure for restore.

I got a message that it should be done by AVRD for a single device like me, Should the installation has limitation of NB 7.0 with Server 2008 Standard R2 x64?

Or it actually a normal procedure?

per Mariannes response to your earlier post: https://www-secure.symantec.com/connect/forums/net...

Similarly for the following:

How to perform Media Management with standalone Drives in NetBackup 5.x and 6.x.
http://seer.entsupport.symantec.com/docs/296268.htm

I have follow exactly but still not working. Would like to confirm;

1. Is there any device drive for the tape (IBM 3580 TD4) from Netbackup that should be used instead of Windows driver?

2. When I change the tape, I check the tape detail, the recorded tape is always "A00000" , I need to manual "down" and "up" to release the tape label, before I can insert a second tape.

3. I still can't label the tape, but if I perform a manul backup on the new inserted tape, it works and AVR will label the tape as A00001.

4. Is the above procedure normal?

I have follow exactly but still not working. Would like to confirm;

1. Is there any device drive for the tape (IBM 3580 TD4) from Netbackup that should be used instead of Windows driver?
no there is no device driver required for netbackup. the tape is found in the HCL

2. When I change the tape, I check the tape detail, the recorded tape is always "A00000" , I need to manual "down" and "up" to release the tape label, before I can insert a second tape.
Once the backup is done you can simply eject the media.
it will no  more be seen under recorded media

3. I still can't label the tape, but if I perform a manul backup on the new inserted tape, it works and AVR will label the tape as A00001.
Netbackup will label the tape automatically when you insert a new tape.
you can run a manual test_policy to check this.

4. Is the above procedure normal?

Have you tried searching the IBM site for drivers?

I don't agree with Nitesh.
This is what the Hardware Compatibility Guide says:

IBM Tape Driver Support
The list below is intended to show the latest versions of the IBM device drivers that have been tested with NetBackup. Older versions may work but using the versions listed here is recommended.
If using the IBM Windows Tape Device Drivers be sure to choose the install_nonexclusive.exe executable. This option permits a tape drive to be accessed by multiple processes on a Media Server, which is a requirement for NetBackup.
NetBackup requires the IBM Data Path Failover feature to be disabled on the IBM tape device driver. To disable this feature, open the reg folder of the IBM driver package, double-click DisableDPF.reg, and reboot the system.

- IBMTape driver level 6.1.9.5 tested on Windows

I try to get the driver from IBM site and test it again. IF the problem still exist, should I consider the tape has problem? I didn't update that at the first time I do the installation and testing, I did one time the device diagnosis is working and can label one time myself vai GUI.

In all honesty, using Microsoft or vendor specific tape drivers instead of the Veritas Tape Drivers is still a bit of a grey area for me - I've had a couple of bad experiencies with vendor drivers on 64-bit O/S (Veritas tape drivers are only for 32-bit O/S).

Using the IBM driver as suggested by the compatibility guide as well as disabling TUR as per this TN has helped:
http://seer.entsupport.symantec.com/docs/268245.htm

After I use the IBM driver, the case is even worst. So I switch back to the Microsoft driver.

Re tape lable issue, I follow exaxctly the procedure but still failed, Here is the steps I followed;

1. New NB installation
2. Go to Volume Netbackup, create a new volume namely ABC000
3. Insert a new tape into the drive
4. Go to command prompt, issue command bplable -m ABC000 -d hcart3 -o -p NetBackup -u 0

it returns with IPC error, daemon not started.

If I remove -u 0, then the job hold and saying pending for resource etc

I have one more question as I will put production very soon, Re label, I think I can modify the pre-fix setting under Host -> Mdeia -> Prefit,

While I still have a question re Erase, I can't erase a tape so far. I test with a used tape, then I bpexpdate the tape, then try to erase, it returns with PENDINg error.

The last equestion is "what is the definition of Assigned"?, if a tape was assigned, then it was backup before, right? Since once backup, AVR will label the tape, and with retention period as stated in the policy.

As a matter of interest - how are you opening the Command Prompt (to do bplabel)?

I  have see all sorts of weird and wonderful errors with different applications (not only NBU) on W2008 if cmd is not started 'with 'run as Administrator' although being logged on as local or even domain admin.