Search results for query: *

Ladies and Gents, I need some help!!! Can someone confirm to me that it is a Vert Bad Idea to have multiple instances of the same client in one group? To explain, one group called "ALL" with 9 instances of client "Client 123" is it, all running differant savesets. I could...

Try this: 1. Stop the NetWorker services (daemons). 2. Delete all files and subdirectories within the \nsr\tmp directory. 3. Ensure that full access of the \nsr\tmp directory is given to all users (groups) that operate NetWorker. 4. Restart the NetWorker services (daemons).

You don't say exactly what your problem is, is it backing up or recovering? If its a backup issue, try running a save from the client. If this works then there is more than likely a name resolution problem between server and client. If the save fails, then the problem is between client and...

Will be cheaper to upgrade! :-)

Funny one this.... Server is AIX 5.2 (32bit) Networker 7.0 Fresh install of OS with all patches Fresh install of Networker server run /etc/rc.nsr start nsrexed X 2 starts fine nsrd will not start No errors in any log files if nsrd is started by hand it tells me that nsrexecd must be started...

I have three XP Pro machines connecting to the internet through a forth XP Pro machine. All machines have the latest patches etc. and all are running Norton Internet Security which is also fully up to date. All machines can see each other for most of the time with no problems at all. In the past...

What Fibre cards are you using, and are you running mini-port or port drivers?

I have a Networker 6.2 server on NT4 When I recover files to a client, it creates two files, one in upper case letters, and one in lower case letters. I have set the following environment variable and done the recovery. NSR_DISABLE_POSIX_CREATE=yes But still no joy. Any Ideas?

I have a small problem! Solaris 8 Networker Server running 6.1.2 Netware 5 Clients running 4.2.1 All Networker machines are fine, but Netware Clients that are NOT Networker Clients seem hang up (not abend) due to RPC packets from the Networker machines. The Packet Buffers on these machine have...

The problem with the indexes may be down to a feature of Networker. The Indexes should have the same retention as the savesets from that client in the group. However if the networker server is not one of the clients in that group all the Indexes for all the clients in that group get a years...

I have been playing with with nsradmin, enabling and disabling devices. Does anyone know how to do this direct from the command line? You would save my life!

NT4 server Networker 6.1.2 Fibre attached Jukebox Inquire -l will show all drives and arm Inquire shows only drives jbconfig or jbconfig -l blue screens storage node. I have tried this on three machines all with the same results, the server is fine however. Any ideas, this is driving me mad!

mmrecov restores the media database to the directory location of that install of networker: Old machines install path /opt/nsr/mm New machines install path /nsr/mm So a an mmrecov run on the new machine will place the media database in the New machines mm folder, however the res.r folder...

The Gents are correct, the only way to recover the data is to use a DR company...

Thanks, worked like a charm!

I have a Win NT Networker server running 6.1.1 Attached to it are two Jukeboxes, one fibre-channel on an LP8000 card, the other scsi on an adaptek 29160. Both Jukeboxes run DLT7000 drives, but the Fibre-channel unit writes to tapes with a block size of 128k and the scsi at 64k. How can I get...

I am getting nowhere fast with this, anyone else had any joy?

Anyone seen this before: MSEXCH:IS Non-cluster environment on node PECKHAM. MSEXCH:IS MSEXCH:IS Backing up Microsoft Exchange Information Store ... MSEXCH:IS HrBackupGetDatabaseNames: The Restore process is already in progress. MSEXCH:IS MSEXCH:IS svmain.c(930): process_is_backup() =...

Getting the following when trying to backup, anyone seen it before: * server:MSEXCH:IS Non-cluster environment on node PECKHAM. * server:MSEXCH:IS * server:MSEXCH:IS Backing up Microsoft Exchange Information Store ... * server:MSEXCH:IS HrBackupGetDatabaseNames: The Restore process is already...

The pathownerignore is a workaround for cluster backups. On each of the physical nodes in the cluster, create a file called "pathownerignore" with no extension and place it in the /bin directory. The pathownerignore file should be empty, it is just a marker file. This should solve...