<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Work on BAFM</title><link>https://christian.blog.pakiheim.de/tags/work/</link><description>Recent content in Work on BAFM</description><generator>Hugo -- 0.160.1</generator><language>en</language><lastBuildDate>Tue, 09 Apr 2013 16:05:30 +0000</lastBuildDate><atom:link href="https://christian.blog.pakiheim.de/tags/work/index.xml" rel="self" type="application/rss+xml"/><item><title>Dealing with SnapVault replication issues</title><link>https://christian.blog.pakiheim.de/posts/2013-04-09_dealing-with-snapvault-replication-issues/</link><pubDate>Tue, 09 Apr 2013 16:05:30 +0000</pubDate><guid isPermaLink="false">http://blog.barfoo.org/?p=4596</guid><description>&lt;p&gt;Well, for the past two months I had a case open with NetApp to figure out this SnapVault replication issue we were seeing. The initial transfer of the SnapVault relation would complete with a hick up, manual snapshot transfers also work - just the scheduled, auto-created Snapshots won&amp;rsquo;t replicate.&lt;/p&gt;
&lt;p&gt;At first I (and the NetApp support) thought this was an issue with SnapVault itself, however after being away for the last four weeks I looked at the issue with fresh eyes. After a short peek into the logs, I found what I had found back when I first looked into this.&lt;/p&gt;</description></item></channel></rss>