NetBackup treats every server the same. It does not do a short cut just because the server doing the backup happens to be the same as the one being backed up. It checks and validates each server before it backs it up, to do this it goes out onto the network. So to the server being backed up and...
If NetBackup is not happy with the drive for any reason then it will down it. This could be anything wrong with the drive even the fact that it is not the same as original drive. Which is why I say delete the details from NB and start fresh. You might want to do the same with the robot.
Quick test can you backup from the destination server?. This will prove the setup. If it can then the issue is restore related, if not then the whole set up has a problem. Once you know this then you know where to look for the fix.
That is a big question and prompts the responce what did you realy want to see. NB is not one of the products that likes to show a list of every single file it backed up. It comes more from the approch that it will show every file it could not back up and you have to belive that the rest have...
As yourself this question 'why am I using a retention of 2 months when I want to be able to restore in 2 years time'.
The set up you have is not the easiest. For a start you are running the risk of having the fullbackups and quarterlies write to the same tape. This means that you will have to...
Have you compared "the expiry date of the physical volume in the volume database" and "the expiry date of the media in the media database" are they the same?
"but the tapes will never expire from the media database, so we'll end up with lots of tapes sitting there, with no valid backups on...
Don't confuse the expiry of the images with the expiry of the tapes. You have done the correct thing. When the expiray of the images was changed then the tapes would need to change to ensure they don't expire before the images. But when you changed the images back again there is no process which...
Was the database backed up off of server A with an agent and do you have that agent loaded on the target server B? Normally get that error when netbackup can't connect to the client deamon or agent
NetBackup treats all clients the same no matter how mighty they be or were they are. All conections are via the network to ensure that authentication is completed. However when the backup runs the data will not be routed via the network.
We are going to have some big changes here, which mean that the old media servers will disapear and some new ones created. Of course I will need to still restore the old tapes for at least a year. This is going to involve thousands of tapes moving into new libraries. It's all a solaris 9...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.