toasters

toasters@lists.teaparty.net

13514 discussions

RE: DLT 7000 question
by Bokkelkamp Ernst SBS ITS ORS AHS 241 20 Oct '01

20 Oct '01

Hallo Rahul, the problem is that the 40/80GB label on the tape package is purely marketing based on the DLT8000 drive. What counts is the type of drive and the compressability of the data. In your case the DLT IV tape is marketed as 35/70GB. Without compression 35 and with 2:1 compression 70 GB. But the compression depends on the data, which means you can have more or less. My experience with the data I back up is about 55 GB compressed, but I have already written 120 GB to one tape. For more information you should read (or download) the DLT Hanbook from www.dlttape.com, this book explains almost everything you would like to know about the current DLT tape drives and cartridges. Bye Ernie -----Original Message----- From: Rahul Kumar [mailto:Rahul.Kumar@sdrc.com] Sent: Samstag, 20. Oktober 2001 05:49 Cc: toasters@mathworks. com Subject: DLT 7000 question Hi All, Can anyone tell me how to enable the compression on DLT7000 tapedrive attached to F740. I use a 40/80GB tape on the filer tape drive. The drive make is tandenberg . I usually see the drive compression led on. Is there any special option in dump command to reflect the compression.... right now i back up around 45 gb data.. but the dlt is asking to insert the second tape. the command which i issue to backup entire volume is (45gb---vol0) dump 0ufb rst0a 63 /vol/vol0 Rahul -----Original Message----- From: Manny Kaiser [mailto:mkaiser@mmcnet.com] Sent: Saturday, October 20, 2001 1:37 AM To: ilya.birman(a)abnamro.com Cc: toasters@mathworks. com Subject: RE: Veritas Netbackup Database Hi, did you test the ability to recover this database? Just to make sure I understand - /usr/openv/netbackup/db is an NFS mounted file system? Did you do a disaster recovery test to see that you can recover the database and then restore files from the database? What is the size of your database? Does the database reside on a Netapp - if so did you attempt to also backup the database using NDMP? I would assume that this won't work well since on the one hand the database changes as the backup progresses, on the other hand, NDMP is backing up a snapshot which will not contain the information of this backup. Manny -----Original Message----- From: ilya.birman(a)abnamro.com [mailto:ilya.birman@abnamro.com] Sent: Friday, October 19, 2001 7:25 PM To: Manny Kaiser Cc: toasters@mathworks. com Subject: Re: Veritas Netbackup Database We did that. Veritas did not tell us not to do it. We have a enormous amount of data do backup so we had to migrate the NteBackup DB of local disk. So for no problem. The concern we had is that on normal backup you can direct Veritas to "Follow NFS". There is no such option on NetBackup Catalog backups. We were concern if the catalog will be backed up properly. As far as NFS not being reliable, I think that battle had been fought many years ago. Ilya "Manny Kaiser" <mkaiser(a)mmcnet.co To: "toasters@mathworks. com" <toasters(a)mathworks.com> m> cc: Sent by: Subject: Veritas Netbackup Database owner-toasters@mat hworks.com 10/19/2001 10:03 AM Has anyone placed the Veritas Netbackup database on an NFS mounted file system? More specifically on a netapp? I was just told by Veritas that they do not recommend doing this because NFS is unreliable. Any feedback would be helpful.

1 0

DLT 7000 question
by Rahul Kumar 20 Oct '01

20 Oct '01

Hi All, Can anyone tell me how to enable the compression on DLT7000 tapedrive attached to F740. I use a 40/80GB tape on the filer tape drive. The drive make is tandenberg . I usually see the drive compression led on. Is there any special option in dump command to reflect the compression.... right now i back up around 45 gb data.. but the dlt is asking to insert the second tape. the command which i issue to backup entire volume is (45gb---vol0) dump 0ufb rst0a 63 /vol/vol0 Rahul -----Original Message----- From: Manny Kaiser [mailto:mkaiser@mmcnet.com] Sent: Saturday, October 20, 2001 1:37 AM To: ilya.birman(a)abnamro.com Cc: toasters@mathworks. com Subject: RE: Veritas Netbackup Database Hi, did you test the ability to recover this database? Just to make sure I understand - /usr/openv/netbackup/db is an NFS mounted file system? Did you do a disaster recovery test to see that you can recover the database and then restore files from the database? What is the size of your database? Does the database reside on a Netapp - if so did you attempt to also backup the database using NDMP? I would assume that this won't work well since on the one hand the database changes as the backup progresses, on the other hand, NDMP is backing up a snapshot which will not contain the information of this backup. Manny -----Original Message----- From: ilya.birman(a)abnamro.com [mailto:ilya.birman@abnamro.com] Sent: Friday, October 19, 2001 7:25 PM To: Manny Kaiser Cc: toasters@mathworks. com Subject: Re: Veritas Netbackup Database We did that. Veritas did not tell us not to do it. We have a enormous amount of data do backup so we had to migrate the NteBackup DB of local disk. So for no problem. The concern we had is that on normal backup you can direct Veritas to "Follow NFS". There is no such option on NetBackup Catalog backups. We were concern if the catalog will be backed up properly. As far as NFS not being reliable, I think that battle had been fought many years ago. Ilya "Manny Kaiser" <mkaiser(a)mmcnet.co To: "toasters@mathworks. com" <toasters(a)mathworks.com> m> cc: Sent by: Subject: Veritas Netbackup Database owner-toasters@mat hworks.com 10/19/2001 10:03 AM Has anyone placed the Veritas Netbackup database on an NFS mounted file system? More specifically on a netapp? I was just told by Veritas that they do not recommend doing this because NFS is unreliable. Any feedback would be helpful.

