Jump to content

V11 - Block level incremental backup - Log questions


Recommended Posts

I enabled block level incremental backup on my main proactive user folder backup script. Looking through the logs to ensure backups are actually being completed, there are a couple of puzzling items.

 

I've noticed that every source states "Backing up -27 files using block level incremental backup."

"-27 files"?? What exactly does that mean? Is that an error message? A number of files? A dash?

 

Also the "Completed", "Remaining", and "completed successfully" entries don't make a lot of sense to me when taken collectively. Why are there still 2145 files remaining, 318 files completed yet the script was completed successfully?

 

Using Instant Scan
Backing up -27 files using block level incremental backup.
3/12/14 3:45:54 PM: Snapshot stored, 323.3 MB
3/12/14 3:46:30 PM: Execution completed successfully
Remaining: 2145 files, 381 MB
Completed: 318 files, 419.5 MB, with 0% compression
Performance: 449.5 MB/minute
Duration: 00:30:29 (00:29:32 idle/loading/preparing)

3/12/14 3:46:35 PM: Script "User Home Folders - RAID 10.5" completed successfully

Link to comment
Share on other sites

Seeing the same result for at least two of my Windows clients being backed-up by Retrospect Desktop 9 on Windows:

 

- 2014-03-13 19:34:25: Copying Ziggy Windows 8.1 Pro (C:) on Ziggy-LT

Backing up -63 files using block level incremental backup.

 

- 2014-03-13 19:11:59: Copying Pushka Windows 7 Professional (C:)... on Pushka-LT

Using Instant Scan

Backing up -11 files using block level incremental backup.

 

It would be nice to know what this means.

 

I have also seen negative values for files remaining after backup completion in the new version.

Link to comment
Share on other sites

Seeing the same result for at least two of my Windows clients being backed-up by Retrospect Desktop 9 on Windows:

 

- 2014-03-13 19:34:25: Copying Ziggy Windows 8.1 Pro (C:) on Ziggy-LT

Backing up -63 files using block level incremental backup.

 

- 2014-03-13 19:11:59: Copying Pushka Windows 7 Professional (C:)... on Pushka-LT

Using Instant Scan

Backing up -11 files using block level incremental backup.

 

It would be nice to know what this means.

 

I have also seen negative values for files remaining after backup completion in the new version.

Is it always the same negative numbers for you or does it vary?

Link to comment
Share on other sites

The two clients I have updated the client software on does vary for the block level backup but not in any way that makes sense to me. Another client which is still running the Windows 8.5 client has not changed. So far I have only seen the negative value for files remaining once.

 

Here are the results for one client since installing Retrospect Desktop 9.0.0:
 

- 2014-03-11 19:51:03: Copying Ziggy Windows 8.1 Pro (C:) on Ziggy-LT
Using Instant Scan
Backing up -64 files using block level incremental backup.
 
- 2014-03-12 20:21:24: Copying Ziggy Windows 8.1 Pro (C:) on Ziggy-LT
Using Instant Scan
Backing up -64 files using block level incremental backup.
 
- 2014-03-13 19:34:25: Copying Ziggy Windows 8.1 Pro (C:) on Ziggy-LT
Backing up -63 files using block level incremental backup.
 
- 2014-03-13 20:34:44: Copying Ziggy Windows 8.1 Pro (C:) on Ziggy-LT
Backing up -65 files using block level incremental backup.
 
- 2014-03-14 18:15:55: Copying Ziggy Windows 8.1 Pro (C:) on Ziggy-LT
Backing up -56 files using block level incremental backup.

 
Running the Block Level Filter selector against this client reveals there are currently 96 files eligible for block level backup.

 

Is the backup set you are using an existing one from a previous Retrospect version or a new one? The backup set I am using was created by an Windows 8.x version of Retrospect Professional.

Link to comment
Share on other sites

 

From the release notes for v 11.0:

 

Known issues with this release

  • Engine: under some circumstances log shows negative file count for block level incremental backup, even though files are correctly backed up and are restorable (#4508).

 

That's somewhat relieving, I think...

Link to comment
Share on other sites

The two clients I have updated the client software on does vary for the block level backup but not in any way that makes sense to me. Another client which is still running the Windows 8.5 client has not changed. So far I have only seen the negative value for files remaining once.

 

Here are the results for one client since installing Retrospect Desktop 9.0.0:

 

- 2014-03-11 19:51:03: Copying Ziggy Windows 8.1 Pro (C:) on Ziggy-LT
Using Instant Scan
Backing up -64 files using block level incremental backup.
 
- 2014-03-12 20:21:24: Copying Ziggy Windows 8.1 Pro (C:) on Ziggy-LT
Using Instant Scan
Backing up -64 files using block level incremental backup.
 
- 2014-03-13 19:34:25: Copying Ziggy Windows 8.1 Pro (C:) on Ziggy-LT
Backing up -63 files using block level incremental backup.
 
- 2014-03-13 20:34:44: Copying Ziggy Windows 8.1 Pro (C:) on Ziggy-LT
Backing up -65 files using block level incremental backup.
 
- 2014-03-14 18:15:55: Copying Ziggy Windows 8.1 Pro (C:) on Ziggy-LT
Backing up -56 files using block level incremental backup.

 

Running the Block Level Filter selector against this client reveals there are currently 96 files eligible for block level backup.

 

Is the backup set you are using an existing one from a previous Retrospect version or a new one? The backup set I am using was created by an Windows 8.x version of Retrospect Professional.

The backup set is an existing Disk set on a 12TB RAID created with Retrospect Macintosh v 10.5

Link to comment
Share on other sites

Also the "Completed", "Remaining", and "completed successfully" entries don't make a lot of sense to me when taken collectively. Why are there still 2145 files remaining, 318 files completed yet the script was completed successfully?

 

Using Instant Scan

Backing up -27 files using block level incremental backup.

3/12/14 3:45:54 PM: Snapshot stored, 323.3 MB

3/12/14 3:46:30 PM: Execution completed successfully

Remaining: 2145 files, 381 MB

Completed: 318 files, 419.5 MB, with 0% compression

This could be caused by the use of Instant Scan. I have seen similar where files have been deleted between Instant Scan running and the backup running. I most often see this in relation to the antivirus updating its definitions. Checking the remaining files leads to files that no longer exist.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...