Search results for query: *

Nothing to add, except that DLT8000 are "supposed" to hold up to 80 gb (supposed).

Savegroup Killer ! ;) You can use nsradmin to stop the group from the CLI ... you don't need to kill him.

You don't have a huge amount of data to backup, VXA-2 is a cheap solution and offers nice throughtput and media capacities. It should be enough. I don't have a lot of feedback regarding VXA problems, so no news is good news !

It means that you have a small problem ... ;) I've seen "exit code 3" with Notes databases that were not upgraded to the last patch level. Have you tried a manual backup from the client side ? Have you specified a remote user/password in the client ressource ? (or modified the client...

I've currently no idea of what your problem might be but ... have you take look at rights ? Maybe you could try to start the Networker Remote Exec service as "Domain Administrator" instead of localsystem and then try to backup again. It could be a nice test ...

What do you want to install a backup client or a backup server ?

Just to say its better to wait for next release ... I'm not Nostradamus !

... And it's better to wait for the 7.2 on windows platform (it has been removed from the website because they're some problems...(installation/ndmp...)

It really looks like a local directive were created. Have you searched for "nsr.dir" files on that client ?

Or if this client has multiple NIC's. One well configured and not the other one... (try to avoid autonegociation as much as possible ... it could decrease the throughtput by 10 sometimes).

It must not be writing to tape but you'd better try to stop/restart services on that Networker client. Because the backup session has not been cleanly closed. If you backup at the same time, one of the both must take the network bandwith (I don't think so) or overload the client. If you backup...

I don't think so... Master and media could share the library, the drives ... but not the media.

It also happen sometimes that the backup session is not properly killed... an easy answer would be "Upgrade to 6.1.3" its a really stable version.

This error happens when you backup something that takes a very long time... (such as thousands of small files) or when the Network connection has really poor throutputs... You could bypass it by increasing the savegroup timeout (on the the group ressource) or even disabling it (set it to 0).

It really looks like a name resolution issue. Try to add all known host name (FQDN) in the leaward Client's aliases field (within Networker). The fact that you can backup from the client go in that way...

Cold backups ?

You don't loose any feature (in both cases). Performance will be very good as long as you use a powerfull enough server (depends on many things).

Could you try a "savegrp -vvv GRP_NAME" from the server, it should be more verbose. You could also check that this client is really using "servers" file and not starting directly with a "nsrexecd -s servername" (with ps -ef| grep nsr). But it really looks like a...

I also agree, it works really well under Windows 2000. For the same reasons that PGPhantom.

There's maybe a difference with drive firmware levels ... It's not absolutly necessary to get those serial numbers (but it's easier to configure later). If you need it to configure devices within Netbackup, try to do it with SCSI ID. Match the physical slot of the drive with its SCSI ID, then...