Jump to content


Photo

How do you handle true incrementals with Robocopy or Allway Sync


  • Please log in to reply
6 replies to this topic

#1 kayache

kayache

    HSS 1 Post Wonder

  • Members
  • 9 posts

Posted 02 August 2012 - 10:56 PM

Question to those that use Robocopy or Allway Sync to backup their data. If I were to use one of these, I understand that I will have an exact copy of my hard drive and that I can restore to the state of the latest backup. But what do I set up so that I can also restore to a state previous to the last backup? Unless I misunderstand, I don't think robocopy or Allway Sync are the right tool for this - correct? Do you rely on Shadow Copy for this or is there a better or more common setup? I want to be able to roll back to a few weeks ago in case I accidentally deleted an important folder of files or something like that.

I know that I can use a number of third party backup programs that do the full and incremental backups, so if I choose one of these, I likely will not be using robocopy or allway sync. So, I am curious about those that are using Robocopy and Allway Sync - how are you handling this?

thanks

#2 kayache

kayache

    HSS 1 Post Wonder

  • Members
  • 9 posts

Posted 02 August 2012 - 11:46 PM

oops - how do I move this to the Backups thread?

#3 pcdoc

pcdoc

    HSS Legend

  • Moderators
  • 3,563 posts
  • LocationLos Angeles, California

Posted 03 August 2012 - 06:27 AM

There are a couple of things. First your true backups (i.e. via the WHS) are always versioned based on the parameters you have setup so you can always go back to a previous backup. Second, you can set file versioning in Allwaysync to a specific number (5, 10, 20, etc.) if that is what you want to do, or you can do both. It depends if you are talking about file restore or system restore.

Main Server - WHS 2011, Core I5-2500, 12T RAID 5 (5x3T) + 2T of Mirror + 2T of backup
Second Server - 2008R2, Core I5-2500, 12T RAID 5
Main Systems - Core I7-2600k, 16 Gigs DDR3-1600, 180 Gig Intel 330 SSD Max IOPS 240 Gig Vertex 3, 2T Sata 3 for local Backup
Other systems - Core I7-2600, Core I3-530's, Core I5-2500, Core I7-920, Core I3-2100, and G620 (see System List)
My Blogs - The Docs Blog and Tablet Resource
BYOB Videos - TheBYOBPodcast
For a complete system List: Computer Systems


#4 ikon

ikon

    HSS Genius

  • Donating Member
  • 8,561 posts

Posted 03 August 2012 - 08:29 AM

AFAIK, you are correct, RoboCopy does not do versioning. If a file in the source directory has changed, that change will be reflected in the destination copy, and the former version will be gone.

Now, if it's just something like accidentally deleting a directory RoboCopy can handle this because its default behaviour is to add to what's already in the destination. IOW, it doesn't delete files or directories from the destination, unless you specify the /MIR paramater. The caveat for this method is that your destination folder will continue to grow in size over time.

If at first you don't succeed, do it like your mother told you.


#5 kayache

kayache

    HSS 1 Post Wonder

  • Members
  • 9 posts

Posted 04 August 2012 - 05:47 PM

pcdoc, I'll check into the file versioning with allway sync. I previously tested a backup and restore with it and it seems great, but I didn't see the versioning feature and thought it was purely sync capability - thanks a lot!. The 40,000 file limit would be a problem but I don't mind paying to handle that.

ikon, using /MIR was exactly what I was thinking, but that causes the versioning problem as you mentioned. That is what made me wonder how people using robocopy, which appears to be many, handle this. Looks like this issue with robocopy may be the big advantage of allway sync. thanks for the feedback.

The only reason I was looking at either of these is because of the 2TB limit for backups with WHS.

#6 ikon

ikon

    HSS Genius

  • Donating Member
  • 8,561 posts

Posted 04 August 2012 - 05:56 PM

The 2TB limit is one main reason I use RoboCopy. The other is that I prefer to be able to get at my backup copies of files in their native format, without having to use some archive browser tool.

If at first you don't succeed, do it like your mother told you.


#7 pcdoc

pcdoc

    HSS Legend

  • Moderators
  • 3,563 posts
  • LocationLos Angeles, California

Posted 05 August 2012 - 11:33 AM

pcdoc, I'll check into the file versioning with allway sync. I previously tested a backup and restore with it and it seems great, but I didn't see the versioning feature and thought it was purely sync capability - thanks a lot!. The 40,000 file limit would be a problem but I don't mind paying to handle that.

ikon, using /MIR was exactly what I was thinking, but that causes the versioning problem as you mentioned. That is what made me wonder how people using robocopy, which appears to be many, handle this. Looks like this issue with robocopy may be the big advantage of allway sync. thanks for the feedback.

The only reason I was looking at either of these is because of the 2TB limit for backups with WHS.


Right click on the backup tab, select properties, and click on "file versioning". You can set what ever level you want.

Main Server - WHS 2011, Core I5-2500, 12T RAID 5 (5x3T) + 2T of Mirror + 2T of backup
Second Server - 2008R2, Core I5-2500, 12T RAID 5
Main Systems - Core I7-2600k, 16 Gigs DDR3-1600, 180 Gig Intel 330 SSD Max IOPS 240 Gig Vertex 3, 2T Sata 3 for local Backup
Other systems - Core I7-2600, Core I3-530's, Core I5-2500, Core I7-920, Core I3-2100, and G620 (see System List)
My Blogs - The Docs Blog and Tablet Resource
BYOB Videos - TheBYOBPodcast
For a complete system List: Computer Systems





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users