Jump to content
mastercam

Windows 8 Support - testing backup and restore!

Recommended Posts

OK then....

 

The current production release installs on Window 8.

The client is seen by the server.

A backup is running now.

 

...and we're off....!

Share this post


Link to post
Share on other sites

Looks like the restore did not...restore.

 

 

 

We are using the production client and server....the Recovery CD is the BETA2 CD (allowing for IP configuration).

 

 

+ Executing Restore from Backup at 10/23/2012 9:45 AM (Execution unit 1)

10/23/2012 9:45:45 AM: Connected to minint-5rboaaf

To volume Local Disk (C:) on minint-5rboaaf...

- 10/23/2012 9:45:45 AM: Restoring from Backup Set H, Snapshot Win-8-Test, 10/22/2012 4:30:30 PM

T-29: MapError: unknown Windows error -2,147,212,270

T-29: VssWBeginRestore: PreRestore failed, osErr -2147212270, error -1001

10/23/2012 9:46:57 AM: Execution incomplete

Duration: 00:00:19 (00:00:03 idle/loading/preparing)

 

 

--------------------edit - add----------------------------------------

 

I re-ran it with the logging turned up:

 

+ Executing Restore from Backup at 10/23/2012 10:34 AM (Execution unit 1)

Progress 23/10/2,012 10:34:41: Preparing to execute...

Progress 23/10/2,012 10:34:41: Preparing to execute...

soctSetThread: socket thread now 0x8f0

necoWritePacket: cmd 101 [ 0 bytes]:

necoWritePacket: cmd 158 [ 0 bytes]:

necoIncoming: cmd 216 [ 218 bytes]: 12 cb 15 ac e2 82 41 be 74 7f 4a 2f 4e 62 b5 34

necoWritePacket: cmd 106 [ 36 bytes]: 00 00 00 00 52 65 73 74 6f 72 65 20 66 72 6f 6d

necoSetReserve: reserved for "Restore from Backup"

necoWritePacket: cmd 101 [ 0 bytes]:

necoWritePacket: cmd 158 [ 0 bytes]:

necoIncoming: cmd 216 [ 218 bytes]: 12 cb 15 ac e2 82 40 bf 75 7e 4b 2e 4f 63 b4 35

10/23/2012 10:34:41 AM: Connected to minint-graud1t

To volume Local Disk (C:) on minint-graud1t...

necoCmd: transaction 16: 'VAcc' on "pcpds"

necoDispatch: transaction 16: result 0

necoCmd: transaction 17: 'VAcc' on "pcpds"

necoDispatch: transaction 17: result 0

- 10/23/2012 10:34:41 AM: Restoring from Backup Set H, Snapshot Win-8-Test, 10/22/2012 4:30:30 PM

necoCmd: transaction 18: 'VAcc' on "pcpds"

necoDispatch: transaction 18: result 0

necoCmd: transaction 19: 'Delt' on "pcpds"

necoDispatch: transaction 19: result 0

necoCmd: transaction 20: 'VAcc' on "pcpds"

necoDispatch: transaction 20: result 0

necoCmd: transaction 21: 'VAcc' on "pcpds"

necoDispatch: transaction 21: result 0

Exec::ExecCreateStateFolder: C:\ProgramData\Retrospect\RtrExec.dir\Exec-1\State...

Progress 23/10/2,012 10:34:46: Retrieving Snapshot...

lvtrRescan: avail - minstart = 858,993,456, minstart = 163,840, minmem = 98,304

VssWEnumWriterMetadata: Excluding writer "System Writer" from the backup.

Excluded 0 files, zero K

Progress 23/10/2,012 10:34:51: Retrieving Snapshot...

Progress 23/10/2,012 10:34:51: Please wait...

Progress 23/10/2,012 10:34:51: Retrieving Snapshot...

vlocDmpDNew: creating directory C:\ProgramData\Retrospect\RtrExec.dir\Exec-1\State\MetaInfo, len 59, volume root C:\ProgramData\Retrospect\RtrExec.dir\Exec-1\State

vlocDmpDNew: creating directory C:\ProgramData\Retrospect\RtrExec.dir\Exec-1\State\MetaInfo\writer0000, len 70, volume root C:\ProgramData\Retrospect\RtrExec.dir\Exec-1\State

vlocDmpDNew: creating directory C:\ProgramData\Retrospect\RtrExec.dir\Exec-1\State\MetaInfo\writer0000\comp0000, len 79, volume root C:\ProgramData\Retrospect\RtrExec.dir\Exec-1\State

vlocDmpDNew: creating directory C:\ProgramData\Retrospect\RtrExec.dir\Exec-1\State\MetaInfo\writer0001, len 70, volume root C:\ProgramData\Retrospect\RtrExec.dir\Exec-1\State

vlocDmpDNew: creating directory C:\ProgramData\Retrospect\RtrExec.dir\Exec-1\State\MetaInfo\writer0001\comp0000, len 79, volume root C:\ProgramData\Retrospect\RtrExec.dir\Exec-1\State

