Direkt zum Inhalt

Print Backup Version List

Thread needs solution

I've been having some disk problems with a server that offers a share that I use Acronis 2013 to backup to. My backup scheme is to run a differential backup nightly, create a full version after 6 differential versions and store no more then 6 version chains. I think that means I'll get nightly diffs, one a week create a full backup and have 6 weeks worth of full and diff backups before celanup deletes older version chains.

I say think because I've never gotten that far. Because of the server disk problems, I've had to move the version chains to different disks. I'm really not trusting the auto cleanup because I noticed once in my backup logs that it had a backup file from a completely different backup job. And a cleanup occurred much sooner then I expected and deleted more backup files then I expected.

Right now, when I do a backup validation of the chain, it says the backup is corrupted. Probably is, so how can I correct this? Just delete the backup files until I've got a valid chain? This might solve my current problem.

But what I'd really like to do is be able to print off what Acronis thinks is my current version chain. Now, when I get a version chain issue, creating an entirely new backup job has been the only way that works.

Thanks

0 Users found this helpful

http://forum.acronis.com/forum/49880#comment-154215
The above link may be of interst as you mention share and server. Having the correct path for a share is of vital importance.
Needles to say, there should be no mixup but just to be safe, I practice there to be no mixing of backups within a single storage folder. Each task has its own folder. I also practice no changes of configuration within a backup task--except scheduling which can be done from the maiin menu without using the edit settings option. If changes needed, a create a new task.

Based on your settings, your recent vesion chain would be 1 full plus 6 inc or 1 chain=7 files
Keepiing 6 recent version chains is keeping 42 files so the cleanup would begin after full #7 or after backup #43 when all of chain 1 would be deleted.

Use notepad and look at the contents of ARCHIVES.XML found in the Database folder inside the Aconis folder.
Search if necessary. This is the storage file for the backup names but it will not clearly show what you want--I do not believe.

If you used the "Move" option, there could be some confusion by the program as to location changes--but that's a guess.

Grover, thanks for the tips. I'm going to start over cleaning up my existing backups and hiding them from Acronis, create a new backup task, a separate folder for each task, add the @exec@ and my before/after cmd file folder contents listing. Then closely monitor what's going on.

The archives.xml looks like it might contain the info I want but it would be too hard to reverse engineer it to generate a report. I'm going to ask Acronis support if they would interpret it.

If you want to attach your log file, I will be happy to look at it to see if anything stands out at me.
Open log file and top right should be an option to save to file which can be attached, if you should wish todo so.

I've included a couple of snippets from my logfile history. There was a lot going on around this time as I struggled with share access to my server which caused a corrupted log file which made me move logfiles using Acronis as well as changing the task parameters. Not sure if it makes much sense to spend any time on this right now as I can't verify the status of the backup task at the time of the logfile. I've implemented the tips you suggested, created a new task and will be monitoring this closely. Then if I have problems I should be better able to report current status of my backup task. Anyway, here are some logfile snippets.

Here are some snippets from my log file question 1 - why isn't the history chronological? The top of the screen goes from 12/18 to 11/08 and then starts again with 12/18. I had been changing the task DataApps, but don't understand why the list is chronological.

For the next snippet, I don't understand why diff 7 was created. My scheme calls for 1 full and then 6 diffs. Around this time I did move the version change using acronis.

Also there was 1 log file that referenced a version chain that was associated with another task. Still looking for that instance.

Well, looks like the posting made my snippets disappear. Tomorrow evening I'll make them as attachements as well as see if I can find the mismatched version chain.

Well, it took awhile but my problem resurfaced again. Steps 16 and 17 in the log show the problem. Line 16 refers to PSC4Local_Full_Backup_diff_b13_sv_v1 which is correct. Then on line 17 it says it cannot find PSC4\DataApps_diff_b9_s4_v1 which is an entirely separate backup task. Because I've been having problems with my server where the backups were initially located, I used the "Acronis" move command to move the backup files to a local disk. I'm concluding that the move command is too buggy to use. So for now, rather then moving, I create an entirely new backup task and delete just the older backup task, all in Acronis, leaving the files. So far everything is working on 2 backup tasks, but then I'm only at B1, S6. I need to get to B6, S7 before the next backup will trigger an auto cleanup. With nightly backups, that's 5 weeks away.

