Jump to content


Photo

Status (not yet determined)


  • Please log in to reply
4 replies to this topic

#1 James Brown

James Brown

    Occasional forum poster

  • Members
  • 72 posts

Posted 09 May 2017 - 06:32 AM

Retrospect version 14.0.0.183

 

Have a few Proactive Backups that have (Not yet determined) as their status, and it doesn't change.

 

Even a restart of the Retrospect Backup Engine doesn't help.

 

Or a restart of the client machine.

 

Anyone know how to get it to make a determination?

 

According to the Sources section of Retrospect, the source is running client version 14.0.0.183. Address is 0.0.0.0 for some reason.

 

Thanks, James.



#2 twickland

twickland

    Retrospect Guru

  • Members
  • 1,503 posts

Posted 09 May 2017 - 01:39 PM

Are you able to refresh or locate the client in the Sources window? Are you performing regular scheduled backups in addition to the proactive backups, and do the scheduled backups run correctly? (If you're not doing this already, try creating and running a regular scheduled backup as a test. You will get an error message if the backup fails, which could help in your diagnosis.)

 

Are the problem clients located in a different subnet than the clients that back up correctly? How are you attempting to connect with the clients: multicast, subnet broadcast, or direct IP?


Tim
________________________________
Retrospect 13.5.0 (173)
Mac Pro 3.7 GHz Quad-Core Xeon E5
16 GB RAM, OS 10.10.5
ATTO ThunderLink SH 2068 SAS HBA


#3 James Brown

James Brown

    Occasional forum poster

  • Members
  • 72 posts

Posted 10 May 2017 - 01:04 AM

No, refresh never finishes. Only Proactive, have no scheduled backups. All clients on same subnet. Just re-installed the Retrospect Client on problem machine, then restarted it.

 

Everything came up - client IP is now correct, not 0.0.0.0.

 

The Proactive Backup started.

 

But kept getting:

 

Additional error information for Disk Backup Set member "1-PP Backup",

Can't write to file /Volumes/HD/Retrospect/PP Backup/1-PP Backup/AB000008,460.rdb, error -1,023 (already exists)
[*] xopWrite: trouble writing, error -106 (data overwrite attempt)
[*] xopWrite: trouble writing, error -106 (data overwrite attempt)
[*] xopFlush: flush failed, error -106 (data overwrite attempt)
!Trouble writing: "1-PP Backup" (553111552), error -106 (data overwrite attempt)
!Trouble writing media:
"1-PP Backup"
error -106 (data overwrite attempt)

 

over and over again. Have stopped the backup.



#4 Lennart Thelander

Lennart Thelander

    Retrospect Veteran

  • Members
  • 3,539 posts
  • LocationHelsingborg, Sweden

Posted 10 May 2017 - 04:59 AM

You have a media set member with the same name as the correct one, but it is not the correct member that you have connected.

 

Retrospect will go far to prevent you from (accidentally) overwrite any backup you already have.



#5 James Brown

James Brown

    Occasional forum poster

  • Members
  • 72 posts

Posted 10 May 2017 - 07:33 AM

Thanks Lennart.

 

Have deleted the old Media Set and re-created it.

 

The proactive backup is running now.

 

All looking good. Thanks again for your help.

 

James.






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users