URGENT: Windows Node wont backup

Jun 10, 2009, 10:04 PM #1
bartdaniels Member Join: Nov 2008 Posts: 46	URGENT: Windows Node wont backup Hi People's, I am hoping someone can help me ASAP. We have just recently updated a Windows Vz4 node and when we backup via command line we get the following error: --------------- C:\Documents and Settings\Administrator>vzbackup 101 -I * Operation backup_env with the Env(s) VPS101 is started * Backing up environment VPS101 locally * Checking parameters * Creating backup 6dba3650-1847-4b74-ba64-f107bd981f13/20090611015137 * Adjusting backup type (incremental) * Backup storage: receiving backup file * Backing up private area * Backing up whole drive C: 100% \|*********************************************** **********\| Operation backup_env with the Env(s) VPS101 is finished with errors: Failed to backup partition Acronis Error: Module=7 Code=1, "Internal error: start sector is not in uncopied area"{=0}, Tag=0 . Backup operation for node 'node14' failed: Failed to backup partition Acronis Error: Module=7 Code=1, "Internal error: start sector is not in uncopied area"{=0}, Tag=0 Backup failed --------------- All VPS's are like this. Anyone can suggest how to resolve this. Thanks Bart

Jun 10, 2009, 10:04 PM

bartdaniels
Member

Join: Nov 2008
Posts: 46

URGENT: Windows Node wont backup

Hi People's,

I am hoping someone can help me ASAP.
We have just recently updated a Windows Vz4 node and when we backup via command line we get the following error:
---------------

C:\Documents and Settings\Administrator>vzbackup 101 -I
* Operation backup_env with the Env(s) VPS101 is started
* Backing up environment VPS101 locally
* Checking parameters
* Creating backup 6dba3650-1847-4b74-ba64-f107bd981f13/20090611015137
* Adjusting backup type (incremental)
* Backup storage: receiving backup file
* Backing up private area
* Backing up whole drive C:
100% |************************************************* *************|
* Operation backup_env with the Env(s) VPS101 is finished with errors: Failed
to backup partition
Acronis Error: Module=7 Code=1, "Internal error: start sector is not in uncopied
area"{=0}, Tag=0
.
Backup operation for node 'node14' failed: Failed to backup partition
Acronis Error: Module=7 Code=1, "Internal error: start sector is not in uncopied
area"{=0}, Tag=0

Backup failed
---------------

All VPS's are like this.

Anyone can suggest how to resolve this.

Thanks
Bart

Jun 11, 2009, 05:46 AM #2
gbevan Junior Member Join: Jun 2008 Posts: 13	Hi Bart. It's a bug (known to the developers) introduced by a recent update. Only workaround is to swap to FULL backups instead of incremental. AFAIK, the developers haven't released a fix yet. By the way, look out for the BSOD's during backups (also caused by a recent update)! Grahame.

Jun 11, 2009, 08:32 PM #3
bartdaniels Member Join: Nov 2008 Posts: 46	G'Day Grahame, Thanks for that, and S*&T...lol.. Well i found another way around it and that was to create a new directory called 'new_backups' and let the sets start again. I have had this problem in the past with Acronis Imaging software itself. It is normally caused by updates where Acronis can't create another incremental for a Full Set that was created by a previous version. Thanks for the info about BSOD, didn't know that one. Would explain why 1 node rebooted itself mid backups. Cheers Bart

Jun 11, 2009, 08:32 PM

bartdaniels
Member

Join: Nov 2008
Posts: 46

G'Day Grahame,

Thanks for that, and S*&T...lol..

Well i found another way around it and that was to create a new directory called 'new_backups' and let the sets start again.

I have had this problem in the past with Acronis Imaging software itself. It is normally caused by updates where Acronis can't create another incremental for a Full Set that was created by a previous version.

Thanks for the info about BSOD, didn't know that one. Would explain why 1 node rebooted itself mid backups.

Cheers
Bart

Jun 12, 2009, 12:14 PM #4
ithomas Senior Member Join: Jun 2008 Posts: 207	I was having all kinds of BSOD problems on my master/ backup node and had a case for this last week. The developers finally provided an updated vzdisk.sys driver file and I'm good as gold at this point. I suspect the fix will be included in an update soon.

Jun 12, 2009, 07:27 PM #5
bartdaniels Member Join: Nov 2008 Posts: 46	Lets hope they fix it sooner rather than later. Or we are all up shit creek without a paddle. We now have 4 Windows Vz nodes that are affected. Cheers Bart

