UNSOLVED
Problem when backing up to disk
Hi,
we have a dedicatedstorage node with Networker 7.3.2 using a backup-to-disk device (mounted as drive s:\b2d and connected via fibre channel). When backing up data we get the following error:
Jan 9 13:32:00 < > root: [ID 702911 daemon.notice] NetWorker media: (emergency) Cannot write to s:\b2d\07\14\d3f0b333-00000006-50a3205d-45a3205d-12b10000-0a018832 - errno=22
The error occurs always after backing up about 188GB of data so it doesn't seem to be a connectivity issue. Can anyone explain what the error number means? There are no more informations in any Logfile on nw server and storage node.
PS: Have the networker 7.3.2 release notes been updated after jumbo release or are there no jumbo release notes? I would be interested in a list of fixed issues in jumbo before applying the patch to our environement. The latest version I found on powerlink is from Dec 4th.
Thanks.
we have a dedicatedstorage node with Networker 7.3.2 using a backup-to-disk device (mounted as drive s:\b2d and connected via fibre channel). When backing up data we get the following error:
Jan 9 13:32:00 < > root: [ID 702911 daemon.notice] NetWorker media: (emergency) Cannot write to s:\b2d\07\14\d3f0b333-00000006-50a3205d-45a3205d-12b10000-0a018832 - errno=22
The error occurs always after backing up about 188GB of data so it doesn't seem to be a connectivity issue. Can anyone explain what the error number means? There are no more informations in any Logfile on nw server and storage node.
PS: Have the networker 7.3.2 release notes been updated after jumbo release or are there no jumbo release notes? I would be interested in a list of fixed issues in jumbo before applying the patch to our environement. The latest version I found on powerlink is from Dec 4th.
Thanks.
397
0
Posted January 11th, 2007 05:00
Well, as I posted in my first message the backup was broken after around 188 GB. This is much more than the 32 GB limit you are describing... Full backups of the same dedicated storage node to the same backup to disk device have been working for several month (full and incremental). I tried staging all savesets, unmounting the tapes, formatting the device and re-mounting the (virutal) device tape. The restarted backup operation is still running so I can't tell if the problem is solved now. I'll keep you up to date.397
0
Posted January 11th, 2007 05:00
Hi, have you set the filesystem blocksize (or whatever windows calls it) large enough to create the saveset? We have found that the standard blocksize will not be usable for networker as that stops at about 32GB filesize and usually saveset (especially full backups) are significantly larger than that.
397
0
Posted April 4th, 2007 03:00
I got the same problem as you described.
Do you find the solution?305
0
Posted April 4th, 2007 06:00
What disk do you use?397
0
Posted April 4th, 2007 06:00
I also have experienced this problem with Backup to disk. It is almost like it hits a bad disk sector or something. I have seen it resolved only by rebooting. Unfortunately the server in question is the storage node and also the client, so I don't know if its a Backup to Disk problem or Disk Array problem.
I have had nothing but headaches since Backup to Disk. And in my case it writes at the same speed as tape even though its connected via Fibre.305
0
Posted April 4th, 2007 07:00
Clariion CX300 with a dedicated RAID 3 LUN. Drives are 500GB ATA in a DAE2.305
0
Posted April 4th, 2007 08:00
I was never able to get good speed with ATA disks... they are fine for slow clients, but if you are looking for solution which would give you speeds above tape then forget ATA.305
0
Posted April 4th, 2007 08:00
What about 300GB Fibre Channel drives? I have an array of those. Only problem is production directories reside currently on the FC's. Would require some downtime to switch'em.169
0
Posted April 4th, 2007 09:00
FC should give you better results, especially if you have multiple streams towards or from those devices.
ble1
6 Operator
•
14354 Posts
•
56186 Points
397
0
Posted January 10th, 2007 13:00
updated after jumbo release or are there no jumbo
release notes? I would be interested in a list of
fixed issues in jumbo before applying the patch to
our environement. The latest version I found on
powerlink is from Dec 4th.
Yes they were. If you check LGTpa list of fixed issues for 7.3.2 you will noticed that new LGTpas addressed by jumbo have been added on top of the list. For full list contact your support. I must say I do not support it in a way as it was done which I also stressed out to some EMC people recently.