Video Screencast Help

Added Media Server

Created: 20 Nov 2012 | 8 comments

Just added a media server to a backup environment that has 4 other media server. Set up local disk storage and it duplicates to two Data Domain systems. Since adding this new media server, none of the back up policies want to go to the other (older) Media servers and all backups try to run off of one Media server. The only way I have found to get the other Media Servers back into the mix is to remove the New one from the Storage Unit Group Group. Once that is done policies start to attach to other Media servers. Any help would be greatful thank you in advance to all.

Comments 8 CommentsJump to latest comment

Marianne's picture

So, you have a Storage Unit Group?

What is the selection criteria for the STUG and in which order are the STU's listed?

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

Nagalla's picture

when you add the media server STU to the stoarge unit group what the selection critiria you selected.. ?

Prioritized

Failover

Round robin

Load balance

you may need to select Round robin,Load balance to make use of all storage units.. 

 

 

Source :-Netbackup admin guide.
 
Storage unit selection criteria within a group:-
The storage unit selection criteria determines the order that storage units are selected when they are included in a group. Choose from one of the following selection criteria.
Prioritized
NetBackup chooses the first storage unit in the list that is not busy, down, or out of media. Also, the storage unit must not have reached the maximum concurrent jobs setting. When one of the specified conditions occurs, the next storage unit in the list is examined until NetBackup finds an available storage unit. If one is not available or if one does not have enough available space, the job fails and is not queued. (Default.)
Failover
NetBackup chooses the first storage unit in the list that is not down, out of media, or full. If a storage unit is only busy, the policy waits to write to it. The other storage units are used as failovers.
NetBackup queues a job to wait for the first storage unit if the maximum concurrent jobs setting is reached.
Round robin
NetBackup chooses the least recently selected storage unit in the list as each new job is started. If a storage unit is not available, or if no unit has available space, the job fails and is not queued. NetBackup does not continue to select the same storage unit.
Load balance
The Load balance option allows NetBackup to select storage units based on a capacity-managed approach. NetBackup avoids sending jobs to busy media servers.
The selection is based on the following factors:
Mark_Solutions's picture

Load Balanced was my thought too ... the new server probably has way more processing power and memory as well as available disk space so wins every time a job gets submitted

Try round robin or limit the number of jobs per storage unit if you can to force jobs to go elsewhere

Hope this helps

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.

OnRappell's picture

As of a little while ago we had it set to Prioritize. Tried it with the new MS at the bottom of the list and then at the top. No change. Changed it to Load Balancing a little while ago to see if that made a difference. Still have not seen much change. And yes it is in a STUG and at the bottome of the list. On the new Media server it has the same processing and memory as the other with 3tb of Drive space, the other have about 8tb of drive space available. The other weird thing that happened as well was when I added the new media server to the clients it wiped out all other media servers that were available. I have been going back to add the old media servers to available media servers. Just an FYI when I added the new media server to the clients I did it in mass and not one at a time? Could that have been the problem?

Mark_Solutions's picture

If you wiped the other media servers out then they would no longer be valid for backups - you may find that your jobs are actually retrying until they got to the new (and only valid) media server before they worked

This would possibly not be obvious without looking at the detailed job status

Of course if your master was included when you did this if may have removed the others as valid media servers from the master too - then it would only have one to choose from!

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.

OnRappell's picture

Well tryed the load balancing and seems I am getting the same results. Should I stop and start services or even reboot the server so that changes take full effect??

Marianne's picture

Try to stop and start NBU on the master server.

I have also had success with this command after making changes to STU or STUG in a busy environment where it was not possible to restart NBU:

nbpemreq -rereadconfig

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

Mark_Solutions's picture

I would go for round robin and then you do not need to reduce the number of streams but do make sure all storage units have the same number of streams to keep it balanced

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.