From c301b1bfd9b3f97207573c01ad08c7af47c32694 Mon Sep 17 00:00:00 2001
From: asdffdsa6131 <42986211+asdffdsa6131@users.noreply.github.com>
Date: Sun, 8 Sep 2019 12:01:26 -0400
Subject: [PATCH] Updated How to enable VSS for rclone (markdown)

---
 How-to-enable-VSS-for-rclone.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/How-to-enable-VSS-for-rclone.md b/How-to-enable-VSS-for-rclone.md
index b0b01a7..6e78222 100644
--- a/How-to-enable-VSS-for-rclone.md
+++ b/How-to-enable-VSS-for-rclone.md
@@ -9,6 +9,7 @@ If Veeam backup software would run again while rclone is still uploading, Veeam
 
 So I create a VSS read-only point-in-time snapshot and have rclone use that as the source.
 Now rclone can takes its time, upload, sync, check or whatever and not be concerned that the data will be modified.
+
 --- The snapshot's files are never in-use. rclone will not get an error about in-use files.
 --- The snapshot's files are never locked. rclone will not get an error about locked files.