Jun 14, 2009, 07:14 AM #6
gbevan Junior Member Join: Jun 2008 Posts: 13	I'm really hacked off with VZ support. I've had a ticket open for weeks on this issue and I find out on the forums that there's an updated vzdisk.sys driver available! I'll be having strong words with them methinks... Thanks for the heads up ithomas! Bart's right, we need this sorting ASAP, I'm at the point now where my host servers are blus screening almost every night. If things don't improve radically (and soon) it'll be Xen here I come...

Jun 14, 2009, 07:14 AM

gbevan
Junior Member

Join: Jun 2008
Posts: 13

I'm really hacked off with VZ support. I've had a ticket open for weeks on this issue and I find out on the forums that there's an updated vzdisk.sys driver available! I'll be having strong words with them methinks... Thanks for the heads up ithomas! Bart's right, we need this sorting ASAP, I'm at the point now where my host servers are blus screening almost every night. If things don't improve radically (and soon) it'll be Xen here I come...

Jun 14, 2009, 06:38 PM #7
bartdaniels Member Join: Nov 2008 Posts: 46	Grahame, Do you know where on the Parallel's website they have any information about the issues with the current updates? Cheers Bart

Jun 14, 2009, 07:51 PM #8
xt881m Member Join: Dec 2008 Posts: 67	Any news on an update to fix this?

Jun 15, 2009, 01:03 AM #9
MitchelP Junior Member Join: Jun 2009 Posts: 1	Linux nodes too! It's not just Windows nodes by the looks, we performed an update of all our Linux nodes last week to latest VZ and since that update it's impossible to backup a container using full or incremental backups locally or remote, all backups error as follows; Operation backup_env with the Env(s) "Container Name" is finished with errors: Failed to start the file backup Acronis Error: Module=0 Code=0, Tag=0,. And this is happening on all our nodes, different types of hardware since the update! Cheers, Mitch

Jun 15, 2009, 01:03 AM

MitchelP
Junior Member

Join: Jun 2009
Posts: 1

Linux nodes too!

It's not just Windows nodes by the looks, we performed an update of all our Linux nodes last week to latest VZ and since that update it's impossible to backup a container using full or incremental backups locally or remote, all backups error as follows;

Operation backup_env with the Env(s) "Container Name" is finished with errors: Failed to start the file backup Acronis Error: Module=0 Code=0, Tag=0,.

And this is happening on all our nodes, different types of hardware since the update!

Cheers,
Mitch

Jun 15, 2009, 04:10 PM #10
ithomas Senior Member Join: Jun 2008 Posts: 207	One more update on this, perhaps getting off topic a bit. I ran 6 days with the updated vzdisk.sys with no blue screens or issues, then the system became completely unresponsive while running the template creation wizard, meaning the screen was black, did not respond to keyboard, mouse, or ping- I had to hit the old power button in the middle of business hours. I gave the dump to support and they say the way the system was process registry keys is at issue and will be fixed in VZ4000022, but the release notes for VZ4000021 are not out yet. 21 does support some Windows Updates, and I'm so desperate to have a stable system I went ahead and applied 21.

Jun 15, 2009, 04:10 PM

#10

ithomas
Senior Member

Join: Jun 2008
Posts: 207

One more update on this, perhaps getting off topic a bit. I ran 6 days with the updated vzdisk.sys with no blue screens or issues, then the system became completely unresponsive while running the template creation wizard, meaning the screen was black, did not respond to keyboard, mouse, or ping- I had to hit the old power button in the middle of business hours.

I gave the dump to support and they say the way the system was process registry keys is at issue and will be fixed in VZ4000022, but the release notes for VZ4000021 are not out yet. 21 does support some Windows Updates, and I'm so desperate to have a stable system I went ahead and applied 21.

Jun 15, 2009, 07:36 PM #11
xt881m Member Join: Dec 2008 Posts: 67	MitchelP - that issue is actually unrelated... we had it on one of our Windows nodes. Curiously Parallels support had no idea about the issue nor what was causing it. Then the issue either fixed itself or Parallels fixed it without telling us.

Jun 16, 2009, 02:41 AM #12
bartdaniels Member Join: Nov 2008 Posts: 46	Hi MitchelP, Thanks for that, I will ensure NOT to update our Linux nodes till this has been resolved. Sigh...4 out of 12 Windows Nodes affected 0 out of 14 Linux Nodes Affected (Well thats a positive ) Thanks Guys, Bart

