<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>BackupChain FAQ &#187; Backup Issues</title>
	<atom:link href="https://backupchain.com/faq/category/backup-issues/feed/" rel="self" type="application/rss+xml" />
	<link>https://backupchain.com/faq</link>
	<description>BackupChain&#039;s Frequently Asked Questions Answered</description>
	<lastBuildDate>Tue, 07 Apr 2026 13:57:16 +0000</lastBuildDate>
	<language>en-US</language>
		<sy:updatePeriod>hourly</sy:updatePeriod>
		<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=4.0</generator>
	<item>
		<title>Fixing VSS_E_FLUSH_WRITES_TIMEOUT on PCs</title>
		<link>https://backupchain.com/faq/fixing-vss_e_flush_writes_timeout-on-pcs/</link>
		<comments>https://backupchain.com/faq/fixing-vss_e_flush_writes_timeout-on-pcs/#comments</comments>
		<pubDate>Thu, 01 Apr 2021 15:44:17 +0000</pubDate>
		<dc:creator><![CDATA[Mel]]></dc:creator>
				<category><![CDATA[Backup Issues]]></category>

		<guid isPermaLink="false">http://backupchain.com/faq/?p=751</guid>
		<description><![CDATA[The error VSS_E_FLUSH_WRITES_TIMEOUT may occur in various circumstances. This error usually means the preparation of a VSS shadow took too long. The timeout is fixed in Windows and can&#8217;t be changed. Usual suspects here are heavy fragmentation on C: or having too many shadows in the system. Please check using vssadmin list shadows there should [&#8230;]]]></description>
		<wfw:commentRss>https://backupchain.com/faq/fixing-vss_e_flush_writes_timeout-on-pcs/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How to Fix: &#8220;Error Creating Hard Drive Snapshot&#8221; and VSS Errors</title>
		<link>https://backupchain.com/faq/how-to-fix-error-creating-hard-drive-snapshot-and-vss-errors/</link>
		<comments>https://backupchain.com/faq/how-to-fix-error-creating-hard-drive-snapshot-and-vss-errors/#comments</comments>
		<pubDate>Wed, 11 Feb 2015 15:57:53 +0000</pubDate>
		<dc:creator><![CDATA[Mel]]></dc:creator>
				<category><![CDATA[Backup Issues]]></category>

		<guid isPermaLink="false">http://backupchain.com/faq/?p=89</guid>
		<description><![CDATA[The log entry &#8220;Error Creating Hard Drive Snapshot&#8221; indicates a &#8216;fatal VSS&#8217; issue in the VSS system of Windows. Without a valid snapshot of the hard drive, BackupChain cannot proceed. To inspect the Windows Event Viewer logs, see Troubleshooting Volume Shadow Copy Errors: First Steps In the case of Hyper-V being used, make sure you [&#8230;]]]></description>
		<wfw:commentRss>https://backupchain.com/faq/how-to-fix-error-creating-hard-drive-snapshot-and-vss-errors/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Network Backups: Common Pitfalls</title>
		<link>https://backupchain.com/faq/network-backups-common-pitfalls/</link>
		<comments>https://backupchain.com/faq/network-backups-common-pitfalls/#comments</comments>
		<pubDate>Thu, 29 Jan 2015 13:33:19 +0000</pubDate>
		<dc:creator><![CDATA[Mel]]></dc:creator>
				<category><![CDATA[Backup Issues]]></category>
		<category><![CDATA[General Backups]]></category>
		<category><![CDATA[Network]]></category>

		<guid isPermaLink="false">http://backupchain.com/faq/?p=80</guid>
		<description><![CDATA[First of all make sure the network drive is NTFS formatted. If it is not, there will be critical limitations, depending on the file system used. NTFS allows paths to reach over 32,000 letters, whereas Linux file systems don’t. Linux file systems have different file size limits and file name limits (not just full path [&#8230;]]]></description>
		<wfw:commentRss>https://backupchain.com/faq/network-backups-common-pitfalls/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How to Fix Hyper-V Backup Errors Quickly</title>
		<link>https://backupchain.com/faq/what-to-do-when-vm-backups-fail/</link>
		<comments>https://backupchain.com/faq/what-to-do-when-vm-backups-fail/#comments</comments>
		<pubDate>Wed, 21 Jan 2015 18:59:43 +0000</pubDate>
		<dc:creator><![CDATA[Mel]]></dc:creator>
				<category><![CDATA[Backup Issues]]></category>
		<category><![CDATA[Hyper-V]]></category>

		<guid isPermaLink="false">http://backupchain.com/faq/?p=52</guid>
		<description><![CDATA[When backing up Hyper-V VMs, VSS errors (Volume Shadow Copy Service) are not uncommon. The error potential for VM backups is much higher than for physical servers because many resources are shared and live backup requires the (error-free) participation of all VSS aware services inside each VM. Any resource shortage of service configuration issue inside a VM [&#8230;]]]></description>
		<wfw:commentRss>https://backupchain.com/faq/what-to-do-when-vm-backups-fail/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How to Fix VSS Errors</title>
		<link>https://backupchain.com/faq/how-to-fix-vss-errors/</link>
		<comments>https://backupchain.com/faq/how-to-fix-vss-errors/#comments</comments>
		<pubDate>Wed, 21 Jan 2015 18:53:55 +0000</pubDate>
		<dc:creator><![CDATA[Mel]]></dc:creator>
				<category><![CDATA[Backup Issues]]></category>

		<guid isPermaLink="false">http://backupchain.com/faq/?p=50</guid>
		<description><![CDATA[VSS (Volume Shadow Copy Service) errors are not uncommon. VSS is a Windows component made by Microsoft and is the key to obtaining consistent and reliable live backups in Windows&#8211;there is no other way to achieve it. VSS errors are known to have thousands of potential origins; therefore, the best thing to do is to [&#8230;]]]></description>
		<wfw:commentRss>https://backupchain.com/faq/how-to-fix-vss-errors/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>What Do I Need to Know When Backing up Hyper-V CSVs?</title>
		<link>https://backupchain.com/faq/what-do-i-need-to-know-when-backing-up-hyper-v-csvs/</link>
		<comments>https://backupchain.com/faq/what-do-i-need-to-know-when-backing-up-hyper-v-csvs/#comments</comments>
		<pubDate>Wed, 21 Jan 2015 17:31:57 +0000</pubDate>
		<dc:creator><![CDATA[Mel]]></dc:creator>
				<category><![CDATA[Backup Issues]]></category>
		<category><![CDATA[Hyper-V]]></category>
		<category><![CDATA[VM Backup]]></category>

		<guid isPermaLink="false">http://backupchain.com/faq/?p=31</guid>
		<description><![CDATA[When you&#8217;re dealing with Windows Server 2012 R2 CSV backups you need to be aware of the following: use Hyper-V Backup types only, not Universal overlapping backups (simultaneous backups between two or more nodes) are now permitted. Server 2008 R2 couldn&#8217;t do that make sure all VM files are on the one and same CSV: [&#8230;]]]></description>
		<wfw:commentRss>https://backupchain.com/faq/what-do-i-need-to-know-when-backing-up-hyper-v-csvs/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Why is &#8220;total bytes read&#8221; so low in the log stats?</title>
		<link>https://backupchain.com/faq/why-is-total-bytes-read-so-low-in-the-log-stats/</link>
		<comments>https://backupchain.com/faq/why-is-total-bytes-read-so-low-in-the-log-stats/#comments</comments>
		<pubDate>Wed, 21 Jan 2015 17:22:59 +0000</pubDate>
		<dc:creator><![CDATA[Mel]]></dc:creator>
				<category><![CDATA[Backup Issues]]></category>

		<guid isPermaLink="false">http://backupchain.com/faq/?p=27</guid>
		<description><![CDATA[The read and write &#8220;total bytes&#8221; are the same when there is no compression or deduplication occurring. When compression or deduplication is being used, the total bytes read should be higher than total bytes written, since compression reduces the write volume. The read volume is less than the total of all original files because some [&#8230;]]]></description>
		<wfw:commentRss>https://backupchain.com/faq/why-is-total-bytes-read-so-low-in-the-log-stats/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
