Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 16 Next »








Confidentiality Notice
The ideas and designs set forth in this document are the property of SkySync and may not be disseminated, distributed, or otherwise conveyed to third persons without the express written permission of SkySync


SkySync, Inc.

30 Parkland Plaza Suite 200 |  Ann  Arbor, MI  48103 | 888.550.3721  | www.skysync.com 


Contact

For more information regarding SkySync Platform Infrastructure & Hardware Considerations, please contact:
info@skysync.com





Content



Infrastructure Recommendations

HardwareRecommendations

SkySync Processing Server

  • {#} of Server(s) required
  • CPU cores: 8
  • RAM: 32GB (minimum)
  • OS disk: 500GB (minimum)
  • OS: Windows Server 2016


If using a cloud server, the following templates are recommended:

  • AWS: 2xlarge
  • Azure: D8S_V3

 

SkySync servers should be installed in the same data center as the data repository or as close to the source as possible to reduce latency.

SkySync SQL Database Server

  • {#} of Database Server(s) required
  • 1 per server farm
  • CPU cores: 16
  • RAM: 64GB (minimum)
  • OS_Vol: 100GB+ SSD – redundant / fault tolerant
  • OS: Windows Server 2016
  • Data_Vol1: 1TB premium SSD
  • Data_Vol2: 1TB premium SSD (optional)
  • Software/templates: SQL Server 2016 SP1 (or higher) enterprise

 

If using a cloud server, the following templates are recommended:

  • AWS: 4xlarge
  • Azure: D16S_V3

Supported Operating Systems

  • Windows Server 2019
  • Windows Server 2016

Supported Databases

Database

  • SQL Server 2016 SP1 (or higher)

Supported Browser

  • Goggle Chrome

Communication Ports

Communication with the following:

  • Port 9090: Bi-directional communication with the SkySync server
  • Port 1433: Communication with SQL Server
  • portalarchitects.com for SkySync License Acquisition
  • API Ports for Cloud Storage Platforms

Application services / processes

Allow List:

  • Skysync.exe


Security Requirements

  • SkySync Platform requires a service account with interactive login rights.
  • Local admin on the SkySync Processing Server(s)
  • Database Owner (DBO) access to SkySync database
  • Transfer account passwords used by the SkySync Platform should be set to not expire
  • The SkySync Platform will need Administrative access to the source and destination storage systems.
    • SkySync will need the username and password, so any validation/investigation can be done.
  • Allow api.portalarchitects.com for SkySync License Acquisition.
  • Application Services/Processes Allow List: skysync.exe

Architecture Firewall/Communication Port Requirements

  • Port 9090 will need to be opened for communication between servers, when more than one SkySync Processing Server is used.
  • Port 1433: Communication with SQL Server
  • From the SkySync server, access the storage platform/repositories should be opened for normal traffic, including HTTP (80) and HTTPS (443).


Remote Desktop Access

  • The Professional Services team will require Remote Desktop Access to the SkySync servers for setup, configuration, and monitoring of the system during the Transfer Management phase.
  • Access via direct RDP access or via VPN
  • Admin level rights to the server(s) to install and configure
  • Provide SkySync access to the username and password/admin-level access rights to the SkySync servers for setup, configuration, and monitoring of the system.


Screen Sharing Control (Optional)

  • SkySync requests a resource that allows our team to leverage screen sharing control with an online meeting service, such as Microsoft Teams or Go to Meeting, so SkySync can perform the installation and configuration of the SkySync platform.


User-Account Mapping Files

  • The mapping files are used for two steps in the transfer process:
    1) Identifying the users/groups that will be migrated
    2) 
    Mapping source accounts to destination accounts.
  • Mapping file(s) that identify the users source account information and their new destination account must be provided.
  • SkySync recommends gathering this information from Active Directory, if possible.
  • Accounts must be created and provisioned on the destination platform prior to migration.
  • Group(s) must be already exist on the destination for the mapping to be successful.


Further information can be found:


Job Mapping Files

  • The SkySync Platform will need a file that maps the users accounts to the specific location as defined by Client. For example:
    * User A on Box will need to be mapped to a specific OneDrive location.
    * User B on Box will need to be mapped to a specific SharePoint Site location.
  • A sample .csv file can be provided by the Professional Services team.


Download Recommended Tools

Web Browser | Google Chrome

REST API Tool | Postman

  • Download the following https://www.postman.com/downloads/ to the server where SkySync will be installed.
  • The SkySync Professional Services team will configure Postman during our installation session.


Account Provisioning

  • Accounts must be created and provisioned on the destination platform prior to migration.


File Transfer Performance

  • All cloud-service platforms have both API-call and throughput rate limits. They can vary from tenant to tenant, time of day, as well as other factors that are solely controlled by the platform vendor(s). These limits can significantly impact SkySync file transfer speeds. SkySync understands the limitations of these platforms and will monitor the migration to ensure throughput is optimized and may request additional hardware, if needed to meet the project timeline.
  • If hardware recommendations made by SkySync (both database and the SkySync application servers) are not feasible to be implement by the Client, transfer performance and timelines could be impacted. SkySync will request a specific number of servers at the beginning of the migration. If throughput numbers are lower than expected due to each platform vendor, SkySync may request additional servers to preserve project timelines.
  • The SkySync architect will tune the system at the beginning of each wave migration and will ensure optimal throughput is achieved throughout the duration of the migration.
  • The Client will be responsible for ensuring the availability and stability of the network where the hardware is provisioned. Latency with internet connections or bandwidth can impact file transfer performance. If latency issues occur, the SkySync architect will work with the Client's team to resolve.




30 Parkland Plaza Suite 200 |  Ann  Arbor, MI  48103 | 888.550.3721  | www.skysync.com 





  • No labels