Resolved Question on Windows Briefcase:

I had a setup (by someone who knew how this worked) whereby I would enter files into a breifcase folder on my desktop and than at night would "update" a similar folder set on a USB stand-alone drive as a backup.

After he left us, the process continued to work until an "outside consultant" came in (my brother-in-law, the Genius) and suddenly the 'synching" stopped working.

I have since determined that the problem is the the synch files are shown on the desktop files as being in drive "F "/, but there IS no drive "F ". My two USB drives are "G" and "H ".

SO: If I can rename "H" to "F ", would the process take off again, and HOW do I rename a drive?

If not that, then I'm open to suggestions, up to and including the scatologically impossible.

 

You can easily rename the usb drives and it's very likely that it will fix your problem. Go to Start > Run > type diskmgmt.msc > press enter or click OK. When the Disk Management applet opens, right-click the usb drive and select "Change Drive Letter and Path." Then click the CHANGE button. You'll be allowed to choose from any available letter. Repeat for the other drive if needed.

 

So far so good...

Surfer! DUDE!! That was indeed the solution to some of the problem! I renamed the drive letter from H to F and the briefcase setup then recognized <some> of the folders, but:

I still have two "orphan" folders and I'm at a total loss to figure out how to fix them.

I read the Microsugar KB's on Briefcase but they are all concerned with setting up a new briefcase and I could find nothing referencing this particular problem, so I'm still open to more excoriation...

 

I don't use the Briefcase but I would think you could create a new one - put the same folders in it - and see if it functions properly. If so, dump the old one since it may be confused.

Right-click the open Desktop and select New > Briefcase.

Or possibly, delete all the contents of the old Briefcase and replace them anew

 

.......oy!

 

Well. Since we really don't ever work on the files once they're in the backup drive, I think that our former IT genius was in error in setting this up as a briefcase scenario.

All we wanted to do was to have newly enterd files (tax return scans) enterd into the main repository on C:/ as well as being put into the F:/ and G:/ drives. The "G:/ was supposed to be removed every nite and taken home with one of the partners as an "off-site" backup.

Clunky, but what I did was to copy the files (7 years of scanning!) to the F:/ and G:/ drives and then set up a new file where the current scanning is done. At the end of the day I simply copy the currently scanned folder into the existing folders on C:/, F:/ and G:/, remove the G:/ and it takes all of ten minutes to do.

Even if the Nummies forget to bring G:/ back in for a day, the catchup is SO much easier than mucking about with the silly Briefcase that the time is worth it.

I'm SURE there are simpler and more efficient ways of accomplishing the objective, but this one works for me.

 

I agree. I tried using the Briefcase and found it to be less than efficient and potentially dangerous to my data.

I currently use Xxcopy in a batch file for backups similar to yours. It is unique in that it skips any files not changed, deletes files in the target drives that are no longer in the original drive, and executes in less than 30 seconds.

If you're happy with your current method, I'll not try to change you unless you ask.

I think you can mark this thread closed. The button is up on the top under Thread Tools and only visible to you, the thread starter.

All the best, Dude

 

That sounds a treat indeed.... more info?

 

Certainly.

The program Xxcopy is available in a free or Pro version at cost. The free version is adequate for most users.

The backup script that I use is named QuickBackup.bat and goes as follows:

Code:

cd \
xxcopy /clone /ff /yy  "%USERPROFILE%\"  "Z:\quickbackup\Owner\ "
xxcopy /clone /ff /yy  "C:\Program Files\OAKLEY\"  "Z:\quickbackup\Oakley\ "
xxcopy /clone /ff /yy  "C:\Program Files\Quick StartUp\"  "Z:\quickbackup\Quick StartUp\ "
xxcopy /clone /ff /yy  "C:\CALENDAR\"  "Z:\quickbackup\Calendar\ "
xxcopy /clone /ff /yy  "C:\DONSMAIL\"  "Z:\quickbackup\donsmail\ "
xxcopy /clone /ff /yy  "C:\QPW\"  "Z:\quickbackup\qpw\ "
xxcopy /clone /ff /yy  "C:\Legacy\Data\"  "Z:\quickbackup\Legacy\Data "

I call it from another batch file that I run when I close the system down. That batch is named ShutDown.bat and goes as follows:

Code:

 "C:\Program Files\CCleaner\CCleaner.exe" /auto
call  "C:\Documents and Settings\Owner\My Documents\Donfiles\Batches\QuickBackup.bat "
%windir%\System32\shutdown.exe -s -t 00

I have a second version of the backup batch file named QuickBackup2.bat and have it pinned to the Start Menu. It performs the same backup tasks but I run it manually and have added a pause command to allow me to review the actions it performs. QuickBackup2.bat goes as follows:

Code:

cd \
 "C:\Program Files\CCleaner\CCleaner.exe" /auto
xxcopy /clone /ff /yy  "%USERPROFILE%\"  "Z:\quickbackup\Owner\ "
xxcopy /clone /ff /yy  "C:\Program Files\OAKLEY\"  "Z:\quickbackup\Oakley\ "
xxcopy /clone /ff /yy  "C:\Program Files\Quick StartUp\"  "Z:\quickbackup\Quick StartUp\ "
xxcopy /clone /ff /yy  "C:\CALENDAR\"  "Z:\quickbackup\Calendar\ "
xxcopy /clone /ff /yy  "C:\DONSMAIL\"  "Z:\quickbackup\donsmail\ "
xxcopy /clone /ff /yy  "C:\QPW\"  "Z:\quickbackup\qpw\ "
xxcopy /clone /ff /yy  "C:\Legacy\Data\"  "Z:\quickbackup\Legacy\Data "
pause
:: pause added for this manually run version. Pinned to Start Menu.

I intentionally allow the commands to echo to the monitor, I like it that way although neither require any interaction.

By using the /clone switch with Xxcopy, the target drive is make to be identical to the source. No files will be orphaned in the target if they don't exist in the source. Truly a clone.

Xxcopy has scores of other switches and allows for very creative applications.

Do take care using the /clone switch since scripting a command line incorrectly can produce some very disappointing results. Eg, inadvertantly getting the source and target reversed could clone an empty directory into a target full of data and cause it to be wiped clean. Another worst case would be cloning some source directory to the root of a drive. All other data on the drive will be wiped clean. That makes for a truly bad day. Always target a directory to avoid that. Powerful tools like this can do powerful damage!

 

Thanks for the Help!

Thanks, SurferDude!

I have an old box I'll put some data onto and practice with so I get it right the first time on my box at work.

Thanks for the help and especially for the code!

I'm sure this will help others in the future.

Thread resolved.

V

 

I should have mentioned that during testing it's best to omit the /ff switch and allow all the warning messages so as to be sure the commands are doing as intended and no missteps have been made in typing, etc. Then after you get everything working correctly, add the /yy switch to allow execution without interaction.

I'll check back occasionally in case you hit a snag with the scripting.

All the best, Dude

 

You da bes' Bla!