Frequently Asked Questions
Search:     Advanced search
Browse by category:

KB263: Ensuring V5 clients can backup to a V6 Storage Platform

Views: 614
Votes: 0
Posted: 21 Oct, 2009
by: Marais D.
Updated: 21 Oct, 2009
by: Marais D.

Description

All V5 clients has the ability to backup to a version 6 Storage Platform and will be auto-updated to V6 if auto updates are enabled.  There is however one scenario where a V5 client will NOT connect to a V6 Platform (not even to auto-update) and that is when the 'Disable SSL Encryption' option has been manually checked in the SE client or applied with profiling.   In such a case the SSL handshake will fail and absolutely no communications between the client and SP will be possible at all.  The client will abort any backup with the following error:
'Remote host closed the connection during handshake'

Note that this is a restriction in .Net and it is not possible to lower the security settings in order to allow SSL communications without encryption.

There are several options to avoid or resolve this issue and these are outlined below.

Option 1

The safest option is to load SP 5.1 update 4 and ensuring auto updates are enabled long before upgrading to V6.  This will ensure all clients auto update to V5.1.3 where the 'Disable SSL Encryption' option is ignored even if it is set.  This means that by the time the Storage Platform is upgraded to V6.0 all the Backup Clients are on V5.1.3 so all will be able to connect (and auto-upgrade to v6) regardless of the SSL setting.  Note that it requires all backup clients using this particular SSL setting to backup at least once to the V5 Storage Platform where the updated is loaded in order to upgrade.
This option is particularly useful for ISP's where the SP administrator has no control over client side settings.

Option 2

Use profiling to set Disable SSL Encryption=false for every group on the Storage Platform - thereby overriding any client side SSL settings.  This may be a tedious excercise on a Platform with many groups, in which case option 1 is more suitable.  It will again require that every backup client backs up at least once to the V5 Storage Platform before the SP is upgraded to V6.

Option 3

Ensure all backup clients use SSL encryption when connecting to the SP.  Do this before upgrading the SP to V6.  This can be done by manually ensuring each backup client has the 'Disable SSL Encryption' check box cleared.  
This option is useful in corporate environments where the SP administrator has full control over all clients or knows that all backup clients use the default options.

Option 4

Do nothing and just upgrade the SP.  Then afterwards manually clear the disable the 'Disable SSL Encryption' check box for each Backup Client that fails to backup.  This option is not possible if the 'Disable SSL Encryption' option has been set with profiling.  In such a case all V5 clients will have to be manually upgraded to V6 in order to be able to back up again.

Others in this Category
document KB006 - Backup Client Cache & ToBackup folders
document KB019: Making a snapshot backup using a Snapshot Server
document KB031: Untrusted SSL cert chain
document KB062: Restoring a single mailbox with SMR and AD
document KB067: Backup fails with "database is full"
document KB082: Corrupt client database
document KB085: 'Could not create the Java virtual machine' when trying to load the Backup Client GUI
document KB091: Backup Client MSI Installer
document KB095: Client error: "String index out of range: -1"
document KB098: Cannot increase the socket time out to more than 600 seconds
document KB100: Username cannot be empty for login
document KB101: Backup fails due to Database errors
document KB105: What are the criteria used to determine the capability of a backup client?
document KB106: Which is faster: backup or restore?
document KB112: Japanese, Chinese or Korean characters display as blocks
document KB132: Scheduler stops working
document KB134: No archive dates available with Snapshot Backup
document KB136: How to upgrade a D&L to SE
document KB137: Enable Debug Logging in SE and D&L
document KB140: Proxy server causes communication problems during a backup
document KB144: Backup fails due to overlimit on FS but limit is correct
document KB147: What do those sizes related to patching mean in the logs?
document KB162: Advanced backups will not always run in V4.4
document KB164: How to include the user's My Documents directory in profiling
document KB165: How to exclude certain files or folders with profiling
document KB166: How does the backup client know which Windows user to use for profiling?
document KB167: Storage Platform 4.4 update 4
document KB174: V3.x clients cannot backup to a V5 Storage Platform
document KB189: How to recover a single Exchange 2003 mailbox without using the Exchange or SMR plug-ins
document KB194: SMR gives 'Invoke of: GetObject' error during backup after upgrade to v5
document KB197: Email Notification fails to send test message with v5 SE.
document KB201: Restoring archived month-ends
document KB202: Month-end archiving not taking place on Mirror Server
document KB203: Resource file missing when trying to start D&L or SE
document KB204: Examples to backup and restore MySQL
document KB206: Storage Platform Console on 64bit
document KB217: How to suppress the bootup/login splash screen
document KB222: Server Edition GUI won't open after upgrade from v4.4 to v5.1
document KB225: Client Error: Cannot connect to storage server
document KB232: Account creation fails on Storage Platform
document KB235: D&L Tray icon not loading when logging on in Vista
document KB238: VSS plugin does not pickup up Exchange on SBS 2003
document KB247: After auto upgrade from V5.0 to V5.1 the tray icon shows the service is stopped during the cache update
document KB249: How to do a Full exchange 2007 restore using VSS plugin
document KB250: Restoring Exchange 2007 into Recovery Storage Group using the VSS plugin
document KB252: V5.1 Advanced scheduler does not work in some cases
document KB254: VSS Backup and Restore of Active Directory
document KB257: MAC Snow Leopard failing to backup



RSS