Jun 17, 2009, 07:47 PM #13
bartdaniels Member Join: Nov 2008 Posts: 46	Hi Y'all, Actually, does anyone know exactly which update caused this? Just if we deploy a new node will ensure it does not have that update. Cheers Bart

Jun 18, 2009, 12:43 AM #14
ithomas Senior Member Join: Jun 2008 Posts: 207	My personal opinion, based somewhat on my logs of updates/ changes on my hardware nodes, is that everything from VZ400011, and the PIM updates from that era, have caused certain problems and solved others. I'm putting a new node in next week, and I intend to bring the updates to current revisions simply because A) I'm pretty tight about wanting Windows Updates in place sooner than later in many cases as Microsoft is terrible on security, still.., and B) I use Provision Networks for access to Virtual Desktops. I still believe that many of the problems we have been talking about are updates to the source code of 4.0 to accommodate the partnership with Quest, and the VZ and PIM updates that have been added since that relationship was forged have fundamentally changed 4.0 into a new version. The trouble is, it wasn't rolled out as a new version and is just now seeming to become more stable. There is more to go, and if they are testing their updates before releasing them, I think things will get back on track. I just wish they would put out real release notes documenting the actual changes that are in the updates so that we can know what to look for when things start breaking. It seems arrogant on their part for the company to assume we will automatically download and install problematic code based on trust.

Jun 18, 2009, 12:43 AM

#14

ithomas
Senior Member

Join: Jun 2008
Posts: 207

My personal opinion, based somewhat on my logs of updates/ changes on my hardware nodes, is that everything from VZ400011, and the PIM updates from that era, have caused certain problems and solved others. I'm putting a new node in next week, and I intend to bring the updates to current revisions simply because A) I'm pretty tight about wanting Windows Updates in place sooner than later in many cases as Microsoft is terrible on security, still.., and B) I use Provision Networks for access to Virtual Desktops.

I still believe that many of the problems we have been talking about are updates to the source code of 4.0 to accommodate the partnership with Quest, and the VZ and PIM updates that have been added since that relationship was forged have fundamentally changed 4.0 into a new version. The trouble is, it wasn't rolled out as a new version and is just now seeming to become more stable. There is more to go, and if they are testing their updates before releasing them, I think things will get back on track.

I just wish they would put out real release notes documenting the actual changes that are in the updates so that we can know what to look for when things start breaking. It seems arrogant on their part for the company to assume we will automatically download and install problematic code based on trust.

Jun 22, 2009, 04:20 AM #15
Ozgur Erdogan Junior Member Join: Mar 2009 Posts: 3	Backup causing some services to stop. I had the same problem and swap backup type to full. But guys I have some other problem, during or after backup not sure, dns service stopped and I set service's properties to restart on failure. But yesterday I saw SQL service was stopped and did not restart. What could causes services to stop when backing up? Should I schedule server to restart after backup is complete? Thanks in advance.

Jun 22, 2009, 04:20 AM

#15

Ozgur Erdogan
Junior Member

Join: Mar 2009
Posts: 3

Backup causing some services to stop.

I had the same problem and swap backup type to full. But guys I have some other problem, during or after backup not sure, dns service stopped and I set service's properties to restart on failure. But yesterday I saw SQL service was stopped and did not restart.

What could causes services to stop when backing up? Should I schedule server to restart after backup is complete?

Thanks in advance.

Jun 24, 2009, 04:05 AM #16
gbevan Junior Member Join: Jun 2008 Posts: 13	Heads up... VZU400022 update for Parallels Virtuozzo Containers 4.0 Release notes -------------------------------------------------------------------------------- Synopsis: New Parallels Virtuozzo Containers 4.0 update fixes the compatibility issues with several applications, provides major improvements in backup technology and a number of other bugfixes. Issue date: 2009-22-06 Product: Parallels Virtuozzo Containers 4.0 Keywords: RGS, Radmin, Wyse TCX USB Virtualizer -------------------------------------------------------------------------------- ...so who dares try it and post back their findings ) Grahame.

Jun 24, 2009, 04:05 AM

#16

gbevan
Junior Member

Join: Jun 2008
Posts: 13

Heads up...

VZU400022 update for Parallels Virtuozzo Containers 4.0

