[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference decwet::networker

Title:	NetWorker
Notice:	kits - 12-14, problem reporting - 41.*, basics 1-100
Moderator:	DECWET::RANDALL.com::lenox

Created:	Thu Oct 10 1996
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	750
Total number of notes:	3361

590.0. "Canceling a Scheduled Backup" by CSC32::L_DVORAK () Thu Apr 17 1997 15:17

Hi.

I have a customer who is running 4.3 of Networker on an Alpha running
Windows NT 3.51.  They were performing a scheduled backup when one of
their tape drives went bad.  The backup is now in a pending state waiting
for the tape to come back.  They need to shutdown to get the tape drive
replaced, but wanted to cancel the backup first.  They tried clicking
on STOP in the Group Control window with no luck.  What should they do
to stop/cancel this backup?  Can they do this from the command line?  If
so, what is the command?  Is it okay for them to shutdown without canceling 
the backup?  What will happen when they reboot?  If the backup is still 
pending, will remounting a tape allow the backup to continue?

Regards,

Lani Dvorak
Windows NT/Backoffice Support
US CSC
Multivendor Customer Service

T.R	Title	User	Personal Name	Date	Lines
590.1		DECWET::LENOX	a bit too exciting	`Thu Apr 17 1997 16:32`	21
	Are there any other drives available to complete the backup? (It sounds like there are from your description). If so then have them disable the bad drive (and possbily) complete the backup. One disables a drive via the admin gui (started with -x) in the media->click on bad drive->change enabled field to no. If there are other drives, removing the drive and rebooting the system can change how the drives are addressed, i.e. if \\.\Tape0 breaks and is removed then on reboot a different tape drive will become \\.\Tape0 (can be confusing to NSR). If the bad drive is one of many in a jukebox, removing it and restarting the system could make the jukebox unusable (if it isn't being replaced right away). To stop NSR, stop the services (via the control panel-> services). Stop the server first, then stop the remote exec service, then the portmapper (if you want all networker related services stopped). If restarting them manually, restart them in reverse order. They can shutdown the system as well, that will definitely stop any problem services, should not every stop nicely.
590.2		CSC32::L_DVORAK		`Fri Apr 18 1997 12:22`	11
	Thanks for the info. If a system is shutdown and the bad drive replaced, does the addressing still change on bootup? You gave instructions for stopping Networker...what are the instructions for stopping a scheduled backup? I found a note that says to do it from the Group Control window, but this didn't work for the customer. I also found a note that says it can be done from the command line, but no specific command was given in the note. Regards, Lani
590.3	Will not stop until tape loads	NQOS01::rdodial_port11.32.81.16.in-addr.arpa::Curle		`Wed Apr 23 1997 11:15`	14
	NetWorker will not stop the backup until the tape mounts and the problem is the tape will not mount because of either a bad tape or tape drive. And you can not disable the tape device because the NetWorker Server is trying to mount the tape. You are in a catch-22. Also if you stop NetWorker services and then physically dismount the tape. Then NetWorker loses the tape label so you have to start all over again with that tape. You have to relabel the label and then remove the tape from the index. This is what happend in my case. Thanks, Allen
590.4	Had to wait about a hour to timeout	NQOS01::rdodial_port12.32.81.16.in-addr.arpa::Curle		`Wed Apr 23 1997 15:31`	6
	Let me clarify the last response. Once I stopped the scheduled backup, it stopped after about a hour with an I/O device error and tape label not found. It looks like we have tape problems were if one tape device writes data and another drive write more data to the same tape then the tape label is lost. We are looking to replace some of the tape drives to fix this problem.
590.5	Bad SCSI Cable	NQOS01::rdodial_port14.32.81.16.in-addr.arpa::Curle		`Mon May 05 1997 10:27`	1
	We had a bad cable. Once we replaced the bad SCSI cable everything works.