I have seen issues where Removable Storage Service has caused issues
with other types of backup software. However we are an all Linux
environment and don't run into these issues. So I am not sure that if
it is enabled what it would do to Legato.
Also some quick SAN notes. Are you using zoning at all? If you are it
is a good idea to be sure that you have a zone for each target
initiator. Meaning if you have the Sun server and the Windows server
and all of your tape drives in one zone this is CAN cause issues, but I
don't think that is the case here. It is recommended that you create a
zone for each target. For example ZONE1 would have the Sun server and
all tape drives. ZONE2 would have the Win2k server and all of the tape
drives.
When you say you set the block size on both servers how did you go about
doing this? I know on Sun there is an stinit file or something similar
to set the block size for. Additional you need to make sure that you
use the following environment variables when you start up Networker.
NSR_DEV_BLOCK_SIZE_8MM_AIT_2=<BLOCK_SIZE>
NSR_DEV_BLOCK_SIZE_8MM_AIT_3=<BLOCK_SIZE>
It is possible that the operating system is determining the block size
and this could vary from OS to OS.
Let me know how it goes because I have had similar issues with block
size settings before.
Regards,
Chad Smykay
-----Original Message-----
From: Legato NetWorker discussion [mailto:NETWORKER AT LISTMAIL.TEMPLE DOT EDU]
On Behalf Of Teresa Biehler
Sent: Friday, August 22, 2003 7:00 AM
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Subject: Re: [Networker] problems reading tapes
The drives are SAN connected.
Both the storage node and server can see the drives - both have done
successful backups and restores.
I need to check on the Removable Storage Service. What harm could that
do?
-Teresa
-----Original Message-----
From: Davina Treiber [mailto:Treiber AT HOTPOP DOT COM]
Sent: Friday, August 22, 2003 2:35 AM
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Subject: Re: [Networker] problems reading tapes
Teresa Biehler wrote:
> I'm in the process of setting up our new backup environment. Here's
> what's been done:
>
> - Installed hardware
> - Installed Networker software (v6.1.3) on new Solaris server (NW
server
> and storage node)
> - Configured library to be used by the server only
> - Ran backup/restore tests - all successful
> - Installed v6.1.3 storage node software on Win2K server
> - Configured library so that all drives but one are controlled by the
> server. One drive is controlled by a Win2K storage node
> - Change block size on Solaris server so that Solaris and Win2K are
> using the same block size
> - Relabeled all tapes
> - Ran backup/restore tests - all successful (including writing on
> server, reading on storage node and the reverse)
> - Configured library so that several drives are shared with DDS
between
> server and storage node
> - Ran lots of backups
> - Tuned the server's parallelism
> - Ran lots of backups
>
> So, now here's what I'm getting when I try to do a restore:
>
>
>>recover -s server -c client
>
> recover: Current working directory is /oradata/TEST/
> .
> . (changed time and recover location)
> .
> recover> recover
> recover: Total estimated disk space needed for recover is 1281 MB.
> Recovering 18 files within /oradata/TEST/ into /test1/oradata/TEST
> Volumes needed (all on-line):
> 000002 at sc10k
> Requesting 18 file(s), this may take a while...
> Error encountered on the following files by NSR server `server': can
not
> read record 968 of file 113 on 8mm AIT-3 tape 000002
> ./mirror_files/control03.ctl @ Sun Aug 17 02:21:36 2003
> ./mirror_files/redo01b.log @ Sun Aug 17 02:21:36 2003
> ./mirror_files/redo02b.log @ Sun Aug 17 02:21:36 2003
> ./mirror_files/redo03b.log @ Sun Aug 17 02:21:36 2003
> ./mirror_files/redo04b.log @ Sun Aug 17 02:21:36 2003
> ./mirror_files/redo05b.log @ Sun Aug 17 02:21:36 2003
> ./mirror_files/ @ Sun Aug 17 02:21:36 2003
> ./redo01a.log @ Sun Aug 17 02:21:36 2003
> ./redo02a.log @ Sun Aug 17 02:21:36 2003
> ./redo03a.log @ Sun Aug 17 02:21:36 2003
> ./rollback01.dbf @ Sun Aug 17 02:21:36 2003
> ./sys01.dbf @ Sun Aug 17 02:21:36 2003
> ./temp01.dbf @ Sun Aug 17 02:21:36 2003
> ./users01.dbf @ Sun Aug 17 02:21:36 2003
> recover: Requesting remaining 4 file(s) from NSR server `server' NSR
> server `server': busy
> recover: waiting 30 seconds then retrying
> .
> .
> .
> Error encountered on the following files by NSR server `server': can
not
> read record 962 of file 114 on 8mm AIT-3 tape 000002
> ./fsg_data01.dbf @ Sun Aug 17 02:21:36 2003
> ./pltw_data01.dbf @ Sun Aug 17 02:21:36 2003
> ./redo04a.log @ Sun Aug 17 02:21:36 2003
> ./redo05a.log @ Sun Aug 17 02:21:36 2003
> Received 0 file(s) from NSR server `server'
> Recover errors with 18 file(s)
> Recover completion time: Mon Aug 18 16:15:40 2003
>
>
> So, to see if I can read the tape at all, I ran scanner:
>
>
> root}25: scanner -iv /dev/rmt/1cbn
> scanner: Opened /dev/rmt/1cbn for read
> scanner: Rewinding...
> scanner: Rewinding done
> scanner: Reading the label...
> scanner: Reading the label done
> scanner: SYSTEM error: Tape label read: Bad file number
> scanner: SYSTEM error: Tape label read: Bad file number
> scanner: scanning for valid records...
> scanner: read: -1 bytes : Not enough space
> scanner: Opened /dev/rmt/1cbn for read
> scanner: read: -1 bytes : Not enough space
>
> This happened with several clients, so I wanted to see if I could read
> any tapes. So, I ran scanner on all 5 tapes that have been used for
> testing (all with at least 3 GB of data, most with nearly 100 GB of
> data). I got the same results from scanner with each tape.
Are these drives SAN connected? Can both the storage node and the server
see the drives? Have you zoned the SAN? Have you disabled Removable
Storage Service on the W2K box?
--
Note: To sign off this list, send a "signoff networker" command via
email to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can also
view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
--
Note: To sign off this list, send a "signoff networker" command via
email to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can also
view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.512 / Virus Database: 309 - Release Date: 8/19/2003
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.512 / Virus Database: 309 - Release Date: 8/19/2003
--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
|
