Backup Central

Content-Transfer-Encoding: quoted-printable

I have several stand alone, non-barcode reading, tape drives. They run
on Win 2k, NBU 4.5fp7. Right now tape #2 is in the drive, when the
backup starts it is looking for #6. Now tape #6 is not expired and can
not be written over, Tape #2 IS expired. Why is it looking for that
specific tape id? How can I circumvent this? The units in question are
overseas and there is quite the language barrier, So I cant really ask
them to keep changing out tapes every time the backup runs.

Any ideas?

If NetBackup is trying to write to tape #6, then #6 is not full and it's
trying to append to the data already on the tape.

If you wish to make a tape unavailable for writing until its data
expires, "suspend" it with the bpmedia command.

cheers, wayne

Zermeno, Brandon (Contractor) wrote, in part, on 1/12/2005 10:13 AM:

I have several stand alone, non-barcode reading, tape drives. They run
on Win 2k, NBU 4.5fp7. Right now tape #2 is in the drive, when the
backup starts it is looking for #6. Now tape #6 is not expired and can
not be written over, Tape #2 IS expired. Why is it looking for that
specific tape id? How can I circumvent this? The units in question are
overseas and there is quite the language barrier, So I cant really ask
them to keep changing out tapes every time the backup runs.

Any ideas?

Well the problem is that I don't know what tape they are putting in the
drive or even how they are labeled. Veritas has over 50 media id's
available in it. I was hoping for something that involves less
maintenance on my part.
Usually they replace the tape on Wednesday or Thursday for the Full
during the weekend, then append to the tape during the week with the
incremental.

-----Original Message-----
From: veritas-bu-admin < at > mailman.eng.auburn.edu
[mailto:veritas-bu-admin < at > mailman.eng.auburn.edu] On Behalf Of Wayne T
Smith
Sent: Wednesday, January 12, 2005 10:28 AM
To: veritas-bu < at > mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Stand-alone drives

If NetBackup is trying to write to tape #6, then #6 is not full and it's

trying to append to the data already on the tape.

If you wish to make a tape unavailable for writing until its data
expires, "suspend" it with the bpmedia command.

cheers, wayne

Zermeno, Brandon (Contractor) wrote, in part, on 1/12/2005 10:13 AM:

I have several stand alone, non-barcode reading, tape drives. They run

on Win 2k, NBU 4.5fp7. Right now tape #2 is in the drive, when the
backup starts it is looking for #6. Now tape #6 is not expired and can

not be written over, Tape #2 IS expired. Why is it looking for that
specific tape id? How can I circumvent this? The units in question are

overseas and there is quite the language barrier, So I cant really ask

them to keep changing out tapes every time the backup runs.

Any ideas?

I'd suggest checking out the section on "How NetBackup Uses Media in
Standalone Drives" in the NBU SAG.

For reference, the 4.5 NBU UNIX SAG has this topic on page 793.

HTH
-Tim

On Jan 12, 2005, at 9:46 AM, Zermeno, Brandon ((Contractor)) wrote:

Well the problem is that I don't know what tape they are putting in the
drive or even how they are labeled. Veritas has over 50 media id's
available in it. I was hoping for something that involves less
maintenance on my part.
Usually they replace the tape on Wednesday or Thursday for the Full
during the weekend, then append to the tape during the week with the
incremental.

-----Original Message-----
From: veritas-bu-admin < at > mailman.eng.auburn.edu
[mailto:veritas-bu-admin < at > mailman.eng.auburn.edu] On Behalf Of Wayne T
Smith
Sent: Wednesday, January 12, 2005 10:28 AM
To: veritas-bu < at > mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Stand-alone drives

If NetBackup is trying to write to tape #6, then #6 is not full and
it's

trying to append to the data already on the tape.

If you wish to make a tape unavailable for writing until its data
expires, "suspend" it with the bpmedia command.

cheers, wayne

