Thanks Raptech.
Did a complete top down and these are my findings.
a) Step 1 - Couldn't find the BOOT media, so created one. In under 5m I was able to "boot" via the CD, get into the FULL version, access the last backup via the NETWORK, recovered selected directories to my notebook. Rebooted. Reviewed the recovered files - all fine. So that satisfies the "sniff" test as far as "can I get to the networked archives and recover?".
I remember having issues with 2010 I believe - had to download some updated ISO to get it to boot.
Tip: I have found that when you DO attempt to recover the drive letters never match what Windows assigns. Not sure why. But for years I have made it habit to name volumes by the letter. So for drive S: I call the volume "Seattle". C: "Clueless" etc. So when Acronis shows "E: Seattle" I know that is "S:"
b) Step 2 - Get a handle on how the backup is setup.
~ First I am doing INCREMENTAL and "create a new full every ... " and used 13. I think I wanted at the time 14 for a set. Either that or it was to match my anniversary day of the month (figured what is not to like with Friday the 13th?).
More below but I have changed that to 6.
c) Step 3 - Review the options.
~ All are based on my flavor but:
PERFORMANCE:
~ Compress level - Max
~ Priority - Low;
ADVANCED
~ Backup split - 1GB
~ Validation was [x] so I guess I turned that on before;
NOTIFICATION:
~ That is a great add-on; have it working perfectly and know everyday that it is complete. Even handles SSL connection.
d) So what is wrong?
~ (1) In my previous post I am full of Canadian Grade "A" Cow Shite. I have no clue what I was saying about creating a FULL then INCREMENTAL when the above is how it was setup.
~ (2) HOWEVER the naming I stated IS exactly as shown. You didn't mention CLEANUP. What are you doing about that? This goes hand in hand with the dates.
After reviewing again it appears that the backups go as follows:
P5(set)Number.tib.
Interestingly.
1st SET - P5.tib, P52.tib There is no "1".
2nd SET - P5(1).tib, P5(1)21.tib. .. something went wrong here. Might have archived.
3rd SET - P5(2)1.tib; P5(2)2.tib .. this one is exactly how I want to see it.
4th SET - P5(3)1.tib; P5(3)2.tib
.. 5th, 6th same thing.
It appears when there is a FIRST set, that a "1" is not being created. But subsequent to that it adds it.
I can add a date but won't the date change each day? I like a way to spot within a slew of files where one set starts and ends. See my question for you below.
I will monitor it going forward to see how this rollas I am cleaning up the directory
~ (3) Though 13 was used (Full after every 13 incrementals) it is clear that it is acting like 7. The Notebook is on everyday and I have backups everyday.
Here are the dates of the fulls:
Apr 5th, Apr 12th, Apr 19th, Apr 27th.
Now why Apr 27th and not Apr 26th is beyond me. For that matter why wasn't it honoring the 13 days I entered?
Anyways adjusted the number to 6 and we will see.
(e) Questions for you:
~ 1) As per your plan - how are you handling the sets once done? Moving them offline? Is the directory empty when the next full is done? Let Acronis handle it?
~ 2) Are you doing SECTOR BY SECTOR on the advanced? I left both boxes unchecked. (Image Creation)
So bottom line:
Acronis is backing up and data can be recovered. I just think I need, like the XP, a way to "clean up" the directory weekly - which is prudent anyways. Clean up as in moving a "week" offline.
Cheers! |
