1) Sounds like you’re hitting the limit for number of jobs that can be run at once. I don’t remember what the default number is, but if you’re inside the networker console go to the configuration tab, right click on your networker server and go to the setup tab. Under the backup section there is a parallelism that can be increased. This number is the total number of save streams the networker environment can run at once. Increase this number then retry your backup. The tuning and admin guide will give some insight on parallelism, cause it can get kinda messy.. ☺
2) It could also be waiting on writable devices. If you’re writing your oracle backups and other backups to the same pool on the same set of devices it’s possible you could be running into this issue. The fix there would be to add more devices to the pool, or adjust the group parallelism
Another thing is to check the device stream settings (default is 4). The fact that once you stop one group the other runs fine suggests it is a either a device settings or Server Parallelism setting. So recheck the following attributes on your Backup Server.
1.) Properties when highlighting the Backup Server on the configuration Tab or the Devices tab.
2.) Increase it on the client for the Backup Server itself.:
3.) The Properties on the device as seen on the Library.
I wanted to update this, because I know how frustrating it is when an issue is resolved and the original poster does not reply to update the status. This has been fixed, even if the parallesim were changed (which did not fix the issue). The issue itself was that the NetWorker was not reading the drive where the data was being stored to backup, so the virtual drive was disconnected. I checked the disk management and was worried because I had a notification next to the virtual drive that it was unrecognizable and unreadable. My boss and I fought with this issue for a few days before we decided to just power down the SAN unit that hosted the drive, unseated and reseated the drives one by one, and then powered on the SAN unit again and low and behold there was the drive again. Backups are running now and I want to thank you for your replies and shared information. They did not work, but it is still information that should be documented and recorded for PM measures, so thank you!
cmartinjr
40 Posts
1
October 15th, 2012 07:00
Hello,
This could be a couple of different things:
1) Sounds like you’re hitting the limit for number of jobs that can be run at once. I don’t remember what the default number is, but if you’re inside the networker console go to the configuration tab, right click on your networker server and go to the setup tab. Under the backup section there is a parallelism that can be increased. This number is the total number of save streams the networker environment can run at once. Increase this number then retry your backup. The tuning and admin guide will give some insight on parallelism, cause it can get kinda messy.. ☺
2) It could also be waiting on writable devices. If you’re writing your oracle backups and other backups to the same pool on the same set of devices it’s possible you could be running into this issue. The fix there would be to add more devices to the pool, or adjust the group parallelism
Thanks.
danag2
20 Posts
0
October 15th, 2012 13:00
Another thing is to check the device stream settings (default is 4). The fact that once you stop one group the other runs fine suggests it is a either a device settings or Server Parallelism setting. So recheck the following attributes on your Backup Server.
1.) Properties when highlighting the Backup Server on the configuration Tab or the Devices tab.
2.) Increase it on the client for the Backup Server itself.:
3.) The Properties on the device as seen on the Library.
4.) Group Parallelism Settings
ALFNetworker
1 Rookie
•
31 Posts
1
October 18th, 2012 07:00
I wanted to update this, because I know how frustrating it is when an issue is resolved and the original poster does not reply to update the status. This has been fixed, even if the parallesim were changed (which did not fix the issue). The issue itself was that the NetWorker was not reading the drive where the data was being stored to backup, so the virtual drive was disconnected. I checked the disk management and was worried because I had a notification next to the virtual drive that it was unrecognizable and unreadable. My boss and I fought with this issue for a few days before we decided to just power down the SAN unit that hosted the drive, unseated and reseated the drives one by one, and then powered on the SAN unit again and low and behold there was the drive again. Backups are running now and I want to thank you for your replies and shared information. They did not work, but it is still information that should be documented and recorded for PM measures, so thank you!