Jump to content

David W Lee

Employee
  • Content count

    185
  • Joined

  • Last visited

  • Days Won

    5

Posts posted by David W Lee


  1. the time ZONE is set one hour off

     

    Entourage (2008) is showing the Sent date as 7/30/18 12:00 AM. The date field in the actual email shows "Date: 6/15/13".

     

    show up in Thunderbird as having been sent at 00:00 (midnight), no matter when they were actually sent.

     

    Specifically regarding the standard Date: field in email header and therefore used by various email client software, the 3 issues above are fixed in the next free update.

     

    Separately, Retrospect's "Date:" text inside the email body remains unchanged in the next free update. Outside the scope of that free update, we are actively working on improving the overall usability of email notifications.


  2. 2. The first is a private/pop account, the second is a gmail account, and the third is an AOL account.

    3. Yes - I found them in my AOL spam box.

     

    These fixes are in the upcoming 8.3 (and 10.3 for Mac):

    • When unable to connect to the email server, 8.2/10.2 logs an error and then automatically fail over to a different method to try to connect. The interim error may appear in the operations log even when email is successfully sent after automatically failing over to a second connection method. 8.3/10.3 will log errors only if both connection methods fail.
    • The Date field used by 8.2/10.2 is 1 hour ahead when daylight saving time is enabled. Due to that and along with another issue, some email services are treating Retrospect generated emails as spam. Fixes for both of these date issues are being tested.

  3. The latest Mac build 10.2.0.207 (with new email fixes since 10.2.0.201) is available through Support so that we can closely track if it fixes specific email notification issues.

     

    In general for Retrospect:

    • For Gmail: On Windows, specifies port 465, i.e. smtp.gmail.com:465. On Mac, leaves out the port number and let Retrospect default to port 587.
    • For Exchange: Configure Exchange to disable TLS and enable Basic Authentication.
    • If port isn't specified and SMTP authentication is enabled in Retrospect's E-mail preferences, Retrospect defaults to port 587.
    • When unable to connect to the email server, Retrospect logs an error and then automatically fail over to a different method to try to connect. The interim error may appear in the operations log even when email is successfully sent after automatically failing over to a second connection method. For future release (v8.3 for Windows and v10.3 for Mac), we will log interim errors only if both connection methods fail.

  4. 1. What's the other issue you're investigating - I'd like to know if that fits my scenario better

    2. How do I get a copy of build 180?

     

    Regarding #1, only on Mac we are seeing one of the mail services treating the Date string used by Retrospect as invalid, while other mail services accept it. The consequence is that the email gets sent, but it may be treated as spam or the sent date is shown with the year 1969.

    We aren't seeing this issue on Windows.

     

    To get 8.2.0.180 for Windows, please email Support using http://retrospect.com/en/support/contact, specifying you want 8.2.0.180 for email fixes. This helps us track issues.


  5. it does, if you use the "Send Test E-Mail" button. But if you actually let an automatic script run, the notification still fails.

     

    In 8.2.0.180 (with new fixes since 8.2.0.177), we have reduced differences between sending test email and engine-generated email. 8.2.0.180 is available through Support so that we can closely track if it fixes specific email issues. For Mac, we are testing new fixes and will provide through Support a new 10.2.0.x build ASAP.


  6. Switching to gmail as recommended has solved getting regular emails - but I now have another email issue. I have 2 email addresses defined to receive emails. One of them seems to receive all of the emails from the backup run. The other (second in the list) does not - it receives the startup message and then a resulting message that indicates that a -530 error occurred during the run, but none of the other messages.

     

    I am using ; (a semicolon) as the separator between email addresses. I have also tried the semicolon with a blank and it seems to work the same. I do not have a separator character at the end of the email addresses - do I need that?

     

    Separator isn't needed after the last email address. A few quick questions:

    • Are you using 8.2.0.177?
    • Are both email addresses (one receiving all emails and the other only receiving some) both on gmail?
    • Are any emails held up by spam filters?

    The Date field used by Retrospect is 1 hour ahead when daylight saving time is enabled. Due to that and along with another issue we are investigating, some email services are treating Retrospect generated emails as spam. We testing fix for the 1-hour ahead problem and working on fixing the other issue for v8.3 (Win) and v10.3 (Mac).


  7. While we test new fixes on Mac, the latest Windows build 8.2.0.180 (with new fixes since 8.2.0.177) is available through Support so that we can closely track if it fixes specific email notification issues.

     

    In general for Retrospect:

    • For Gmail: On Windows, specifies port 465, i.e. smtp.gmail.com:465. On Mac, leaves out the port number and let Retrospect default to port 587.
    • For Exchange: Configure Exchange to disable TLS and enable Basic Authentication.
    • If port isn't specified and SMTP authentication is enabled in Retrospect's E-mail preferences, Retrospect defaults to port 587.
    • When unable to connect to the email server, Retrospect logs an error and then automatically fail over to a different method to try to connect. The interim error may appear in the operations log even when email is successfully sent after automatically failing over to a second connection method. For future release (v8.3 for Windows and v10.3 for Mac), we will log interim errors only if both connection methods fail.

  8. The emails come in with the right timestamps, but the time ZONE is set one hour off

     

    We are testing the fix for the next public release (v10.3).

     

     

    Microsoft Entourage (2008) is showing the Sent date as 7/30/18 12:00 AM. The date field in the actual email shows "Date: 6/15/13".

     

    We are actively working on this fix, also slated for the next public release (v10.3).

    • Like 1

  9. The server (File server) is running 10.4.7, not the Retrospect Server which is on 10.7.5.

    The XServe RAID is connected to the Apple File Server locally. The Retrospect system backs it up just as any other client...

     

    Is the Retrospect engine (running on Mac OS 10.7.5) directly backing up the file server as a network share, or via a Retrospect Client running on the file server (Mac OS 10.4.7 which Retrospect no longer supports)? As mentioned, that distinction helps narrow down what (AFP vs. HFS+) metadata are available to Retrospect for determining if a file matches the ones in the media set.


  10. The Dissimilar Hardware Restore add-on works for Retrospect Professional as well. Because of the Windows configurations that need to be made, Dissimilar Hardware Restore can only be invoked by booting with Retrospect Emergency Recovery Disc (i.e. in WinPE).

     

    For the hidden partitions that are required to boot Windows, such as Windows 7's boot partition containing bootmgr and BCD, their contents are backed up by Retrospect if the "Back Up System State" option is explicitly enabled in the backup options, or automatically enabled by selecting the "Operating System and Applications" for the types of files to back up (see http://www.retrospect.com/en/documentation/user_guide/win8/immediate_operations#50458633_30654). During Disaster Recovery, you can create the partitions and Retrospect will restore them as part of the system state (see http://www.retrospect.com/en/documentation/user_guide/win8/disaster_recovery#using-the-retrospect-emergency-recovery-disc).

     

    For the hidden partitions that aren't required to boot Windows, such as PC manufacturer's specific factory recovery tool and image partitions, often they aren't applicable to a different machine. If you would like to make them visible to Windows for Retrospect to back up, try assigning drive letters to them using Windows: http://windows.microsoft.com/en-ie/windows7/change-add-or-remove-a-drive-letter.


  11. After reviewing your support ticket history, please open a new ticket for this specific issue and provide to Support the following info:

     

    1. Change retro.ini:

    SetEngineLogging=4

    SetVolumesLogging=5

    More info at: http://kb.retrospect...s-and-Macintosh

     

    2. After restarting the Engine, subsequent backup should show more detailed info in Activity Monitor > Executing > Log... while the backup is ongoing.

     

    3. Some time into the "Building snapshot..." phase (say 30 minutes), copy log entries from the log window specific to the executing activity mentioned above and save them in a text file somewhere.

     

    4. If more log entries appear in that log window later on, copy and save the log entries again.

     

    5. Provide Support the latest log entries from step 3 or 4.

     

    That would help us narrow down where building snapshot is stuck on.


  12. stuck on Building Snapshot for another 4 hours

     

    You mentioned recently this is for backing up Windows Client using Windows Retrospect Server. Because "Building snapshot..." is sufficiently different between the platforms, I have created a new post on the Windows forum and commented here: http://forums.retrospect.com/index.php?/topic/150440-stuck-on-building-snapshot-for-another-4-hours/


  13. Moved from another thread to this Windows forum:

     

    We just had another case like this.

     

    The backup job went thru 100+GB in around 4+ hours..only to be stuck on Building Snapshot for another 4 hours - at which time the client left.

     

    What stayed active - the server job.

     

    This is a fairly regular occurence and becoming an annoyance - as the process has to be shut down - and in most cases a backup set needs to be rebuilt.

     

    With nearly 2TB backup sets, this can take 18-22 hours!

     

    Please let us know if anything else has been found.


  14. can you explain why retrospect 9 performs backups without my issue and why 10 does not?

     

    We have found any related change so far between 9 and 10. In an earlier post (quoted below) you mentioned the same issue also happened on Retrospect 9, right?

     

     

     

    Our main file server which has several TB of data needing backed up has been backed up, in its entirety, by two of two scripts. One of which seems to forget what has already been backed up and backs up the whole darn thing again. This happened in version 9 as well and with a different script.

     

    To CallMeDave's points:

    - We don't support Mac OS 10.4.7 any more.

    - Is XServe RAID connected to Retrospect Server/Client locally as an HFS volume, or as a network share via AFP? That changes the file metadata available to Retrospect for determining if a file matches the ones in the media set.

×