Jump to content

evaldas

Members
  • Content count

    12
  • Joined

  • Last visited

Community Reputation

0 Neutral

About evaldas

  • Rank
    Occasional Forum Poster
  1. evaldas

    No media looping on HP D2D

    Hi, Good, thank you, Mayoff. I think Retrospect should remove HP D2D backup system as soon as possible from their device compatibility page , it is confusing happy customers and making them unhappy. Regards,
  2. evaldas

    No media looping on HP D2D

    Hi, Current Retrospect windows server version in updates download page shows as v7.6.123 - this package installs driver version: v7.6.2.101 (visible in About menu), but this web page about latest versions says that latest windows driver is version is: 7.6.14.102 Which one is latest then ? :confused2: If the one included in v7.6.123 package is outdated, where can we find the latest one ? Hoping that this loop issue with HP D2D gets fixed sometime.. Regards,
  3. evaldas

    No media looping on HP D2D

    Greets and Happy New Year 2009 to everyone! Anybody could confirm that Retrospect Server v7.5+ (tried also with latest v7.6.123 with no luck) is working correctly with HP D2D virtual iSCSI library as stated in this Retrospect device compatibility page ? Thanks,
  4. evaldas

    No media looping on HP D2D

    If I disable device in Windows Device Manager, Retrospect doesn't see it anymore and says "Not responding". Retrospect must be using its own drivers via NT Passthrough mechanism, so windows drivers do not really matter, but device itself has to be enabled however. I tried all 3 possible HP D2D drive emulations, Retrospect sees them as following drives: HP Ultrium Gen 2 DC (1.41) HP Ultrium Gen 3 DC (1.41) HP Ultrium Gen 4 DC (1.41) Could that be a driver problem for iSCSI situation in Retrospect ? Regards,
  5. Greetings, I'm trying to use HP D2D virtual library in Retrospect server (latest v7.6) with no luck, library and drive shows ok in device list, but when moving cartridge into drive, Retrospect says "Reading.." then next second "No media", and then again "Reading..", and the never ending loop goes on. Tryed on a clean Retrospect install from scratch, with latest Microsoft iSCSI initiator version - same problem, Removable drive service is stopped, HP D2D virtual library and drive show up ok in windows device manager, also tested in NTBackup - works like a charm, for backup and verify. Any idea what could possible be wrong ? Compatibility page shows this device as Qualified. Here is a link with some debug info: it contains flash video showing the loop, retrospect device debug log during the loop, and screen capture showing HP D2D iSCSI virtual library status. Thanks,
  6. evaldas

    SQl Agent Authentication

    Hi, Ok, solved, the MS SQL 2005 installation was for SAP and it has no "MS SQL 2005 backwards compatibility package", in fact only SQL-DMO is needed from this package, which can be installed separately, screenshot attached: missing component install screenshot Regards,
  7. evaldas

    SQl Agent Authentication

    Hi, sorry, below are the details: Retrospect multi-server v7.5.508 running on windows xp x64. SQL server is a client (MS-SQL 2005 x64), running on windows server 2003 R2 Enterprise x64 SP1. No, I'm not using RBU, the client is on a different network and not part of the retrospect server domain. Configure->Volumes->BackupClients->Client1->SQLserver thats where a window pops up for authentication to SQL server, and I use "Domain authentication". The client with SQL server is not part of any domain, so in "Domain:" part I use client netbios name, and then administrator/pass for the rest. I have another client, where it works, and the only diffs between the two are: - OS, OKclient has win 2003 R2 Std x64 SP2 BADclient has win 2003 R2 Enterprise x64 SP1 - installed software list on OKclient has "MSSQL server 2005 Backward compatibility" which is missing on BADclient. I'll check if there are any updates for Enterprise x64 SP1, and add missing software component on BADclient, and then do some more testing, thanks.
  8. evaldas

    SQl Agent Authentication

    Hi, Thanks for sharing the info, the registry trick is useful and it worked very well on 32bit version of SQL server. However, another host which has 64bit SQL server is still refusing retrospect logins and the registry keys have correct values already. I tried every possible solution given in this topic - no good, il always fails, but win event security log on sql server host shows "login success..", any idea what's wrong ? Regards.
  9. *signed* ! I agree, too bad to ignore BSD like that.. FreeBSD 4.x may still work under linux emulation, but it no longer works in FreeBSD 5.. If source is a problem, why not to release a binary port ? Others do that, like Adaptec with their RAID administration tool raidutil.
  10. Hi again, forgot about the libs - verified, all libs are in place (retroclient 6.5): ldd retroclient retroclient: libgthread-1.2.so.0 => /usr/lib/libgthread-1.2.so.0 (0x28086000) libglib-1.2.so.0 => /usr/lib/libglib-1.2.so.0 (0x28089000) libpthread.so.0 => /lib/libpthread.so.0 (0x280ab000) libc.so.6 => /lib/libc.so.6 (0x280be000) /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x2806f000) Also, killing retroclient process on FreeBSD 5, leaves zombie processes: root 0 0.0 0.0 0 0 ?? ZW - 0:00.00 (retroclient) root 0 0.0 0.0 0 0 ?? ZW - 0:00.00 (retroclient) root 0 0.0 0.0 0 0 ?? ZW - 0:00.00 (retroclient) Thanks, Evaldas
  11. Hello, Ok, thanks, it's not the java After some further testings on FreeBSD 5 and FreeBSD 4 (both using the same linux_base-6 port, actually results are the same using linux_base-7 and linux_base-8) : It works fine on FreeBSD 4 (FreeBSD 4.9-RELEASE), here is how retroclient.log starts : 1088148473: SopsLoad: Handle 4 open 1088148473: SopsLoad: Handle 4 closed 1088148473: SopsSave: Handle 4 open 1088148473: SopsSave: Handle 4 closed 1088148473: SopsSave: Handle 0 open 1088148473: SopsSave: Handle 0 closed 1088148473: ServiceInstall: allocating memory for Builtin 1088148473: ServiceInstall: allocating memory for RfsCountdown 1088148473: ServiceInstall: allocating memory for RfsDownload 1088148473: SThreadSpawn: starting thread 1026 1088148473: netDoAccept: Releasing thread for NetDoShutdownTest() 1088148473: NetDoShutdownTest: shutdown test passed 1088148473: netDoAccept: socket 0 shutdown 1088148473: sThreadExit: exiting thread 1026 1088148473: SThreadSpawn: starting thread 2051 1088148473: netCheckNewInterfaces: Handle 0 open 1088148473: netCheckNewInterfaces: found new address 172.16.255.12:0 1088148473: NetAddInterface: adding ip: 172.16.255.12:0 to list 1088148473: IPNSStart: starting thread iplud 1088148473: SThreadSpawn: starting thread 3074 1088148473: iplud: interface for socket 4 open 1088148473: NetSockAdd: adding socket 4 to interface 1 1088148473: iplud: bound to address 0.0.0.0 1088148473: ipludAddMembership: adding membership for 0.0.0.0 1088148473: ipnsBroadcast: Handle 6 open 1088148473: iplud: got 196 bytes from 172.16.255.12:1060 Output from "netstat -na|grep 497": tcp4 0 0 127.0.0.1.497 *.* LISTEN tcp4 0 0 172.16.255.12.497 *.* LISTEN udp4 0 0 *.497 *.* Output from "retrocpl": Version 6.5.108 back up according to normal schedule currently on readonly is off exclude is off 0 connections, 0 authenticated ============================================= Now, on FreeBSD 5 (FreeBSD 5.2.1-RELEASE-p1) etroclient.log starts : 1088149113: SopsLoad: Handle 4 open 1088149113: SopsLoad: Handle 4 closed 1088149113: SopsSave: Handle 0 open 1088149113: SopsSave: Handle 0 closed 1088149113: ServiceInstall: allocating memory for Builtin 1088149113: ServiceInstall: allocating memory for RfsCountdown 1088149113: ServiceInstall: allocating memory for RfsDownload 1088149113: SThreadSpawn: starting thread 1026 1088149113: netDoAccept: Releasing thread for NetDoShutdownTest() 1088149113: NetDoShutdownTest: shutdown test passed 1088149113: netDoAccept: socket 0 shutdown 1088149113: SThreadSpawn: starting thread 2051 1088149113: netCheckNewInterfaces: Handle 4 open 1088149113: netCheckNewInterfaces: found new address 172.16.255.10:0 1088149113: NetAddInterface: adding ip: 172.16.255.10:0 to list 1088149113: IPNSStart: starting thread iplud 1088149113: sThreadExit: exiting thread 1026 1088149113: SThreadSpawn: starting thread 3076 1088149113: iplud: interface for socket 0 open 1088149113: NetSockAdd: adding socket 0 to interface 1 1088149113: iplud: bound to address 0.0.0.0 1088149113: ipludAddMembership: adding membership for 0.0.0.0 1088149113: ipnsBroadcast: Handle 6 open 1088149113: iplud: got 196 bytes from 172.16.255.10:55208 Output from "netstat -na|grep 497": udp4 0 0 *.497 *.* and output from "retrocpl": Retrospect client is not running which looks normal as retroclient is not listening on localhost:TCP:497 . I guess in FreeBSD 5 there are some changes in a way socket opens are done, or retroclient is trying to do it in a way FreeBSD does not understand, maybe some more debug info could help, but how to activate it ? Anyway the point is, retroclient fails to open TCP port on FreeBSD 5 at the moment. Regards, Evaldas
  12. Hi, Anybody had success in running Linux client under FreeBSD 5 ? I run it here simply by execing "retroclient -daemon", it starts listening on UDP 497, and Retrospect server sees it, but is unable to activate it. I suspect "retrocpl -on" should be run before because the client is running, but not enabled ? But I don't see java on FreeBSD 5, yet, so no way to execute retrocpl.. Any ideas ?
×