similar to: Symantec Backup Exec (formerly Veritas) agent

Hi I've suddenly lost access to some permanent cross-server shares. I think this was following the Nov 5 new kernel, rather than the Centos version upgrade. I don't see any difference to man mount.nfs I have:- [root at hs6 ~]# mount hs8:/data /sysback/hs8-data -v mount: no type was given - I'll assume nfs because of the colon mount: trying 172.26.0.8 prog 100003 vers 3 prot tcp port

I thought this had been fixed with newer kernels? We have an old Maxtor Snap Server, an 80 GB NAS unit, containing some of our archives. Both of our CentOS servers have it permanently mounted by NFS for convenient access. This weekend, I discovered remotely that, although all systems except the VRTSralus remote agents for Veritas (now Symantec) Backup Exec were working just fine, both servers

Hi I get this on every scan report:- LibClamAV Warning: *********************************************************** LibClamAV Warning: *** This version of the ClamAV engine is outdated. *** LibClamAV Warning: *** DON'T PANIC! Read http://www.clamav.net/support/faq *** LibClamAV Warning: *********************************************************** ----------- SCAN SUMMARY

Hello, I'm trying to calculate non-parametric probabilities using the np package and having some difficulties. OS is Windows, R version 2.11.1 Here is what I've done so far. library(np) veg <- data.frame(factor(Physiogomy), meanAnnualDepthAve, TP) attach(veg) : for clarification dim(veg) returns 1292 3 fy.x <- npcdens(veg$factor.Physiogomy ~ veg$meanAnnualDepthAve, nmulti=1) #

Hello, I tried to post this earlier, but it seems that it did not appear on the list. If you've rec'd 2 m I'm trying to calculate non-parametric probabilities using the np package and having some difficulties. OS is Windows, R version 2.11.1 Here is what I've done so far. library(np) veg <- data.frame(factor(Physiogomy), meanAnnualDepthAve, TP) attach(veg) : for

I am having difficulty understanding how I would constrain a data set by filtering out 'records' based on certain criteria. Using SQL I could query using 'select * from my.data where LithClass in ('sand', 'clay')' or some such. Using subset, there seem to be ghosts left behind (that is, all of the LithClass *.Labels* remain after subset) > dput(tcc)

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I'm setting up a new mailserver with postfix and Dovecot. I'd like to prepare a skeleton for the users maildir to create i.e. a spam folder and a sieve file per default. Is there any chance to realize this with dovecot? Regards Sebastian - -- Sebastian Ganschow K?nigsberger Str. 17 45770 Marl Germany Phone: +49 2365 9 24 96 76

Hello. Has this been tried by anybody? I would appreciate any practical feedback on a setup where Dovecot was clustered with Veritas software. Best regards, Dmitrij Malakhov

Hi, I''m aware that if we talking about DMP on Solaris the preferred way is to use MPxIO, still I have a question if any of you got any experience with ZFS on top of Veritas DMP? Does it work? Is it supported? Any real life experience/tests in this subject? Regards, sendai -- This message posted from opensolaris.org

Hi all, How to dtrace a who is writing a veritas volume? Thanks. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20070412/dfd8c254/attachment.html>

Hi, gang, There have been numerous postings, scattered across various Internet forums (including this one), about problems encountered using Veritas Backup Exec 8.6 and higher with Samba-sourced shares from *nix servers. In my particular case, I have a Windows NT Server 4.0-based backup system, which is supposed to be able to back up the other Windows systems on the LAN, plus several SPARC boxes

Hi all, Wondering if anyone can help me here? Having just upgraded from Samba 3.0.2a to Samba 3.0.4, I've found that Veritas Backup Exec 8.6 is no longer able to browse my shares. A quick "make revert" and everything is back as it should be. The things I see in the samba log are like this: [2004/05/19 12:46:40, 1] smbd/service.c:make_connection_snum(619) titanium

I figured out a previous issue to allow you to connect veritas BE to a samba system. You basically just defind a c$ share, and it was happy (Veritas BE version 8.5 Rev 3572) Now, I cannot get the user defined share to connect for the life of me anymore. The backup user can connect using windows shares, but within the application, I'm out of luck. It keeps asking for a username/password

On Mon, Jul 03, 2000 at 02:48:59PM -0700, Richard Fox wrote: > > Running the SAMBA that is released with RedHat 6.2, Veritas Backup Exec > 8.0 does not work. However, when running the latest dev version of SAMBA > Backup Exec does work. What files were changed to fix this bug? I would > like to update what I am running without having to go to the dev version. > > I have

We installed BMR boot server version 6.0 on DELL server. This DELL server have CENTOS 3.7 in it. We got error message when we tried to use "bmrsrtadm". Anyone know how to fix it or work around? ./bmrsrtadm Select one of the following options: 1. Create a new Shared Resource Tree. 2. Create a new CD image based Shared Resource Tree. 3. Copy an existing

Subject of the message: Re: Your music Recipient of the message: Jenny Ong Pei Pei Prohibited attachment: mp3music.pif ---------------------------------------------------------------- Privileged/Confidential Information may be contained in this message. If you are not the addressee indicated in this message (or responsible for delivery of the message to such person), you may not copy or

Please contact your system administrator. The scanned document was QUARANTINED. Virus Information: The attachment details.zip contained the virus W32.Netsky.P@mm and could NOT be repaired. The attachment details.zip(data.rtf .scr) contained the virus W32.Netsky.P@mm and could NOT be repaired.

Dear Symantec Customer, E-Mail technical support is not available for your product. However, Symantec offers a wide variety of online and telephone support options including technical tips, frequently-asked-questions documents, fax-on-demand documents, and an online knowledgebase with every known issue regarding your Symantec software. For a list of these options, please refer to your product

Please contact your system administrator. The scanned document was QUARANTINED. Virus Information: The attachment document09.scr contained the virus W32.Netsky.P@mm and could NOT be repaired.

Hi: I get emails with *.FXM files attached that are faxes forwarded by WinFax Pro. The message attached says to download Miniview.exe from the Symantec web site which I did and it appears to run in under WINE except that the faxes show up in black. Curiously when I laterally resize the viewer I can view the fax but as soon as I stop resizing it the fax reverts to a blaxk screen. I attempted to