We have the Push Agent. If by the open file agent you are referring to that Groupwise agent they have now - we don't haVE IT.<br><br>Anyway the backup issue has become a server issue now. A total length of about 4 hours like we have now is really an improvement for us. The problem now seems to...
We saw great improvements playing with the parameters suggested above - Thanks. BUT the server is crashing every morning around 4:30 to 6:00 A.M. - now AFTER the backup gets done.<br><br>It's not crystal clear obvious to us why this is happening. The performance improvements do not seem directly...
Groupwise is a separate server. Arcserve backs it up from our main file and print server, which I called SERVER above (it's the name in our tree too). We thought in the beginning this would be a through[ut problem in the main server, but the crashes suggest it's the Groupwise server the one...
In response to the question on the number of users and such: We have a network of about 250 users. And yes, we do a full backup nightly.<br><br>The problem with the parameters change on the server is that it worked for a while. We upgraded Arcserve and after latest patch was applied we were back...
We have a Groupwise server which gets backed up nightly from a Novell Arcserve application. Numerous support documents have been read and we have tried to apply all solutions found. It stills sits in there more than 10 hours every day - even after latest service pack was applied and everything...
We have a Groupwise server which gets backed up nightly from a Novell Arcserve application. Numerous support documents have been read and we have tried to apply all solutions found. It stills sits in there more than 10 hours every day - even after latest service pack was applied and everything...
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.