Search results for query: *

Known Issue LGTpa59785. Contact Legato support. Regards Stefan

If you are running Exchange 5.5 and Exhchange module v.2, I would strongly reckommend upgrading module to v.2.0-005, if you not already have. All the previous versions of the v2 module has a nasty bug (LGTpa31300) making restore impossible under certain conditions.

I'm not quite sure what you mean. But I do know that the RepliStor Switch-Over feature does NOT work in a environment where the target is a MSCS cluster. This is per design, according to Legato Support.

I have seen this too. It is a known issue and as far as I know it is still unresolved. My only advise is to contact Legato support.

Could be because of a wrong newline charcter. I've seen the ^M thing on Windows text files in UNIX. Open the file in VI and remove them. Regards, StefanS

On your SQL Server, open taskmanager and check if there is any process instance of "nsrsqlsv.exe" still running. If so, kill it using "kill.exe". Then the backup process in SQL Server should die. Regards, StefanS

When using 6.1.2 we experienced problems with pools requesting tapes to be mounted at the wrong storage node. We had to revert back to v.6.1.1, which has been running very stable in our environment. Regards, StefanS

I'm almost certain that the problem is in the Exchange module. See my previous post. Regards, Stefan

What version of Exchange Module ? If your using v2 try updating to the latest version; v2.00-005. The release notes for version 2.0-005 mentions a bug which sounds like the problem you're having: "LGTpa30271: On a clustered Exchange Server, a backup could fail and log the following...

Make sure the jukebox is online and ready. Also check that everything is properly connected. Are you able to perform any jukebox operation (label/inventory/backup etc) ? Regards, StefanS

Hi, I just wonder if any of you people have any experiences of Networker Recovery Manager for NT? Is it any good? Whats your impressions? Is there any alternative software ? Where using Networker on Windows NT/2000 plattform and are interested in some kind of bare-metal recovery solution. Any...

Verify that Windows 2000 itself sees the tapedevices. If not, check cabeling, terminations and that everything is connected and powered on. Had the same error a long time ago when trying to perform any tape/jukebox operation. It turned out to be a SCSI connectivety error. Regards, StefanS

I think I've read somewhere (MS SQL Module manual?) that it needs to be the same version of MS SQL Server. Directed recover to another 7.0 SQL server should work just fine though. Regards, StefanS

Make sure the username you're logged in with is on the administrators list in Networker (Setup server) together with the hostname of the server you're logged on. For example: admin@destinationhost StefanS

Is there a firewall between the server & client? Do they have the same ports configured? StefanS

The file you specified seems to me like a database device-file (logdevice to be specific). These files are always in use by the SQL Server and can't be backed up from the filesystem by Legato, not even with the SQL Networker module, therefore the error 32. SQL Module works by connecting to the...

We are using Compaq hardware.

Ok. Keep us posted if they do come up with a fix for it. It's a rather nasty bug so they better fix it ASAP! There are probably lots of other people out there also affected, only they dont know it yet... I guess Legato wont tell them either since we havent heard anything from them about this...

Yes, without the consistency checks everything is fine. xbsa.messages contains no information. Regards, StefanS

Same problem occurs when backing up a Windows 2000 Server running Share Portal Server. Our workaround for this is defining a seperate client with saveset "C:\winnt\system32". Regards, StefanS