Zermeno, Brandon (Contractor) wrote, in part, on 1/12/2005 10:13 AM:

I have several stand alone, non-barcode reading, tape drives. They run

on Win 2k, NBU 4.5fp7. Right now tape #2 is in the drive, when the
backup starts it is looking for #6. Now tape #6 is not expired and can

not be written over, Tape #2 IS expired. Why is it looking for that
specific tape id? How can I circumvent this? The units in question are

overseas and there is quite the language barrier, So I cant really ask

them to keep changing out tapes every time the backup runs.

Any ideas?

_______________________________________________

_______________________________________________

When the tape is loaded (assuming that it has been written to before),
you can use vmoprcmd or device monitor in the GUI to see what tape is
loaded (by looking at the recorded ID).

If you are only wanting to keep one copy of the backup, then expire the
tape loaded. Not the safest or smartest way to do this.

2 suggestions:
1. Have 4 tapes that are labeled (for human viewing) Week A, Week B,
..,Week D. Have your policy set with a retention rate of 3 weeks. Tell
them to rotate the tapes based on the external label. You can also
write the tape ID with NB by labeling the tape. Have your backup end
script to suspend the tape at the conclusion of the backup.

2. Don't use NB to do the backups. Since you are not managing a tape
library, it would seem cheaper to just use the backup feature of Win2k.
It works.



Bobby Williams
Senior Systems Engineer
GTSI Corp, State and Local, Southeast
4250-A Benton Drive
Chattanooga, Tennessee 37406
Phone: 423-624-2600
Pager: 423-819-3336
Fax: 423-629-9669

-----Original Message-----
From: veritas-bu-admin < at > mailman.eng.auburn.edu
[mailto:veritas-bu-admin < at > mailman.eng.auburn.edu] On Behalf Of Zermeno,
Brandon (Contractor)
Sent: Wednesday, January 12, 2005 10:46 AM
To: Wayne T Smith; veritas-bu < at > mailman.eng.auburn.edu
Subject: RE: [Veritas-bu] Stand-alone drives

Well the problem is that I don't know what tape they are putting in the
drive or even how they are labeled. Veritas has over 50 media id's
available in it. I was hoping for something that involves less
maintenance on my part.
Usually they replace the tape on Wednesday or Thursday for the Full
during the weekend, then append to the tape during the week with the
incremental.

-----Original Message-----
From: veritas-bu-admin < at > mailman.eng.auburn.edu
[mailto:veritas-bu-admin < at > mailman.eng.auburn.edu] On Behalf Of Wayne T
Smith
Sent: Wednesday, January 12, 2005 10:28 AM
To: veritas-bu < at > mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Stand-alone drives

If NetBackup is trying to write to tape #6, then #6 is not full and it's

trying to append to the data already on the tape.

If you wish to make a tape unavailable for writing until its data
expires, "suspend" it with the bpmedia command.

cheers, wayne

Zermeno, Brandon (Contractor) wrote, in part, on 1/12/2005 10:13 AM:

I have several stand alone, non-barcode reading, tape drives. They run

on Win 2k, NBU 4.5fp7. Right now tape #2 is in the drive, when the
backup starts it is looking for #6. Now tape #6 is not expired and can

not be written over, Tape #2 IS expired. Why is it looking for that
specific tape id? How can I circumvent this? The units in question are

overseas and there is quite the language barrier, So I cant really ask

them to keep changing out tapes every time the backup runs.

Any ideas?

I cant believe it!! The Stand Alone Drive Extensions were disabled!
Thanks for the tip! I have never worked with out a bar-code reader.

-----Original Message-----
From: Tim Hoke [mailto:thoke < at > northpeak.org]
Sent: Wednesday, January 12, 2005 10:52 AM
To: Zermeno, Brandon (Contractor)
Cc: veritas-bu < at > mailman.eng.auburn.edu; Wayne T Smith
Subject: Re: [Veritas-bu] Stand-alone drives

