Jump to content

kgleason

Members
  • Content count

    5
  • Joined

  • Last visited

Community Reputation

0 Neutral

About kgleason

  • Rank
    Occasional forum poster
  1. Hello all, I currently have several PowerPC based Mac servers, and I am reworking my backup solution. I would like to run a Dell PowerVault 124T using a SCSI connection from a PowerPC based Mac (running either 10.4 server or 10.5 server). It would appear that there has been a driver update recently that supports the PV124T, but I am not sure if support was added for the Mac product or not. So does anyone know if Retrospect 6 for PowerPC based Mac will support that model tape drive, and if so, will I be able to use LTO4 tapes, or would I be better off with something like LTO2? Thanks in advance.
  2. kgleason

    SQl Agent Authentication

    We haven't really done anything fancy with SQL Server or Retrospect. Stock install of SQL Server on 2 different servers. One server is a Dell 2850 (32bit) running Windows 2003 STandard. The other server is a Dell 2950 (64bit) running Windows 2003 Standard for 64 bit. The 32bit SQL server is letting me authenticate. However, the 64 bit one is not. All services are running with default credentials, and SQL has NT and SQL authentication enabled. Both SQL Servers are only running a default instance. I have tried authenticating as the following users: 1. Domain Administrator 2. Active Directory user who is also a domain administrator. 3. An RBU account that I created according to the specs in the help. 4. sa 5. another sql user who has DBO on all databases None of them work on the 64 bit SQL server. (The Domain Administrator works on the 32 bit SQL server). I have tried forgetting clients, forgetting licenses, just about everything you have mentioned. I am not going to remove / rename the retrospect config because there is too much stuff configured on that thing, and the last time I tried renaming it (based on advice from Tech support), I had to reconfigure everything from scratch, and it obviously didn't work anyhow. Sorry, not gonna do it. I did have a look at the logs. I cleared the Security log, and then attempted to make Retrospect connect to the database, and here is what I am seeing: Code: Date,Source,Severity,Message,Category,Event,User,Computer 07/17/2007 12:59:11,Security,Success Audit,User Logoff:<nl/><nl/> User Name: administrator<nl/><nl/> Domain: RMGCOM<nl/><nl/> Logon ID: (0x2<c/>0x115F4277)<nl/><nl/> Logon Type: 5,Logon/Logoff,538,RMGCOM\administrator,DB1 07/17/2007 12:59:04,Security,Success Audit,User Logoff:<nl/><nl/> User Name: Administrator<nl/><nl/> Domain: RMGCOM<nl/><nl/> Logon ID: (0x2<c/>0x115F78EB)<nl/><nl/> Logon Type: 3,Logon/Logoff,538,RMGCOM\administrator,DB1 07/17/2007 12:59:04,Security,Success Audit,Successful Network Logon:<nl/><nl/> User Name: Administrator<nl/><nl/> Domain: RMGCOM<nl/><nl/> Logon ID: (0x2<c/>0x115F78EB)<nl/><nl/> Logon Type: 3<nl/><nl/> Logon Process: Kerberos<nl/><nl/> Authentication Package: Kerberos<nl/><nl/> Workstation Name: <nl/><nl/> Logon GUID: {0c87f0e4-59a0-ae31-7de5-f98c8195d0f3}<nl/><nl/> Caller User Name: -<nl/><nl/> Caller Domain: -<nl/><nl/> Caller Logon ID: -<nl/><nl/> Caller Process ID: -<nl/><nl/> Transited Services: -<nl/><nl/> Source Network Address: -<nl/><nl/> Source Port: -,Logon/Logoff,540,RMGCOM\administrator,DB1 07/17/2007 12:59:04,Security,Success Audit,Special privileges assigned to new logon:<nl/><nl/> User Name: Administrator<nl/><nl/> Domain: RMGCOM<nl/><nl/> Logon ID: (0x2<c/>0x115F78EB)<nl/><nl/> Privileges: SeAssignPrimaryTokenPrivilege<nl/> SeSecurityPrivilege<nl/> SeBackupPrivilege<nl/> SeRestorePrivilege<nl/> SeTakeOwnershipPrivilege<nl/> SeDebugPrivilege<nl/> SeSystemEnvironmentPrivilege<nl/> SeLoadDriverPrivilege<nl/> SeImpersonatePrivilege,Logon/Logoff,576,RMGCOM\administrator,DB1 07/17/2007 12:59:04,Security,Success Audit,User Logoff:<nl/><nl/> User Name: Administrator<nl/><nl/> Domain: RMGCOM<nl/><nl/> Logon ID: (0x2<c/>0x115F77E7)<nl/><nl/> Logon Type: 3,Logon/Logoff,538,RMGCOM\administrator,DB1 07/17/2007 12:59:04,Security,Success Audit,Successful Network Logon:<nl/><nl/> User Name: Administrator<nl/><nl/> Domain: RMGCOM<nl/><nl/> Logon ID: (0x2<c/>0x115F77E7)<nl/><nl/> Logon Type: 3<nl/><nl/> Logon Process: Kerberos<nl/><nl/> Authentication Package: Kerberos<nl/><nl/> Workstation Name: <nl/><nl/> Logon GUID: {0c87f0e4-59a0-ae31-7de5-f98c8195d0f3}<nl/><nl/> Caller User Name: -<nl/><nl/> Caller Domain: -<nl/><nl/> Caller Logon ID: -<nl/><nl/> Caller Process ID: -<nl/><nl/> Transited Services: -<nl/><nl/> Source Network Address: -<nl/><nl/> Source Port: -,Logon/Logoff,540,RMGCOM\administrator,DB1 07/17/2007 12:59:04,Security,Success Audit,Special privileges assigned to new logon:<nl/><nl/> User Name: Administrator<nl/><nl/> Domain: RMGCOM<nl/><nl/> Logon ID: (0x2<c/>0x115F77E7)<nl/><nl/> Privileges: SeAssignPrimaryTokenPrivilege<nl/> SeSecurityPrivilege<nl/> SeBackupPrivilege<nl/> SeRestorePrivilege<nl/> SeTakeOwnershipPrivilege<nl/> SeDebugPrivilege<nl/> SeSystemEnvironmentPrivilege<nl/> SeLoadDriverPrivilege<nl/> SeImpersonatePrivilege,Logon/Logoff,576,RMGCOM\administrator,DB1 07/17/2007 12:59:04,Security,Success Audit,User Logoff:<nl/><nl/> User Name: Administrator<nl/><nl/> Domain: RMGCOM<nl/><nl/> Logon ID: (0x2<c/>0x115F76AD)<nl/><nl/> Logon Type: 3,Logon/Logoff,538,RMGCOM\administrator,DB1 07/17/2007 12:59:04,Security,Success Audit,Successful Network Logon:<nl/><nl/> User Name: Administrator<nl/><nl/> Domain: RMGCOM<nl/><nl/> Logon ID: (0x2<c/>0x115F76AD)<nl/><nl/> Logon Type: 3<nl/><nl/> Logon Process: Kerberos<nl/><nl/> Authentication Package: Kerberos<nl/><nl/> Workstation Name: <nl/><nl/> Logon GUID: {0c87f0e4-59a0-ae31-7de5-f98c8195d0f3}<nl/><nl/> Caller User Name: -<nl/><nl/> Caller Domain: -<nl/><nl/> Caller Logon ID: -<nl/><nl/> Caller Process ID: -<nl/><nl/> Transited Services: -<nl/><nl/> Source Network Address: -<nl/><nl/> Source Port: -,Logon/Logoff,540,RMGCOM\administrator,DB1 07/17/2007 12:59:04,Security,Success Audit,Special privileges assigned to new logon:<nl/><nl/> User Name: Administrator<nl/><nl/> Domain: RMGCOM<nl/><nl/> Logon ID: (0x2<c/>0x115F76AD)<nl/><nl/> Privileges: SeAssignPrimaryTokenPrivilege<nl/> SeSecurityPrivilege<nl/> SeBackupPrivilege<nl/> SeRestorePrivilege<nl/> SeTakeOwnershipPrivilege<nl/> SeDebugPrivilege<nl/> SeSystemEnvironmentPrivilege<nl/> SeLoadDriverPrivilege<nl/> SeImpersonatePrivilege,Logon/Logoff,576,RMGCOM\administrator,DB1 07/17/2007 12:59:04,Security,Success Audit,Successful Network Logon:<nl/><nl/> User Name: Administrator<nl/><nl/> Domain: RMGCOM<nl/><nl/> Logon ID: (0x2<c/>0x115F7575)<nl/><nl/> Logon Type: 3<nl/><nl/> Logon Process: Kerberos<nl/><nl/> Authentication Package: Kerberos<nl/><nl/> Workstation Name: <nl/><nl/> Logon GUID: {0c87f0e4-59a0-ae31-7de5-f98c8195d0f3}<nl/><nl/> Caller User Name: -<nl/><nl/> Caller Domain: -<nl/><nl/> Caller Logon ID: -<nl/><nl/> Caller Process ID: -<nl/><nl/> Transited Services: -<nl/><nl/> Source Network Address: -<nl/><nl/> Source Port: -,Logon/Logoff,540,RMGCOM\administrator,DB1 07/17/2007 12:59:04,Security,Success Audit,Special privileges assigned to new logon:<nl/><nl/> User Name: Administrator<nl/><nl/> Domain: RMGCOM<nl/><nl/> Logon ID: (0x2<c/>0x115F7575)<nl/><nl/> Privileges: SeAssignPrimaryTokenPrivilege<nl/> SeSecurityPrivilege<nl/> SeBackupPrivilege<nl/> SeRestorePrivilege<nl/> SeTakeOwnershipPrivilege<nl/> SeDebugPrivilege<nl/> SeSystemEnvironmentPrivilege<nl/> SeLoadDriverPrivilege<nl/> SeImpersonatePrivilege,Logon/Logoff,576,RMGCOM\administrator,DB1 07/17/2007 12:59:03,Security,Success Audit,Special privileges assigned to new logon:<nl/><nl/> User Name: <nl/><nl/> Domain: <nl/><nl/> Logon ID: (0x2<c/>0x115F4277)<nl/><nl/> Privileges: SeAssignPrimaryTokenPrivilege<nl/> SeImpersonatePrivilege<nl/> SeSecurityPrivilege<nl/> SeBackupPrivilege<nl/> SeRestorePrivilege<nl/> SeTakeOwnershipPrivilege<nl/> SeDebugPrivilege<nl/> SeSystemEnvironmentPrivilege<nl/> SeLoadDriverPrivilege,Logon/Logoff,576,RMGCOM\administrator,DB1 07/17/2007 12:59:03,Security,Success Audit,Successful Logon:<nl/><nl/> User Name: administrator<nl/><nl/> Domain: RMGCOM<nl/><nl/> Logon ID: (0x2<c/>0x115F4277)<nl/><nl/> Logon Type: 5<nl/><nl/> Logon Process: Advapi <nl/><nl/> Authentication Package: Negotiate<nl/><nl/> Workstation Name: DB1<nl/><nl/> Logon GUID: {ba5a6fc9-8d55-cbde-e357-de383140fb15}<nl/><nl/> Caller User Name: DB1$<nl/><nl/> Caller Domain: RMGCOM<nl/><nl/> Caller Logon ID: (0x0<c/>0x3E7)<nl/><nl/> Caller Process ID: 5704<nl/><nl/> Transited Services: -<nl/><nl/> Source Network Address: -<nl/><nl/> Source Port: -,Logon/Logoff,528,RMGCOM\administrator,DB1 07/17/2007 12:59:03,Security,Success Audit,Logon attempt using explicit credentials:<nl/><nl/>Logged on user:<nl/><nl/> User Name: DB1$<nl/><nl/> Domain: RMGCOM<nl/><nl/> Logon ID: (0x0<c/>0x3E7)<nl/><nl/> Logon GUID: {343938d7-190f-67ad-00dc-1d99b5eeeccc}<nl/><nl/>User whose credentials were used:<nl/><nl/> Target User Name: administrator<nl/><nl/> Target Domain: RMGCOM<nl/><nl/> Target Logon GUID: {ba5a6fc9-8d55-cbde-e357-de383140fb15}<nl/><nl/><nl/>Target Server Name: localhost<nl/><nl/>Target Server Info: localhost<nl/><nl/>Caller Process ID: 5704<nl/><nl/>Source Network Address: -<nl/><nl/>Source Port: -,Logon/Logoff,552,NT AUTHORITY\SYSTEM,DB1 07/17/2007 12:58:37,Security,Success Audit,The audit log was cleared<nl/><nl/><nl/> Primary User Name: SYSTEM<nl/><nl/> Primary Domain: NT AUTHORITY<nl/><nl/> Primary Logon ID: (0x0<c/>0x3E7)<nl/><nl/> Client User Name: administrator<nl/><nl/> Client Domain: RMGCOM<nl/><nl/> Client Logon ID: (0x0<c/>0x1DA6D),System Event,517,NT AUTHORITY\SYSTEM,DB1
  3. kgleason

    SQl Agent Authentication

    Did anyone ever get any of this stuff resolved? If not, I am gonna have to drop retrospect and move to something else. Seems ridiculous that this does not work ....
  4. Hello all, Here is my predicament. I have an OS X Server (10.4.x) running Retrospect 6.1. The server has 2TB of RAID storage attached, which I back up to a Lacie Bigger Disk Extreme (2TB). I split the LaCie disk in 2 Volumes, to deal with the 1TB limit in Retrospect. I did all of this in Dec 2006. Yesterday, a sys admin noticed that the time was off on the server, and it turned out to be that the time zone was not set properly. He fixed the timezone, which immediately fixed the time on the server. However, when the backups were running, an error popped up stating something like this: "2-MediaB is not a member of this backup set. Although it is named correctly, it has a different creation date: 12/1/2006 10:47PM instead of the desired 12/1/2006 7:47PM". The 3 hour discrepancy between the times is the amount of time offset between the old time zone on the server, and the correct timezone on the server (the change made yesterday). Is there any way that I can continue to use this set without reformatting the media? Please help!
  5. kgleason

    SQl Agent Authentication

    Hello all, Here is my situation ... 1. Windows 2003 Server 32 bit running RetroSpect MultiServer backups & 1 SQL Agent License. RetroSpect version is 7.5.330. 2. SQL Server 2005 64 bit running on WIndows 2003 (default instance -- no cluster). When I attempt to assign the SQL Agent license to the SQL Instance on that client, Retrospect pops up with an authentication dialog box. I have tried everything, but it always fails. I have an RBU user as outlined in the Users guide / Help which does not work. I have also tried a domain administrator, a local administrator, sa, another SQL user that has dbo rights on the database. None of them work. All I can get from RetroSpect support is "it should be working.". If anyone has any ideas about what it could be, I would really appreciate the help.
×