vlocDmpDNew: creating directory C:\ProgramData\Retrospect\RtrExec.dir\Exec-1\State\MetaInfo\writer0002, len 70, volume root C:\ProgramData\Retrospect\RtrExec.dir\Exec-1\State

vlocDmpDNew: creating directory C:\ProgramData\Retrospect\RtrExec.dir\Exec-1\State\MetaInfo\writer0002\comp0000, len 79, volume root C:\ProgramData\Retrospect\RtrExec.dir\Exec-1\State

vlocDmpDNew: creating directory C:\ProgramData\Retrospect\RtrExec.dir\Exec-1\State\MetaInfo\writer0003, len 70, volume root C:\ProgramData\Retrospect\RtrExec.dir\Exec-1\State

vlocDmpDNew: creating directory C:\ProgramData\Retrospect\RtrExec.dir\Exec-1\State\MetaInfo\writer0004, len 70, volume root C:\ProgramData\Retrospect\RtrExec.dir\Exec-1\State

vlocDmpDNew: creating directory C:\ProgramData\Retrospect\RtrExec.dir\Exec-1\State\MetaInfo\writer0004\comp0000, len 79, volume root C:\ProgramData\Retrospect\RtrExec.dir\Exec-1\State

vlocDmpDNew: creating directory C:\ProgramData\Retrospect\RtrExec.dir\Exec-1\State\MetaInfo\writer0005, len 70, volume root C:\ProgramData\Retrospect\RtrExec.dir\Exec-1\State

vlocDmpDNew: creating directory C:\ProgramData\Retrospect\RtrExec.dir\Exec-1\State\MetaInfo\writer0006, len 70, volume root C:\ProgramData\Retrospect\RtrExec.dir\Exec-1\State

vlocDmpDNew: creating directory C:\ProgramData\Retrospect\RtrExec.dir\Exec-1\State\MetaInfo\writer0006\comp0000, len 79, volume root C:\ProgramData\Retrospect\RtrExec.dir\Exec-1\State

vlocDmpDNew: creating directory C:\ProgramData\Retrospect\RtrExec.dir\Exec-1\State\MetaInfo\writer0006\comp0001, len 79, volume root C:\ProgramData\Retrospect\RtrExec.dir\Exec-1\State

vlocDmpDNew: creating directory C:\ProgramData\Retrospect\RtrExec.dir\Exec-1\State\MetaInfo\writer0006\comp0002, len 79, volume root C:\ProgramData\Retrospect\RtrExec.dir\Exec-1\State

vlocDmpDNew: creating directory C:\ProgramData\Retrospect\RtrExec.dir\Exec-1\State\MetaInfo\writer0006\comp0003, len 79, volume root C:\ProgramData\Retrospect\RtrExec.dir\Exec-1\State

vlocDmpDNew: creating directory C:\ProgramData\Retrospect\RtrExec.dir\Exec-1\State\MetaInfo\writer0006\comp0004, len 79, volume root C:\ProgramData\Retrospect\RtrExec.dir\Exec-1\State

vlocDmpDNew: creating directory C:\ProgramData\Retrospect\RtrExec.dir\Exec-1\State\MetaInfo\writer0006\comp0005, len 79, volume root C:\ProgramData\Retrospect\RtrExec.dir\Exec-1\State

vlocDmpDNew: creating directory C:\ProgramData\Retrospect\RtrExec.dir\Exec-1\State\MetaInfo\writer0007, len 70, volume root C:\ProgramData\Retrospect\RtrExec.dir\Exec-1\State

vlocDmpDNew: creating directory C:\ProgramData\Retrospect\RtrExec.dir\Exec-1\State\MetaInfo\writer0007\comp0000, len 79, volume root C:\ProgramData\Retrospect\RtrExec.dir\Exec-1\State

vlocDmpDNew: creating directory C:\ProgramData\Retrospect\RtrExec.dir\Exec-1\State\MetaInfo\writer0008, len 70, volume root C:\ProgramData\Retrospect\RtrExec.dir\Exec-1\State

vlocDmpDNew: creating directory C:\ProgramData\Retrospect\RtrExec.dir\Exec-1\State\MetaInfo\writer0008\comp0000, len 79, volume root C:\ProgramData\Retrospect\RtrExec.dir\Exec-1\State

vlocDmpDNew: creating directory C:\ProgramData\Retrospect\RtrExec.dir\Exec-1\State\RtrRSM, len 57, volume root C:\ProgramData\Retrospect\RtrExec.dir\Exec-1\State

Progress 23/10/2,012 10:34:54: Completing restore...

necoCmd: transaction 22: 'VAcc' on "pcpds"

necoDispatch: transaction 22: result 0

necoCmd: transaction 23: 'VAcc' on "pcpds"

necoDispatch: transaction 23: result 0

necoCmd: transaction 24: 'VAcc' on "pcpds"

necoDispatch: transaction 24: result 0

necoCmd: transaction 25: 'VAcc' on "pcpds"

necoDispatch: transaction 25: result 0

necoCmd: transaction 26: 'XTpF' on "pcpds"

