similar to: Samba and Seagate BackupExec

Hi, I'm searching for 2 months on this problem (I've searched in the archive of course and I've sent a message on this mailing list, the suggestions had helped me but I didn't manage to resolve the problem). The problem: ------------ I've got Samba 2.0.2 on a Linux Red Hat 5.2 and a server NT4 SP3 with Seagate BackupExec 7.0. When I want to backup Samba with Seagate

Hi, I've got Samba 2.0.2 and a server NT4 SP3 with Seagate BackupExec 7.0. When I want to backup Samba with Seagate BackupExec, I get a message saying "Unable to connect to server, <F5> to retry", and then another one saying "A device specific error occured". I've read all the Samba archive about that subject, but I do not find any solution. I don't

Hi Franck, to my knowledge, the Backup Exec service "runs" under a certain user. In most cases it is the user who installed it, so very often "Administrator". Now if you try to backup a Samba share, Backup Exec tries to retrieve the files of this share and has to authenticate to the Samba Server. I suspect it will do this with the "credentials" of the user the Backup

--- samba@samba.org wrote: > SAMBA Digest 2218 > > For information on unsubscribing see > http://samba.org/listproc/ > Topics covered in this issue include: > > 1) > by "Brandon Schnell" <brandonschnell@hotmail.com> > 2) AutoCAD R14 and Eagle Point > by Hank Burton <wburton@literati.com> > 3) Can't locate point and

Hi, I have a problem with the Parameter map system and map hidden. I have both activated, but when I change it under Win9x oder NT it doesn`t change anything and dont write the maping on the x-Bit of group and world. When I change it by hand "chmod go+x *" it shows the correct maping but when I save it it`s gone again. I thought maybe it came from the WinNT support and deaktivted nt

Hi, Does anyone have experience with BackupExec and Samba? BackupExec refuse to access Samba shares. Windows shares are OK, but all my Samba shares are not. I have Samba on at least 2 Linux 2.4 machines + 1 on Solaris. Neither ones work with BExec. Any idea? Other have experience with BExec and Samba? Thanks a lot -jec _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Jean-Eric Cuendet

Hello, I've compiled and configured Samba 1.9.18p8 on a DEC Alpha running DEC Unix 4.0b for the express purpose of enabling a Windows NT 4.0 server running Seagate BackupExec software to be able to see my Unix filesystems as NT shares and back them up (as of this time BackupExec does not support DEC Unix clients). Test backups have worked OK, but I'm having problems restoring the

Is there an improved BackupExec Unix agent available that works with Samba? If not, can someone tell me how to work around the lack of the archive bit that Linux has? In particular, RedHat Linux 7.2 is the system I'm looking for help on. I found the following hints in an older version of this newsletter, Samba Digest, Vol. 3, Issue 34, sent March 21, 2003, that had this in it: Yes, we have

If you can see the server, but not shares, you most likely have not published any directories. What version of the BE agent are you using? I've noticed 4.6 works well (the install actually works well and will walk you through the setup to publish the directories to be backed up). It's often easier to just publish root (but exclude /proc /tmp). Also, I've found out that in the hosts

FYI, Seagate has announced a new enterprise SSD. The specs appear to be competitive: + 2.5" form factor + 5 year warranty + power loss protection + 0.44% annual failure rate (AFR) (2M hours MTBF, IMHO too low :-) + UER 1e-16 (new), 1e-15 (5 years) + 30,000/25,000 4 KB read IOPS (peak/aligned zero offset) + 30,000/10,500 4 KB write IOPS (peak/aligned zero offset)

On Wed, Sep 26, 2018 at 3:37 PM, lejeczek via CentOS <centos at centos.org> wrote: > > > On 26/09/18 20:19, Mauricio Tavares wrote: >> >> If ti makes you feel any better, I am not having stellar service from >> WD's support. In fact, they act like they never received the HD I sent >> for RMA whose tracking number says they did 10 days ago. >>

On 26/09/18 19:16, lejeczek via CentOS wrote: > hi guys > > I have rather a large set of Seagate's SAS ST32000444SS, over a > hundred - experience I'm having from those in conjunction with their > tech support is abysmal. > > I'm trying to update firmware of these drives and nothing works, > including tech support. > > ... and I cannot help but wonder -

All, I have a problem with a new Seagate hard disk. The problem occurs when i go to install CentOS, i insert the cd and start the boot up process, when it gets to the section where it detects the hard disks, the driver is seems crashes, the message it produces complains about no one caring about a interrupt on IRQ11. The hard disk is a Seagate 200GB 8MB SATA150 NCQ drive, on a SilliconImage

Hi there, http://www.seagate.com/support/disc/download/seatoold_en.exe Seagate offers a Windows executable (needs Win98 or better, 1,9MB) that should create 2 bootable floppy disks that contain a harddrive check program. Invoking "wine seatoold_en.exe" works, but when the floppy should be written, an error occurs "insert 1.44 MB...click retry". I tried to mount a DOS

Hi list I am running out of space on my notebook. So wanna buy additional and external storage. I don't wanna do a DIY-work, so searching for pre-built external hard disks. I wish to buy Seagate FreeAgent Pro [0]. Does it work under CentOS 5? Would you recommend me even better products? I am searching for good performance, noise-less, smart standard support and no useless features like

Hi all! I'm using syslinux & memdisk (3.11 version) to boot a floppy disk image of the seagate disk diagnostic tools via an usb key. When booting directly from the floppy disk, every thing is all right and my seagate disk is detected. But when booting the disk image via memdisk & syslinux on my USB key, every thing seems all right *except* that no disk is detected by the tools

On 26/09/18 20:19, Mauricio Tavares wrote: > If ti makes you feel any better, I am not having stellar service from > WD's support. In fact, they act like they never received the HD I sent > for RMA whose tracking number says they did 10 days ago. > > On Wed, Sep 26, 2018 at 2:16 PM, lejeczek via CentOS <centos at centos.org> wrote: >> hi guys >> >> I have

Hi all, I''m getting a very strange problem with a recent OpenSolaris b134 install. System is: Supermicro X5DP8-G2 BIOS 1.6a 2x Supermicro AOC-SAT2-MV8 1.0b 11 Seagate Barracuda 1TB ES.2 ST31000340NS drives If I have any of the 11 1TB Seagate drives plugged into the controller, the AOC-SAT2-MV8 BIOS appears to detect them just fine, but I get the following problems: 1. Grub takes a

If ti makes you feel any better, I am not having stellar service from WD's support. In fact, they act like they never received the HD I sent for RMA whose tracking number says they did 10 days ago. On Wed, Sep 26, 2018 at 2:16 PM, lejeczek via CentOS <centos at centos.org> wrote: > hi guys > > I have rather a large set of Seagate's SAS ST32000444SS, over a hundred - >

Hi all, As a disclaimer, I'm new to this list and very green administering CentOS. I run it on my test servers and do very basic networking and server administration (most users, permissions, and web app stuff). I have a backup server that I am using rsync to collect important in-process file for our digital library from both Windows and Linux servers, as well as a specific applications