Jump to content

rtswis

Members
  • Content count

    14
  • Joined

  • Last visited

Community Reputation

0 Neutral

About rtswis

  • Rank
    Occasional forum poster
  1. MrPete -- It turns out it is not as bad as I had thought. In my case the Sources view did not show the new drives, as you suggested and as mentioned in an earlier Topic (#109114) in Server, SBC and Multi-Server. I surmise that Retrospect only shows the new partitions without prompting when the resized drives are on the host machine; when they're on a client the solution is a little more complicated than Mayoff suggested there: you do have to discard the listed partitions on the client; but you must then also add the new ones back using "Configure-Client." What I then discovered (skipping the trial and error details) is that once Retrospect has been made to recognize the new partition configuration on the client it can be made to associate the old backup sets with the new partition configuration (at least assuming, as in my case, I just resized the partitions, without any change in logical drive structure or data). I have no idea whether it does so automatically; in an effort to get to a solution I had already "forgotten" the old backup sets, assuming they were no longer of any use. I had not, however, deleted either the underlying backup data or the catalog files. Hence, if you follow the procedure (pp 272-273 of the 7.5 User Guide) for recognizing old backup sets after moving Retrospect to a new machine -- basically dragging the catalog to the Retrospect program icon -- the program will recognize and continue to backup up the data from the resized partitions to pre-existing backup sets. That same procedure, I discovered along the way, can perhaps be used to workaround the problem of the time it takes to create a new backup set over a wireless connection. It may be possible to write the backup set initially to a USB drive directly connected to the client, move the USB drive and copy the backup file(s) to a backup location hard wired to the Retrospect host, and then force Retrospect to recognize it in the new location. I tried that successfully using on old copy of Express (5.5.158) on the client machine, although for some reason the program is much, much slower updating that backup set than it is with those created directly in Professional. It seems to want to read through the entire catalog of files on the client, rather than just those with attribute bits set to show that they have changed. For what it's worth.
  2. For Mayoff: I've asked essentially the same question in a post earlier today in the Professional forum, and if the answer is that you cannot thereafter add to the existing backup sets, let me ask a couple of additional questions: (1) How about restores? If something had mis-fired in resizing the partitions on the client could I have restored the data from the old backup sets to the newly sized partitions, or can it only restore data to an identically sized (or newly created) partition? If the answer to that is no, it cannot restore to the resized partition, then it seems like Retrospect is less flexible in that respect than my old DOS backup solution (Fastback, RIP), and provides no help for someone who wants the security of a backup set before (modestly) reconfiguring a drive. If the answer is yes, why is it that you can restore to a different sized partition but not continue to back up from it? Assuming (as I think likely in my case) that the resizing did not alter the other characteristics of the partition, why does the amount of free space on the drive affect Retrospect's ability to recognize it and continue to increment a backup set from it? (2) Isn't this something you ought to be able to (and ought to) address? If I have the flexibility to resize drives it seems to me that a well thought out back-up solution ought to be able to keep up with changes that do not alter the data without having to start afresh, which for us, given that the client has a wireless connection to the network, means a full day (for each backup set) of bogging down the network to recreate what we already have. (3) Is there a workaround for the slow creation of a backup over a wireless connection? The client owns a copy of Express (5.5.158), and as a precaution I made a new backup set today to a file on an external drive. Is it possible to copy that file directly to the physical (NAS) drive where we normally put the Professional backup sets, and then point Professional to the file and direct it to increment the set? Is the catalog for that set integrated with the backup file itself? Just asking. Thanks for any help you might have to offer. Ted Sims (see #110074, 8/04/08, on Professional)
  3. I've just experienced a backup failure after defragmenting and re-sizing drive partitions on a backup client. Version is 7.5.512, and both the backup host and client are running xp. The client is an older machine with a 37GB drive partitioned into C:-E:, with the OS and some apps on C: (7GB, 6+ used), apps on D: (15GB, 3 used), and data on E: (15GB, 5 used). C was becoming clogged, so, after updating two (of three) backup sets I first degragmented it (using PerfectDisk 8), and then decided to reallocate space among the partitions using PartitionMagic 7. Both D: and E: were reduced in size by 2GB and moved to the end of the physical drive, then C: was enlarged to fill the relinquished space. All of this was accomplished without incident, and as far as I am aware none of the file contents was altered in doing so. When I tried to update the remaining backup set I got a message that read "Can't access local disk, error-1102 (drive missing/unavailable)". I tried rebooting the client (no change) and then the host. On restarting Retrospect after the reboot the program initially hung, so I killed it with the task manager, at which point I received another warning: "Assertion Failure at wind.cpp-7050 UCreateMDIWindow failed OS err 2," and I permitted the resulting report ("assert_log.utx") to be transmitted to EMC. I have since verified that I can continue to backup the other client, but get the same "Can't access local disk [etc]" message when trying to update any of the sets for the reconfigured client. (The machine and all drives are visible on the network.) I assume I can start new backup sets for the reconfigured machine, but it is not a happy prospect since it has only a wireless connection, and even with only 15GB to backup creating each new set consumes a couple of days. So, does anyone out there have any insight to offer on what is going one? I'm no techie, but it seems as though Retrospect required either (1) no change in the physical location of the client files (seems unlikely to me) or (2) no change in the size (or maybe physical location) of the logical partitions. Thanks for any help. Ted Sims
  4. rtswis

    Retrospect 7.5 and pcpds.exe

    Appears to have solved the problem for me, too. Thanks very much. Is there anything you can say by way of explaining what happened that might be intelligible to ordinary mortals?
  5. rtswis

    Retrospect 7.5 and pcpds.exe

    It's going on two weeks since I last backed up the NT Box. Is there any software to rollback the prior upgrade? Assuming not, if I dump and then reinstall the original program how much work will be required to recreate catalogs to existing backup sets? Thanks.
  6. rtswis

    Retrospect 7.5 and pcpds.exe

    Away until 6:00 p.m. (pst) tomorrow.
  7. rtswis

    Retrospect 7.5 and pcpds.exe

    An update. I just restarted the NT system and got a new error message. It read: "rthlpvsc.exe - Entry Point Not Found. The procedure entry point SHGetSpecialFolderPathA could not be located in the dynamic link library Shell32.dll." Same message as before but reported with respect to a different program. And since the executable has the same name as the error log I reported in the fifth post above I assume it is related to the existing problem with Retrospect.
  8. rtswis

    Retrospect 7.5 and pcpds.exe

    Thank you.
  9. rtswis

    Retrospect 7.5 and pcpds.exe

    Version 4.00 (file size is 1,280,272B).
  10. rtswis

    Retrospect 7.5 and pcpds.exe

    Not at this time. It's at home and I am now at work. I should be back about 4:00 p.m. pst. I'll report back then, or earlier if someone at home can obtain the information. If I had to guess, though, I would say it was 4.00.
  11. rtswis

    Retrospect 7.5 and pcpds.exe

    IE 5.5 resides on the machine but is used rarely and only in desperation; default browser is Firefox 2.0.0.12.
  12. rtswis

    Retrospect 7.5 and pcpds.exe

    By the way, at some point, when trying to close the program, I got a message that (roughly) said "Retrospect has encountered a serious error" and requested permission to send a report to EMC, which I granted. The program directory now contains a file entitled "rthlpsvc.log", dated 10:00 p.m. (est) last night, which I assume contains the contents of that report. The file contents follow. I add that if those file references are to the client machine, the OS on the NT 4.0 machine is not on C: but in D:\WINNT\.... Thanks again. Contents of rthlpsvc.log: HSvcRestoreReg: FindFirstFileW(rtregrst.ini) failed 2 hsvcWin2kDbRestore: GetFileAttributes(C:\WINDOWS\ComRegBk\RtrComRg.ini) failed 3 hsvcWin2kDbRestore: GetFileAttributes(C:\WINDOWS\IISMetBk\RtrIISM.ini) failed 3 hsvcWin2kDbRestore: GetFileAttributes(C:\WINDOWS\WMIBk\RtrWMI.ini) failed 3 hsvcWin2kDbRestore: GetFileAttributes(C:\WINDOWS\ActDirBk\RtrActDr.ini) failed 3 hsvcWin2kDbRestore: GetFileAttributes(C:\WINDOWS\CertSvBk\RtrCertS.ini) failed 3 hsvcWin2kDbRestore: GetFileAttributes(C:\WINDOWS\RSMBk\RtrRsm.ini) failed 3 HSvcWriteDVDAddToReg: CreateFile(C:\WINDOWS\retregld.dat) failed 2 No work to do, quitting...
  13. rtswis

    Retrospect 7.5 and pcpds.exe

    Version is 7.5.508. The date of the update, as reflected in the file time stamps, is in fact 2/11/2008 at 2:18 p.m. The time stamp on pcpds.exe is 2/11/2008, 4:28 p.m. Thanks.
  14. I've been using Retrospect Professional 7.5 for about six months. (It came bundled with an NAS device.) It has been running on an XP machine, backing up two clients, one running XP the other NT4-SP6, without incident. In the past week -- I am guessing on February 11 -- I allowed it to update to version 7.5.13.100. This evening I updated two backup sets from the XP client, and then initiated an update of the backup set on the NT machine, and received an error message on the client that read "pcpds.exe -- Entry Point Not Found. The procedure entry point SHGetSpecialFolderPathA could not be located in the dynamic link library Shell32.dll." The host machine reports something like "Unable to Access Drive Error -557", or the program hangs. I have retried this several times with the same result. I have rebooted both machines and the error persists. It is not manifest on the XP client, which I again successfully backed up. Both clients contain the file pcpds.exe in the \Retrospect Client directory; they are of identical size, and both are stamped at about the same time on February 11, differing in time by 1 second. That is why I surmise the program update was permitted on February 11. The NT backup set has been successfully updated at least once since February 11, on February 15. I'd appreciate it if anyone could shed light on what might be going on. As a rule I do not download files from unknown sources; I use pine for email and so have to make a decision and expend some effort to extract email attachments. Thanks. Ted Sims
×