necoDispatch: transaction 26: result 0

necoCmd: transaction 27: 'FWrt' on "pcpds"

necoDispatch: transaction 27: result 0

necoCmd: transaction 28: 'XPrR' on "pcpds"

T-28: VssWPrepareForRestore: Volume changed, ASR will Recreate disk and format volumes

necoDispatch: transaction 28: result 0

necoWritePacket: cmd 302 [ 0 bytes]:

necoIncoming: cmd 303 [ 0 bytes]:

necoCmd: transaction 29: 'XBgR' on "pcpds"

T-29: MapError: unknown Windows error -2,147,212,270

T-29: VssWBeginRestore: PreRestore failed, osErr -2147212270, error -1001

necoDispatch: transaction 29: result 0

xpmrBeginRestore: Begin restore failed, error -1001 ( unknown Windows OS error)

10/23/2012 10:35:25 AM: Execution incomplete

Duration: 00:00:13 (00:00:04 idle/loading/preparing)

Progress 23/10/2,012 10:35:25: Execution incomplete

soccRecv: connection closed cleanly

necoWritePacket: cmd 101 [ 0 bytes]:

necoWritePacket: cmd 101 [ 0 bytes]:

necoWritePacket: cmd 101 [ 0 bytes]:

soctPreDispose: maximum queue depth was 1

Share this post


Link to post
Share on other sites

Restore is in progress!

 

It seems we really do need a drive the same or larger than the original - regardless of the fact the backup was only 20GB.

 

Original drive 150GB with 20GB of data

First restore drive 120GB - fail

Second restore drive 320GB - working!!

Share this post


Link to post
Share on other sites

Restore is in progress!

 

It seems we really do need a drive the same or larger than the original - regardless of the fact the backup was only 20GB.

 

Original drive 150GB with 20GB of data

First restore drive 120GB - fail

Second restore drive 320GB - working!!

Was the 120GB drive formatted using Windows 8?

Was the 320GB drive formatted using Windows 8?

 

What happens if you run CHKDSK on the 120GB drive, including surface scan? Or maybe format it using a "long" format (to flag off every bad sector)? Then try restoring again.

Share this post


Link to post
Share on other sites

The original drive was 250GB...formatted with WIn8 and Windows 8 installed.

A 120GB partition was set on it for the c:\drive...and that's all that was backed up. (in my earlier post I had 150GB...it should be 120GB)

 

The 'restore to' drive was a 120GB that we put in and just had the DR disk set up. (removed partion and added one).

We thought this would work because the backup was only around 20GB.

 

The 320GB was connected as a second drive to a computer(WIndows 7) and formatted. Then put into the notebook and the DR disk set the partition.

 

No, we did not run scans.

 

When we put in the larger drive...it worked!

Share this post


Link to post
Share on other sites

Yes, you wrote that the larger drive worked.

 

I try to understand why the smaller drive didn't work. I got the impression that you were working with different physical drives. A 120GB drive is probably old. Now you write the 120GB "drive" was just a partition.

 

Maybe the 320GB drive worked simply because it had only one partition? As I understand it now, the 120GB partition was one of the partitions on a drive. Maybe that would have worked if that was the only partition? Or the first partition?

Share this post


Link to post
Share on other sites

I contacted support and the error was due to the ASR writer looking for a drive the same size or larger than what was backed up.

 

Sorry for the confusion, I am working with someone that set up the machine for backup and restore - when I asked about the original drive, I was told it was 120GB...actually it was 250GB with a 120GB partition.

So, even though the backup was only for the C:\drive of 120GB....the drive itself was 250GB.

 

Here's a response from the tech:

Agent Response:

 

The issue is not the total amount of data you need to restore. The issue is that the ASR Writer that is looking for a specific disk size and when the disk size is smaller, the ASR writer fails.

 

Thank you for using Retrospect,

The Retrospect Support Team

Share this post


Link to post
Share on other sites

I'm familiar with it, as a lot of backup software just uses Microsofts built in components along with Volume Shadow Service (VSS)..

ASR is the WIndows API. http://blogs.technet.com/b/filecab/archive/2008/02/11/automated-system-recovery-asr-in-windows-server-2008-and-vista-sp1.aspx

 

But yea...I learned that Retrospect uses it too! :D

  • Like 1

Share this post


Link to post
Share on other sites

We restored a Windows 8 backup to a machine that had Win8 and a Mac OS on it (partitioned).

 

The restore went as planned and Win8 came up...however...the Mac OS was wiped out.

 

Can a restore be done to a partition?

Share this post


Link to post
Share on other sites

Please provide complete steps of what you did.

 

A "partition" is a "volume" and you always restore to a "volume", so I can't image what happened.

Share this post


Link to post
Share on other sites

I backed up a Windows 8 machine (Win 8 and Mac OS partitions).

 

Took machine with Mac OS and a clean partition and did a restore of Win 8.

 

I did not look to see about just restoring to a partition - I think that may be the issue.

 

I'm booting to the recovery disk to add it as a client - then see if I can view both paritions.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×