|
Home > Archive > Backup Software > March 2005 > Caveat Retrospect
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
| Howard Kaikow 2005-01-27, 5:46 pm |
| I lost a hard drive two weeks ago.
Used Retrospect DR to restore drive.
Apparently, either Retrospect does not properly back up Office or Retrospect
does not properly restore files in a disaster recovery!
I ran a Detect and Repair on Office 2003 and rebooted, problem went away!
--
http://www.standards.com/; See Howard Kaikow's web site.
| |
|
| I had similar problems with Backup MyPC a while ago... had to repair some
installations. I thought it was a side-effect of file backups that use the
file system calls to restore files so that items might not be exactly the
way they were backed up as - for example, the 8.3 name might not be the same
for a file - since some registry entries use 8.3 names, this could cause
problems. That's one of the reasons why I started using image backups.
"Howard Kaikow" <kaikow@standards.com> wrote in message
news:ctau84$ru7$1@pyrite.mv.net...
>I lost a hard drive two weeks ago.
>
> Used Retrospect DR to restore drive.
>
> Apparently, either Retrospect does not properly back up Office or
> Retrospect
> does not properly restore files in a disaster recovery!
>
> I ran a Detect and Repair on Office 2003 and rebooted, problem went away!
>
>
> --
> http://www.standards.com/; See Howard Kaikow's web site.
>
>
| |
| Howard Kaikow 2005-03-09, 5:46 pm |
| the 8.3 issue should not be relevant when doing a full restore of a volume
that includes the registry for the os.
--
http://www.standards.com/; See Howard Kaikow's web site.
"JohnA" <John@discardstring-TheAtas.org> wrote in message
news:f8dXd.25838$Sn6.9943@lakeread03...
> I had similar problems with Backup MyPC a while ago... had to repair some
> installations. I thought it was a side-effect of file backups that use
the
> file system calls to restore files so that items might not be exactly the
> way they were backed up as - for example, the 8.3 name might not be the
same
> for a file - since some registry entries use 8.3 names, this could cause
> problems. That's one of the reasons why I started using image backups.
>
> "Howard Kaikow" <kaikow@standards.com> wrote in message
> news:ctau84$ru7$1@pyrite.mv.net...
away![vbcol=seagreen]
>
>
| |
|
| Hi Howard,
You write:
>the 8.3 issue should not be relevant when doing a full restore of a volume
> that includes the registry for the os.
I am curious why this is true... If the current registry contains keys that
contain
8.3 pathnames, and the restore creates pathnames with different 8.3
pathnames than were saved, and the filename no longer matches the keys, why
isn't there a
problem anymore? Remember, the 8.3 names are derived from the contents of
the directory at the time of file creation... how does a restore program
even know the contents of the directory at the time each file that was
backed up was originally created...
-- John
"Howard Kaikow" <kaikow@standards.com> wrote in message
news:d0n7p2$fnc$1@pyrite.mv.net...
> the 8.3 issue should not be relevant when doing a full restore of a volume
> that includes the registry for the os.
> --
> http://www.standards.com/; See Howard Kaikow's web site.
> "JohnA" <John@discardstring-TheAtas.org> wrote in message
> news:f8dXd.25838$Sn6.9943@lakeread03...
> the
> same
> away!
>
>
| |
|
| Ahh... I see how it could be done. The following would have to take place,
however.
1) The backup program needs to save the short name along with the full
pathname
2) Windows XP (not other flavors of Windows) provides an API to set the
short file name so the backup program would have to set this on each file it
restored.
I think the shortname for files and directories must both be settable for
this to work.
I know earlier versions of Dantz didn't address this. See:
http://forums.dantz.com/ubbthreads/...11&o=&fpart=all
-- John
"JohnA" <John@discardstring-TheAtas.org> wrote in message
news:uwdYd.26555$Sn6.22381@lakeread03...
> Hi Howard,
>
> You write:
>
> I am curious why this is true... If the current registry contains keys
> that contain
> 8.3 pathnames, and the restore creates pathnames with different 8.3
> pathnames than were saved, and the filename no longer matches the keys,
> why isn't there a
> problem anymore? Remember, the 8.3 names are derived from the contents of
> the directory at the time of file creation... how does a restore program
> even know the contents of the directory at the time each file that was
> backed up was originally created...
>
> -- John
>
> "Howard Kaikow" <kaikow@standards.com> wrote in message
> news:d0n7p2$fnc$1@pyrite.mv.net...
>
>
>
|
|
|
|
|