<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
	<channel>
		<title><![CDATA[Latest posts for the topic "offsite network backup"]]></title>
		<link>https://forums.qrecall.com/posts/list/2.page</link>
		<description><![CDATA[Latest messages posted in the topic "offsite network backup"]]></description>
		<generator>JForum - http://www.jforum.net</generator>
			<item>
				<title>offsite network backup</title>
				<description><![CDATA[ I currently use Apple's Backup program to maintain an offsite backup of important files on dot Mac (soon to be mobileme), and I'm wondering if qrecall might do a better job. I'd like to check out some of the assumptions I'm making about how things work over a network, though, and get any other thoughts you might have before I try it. <br> <br>Would the processing reduction gained by using smaller archives make it worthwhile to have separate archives for different groups of files, particularly for groups of files that I might want to update less frequently? <br> <br>Capture compression should reduce the amount of backup data to be transmitted, but would it also impose additional interchanges between qrecall and the archive that would negate these savings? <br> <br>Would merging and other management processes be inordinately time-consuming over the internet? <br> <br>Do you have any other thought pro or con about using qrecall over the internet? <br> <br>Ralph]]></description>
				<guid isPermaLink="true">https://forums.qrecall.com/posts/preList/138/576.page</guid>
				<link>https://forums.qrecall.com/posts/preList/138/576.page</link>
				<pubDate><![CDATA[Thu, 10 Jul 2008 21:33:34]]> GMT</pubDate>
				<author><![CDATA[ Ralph Strauch]]></author>
			</item>
			<item>
				<title>offsite network backup</title>
				<description><![CDATA[ [quote=Ralph Strauch]I currently use Apple's Backup program to maintain an offsite backup of important files on dot Mac (soon to be mobileme), and I'm wondering if qrecall might do a better job.[/quote]Alas, .Mac/MobileMe and QRecall are not a good mix. There's a long-winded discussion about why in the <a href="http://forums.qrecall.com/posts/list/91.page">Online storage</a> thread. But the short version is this: MobileMe is based on WebDAV which does not play well with QRecall. <br> <br>[quote]Would the processing reduction gained by using smaller archives make it worthwhile to have separate archives for different groups of files, particularly for groups of files that I might want to update less frequently?[/quote]Probably not. There's not much overhead associated with the data in an archive that [i]isn't[/i] being updated. The overhead of managing multiple archives probably outweighs the overhead of a lot of data that doesn't get updated that often. <br> <br>[quote]Capture compression should reduce the amount of backup data to be transmitted, but would it also impose additional interchanges between qrecall and the archive that would negate these savings?[/quote]Compress doesn't involve any additional communications. Overall, less data is transferred to a compressed archive than an uncompressed one. The penalty for compressing an archive is computational: Every time data is accessed from the archive it has be be decompressed and all new data has to be compressed. That just takes a lot of additional CPU cycles. <br> <br>[quote]Would merging and other management processes be inordinately time-consuming over the internet?[/quote]Yes. The best strategy would be to avoid them, or run them very infrequently (like once a month), if your only connection to the archive was over a slow communications link. <br> <br>[quote]Do you have any other thought pro or con about using qrecall over the internet?[/quote]If the file server you are storing the archive on is using a "real" remote file system protocol (like an AppleShare server) then you'll probably be OK capturing a modest amount of data and scheduling infrequent merge and capture actions. <br> <br>However, if you are using any WebDAV based service (MobileMe, Amazon SSS, AOL, ...) then it's impractical to use QRecall on the remote archive directly. Instead, consider getting a small USB thumb drive or small external drive and performing your captures to that. Once a week, or once a month, upload the archive to your off-site data store.]]></description>
				<guid isPermaLink="true">https://forums.qrecall.com/posts/preList/138/577.page</guid>
				<link>https://forums.qrecall.com/posts/preList/138/577.page</link>
				<pubDate><![CDATA[Thu, 10 Jul 2008 23:18:15]]> GMT</pubDate>
				<author><![CDATA[ James Bucanek]]></author>
			</item>
			<item>
				<title>Re:offsite network backup</title>
				<description><![CDATA[ Thanks for the explanations, James. I'm glad I asked before I set it up. I'll probably keep using Apple's Backup for the offsite backup. It does work, but is a far less elegant solution than qrecall. <br> <br>Ralph]]></description>
				<guid isPermaLink="true">https://forums.qrecall.com/posts/preList/138/580.page</guid>
				<link>https://forums.qrecall.com/posts/preList/138/580.page</link>
				<pubDate><![CDATA[Fri, 11 Jul 2008 08:45:48]]> GMT</pubDate>
				<author><![CDATA[ Ralph Strauch]]></author>
			</item>
	</channel>
</rss>