I cant see why this sould bee a problem for you. If there are index-savesets from group B,C & D in pool A, the only problem is that you have used some tape more tape than you really need..... Index's is so small and don't take much space on a tape so why bother...
If savesets from group A is...
Hmmmm.... I cant see why this shouldn't work... but why do you want to do that... why would you like to browse one clients index if it's impossible to recover the data.The data is located on the other servers backup tapes....
If you would like to move the server to a new one... use mmrecov...
Well.... this is a known issue. NetWorker is opening a port in the firewall during the start of the backup and is supposed to get some inforamtion from the client behind the firewall after the backup has been preformed (index and stuff).
The firewall isn't glad about this and is closing this...
Well.... this is a known issue. NetWorker is opening a port in the firewall during the start of the backup and is supposed to get some inforamtion from the client behind the firewall after the backup has been preformed (index and stuff).
The firewall isn't glad about this and is closing this...
jkalbus...
When you configure a backup-server you shouldn't use a certain pool for index and bootstraps.... you will get almost all bootstraps and index's on one single tape (they are not so large) and what do you think happends if you loose that tape and your backup-sever crashes? You can't...
lahrg...
You will have to check the volumes who haven't been recyclable as they should, probobly you will find a client who have savesets located on that volume who is still browseable.
Why are they still browseable?
Well... maybe you have removed a klient from the GUI but it has still some...
Hi,
If you recive something like this..... then you should upgrade your server to 6.0.3 or 6.1.1 since this is a known bug. (LGTpa30132)
Error encountered by NSR server `NW1': Bad or missing
record: saveset ID 1144599809, low water mark
139303368, current offset 139283040.
About that...
Hi,
I discovered this problem and logged a case with Legato..... This is the latest reply in this case.
My server is saying "Failed to create quota" so it might not bee the same problem, but Legato is having some problem with their 6.1.1 version on w2k that's for sure...
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.