[AccessD] System Image Failure

James Button jamesbutton at blueyonder.co.uk
Sat Jul 22 12:24:04 CDT 2017


Rocky,
I have a 64bit win-10 Pro system that was updated from 2K to XP to 7 ultimate to
the win-10  

And have given up on the Microsoft built-in to windows backup facilities - 
Basically File-History will NOT backup files with long full-names, and 
I get System Image working to do backups on a monthly basis - and after a couple
of backups it stops working again.

There is the additional consideration that the backup processes REQUIRE the
backup destination to be accessible at all times so that any crypto-malware can
make them inaccessible.

I now use Todo for monthly backup images and Paragon for full sets of the OS
partition and daily incrementals to a removable drive and - as the user can
access those backup files, they get copied to additional cycle of drives that
get cycled - so the most recent full backup is also on a device that is not
accessible to crypto=malware, and is also safe from a system failure - (had one
that took out the OS drive, data drive, and the backup drive)  
I also run a script to backup the files from my data areas where the file has a
date that is = or later than the last backup done to the selected backup drive 
And run spideroak to have the really-don't-want-2-lose files to their free 2GB
of cloud space 
You could take up a crashplan sub for unlimited space for that sort of thing 

Considerations:
Cloud upload speed 
Uploaded file management facility - so that's Onedrive out of consideration

What are you thinking of recovering from 
Lost file - finger trouble - The incrementals - or maybe if it actually saved
the file, File-History - just go to the store and pick the copy you want to edit
Or Crashplan - as a replacement for the FileHistory - no sub - just use your own
drives for the storage
Or Crashplan with sub - and pick whichever of the backups you want to recover  
Or Spideroak 
Both Crashplan and Spideroak can be set to take frequent copies of whatever you
change in the specified folders - and the encrypted backups can be downloaded to
any PC you set to be allowed to access your store, and enter the decryption code
into.

Hard drive died - so you'll be replacing the drive - need a drive image - that's
Todo or Paragon (etc.)
PC died - new PC will probably mean newer motherboard and CPU - So need the have
a facility to download the old OS to the new drive, then do a PE type update to
that OS to have it work on the new hardware - (OS licence needed too)

PC taken away - with the backup devices and all paperwork - You'll need to get
the backup from offsite store 
That's where maybe Crashplan comes in - having allowed Crashplan the time needed
to upload a backup fileset of your old system
And set Crashplan to also upload the incrementals - of the backups, 
or just changes to your data and rely on the windows-update to update the old
windows system backup to the current windows update status ( the office apps
etc. too)

For that - consider the upload speed - for the backups - 
OS - maybe a 100GB backup set for 200GB of Windows OS  
and maybe 8GB for each day's incrementals on that

How often will you take - and backup a new full image - on the basis that the
incrementals for a fortnight may be as much as a new full set 
And the restore will need all the incrementals from the last full set you
download

Then you'll have to bring your data and things like email stores up-to-date

So- decide what you would need to recover from, and the time, money and effort
you are willing to put into the backup and the recovery process 
But - whatever 

DO NOT RELY on MICROSOFT built-in to WINDOWS facilities


JimB
  


-----Original Message-----
From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Rocky
Smolin
Sent: Saturday, July 22, 2017 3:39 PM
To: List <dba-tech at databaseadvisors.com>; 'Access Developers discussion and
problem solving' <accessd at databaseadvisors.com>; 'Off Topic'
<dba-ot at databaseadvisors.com>
Subject: [AccessD] System Image Failure

Dear List(s):

 

Per advice from MS on W10 (Control Panel\All Control Panel Items\Backup and
Restore (Windows 7)) I decided to do the system image and system repair
disk. (Why it says Windows 7 when I am running Windows 10 is another
mystery).  But it seems like having a system image file on an external HD or
DVD would be a good thing in case of a catastrophic failure of the SSD - my
primary C drive.

 

Creating the repair disk went fine, but I got a message from Image:

 

The Backup Failed. There is not enough disk space to create the volume
shadow copy.etc.  (0x80780119)  I checked my backup drive - nope - nearly a
TB available.  So I went to the internets and found this:

 

http://www.techrepublic.com/blog/windows-and-office/fix-the-0x80780119-error
-when-creating-a-system-image-in-windows-7-and-8/

 

which also shows a suitable for framing picture of my error message. There
follows an explanation that is such a rabbit hole that, in spite of my best
intentions to create a system image) I'm inclined to just keep using Norton
Ghost - which has been very effective and reliable for many years, instead
of trying to figure out how to repartition my SSD.

 

I'm trying to create a system image of the C drive.

 

My Disk 1 (disk 0 is the old rotator which I use for data storage, disk 1 is
the SSD)  partitions are 1) System Reserved 100MB 14% free, 2) Recovery
Partition 449MB 100% free, and C: 223BG NTFD 34% free.

 

Any advice on how to proceed here or an alternate backup system that would
be SIMPLE (legitimate advice includes walk away from the computer and take a
nice long bike ride down by the ocean)?

 

r

 

 

 

 

-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com



More information about the AccessD mailing list