Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
NetWorker 6.02 bug fix! 2
- Thread starter ag100
- Start date
- Status
-
1
- Thread starter
- #3
-
1
- #5
- Thread starter
- #6
Hi,
I discovered the bugs during testing, and yes, I have applied the new binaries, and confirmed it fixes the problems.
The "pending bug", causes alerts and other messages to stay in the pending window on the nwadmin screen. It was getting pretty annoying when NetWorker was up for more than a few weeks and there were 100+ messages in the pending window.
-ag100
I discovered the bugs during testing, and yes, I have applied the new binaries, and confirmed it fixes the problems.
The "pending bug", causes alerts and other messages to stay in the pending window on the nwadmin screen. It was getting pretty annoying when NetWorker was up for more than a few weeks and there were 100+ messages in the pending window.
-ag100
Do you have any idea who you talked to at legato to get these binaries? Any tracking info or open call number? I am desperate to get these fixes. My support company cannot find any info on these and they are being snowed by the legato folks.
Thanks for your help
Thanks for your help
- Thread starter
- #8
Be forewarned. They "forgot" to include a lot of fixes in 6.1 that were included in 6.0.2. I have three specific issues that were addressed in 6.0.2 that were still problems in 6.1. When I called for support, I was told that the fixes were left out and would be reincluded in 6.1.1.
I was also told to revert to 6.0.2 if I needed immediate fixes. How's that for good quality control on a product?
I was also told to revert to 6.0.2 if I needed immediate fixes. How's that for good quality control on a product?
- Thread starter
- #10
- Thread starter
- #11
1. Repeated mount requests that are canceled by the server. This can go on for 20 minutes before the Netware recovery starts working, even though the tape has been in the drive and mounted the entire time.
2. Miswritten media database. The only workaround is to remove the volume and rescan it back into the database. That's only a 4 hour operation.
3. "Missing" volumes and files in the Netware index. The only recovery option is to know it's missing and manually select it using "change selecton". If you don't know it isn't visible, you have to wait until the volume is recovered, then go back and look for what isn't there.
and one more:
I have a client with 25 savesets. All 25 are in the worklist, but only 21 are backed up. There isn't even an error message stating that some weren't worked. I only found this when I started scrutinizing my backups heavily due to restoration problems.
You'll notice that these are all recovery issues except the last one. Unless you do a lot of restores, you won't see them all very often, if at all. We maintain multiple QA and Development environments that are kept current and clean through restores. That's why I see them so often. Imagine your server crashing hard requiring a full restore, but you can't restore it because the database is corrupt, or the restore just didn't find the files. That means even more down time and angrier executives. That's not something I like to think about. Fortunately, I didn't make the decision to go with Legato, but unfortunately, I have to deal with that other person's decision.
2. Miswritten media database. The only workaround is to remove the volume and rescan it back into the database. That's only a 4 hour operation.
3. "Missing" volumes and files in the Netware index. The only recovery option is to know it's missing and manually select it using "change selecton". If you don't know it isn't visible, you have to wait until the volume is recovered, then go back and look for what isn't there.
and one more:
I have a client with 25 savesets. All 25 are in the worklist, but only 21 are backed up. There isn't even an error message stating that some weren't worked. I only found this when I started scrutinizing my backups heavily due to restoration problems.
You'll notice that these are all recovery issues except the last one. Unless you do a lot of restores, you won't see them all very often, if at all. We maintain multiple QA and Development environments that are kept current and clean through restores. That's why I see them so often. Imagine your server crashing hard requiring a full restore, but you can't restore it because the database is corrupt, or the restore just didn't find the files. That means even more down time and angrier executives. That's not something I like to think about. Fortunately, I didn't make the decision to go with Legato, but unfortunately, I have to deal with that other person's decision.
- Thread starter
- #13
Hmm.. Let see what can be adderssed here...
I do perform a lot of restores, but I don't run too many NetWare clients so I can't say I've had to deal with too many of the issues you speak of...
As for tapes being miswritten to the media database.. I haven't seen this problem in 6.1 I know this was a major issue from NetWorker 6.0 Is your 6.1 server an upgrade from 6.0? Do you know if this is related to that bug? If so, I know the data is on the tape, it's just a bit harder to restore.
As for your work list issue.. Why do you list 25 save sets in a client? ( I agree, you should be able to).. Why not just use the "All" save set? If you're looking to improve backup speed, I would create 3 or 4 client profiles with 3 or 4 schedules and list the save sets individually within the client profiles (split them out to 8 save sets per client). This would allow you to control which save sets get backed up at which levels on which days, without dealing with a lot of directives.
Hang in there.. There aren't a lot of good products with great cross platform support. Overall, while I don't love Legato's support, I do like their product. They have a few bugs, but so do most!
Good Luck!
-ag100
I do perform a lot of restores, but I don't run too many NetWare clients so I can't say I've had to deal with too many of the issues you speak of...
As for tapes being miswritten to the media database.. I haven't seen this problem in 6.1 I know this was a major issue from NetWorker 6.0 Is your 6.1 server an upgrade from 6.0? Do you know if this is related to that bug? If so, I know the data is on the tape, it's just a bit harder to restore.
As for your work list issue.. Why do you list 25 save sets in a client? ( I agree, you should be able to).. Why not just use the "All" save set? If you're looking to improve backup speed, I would create 3 or 4 client profiles with 3 or 4 schedules and list the save sets individually within the client profiles (split them out to 8 save sets per client). This would allow you to control which save sets get backed up at which levels on which days, without dealing with a lot of directives.
Hang in there.. There aren't a lot of good products with great cross platform support. Overall, while I don't love Legato's support, I do like their product. They have a few bugs, but so do most!
Good Luck!
-ag100
- Thread starter
- #15
- Status
Similar threads
- Locked
- Question