1 0

Re: Veritas Netbackup Database
by ilya.birman＠abnamro.com 19 Oct '01

19 Oct '01

We did that. Veritas did not tell us not to do it. We have a enormous amount of data do backup so we had to migrate the NteBackup DB of local disk. So for no problem. The concern we had is that on normal backup you can direct Veritas to "Follow NFS". There is no such option on NetBackup Catalog backups. We were concern if the catalog will be backed up properly. As far as NFS not being reliable, I think that battle had been fought many years ago. Ilya "Manny Kaiser" <mkaiser(a)mmcnet.co To: "toasters@mathworks. com" <toasters(a)mathworks.com> m> cc: Sent by: Subject: Veritas Netbackup Database owner-toasters@mat hworks.com 10/19/2001 10:03 AM Has anyone placed the Veritas Netbackup database on an NFS mounted file system? More specifically on a netapp? I was just told by Veritas that they do not recommend doing this because NFS is unreliable. Any feedback would be helpful.

2 1

RE: Netapp hardware
by McCarthy, Tim 19 Oct '01

19 Oct '01

You can add 36s and 18s in the same volume. If you add them to the same RAID group, the *first* 36GB disk becomes the parity(needed for the extra stripes) and the 18GB parity becomes a data drive(they flip roles). However, it is in my opinion, better to just simply make a new RAID group with the 36GB disks. They will be taken fully advantage of (i.e. they will be 36GB disks). However, if your current volume is a Zoned Checksum volume, and you add the new 36GB(34F) disks, you will lose the benefits of the BCS disks and they will work like Zoned checksum disks. Chances are your current 18GB disks do not have the little yellow labels and are ZCS. So you may want to create a new volume with the 36GB disks unless they are BCS disks already. This is perfectly legal, it has been being done for a long time now. (mixing drives of varying sizes). The one thing to remember, the largest disk in the RAID group is *always* the parity disk, unless of course they are all the same size in the RAID group. --tmac Timothy A. McCarthy System Engineer Network Appliance Federal Systems INC. http://www.netapp.com <http://www.netapp.com> 410-290-1581 Office Page Me at: 877-5-NETAPP --> -----Original Message----- --> From: White, Lance [mailto:Lance.White@netapp.com] --> Sent: Friday, October 19, 2001 2:34 PM --> To: 'Viper Rinspeed'; toasters(a)mathworks.com --> Subject: RE: Netapp hardware --> --> --> 1)Yes...but you won't want to do this for an extended --> period as you'll only be using half of the 36GB as a spare --> if an 18GB drive fails. Hence, when you get your --> replacement 18GB drive, simply replace the failed 18GB --> drive (new drive will show up as a spare), then MANUALLY --> fail the 36GB drive so that the 18GB reclaims the role, and --> 36GB goes back into the spares pool. --> 2) Same issue as above...the 36GB drives will essentially --> become 18GB drives. Rather wasteful. You CAN do this, but --> you probably won't want to. --> 3) Not a performance or reliability issue...more of a --> "digital waste" issue. --> --> -----Original Message----- --> From: Viper Rinspeed [mailto:debian22@yahoo.fr] --> Sent: Friday, October 19, 2001 11:19 AM --> To: toasters(a)mathworks.com --> Subject: Netapp hardware --> --> --> Hi, --> --> We have a Netapp 740 with a FC9 shelf (18Gb disks). --> We are planning to get a DS14 shelf with 36Gb disks. --> I have two questions: --> 1- Can we use only one spare disk (36Gb disk) instead of two --> (1 18Gb and 1 36Gb)? Will the spare 36Gb disk be used correctly --> to replace a failed 18Gb disk ? --> 2- Can I mix 18Gb and 36Gb disks in the same volume (same RAID)? --> If yes, how the data will be written? Let's say, I have --> 2x18G+2x36Gb (+parity). --> Will the 36Gb disks stored twice more data than the 18Gb ? --> Is there a performance issue ? a reliability issue (more --> data written-> more --> risk of failure?) ? --> --> Thank you very much. --> --> Jn --> --> --> ___________________________________________________________ --> Un nouveau Nokia Game commence. --> Allez sur http://fr.yahoo.com/nokiagame avant le 3 novembre --> pour participer à cette aventure tous médias. -->