I'd suggest checking out the section on "How NetBackup Uses Media in
Standalone Drives" in the NBU SAG.

For reference, the 4.5 NBU UNIX SAG has this topic on page 793.

HTH
-Tim

On Jan 12, 2005, at 9:46 AM, Zermeno, Brandon ((Contractor)) wrote:

Well the problem is that I don't know what tape they are putting in
the
drive or even how they are labeled. Veritas has over 50 media id's
available in it. I was hoping for something that involves less
maintenance on my part.
Usually they replace the tape on Wednesday or Thursday for the Full
during the weekend, then append to the tape during the week with the
incremental.

-----Original Message-----
From: veritas-bu-admin < at > mailman.eng.auburn.edu
[mailto:veritas-bu-admin < at > mailman.eng.auburn.edu] On Behalf Of Wayne T
Smith
Sent: Wednesday, January 12, 2005 10:28 AM
To: veritas-bu < at > mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Stand-alone drives

If NetBackup is trying to write to tape #6, then #6 is not full and
it's

trying to append to the data already on the tape.

If you wish to make a tape unavailable for writing until its data
expires, "suspend" it with the bpmedia command.

cheers, wayne

Zermeno, Brandon (Contractor) wrote, in part, on 1/12/2005 10:13 AM:

I have several stand alone, non-barcode reading, tape drives. They
run

on Win 2k, NBU 4.5fp7. Right now tape #2 is in the drive, when the
backup starts it is looking for #6. Now tape #6 is not expired and
can

not be written over, Tape #2 IS expired. Why is it looking for that
specific tape id? How can I circumvent this? The units in question
are

overseas and there is quite the language barrier, So I cant really
ask

them to keep changing out tapes every time the backup runs.

Any ideas?

_______________________________________________

_______________________________________________

I have mentioned going to backup exec but the response was "is it free?"
I am going to test out using NT Backup on some of these sites. I have 7
I think I can dump.

-----Original Message-----
From: Bobby Williams [mailto:Bobby.Williams < at > gtsi.com]
Sent: Wednesday, January 12, 2005 11:03 AM
To: Zermeno, Brandon (Contractor); Wayne T Smith;
veritas-bu < at > mailman.eng.auburn.edu
Subject: RE: [Veritas-bu] Stand-alone drives

When the tape is loaded (assuming that it has been written to before),
you can use vmoprcmd or device monitor in the GUI to see what tape is
loaded (by looking at the recorded ID).

If you are only wanting to keep one copy of the backup, then expire the
tape loaded. Not the safest or smartest way to do this.

2 suggestions:
1. Have 4 tapes that are labeled (for human viewing) Week A, Week B,
..,Week D. Have your policy set with a retention rate of 3 weeks. Tell
them to rotate the tapes based on the external label. You can also
write the tape ID with NB by labeling the tape. Have your backup end
script to suspend the tape at the conclusion of the backup.

2. Don't use NB to do the backups. Since you are not managing a tape
library, it would seem cheaper to just use the backup feature of Win2k.
It works.



Bobby Williams
Senior Systems Engineer
GTSI Corp, State and Local, Southeast
4250-A Benton Drive
Chattanooga, Tennessee 37406
Phone: 423-624-2600
Pager: 423-819-3336
Fax: 423-629-9669

-----Original Message-----
From: veritas-bu-admin < at > mailman.eng.auburn.edu
[mailto:veritas-bu-admin < at > mailman.eng.auburn.edu] On Behalf Of Zermeno,
Brandon (Contractor)
Sent: Wednesday, January 12, 2005 10:46 AM
To: Wayne T Smith; veritas-bu < at > mailman.eng.auburn.edu
Subject: RE: [Veritas-bu] Stand-alone drives

Well the problem is that I don't know what tape they are putting in the
drive or even how they are labeled. Veritas has over 50 media id's
available in it. I was hoping for something that involves less
maintenance on my part.
Usually they replace the tape on Wednesday or Thursday for the Full
during the weekend, then append to the tape during the week with the
incremental.

