Jump to content
jlbrown

Stalling when backing up. v14

Recommended Posts

Mac Server, Mac & PC clients.

 

I have three backups running, but they have all stalled early on in the copy stage.

 

Retrospect Log shows:

 

+ Retrospect version 14.0.0.183

Launched at 1/05/2017 7:58:47 PM
[*] Captured signal SIGPIPE!

 

Logs for the individual backups:

 

+ Normal backup using EAB Backup at 1/05/2017, 7:59:49 PM (Activity Thread 1)

1/05/2017 8:00:13 PM: Finished scanning backup set data files
To Backup Set EAB Backup...
- 1/05/2017 7:59:49 PM: Copying Local Disk (C:) on EDWARD
Using Instant Scan data for Local Disk (C:) on EDWARD
1/05/2017 8:02:06 PM: Found: 1637065 files, 51558 folders, 83.9 GB
1/05/2017 8:08:49 PM: Finished matching
Backing up 9 out of 12 files using block level incremental backup, storing full backups for remaining 3.
1/05/2017 8:18:55 PM: Copying: 262774 files (7.7 GB) and 17 hard links

 

+ Normal backup using SecuritySpy Backup at 1/05/2017, 8:00:26 PM (Activity Thread 2)

1/05/2017 8:01:00 PM: Finished scanning backup set data files
To Backup Set SecuritySpy Backup...
- 1/05/2017 8:00:26 PM: Copying Macintosh HD on Sapphire Server DR
Using Instant Scan data for Macintosh HD on Sapphire Server DR
1/05/2017 8:02:33 PM: Found: 905426 files, 207607 folders, 428.5 GB
1/05/2017 8:05:33 PM: Finished matching
Backing up 5 out of 31 files using block level incremental backup, storing full backups for remaining 26.
1/05/2017 8:11:48 PM: Copying: 103562 files (69 GB) and 1 hard links [*] soccSend: send failed, err 32

 

+ Normal backup using Mail Backup at 1/05/2017, 8:01:00 PM (Activity Thread 3)

1/05/2017 8:02:04 PM: Finished scanning backup set data files
To Backup Set Mail Backup...
- 1/05/2017 8:01:00 PM: Copying Macintosh SSD on mail.bordo.com.au1
1/05/2017 8:21:37 PM: Found: 1805110 files, 143947 folders, 388.2 GB
1/05/2017 8:22:39 PM: Finished matching
Backing up 22 files using block level incremental backup.
1/05/2017 8:25:29 PM: Copying: 16287 files (9.5 GB) and 1102 hard links [*] soccRecv: connection unexpectedly closed, error 35

 

Note, the last entries are over 14 hours ago.

 

The EAB Backup shows status of 'Copying Local Disk (C:)' and has only completed 118MB of 7.6GB.

The SecuritySpy Backup is showing 'Closing', as is Mail Backup.

 

Just noticed that the PC is running version 11 of the client. Maybe that's the problem. Will update it and see.

 

Any other suggestions?

 

Share this post


Link to post
Share on other sites

Getting desperate here. Something's not right.

 

After 40 mins, 1165 files copied, but only 54MB. Told it to stop the backup. It has been on 'Cancelling execution...' for over half an hour. It's log says:

 

+ Normal backup using BSB Backup at 8/05/2017, 5:34:46 PM (Activity Thread 1)

8/05/2017 5:34:47 PM: Finished scanning backup set data files
To Backup Set BSB Backup...
- 8/05/2017 5:34:46 PM: Copying Macintosh HD on Bob Brown’s Computer
Using Instant Scan data for Macintosh HD on Bob Brown’s Computer
8/05/2017 5:36:09 PM: Found: 1676073 files, 482689 folders, 637.3 GB
8/05/2017 5:37:05 PM: Finished matching
Backing up 11 out of 44 files using block level incremental backup, storing full backups for remaining 33.
8/05/2017 5:40:53 PM: Copying: 17318 files (16.4 GB) and 2 hard links

 

Other issues: Have changed the number of allowed activity threads from 1 to 3. But I have only one running (the one cancelling execution) and all other Proactive Backups say 'waiting for execution unit'.

 

The Retrospect log simply says:

 

+ Retrospect version 14.0.0.183

Launched at 8/05/2017 5:32:23 PM

 

Is there a config file that is corrupt of something? Really not sure what to do next. Any help would be much appreciated.

 

Thanks, James.

Share this post


Link to post
Share on other sites

Perhaps it is not actually stalled!

 

On the Client, it says:

 

"Backing up: 39.5 GB of 68.1 GB - 49 minutes remaining"

 

 

Even though according to Retrospect on the server, Activities section, the Backup is stuck on 727.3 MB Completed, 67.4GB Remaining. 

 

So looks like it is a bug in the display on the Retrospect app. The Retrospect Engine and the client are doing their job properly.

 

James.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×