1 0

RE: "unrecognized error 0xb" -- correct slot for tape scsi?
by Toal, Dave 19 Oct '01

19 Oct '01

Steve, Unstable scsi bus, ok, thanks for the info. The dlt was originally on the filer's motherboard scsi; but now all combinations of cable, dlt, and filer I've tried are returning that error. 2 dlt's, 2 740's, mobo and pci scsi on both, 3 cables... no common bus in the tape library, it's all direct scsi. The dlt was checked first, but I asked netapp support to close the case when I discovered both 740's saw the same error. Time for another go-round with StorageTek, it looks like. Dave -----Original Message----- From: Parsons, Steve To: 'Toal, Dave'; toasters(a)mathworks.com Sent: 10/19/01 11:27 AM Subject: RE: "unrecognized error 0xb" -- correct slot for tape scsi? Dave, Fri Oct 19 02:03:10 GMT [isp_main]: Tape (1.0.0):cmdblk 0xfffffc0000e020f8 op 0xa block 64512 aborted command (b 47, 0) The numbers in parentheses are SCSI status, ASC, and ASCQ, respectively. According to the SCSI spec, the drive is aborting the command (b) because it detected SCSI PARITY ERROR (47,0). It denotes an unstable SCSI bus, and could be caused by the adapter, the cable, the tape drive, or termitator. (The "unrecognized" is just a hint from the filer that it wasn't one of the errors that the filer would attempt to recover from on its own.) Steve -----Original Message----- From: Toal, Dave [mailto:dave.toal@t-t.com] Sent: Thursday, October 18, 2001 7:58 PM To: toasters(a)mathworks.com Subject: "unrecognized error 0xb" -- correct slot for tape scsi? Folks, I've been trying to get an F740 filer to recognize a dlt for several weeks. The error it returns is below. This same error also happens on another filer, also a 740. DLT checks out ok, according to the StorageTek tech's dignostics box. Have tried swapping cables, and using different dlt's -- _always_ this "unrecognized error". The filer has been rebooted many times during this process. mt fsf, bsf, weof, &c all work ok, according to mt status, but all tape writes fail. -- Dave Toal unix person T&T, nq, MA statler> dump u0f nrst0a /vol/spool DUMP: Dumping tape file 1 on nrst0a DUMP: creating "/vol/spool/../snapshot_for_backup.0" snapshot. DUMP: Using Full Volume Dump DUMP: Date of this level 0 dump: Fri Oct 19 02:02:52 2001. DUMP: Date of last level 0 dump: the epoch. DUMP: Dumping /vol/spool/ to nrst0a DUMP: mapping (Pass I)[regular files] DUMP: mapping (Pass II)[directories] Fri Oct 19 02:03:10 GMT [isp_main]: Tape (1.0.0):cmdblk 0xfffffc0000e020f8 op 0xa block 64512 aborted command (b 47, 0) DUMP: Tape write failed. Fri Oct 19 02:03:10 GMT [isp_main]: Tape (1.0) unrecognized error 0xbunrecognized error 0xb. DUMP: DUMP IS ABORTED DUMP: Deleting "/vol/spool/../snapshot_for_backup.0" snapshot. statler>

1 0

RE: Netapp hardware
by White, Lance 19 Oct '01

19 Oct '01

1)Yes...but you won't want to do this for an extended period as you'll only be using half of the 36GB as a spare if an 18GB drive fails. Hence, when you get your replacement 18GB drive, simply replace the failed 18GB drive (new drive will show up as a spare), then MANUALLY fail the 36GB drive so that the 18GB reclaims the role, and 36GB goes back into the spares pool. 2) Same issue as above...the 36GB drives will essentially become 18GB drives. Rather wasteful. You CAN do this, but you probably won't want to. 3) Not a performance or reliability issue...more of a "digital waste" issue. -----Original Message----- From: Viper Rinspeed [mailto:debian22@yahoo.fr] Sent: Friday, October 19, 2001 11:19 AM To: toasters(a)mathworks.com Subject: Netapp hardware Hi, We have a Netapp 740 with a FC9 shelf (18Gb disks). We are planning to get a DS14 shelf with 36Gb disks. I have two questions: 1- Can we use only one spare disk (36Gb disk) instead of two (1 18Gb and 1 36Gb)? Will the spare 36Gb disk be used correctly to replace a failed 18Gb disk ? 2- Can I mix 18Gb and 36Gb disks in the same volume (same RAID)? If yes, how the data will be written? Let's say, I have 2x18G+2x36Gb (+parity). Will the 36Gb disks stored twice more data than the 18Gb ? Is there a performance issue ? a reliability issue (more data written-> more risk of failure?) ? Thank you very much. Jn ___________________________________________________________ Un nouveau Nokia Game commence. Allez sur http://fr.yahoo.com/nokiagame avant le 3 novembre pour participer à cette aventure tous médias.