Release notes
--------------------------------------------------------------------------------
Synopsis: New Parallels Virtuozzo Containers 4.0 update fixes the compatibility issues with several applications, provides major improvements in backup technology and a number of other bugfixes.
Issue date: 2009-22-06
Product: Parallels Virtuozzo Containers 4.0
Keywords: RGS, Radmin, Wyse TCX USB Virtualizer
--------------------------------------------------------------------------------

...so who dares try it and post back their findings

)

Grahame.

Jun 24, 2009, 06:49 PM #17
ithomas Senior Member Join: Jun 2008 Posts: 207	I was installing a new hardware node yesterday and got patch 22 during the install. The server is blue screening in a loop today, (it started while building the service container) and I am not in that building, but I suspect that there is a driver issue on the NICS that didn't play well with Windows/ Virtuozzo Clustering. I'll post when I know something, and I hope someone with a Virtuozzo sandbox will test this out for us. The release notes were nicely detailed this time so we know what this patch fixes, and when to suspect the patch if there are new problems; as far as I can tell, there were never any release notes for Patch 21.

Jun 24, 2009, 06:49 PM

#17

ithomas
Senior Member

Join: Jun 2008
Posts: 207

I was installing a new hardware node yesterday and got patch 22 during the install. The server is blue screening in a loop today, (it started while building the service container) and I am not in that building, but I suspect that there is a driver issue on the NICS that didn't play well with Windows/ Virtuozzo Clustering. I'll post when I know something, and I hope someone with a Virtuozzo sandbox will test this out for us.

The release notes were nicely detailed this time so we know what this patch fixes, and when to suspect the patch if there are new problems; as far as I can tell, there were never any release notes for Patch 21.

Jun 25, 2009, 10:07 AM #18
ithomas Senior Member Join: Jun 2008 Posts: 207	VZ400022 was a machine killer for me with a Blue Screen Windows Protection error. I had to go into safe mode, disable all Virutozzo services, reboot, uninstall the patch, re-enable all services, reboot to get back in business. The problem occured on two nodes, one non-production and one production.

Jun 26, 2009, 06:08 AM #19
gbevan Junior Member Join: Jun 2008 Posts: 13	I was desparate for the backup / blue screen fix, so I went ahead and installed update 22. It's been running on 2 nodes now for a couple of days and (so far) it seems OK. The backups are now working correctly and I haven't had any more blue screens (yet). Early days, but it looks promising. If anything to the contrary crops up I'll post again as a warning to others. Thankfully I haven't had the same experience as ithomas (bad luck mate )

Jun 26, 2009, 06:08 AM

#19

gbevan
Junior Member

Join: Jun 2008
Posts: 13

I was desparate for the backup / blue screen fix, so I went ahead and installed update 22. It's been running on 2 nodes now for a couple of days and (so far) it seems OK. The backups are now working correctly and I haven't had any more blue screens (yet). Early days, but it looks promising. If anything to the contrary crops up I'll post again as a warning to others. Thankfully I haven't had the same experience as ithomas (bad luck mate

)

Jun 26, 2009, 07:19 AM #20
ithomas Senior Member Join: Jun 2008 Posts: 207	I can't figure out why this keeps happening to me. My master node is constant trouble, my slave is no trouble at all. The new cluster master node looks like it has already picked up the issues of the older master. Parallels support is being great, they are not saying I have any mis configurations, and the latest reasons for my blue screens were specifically addressed in the release notes for 22. On the new node, the installer ran, auto applied all patches, and the minute it started building the service container I was dead in the water-- go figure.

Jun 26, 2009, 07:19 AM

#20

ithomas
Senior Member

Join: Jun 2008
Posts: 207

I can't figure out why this keeps happening to me. My master node is constant trouble, my slave is no trouble at all. The new cluster master node looks like it has already picked up the issues of the older master. Parallels support is being great, they are not saying I have any mis configurations, and the latest reasons for my blue screens were specifically addressed in the release notes for 22.

On the new node, the installer ran, auto applied all patches, and the minute it started building the service container I was dead in the water-- go figure.

Post Reply

« Previous Thread | Next Thread »

1 | 2 | >

Search this thread	Forum jump
Advanced Search

Thread tools	Display modes
Printable Version Email this Page	Linear Mode Hybrid Mode Threaded Mode

Parallels Technology Network

URGENT: Windows Node wont backup