1 Information 13/12/27 2:00:01 AM Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
2 Information 13/12/27 2:00:02 AM Operation PSC4local_Full_Backup started by schedule.
3 Information 13/12/27 2:00:02 AM Operation description: Stage Description.
4 Information 13/12/27 2:00:05 AM Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
5 Information 13/12/27 2:00:06 AM Child process has exited with code '0'.
6 Information 13/12/27 2:00:06 AM Execution of user command succeeded: V:/Backup/PSC4/PSC4local.cmd
7 Information 13/12/27 2:00:06 AM Create Backup Archive From: C_PSC3 (C:), D_PSC3XP (D:) To file: "V:\Backup\PSC4\PSC4local_Full_Backup_diff_b13_s3_v1.tib" Compression: High
8 Information 13/12/27 2:00:06 AM Pending operation 152 started: 'Creating partition image'.
9 Information 13/12/27 2:00:32 AM Writing differential version to file: PSC4local_Full_Backup_diff_b13_s4_v1.tib
10 Information 13/12/27 2:02:13 AM Pending operation 152 started: 'Creating partition image'.
11 Information 13/12/27 2:02:36 AM Pending operation 149 started: 'Saving partition structure'.
12 Information 13/12/27 2:02:36 AM The following backups have been successfully created: "V:\Backup\PSC4\PSC4local_Full_Backup_diff_b13_s4_v1.tib"
13 Information 13/12/27 2:02:37 AM Validate Backup Archive Location: "V:\Backup\PSC4\PSC4local_Full_Backup_diff_b13_s4_v1.tib"
14 Information 13/12/27 2:02:37 AM Pending operation 3 started: 'Validate Backup Archive'.
15 Information 13/12/27 2:14:32 AM Consolidate Backup Archive Location: "V:\Backup\PSC4\PSC4local_Full_Backup_diff_b13_s4_v1.tib" Destination: "V:\Backup\PSC4\PSC4local_Full_Backup_diff_b13_s4_v1_39C846AF-58CE-4DDF-B07D-5E971A3239F0.tib"
16 Information 13/12/27 2:14:32 AM Consolidate Backup Archive Location: "V:\Backup\PSC4\PSC4local_Full_Backup_diff_b13_s4_v1.tib" Destination: "V:\Backup\PSC4\PSC4local_Full_Backup_diff_b13_s4_v1_39C846AF-58CE-4DDF-B07D-5E971A3239F0.tib"
17 True Image 13/12/27 2:14:32 AM Failed to open backup \\192.168.1.116\d1\Backup\PSC4\DataApps_diff_b9_s4_v1.tib. Make sure the backup location is accessible and contains all versions of the backup. This backup may also be corrupted.
18 True Image 13/12/27 2:14:32 AM ARsECwDPPUUq13X1LQAkbW9kdWxlAFdDOlxQcm9ncmFtIEZpbGVzICh4ODYpXENvbW1vbiBGaWxlc1xBY3JvbmlzXFRydWVJbWFnZUhvbWVcVHJ1ZUltYWdlSG9tZVNlcnZpY2UuZXhlAAARAAQA/fchO3t0X/NUaGUgc3BlY2lmaWVkIGZpbGUgZG9lcyBub3QgZXhpc3QuAGZ1bmN0aW9uAEFPcGVuRmlsZVcAZmlsZW5hbWUAV1xcP1xVTkNcMTkyLjE2OC4xLjExNlxkMVxCYWNrdXBcUFNDNFxEYXRhQXBwc19kaWZmX2I5X3M0X3YxLnRpYgAA8P8AAMO47WS9/Si9VGhlIHN5c3RlbSBjYW5ub3QgZmluZCB0aGUgZmlsZSBzcGVjaWZpZWQAY29kZQBOAgAHgAAAAAAA; ARsECwDPPUUq13X1LQAkbW9kdWxlAFdDOlxQcm9ncmFtIEZpbGVzICh4ODYpXENvbW1vbiBGaWxlc1xBY3JvbmlzXFRydWVJbWFnZUhvbWVcVHJ1ZUltYWdlSG9tZVNlcnZpY2UuZXhlAAARAAQA/fchO3t0X/NUaGUgc3BlY2lmaWVkIGZpbGUgZG9lcyBub3QgZXhpc3QuAGZ1bmN0aW9uAEFPcGVuRmlsZVcAZmlsZW5hbWUAV1xcP1xVTkNcMTkyLjE2OC4xLjExNlxkMVxCYWNrdXBcUFNDNFxEYXRhQXBwc19kaWZmX2I5X3M0X3YxLnRpYgAA8P8AAMO47WS9/Si9VGhlIHN5c3RlbSBjYW5ub3QgZmluZCB0aGUgZmlsZSBzcGVjaWZpZWQAY29kZQBOAgAHgAAAAAAA; AQIAPABWQRqW7k//zkVycm9yOiB1bmFibGUgdG8gb3BlbiB2aXJ0dWFsIGRpc2suACRtb2R1bGUAV0M6XFByb2dyYW0gRmlsZXMgKHg4NilcQ29tbW9uIEZpbGVzXEFjcm9uaXNcVHJ1ZUltYWdlSG9tZVxUcnVlSW1hZ2VIb21lU2VydmljZS5leGUAABEABAD99yE7e3Rf81RoZSBzcGVjaWZpZWQgZmlsZSBkb2VzIG5vdCBleGlzdC4AZnVuY3Rpb24AQU9wZW5GaWxlVwBmaWxlbmFtZQBXXFw/XFVOQ1wxOTIuMTY4LjEuMTE2XGQxXEJhY2t1cFxQU0M0XERhdGFBcHBzX2RpZmZfYjlfczRfdjEudGliAADw/wAAw7jtZL39KL1UaGUgc3lzdGVtIGNhbm5vdCBmaW5kIHRoZSBmaWxlIHNwZWNpZmllZABjb2RlAE4CAAeAAAAAAAA=; AfL/CwBncY5ByzQhEwAkbW9kdWxlAFdDOlxQcm9ncmFtIEZpbGVzICh4ODYpXENvbW1vbiBGaWxlc1xBY3JvbmlzXFRydWVJbWFnZUhvbWVcVHJ1ZUltYWdlSG9tZVNlcnZpY2UuZXhlAAA=; AfL/CwB/cY5ByzQhEwAkbW9kdWxlAFdDOlxQcm9ncmFtIEZpbGVzICh4ODYpXENvbW1vbiBGaWxlc1xBY3JvbmlzXFRydWVJbWFnZUhvbWVcVHJ1ZUltYWdlSG9tZVNlcnZpY2UuZXhlAAA=; AR0ECwAL8imOlCI/TQAkbW9kdWxlAFdDOlxQcm9ncmFtIEZpbGVzICh4ODYpXENvbW1vbiBGaWxlc1xBY3JvbmlzXFRydWVJbWFnZUhvbWVcVHJ1ZUltYWdlSG9tZVNlcnZpY2UuZXhlAAARAAQA/fchO3t0X/NUaGUgc3BlY2lmaWVkIGZpbGUgZG9lcyBub3QgZXhpc3QuAGZ1bmN0aW9uAEFPcGVuRmlsZVcAZmlsZW5hbWUAV1xcP1xVTkNcMTkyLjE2OC4xLjExNlxkMVxCYWNrdXBcUFNDNFxEYXRhQXBwc19kaWZmX2I5X3M0X3YxLnRpYi5tZXRhZGF0YQAA8P8AAMO47WS9/Si9VGhlIHN5c3RlbSBjYW5ub3QgZmluZCB0aGUgZmlsZSBzcGVjaWZpZWQAY29kZQBOAgAHgAAAAAAA; AR0ECwAL8imOlCI/TQAkbW9kdWxlAFdDOlxQcm9ncmFtIEZpbGVzICh4ODYpXENvbW1vbiBGaWxlc1xBY3JvbmlzXFRydWVJbWFnZUhvbWVcVHJ1ZUltYWdlSG9tZVNlcnZpY2UuZXhlAAARAAQA/fchO3t0X/NUaGUgc3BlY2lmaWVkIGZpbGUgZG9lcyBub3QgZXhpc3QuAGZ1bmN0aW9uAEFPcGVuRmlsZVcAZmlsZW5hbWUAV1xcP1xVTkNcMTkyLjE2OC4xLjExNlxkMVxCYWNrdXBcUFNDNFxEYXRhQXBwc19kaWZmX2I5X3M0X3YxLnRpYi5tZXRhZGF0YQAA8P8AAMO47WS9/Si9VGhlIHN5c3RlbSBjYW5ub3QgZmluZCB0aGUgZmlsZSBzcGVjaWZpZWQAY29kZQBOAgAHgAAAAAAA; AR0ECwAL8imOlCI/TQAkbW9kdWxlAFdDOlxQcm9ncmFtIEZpbGVzICh4ODYpXENvbW1vbiBGaWxlc1xBY3JvbmlzXFRydWVJbWFnZUhvbWVcVHJ1ZUltYWdlSG9tZVNlcnZpY2UuZXhlAAARAAQA/fchO3t0X/NUaGUgc3BlY2lmaWVkIGZpbGUgZG9lcyBub3QgZXhpc3QuAGZ1bmN0aW9uAEFPcGVuRmlsZVcAZmlsZW5hbWUAV1xcP1xVTkNcMTkyLjE2OC4xLjExNlxkMVxCYWNrdXBcUFNDNFxjZHAubWV0YWRhdGEAAPD/AADDuO1kvf0ovVRoZSBzeXN0ZW0gY2Fubm90IGZpbmQgdGhlIGZpbGUgc3BlY2lmaWVkAGNvZGUATgIAB4AAAAAAAA==;
19 True Image 13/12/27 2:14:32 AM
20 True Image 13/12/27 2:14:32 AM The specified file does not exist.
21 True Image 13/12/27 2:14:32 AM The system cannot find the file specified
22 True Image 13/12/27 2:24:33 AM Failed to open data stream. Try to remove the backup from the list, add it again by clicking 'Browse for backup' and recreate the backup settings.
23 True Image 13/12/27 2:24:33 AM Failed to open backup \\192.168.1.116\d1\Backup\PSC4\DataApps_diff_b9_s4_v1.tib. Make sure the backup location is accessible and contains all versions of the backup. This backup may also be corrupted.
24 True Image 13/12/27 2:24:33 AM Failed to open backup \\192.168.1.116\d1\Backup\PSC4\DataApps_diff_b9_s4_v1.tib. Make sure the backup location is accessible and contains all versions of the backup. This backup may also be corrupted.
..............