1 0

Netapp hardware
by Viper Rinspeed 19 Oct '01

19 Oct '01

Hi, We have a Netapp 740 with a FC9 shelf (18Gb disks). We are planning to get a DS14 shelf with 36Gb disks. I have two questions: 1- Can we use only one spare disk (36Gb disk) instead of two (1 18Gb and 1 36Gb)? Will the spare 36Gb disk be used correctly to replace a failed 18Gb disk ? 2- Can I mix 18Gb and 36Gb disks in the same volume (same RAID)? If yes, how the data will be written? Let's say, I have 2x18G+2x36Gb (+parity). Will the 36Gb disks stored twice more data than the 18Gb ? Is there a performance issue ? a reliability issue (more data written-> more risk of failure?) ? Thank you very much. Jn ___________________________________________________________ Un nouveau Nokia Game commence. Allez sur http://fr.yahoo.com/nokiagame avant le 3 novembre pour participer à cette aventure tous médias.

1 0

RE: Veritas Netbackup Database
by Hubbard, Dan 19 Oct '01

19 Oct '01

Thats funny because I was just told by Veritas that this is a decent way of backing up ? Of course NDMP will be faster, but with the Solaris Vertias client / NFS its much cheaper (ie: no NDMP license needed). -----Original Message----- From: Manny Kaiser [mailto:mkaiser@mmcnet.com] Sent: Friday, October 19, 2001 10:03 AM To: toasters@mathworks. com Subject: Veritas Netbackup Database Has anyone placed the Veritas Netbackup database on an NFS mounted file system? More specifically on a netapp? I was just told by Veritas that they do not recommend doing this because NFS is unreliable. Any feedback would be helpful.

1 0

Veritas Netbackup Database
by Manny Kaiser 19 Oct '01

19 Oct '01

Has anyone placed the Veritas Netbackup database on an NFS mounted file system? More specifically on a netapp? I was just told by Veritas that they do not recommend doing this because NFS is unreliable. Any feedback would be helpful.

2 1

RE: "unrecognized error 0xb" -- correct slot for tape scsi?
by Parsons, Steve 19 Oct '01

19 Oct '01

Dave, Fri Oct 19 02:03:10 GMT [isp_main]: Tape (1.0.0):cmdblk 0xfffffc0000e020f8 op 0xa block 64512 aborted command (b 47, 0) The numbers in parentheses are SCSI status, ASC, and ASCQ, respectively. According to the SCSI spec, the drive is aborting the command (b) because it detected SCSI PARITY ERROR (47,0). It denotes an unstable SCSI bus, and could be caused by the adapter, the cable, the tape drive, or termitator. (The "unrecognized" is just a hint from the filer that it wasn't one of the errors that the filer would attempt to recover from on its own.) Steve -----Original Message----- From: Toal, Dave [mailto:dave.toal@t-t.com] Sent: Thursday, October 18, 2001 7:58 PM To: toasters(a)mathworks.com Subject: "unrecognized error 0xb" -- correct slot for tape scsi? Folks, I've been trying to get an F740 filer to recognize a dlt for several weeks. The error it returns is below. This same error also happens on another filer, also a 740. DLT checks out ok, according to the StorageTek tech's dignostics box. Have tried swapping cables, and using different dlt's -- _always_ this "unrecognized error". The filer has been rebooted many times during this process. mt fsf, bsf, weof, &c all work ok, according to mt status, but all tape writes fail. -- Dave Toal unix person T&T, nq, MA statler> dump u0f nrst0a /vol/spool DUMP: Dumping tape file 1 on nrst0a DUMP: creating "/vol/spool/../snapshot_for_backup.0" snapshot. DUMP: Using Full Volume Dump DUMP: Date of this level 0 dump: Fri Oct 19 02:02:52 2001. DUMP: Date of last level 0 dump: the epoch. DUMP: Dumping /vol/spool/ to nrst0a DUMP: mapping (Pass I)[regular files] DUMP: mapping (Pass II)[directories] Fri Oct 19 02:03:10 GMT [isp_main]: Tape (1.0.0):cmdblk 0xfffffc0000e020f8 op 0xa block 64512 aborted command (b 47, 0) DUMP: Tape write failed. Fri Oct 19 02:03:10 GMT [isp_main]: Tape (1.0) unrecognized error 0xbunrecognized error 0xb. DUMP: DUMP IS ABORTED DUMP: Deleting "/vol/spool/../snapshot_for_backup.0" snapshot. statler>

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

1997

toasters