-----Original Message-----
From: veritas-bu-admin < at > mailman.eng.auburn.edu
[mailto:veritas-bu-admin < at > mailman.eng.auburn.edu] On Behalf Of Wayne T
Smith
Sent: Wednesday, January 12, 2005 10:28 AM
To: veritas-bu < at > mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Stand-alone drives

If NetBackup is trying to write to tape #6, then #6 is not full and it's

trying to append to the data already on the tape.

If you wish to make a tape unavailable for writing until its data
expires, "suspend" it with the bpmedia command.

cheers, wayne

Zermeno, Brandon (Contractor) wrote, in part, on 1/12/2005 10:13 AM:

I have several stand alone, non-barcode reading, tape drives. They run

on Win 2k, NBU 4.5fp7. Right now tape #2 is in the drive, when the
backup starts it is looking for #6. Now tape #6 is not expired and can

not be written over, Tape #2 IS expired. Why is it looking for that
specific tape id? How can I circumvent this? The units in question are

overseas and there is quite the language barrier, So I cant really ask

them to keep changing out tapes every time the backup runs.

Any ideas?

It may be possible that the tape in the drive is either not in the volume
pool that is set in the policy or there is valid data on the tape of a
different retention to the policy or schedule that is attempting to run.
The default setting is to not allow multiple retentions.

From: "Zermeno, Brandon (Contractor)" <BZERMENO < at > intersil.com>
To: <veritas-bu < at > mailman.eng.auburn.edu>
Subject: [Veritas-bu] Stand-alone drives
Date: Wed, 12 Jan 2005 10:13:17 -0500

I have several stand alone, non-barcode reading, tape drives. They run
on Win 2k, NBU 4.5fp7. Right now tape #2 is in the drive, when the
backup starts it is looking for #6. Now tape #6 is not expired and can
not be written over, Tape #2 IS expired. Why is it looking for that
specific tape id? How can I circumvent this? The units in question are
overseas and there is quite the language barrier, So I cant really ask
them to keep changing out tapes every time the backup runs.

Any ideas?

Another note:

If there are several tapes in the media pool - unassigned,
Then the tapes with the LOWEST MOUNT COUNT get mounted first.

Example: to set mount count to 0 so that tape will be used 1st for tape
NTY365 =

You can change the mount count in volmgr\bin vmchange -m NTY365 -n 0

This is also nice to keep tapes mounting in sequence in media pools.


Eric Ljungblad
Computer Operator
Copley Information Services
Eric.Ljungblad < at > copleypress.com
(858) 729-8010

-----Original Message-----
From: c h [mailto:dungee < at > hotmail.com]
Sent: Wednesday, January 12, 2005 3:51 PM
To: BZERMENO < at > intersil.com; veritas-bu < at > mailman.eng.auburn.edu
Subject: RE: [Veritas-bu] Stand-alone drives

It may be possible that the tape in the drive is either not in the volume
pool that is set in the policy or there is valid data on the tape of a
different retention to the policy or schedule that is attempting to run.
The default setting is to not allow multiple retentions.

From: "Zermeno, Brandon (Contractor)" <BZERMENO < at > intersil.com>
To: <veritas-bu < at > mailman.eng.auburn.edu>
Subject: [Veritas-bu] Stand-alone drives
Date: Wed, 12 Jan 2005 10:13:17 -0500

I have several stand alone, non-barcode reading, tape drives. They run
on Win 2k, NBU 4.5fp7. Right now tape #2 is in the drive, when the
backup starts it is looking for #6. Now tape #6 is not expired and can
not be written over, Tape #2 IS expired. Why is it looking for that
specific tape id? How can I circumvent this? The units in question are
overseas and there is quite the language barrier, So I cant really ask
them to keep changing out tapes every time the backup runs.

Any ideas?