[CRTech] Christian Radio Tech [MSG 82207]
[Thread Prev] [-- Thread Index --] [Thread Next] [Date Prev] [-- Date Index --] [Date Next]
Re: AOMEI Backupper hiccups!
To: crtech@crtech.org
Subject: Re: AOMEI Backupper hiccups!
From: Terry Cowan <tcowan@knlr.com>
Date: Wed, 21 Feb 2018 12:44:48 -0800
Content-language: en-US
In-reply-to: <CAOkhgWpC+R5_pENKweoikH2U+5u+aWWbzsRGXe7GEgsMrPQ83g@mail.gmail.com>
References: <CAOkhgWpC+R5_pENKweoikH2U+5u+aWWbzsRGXe7GEgsMrPQ83g@mail.gmail.com>
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0

There is a little known command line copy utility which works well.  It can be placed in a batch file as follows and the batch file can be called by Scheduled Tasks.

The utility is called "robocopy" and has  attributes which allow you to copy new files to old and/or delete files on the target drive that no longer exist on the source drive.  You can get the attributes of RoboCopy by typing RoboCopy /? in a command prompt.

Here is a sample of code that I am using in a batch file.  The first thing it does is open a file which logs activity. 

In my case "q:" is the destination drive. 

Echo Backup Log For %date%  > c:\AutoBackup\MyCloudBackupLog.txt

Echo  %time% Copying C Drive >> c:\AutoBackup\MyCloudBackupLog.txt
RoboCopy c:\ q:\CBak /E /Purge /R:0 /W:0

****Additional Drives or folders to be copied****

Echo  %time% Finished >> c:\AutoBackup\MyCloudBackupLog.txt

Terry Cowan

KNLR/KNLX



On 02/21/18 11:55, Willie Barnett wrote:
Just FYI to the Braintrust...

I discovered (the HARD way) that the AOMEI Backupper V 3.5 (Free version) has a bug that crashes to BSOD with larger backups! (Over 50Gigs) It happened on two different machines, and different USB drives. Unfortunately, one of the USB drives appears to have been bricked! :(

I just tried V4.05 and it worked to create 53 Gig backup just fine! (Where 3.5 crashed.)

However, when I tried to restore a different file (33 Gigs) for another machine, the restored drive wouldn't boot! Plugged into my workhorse machine, the drive appeared empty! I rolled back to 3.2 and I'm trying that restore again.

I have had much success with V3.2 in the past, so here's hoping and praying it works for this important backup!! :o

Willie...



Follow-Ups: Re: AOMEI Backupper hiccups!
(Willie Barnett <wbradiolists@gmail.com>, 21 Feb 2018 20:50:16 -0000)
Re: AOMEI Backupper hiccups!
(John Stortz <ka4flx@gmail.com>, 26 Feb 2018 03:33:21 -0000)
References: AOMEI Backupper hiccups!
(Willie Barnett <wbradiolists@gmail.com>, 21 Feb 2018 19:55:45 -0000)
Prev by date: AOMEI Backupper hiccups!
(Willie Barnett, 21 Feb 2018 19:55:45 -0000)
Next by date: Re: AOMEI Backupper hiccups!
(Willie Barnett, 21 Feb 2018 20:50:16 -0000)
Prev by thread: AOMEI Backupper hiccups!
(Willie Barnett, 21 Feb 2018 19:55:45 -0000)
Next by thread: Re: AOMEI Backupper hiccups!
(Willie Barnett, 21 Feb 2018 20:50:16 -0000)
CRTech.org