![]() ![]() At this point bvckup2 will think that nothing's changed in terms of source/dest disposition, so it will happily use the snapshot of the directory tree from the last run and skip the scanning of the destination altogether (this is configurable, of course, and the controlling setting in the "Detecting changes" section of the backup configuration). Bvckup 2 is a powerful backup utility that has the pedal-to-the-metal mindset of a command-line tool, but comes with a beautifully functional graphical user interface. Unhook the drive, take it to the remote location, hook it up there, then share the drive out and map it locally as X:\. You hook up a spare drive, mount it as X:\, add a job from C:\Foo\Bar to X:\, run it. To be more specific, say, you need to clone parts of a local machine. This does however require destination path to stay exactly the same between 1st and 2nd run, which can be done by using mapped drives. I have it set to watch my movie, pics, and music folders and automatically copy the files over to another drive for a good back up solution. If I run a robocopy job with '/B' it works though. Even though we are following the 'best practice' permission advice from Microsoft it seems that bvckup has an issue with the profile folders. Bvckup 2 Bvckup2 ( is a great little program that I came across. Since those shares are hosted on Windows Server 2008 I can't use VSS over SMB. You can also use the app itself to do the initial seed, and this also allows the app to build *and retain* the index of the backup location so it will not need to re-scan destination (over a slow link) on the 2nd run. Simple, effective, and cheap file back up solution. That is to seed a backup locally with "robocopy /mir" or similar, take it to the remote site and run an update over a slower link. What you described is a fairly common use for the app. Second, it could've been caused by the source location not being accessible, but then you should've not see the job to proceed with copying files after the archiving. the source was C:\Users\alex and the destination was just X:\Users). First is simply a mistake in source and destination (e.g. The fact that running a backup job caused it to archive everything could mean two things. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |