insync Installation Guide 5.2 Private Cloud Druva Software June 21, 13 Copyright 2007-2013 Druva Inc. All Rights Reserved.
Table of Contents Deploying insync Private Cloud... 4 Installing insync Private Cloud... 6 Installation Roadmap... 6 Installation Prerequisites... 7 Installing insync Master Server... 11 Installing Master Server on Windows... 11 Installing Master Server on Linux... 12 Configuring the Master Server... 13 Installing insync Storage Node... 17 Installing Storage Node on Windows... 17 Installing Storage Nodes on Linux... 18 Configuring the Storage Nodes... 19 insync Log and Configuration Files... 21 insync Log Files... 21 insync Configuration Files... 22 insync Services... 22 Upgrading insync Private Cloud... 24 Upgrade Roadmap... 24 Upgrade Prerequisites... 25 Upgrade Procedure... 25 Post-upgrade Configurations... 27 Uninstalling insync Private Cloud... 30 Uninstallation Roadmap... 30 Uninstalling the Storage Nodes... 31 2
Uninstalling the Master Server... 32 3
Deploying insync Private Cloud Druva insync Private Cloud is a scalable solution for data backup and protection for organizations that are spread across geographies. With insync Private Cloud, organizations can effectively protect their data by synchronizing multiple Storage Nodes with a Master Server. A Private Cloud implementation has the following advantages: New storage nodes can be added as required, making the solution scalable. Users can be grouped depending on their functional role or their proximity to a storage node. This allows for efficient management of users. To deploy insync Private Cloud, you must have a Master Server and one or more Storage Nodes. The following illustration depicts a simple deployment of insync Private Cloud. 4
The components of insync Private Cloud are explained in the following table. Component Description Master Server The Master Server, which is installed within an organization's premises, effectively manages Storage Nodes as well as user information. The Master Server ensures that insync Client requests (for backup and restore) are authenticated and assigned to a Storage Node. To sum it up, the Master Server provides a unified view of all Storage Nodes. Storage Node Multiple Storage Nodes are located across geographies. A Storage Node is a server that actually performs a backup or restore. Storage Nodes also store data that is backed up from endpoints. A collection of such Storage Nodes is nothing but a private cloud. insync Client insync Client components, which are installed on endpoints, initiate backup or restore requests. The client components communicate with the Master Server following a request-response messaging pattern over a local area network (LAN) or a wide area network (WAN). Copyright 2007-2013 Druva Inc. All Rights Reserved.
Installing insync Private Cloud When you install insync Private Cloud, you must first install the Master Server and then install the Storage Nodes. The Master Server and the Storage Nodes can be installed on Windows or Linux operating systems. The Storage Nodes need not necessarily be installed on the same operating system as the Master Server. Note: You must install Master Server on only one server. Storage Nodes can be installed on multiple servers. The number of Storage Nodes depends on your organization's data needs. Installation Roadmap This topic contains the high-level steps for installing insync Private Cloud. To ensure that your installation completes successfully, follow the chronology of this roadmap. Step Task Description 1 Check prerequisites Make sure that the computers on which you plan to install the Master Server and Storage Nodes meet the system requirements. For information about Master Server requirements, see Prerequisites for Master Server. For information about Storage Nodes requirements, see Prerequisites for Storage Node. 2 Install MySQL database Install and configure the MySQL database on the computer on which you plan to install the Master Server. As a next step, create an account on the MySQL database. For more information about installing and configuring your MySQL database, see MySQL Documentation Library. Copyright 2007-2013 Druva Inc. All Rights Reserved.
3 Install Master Server Install a single instance of Master Server. For more information, see Installing insync Master Server. 4 Configure Master Server Configure the Master Server. For more information, see Configuring the Master Server. 5 Install Storage Nodes Install multiple instances of Storage Nodes. For more information, see Installing insync Storage Node. 6 Configure Storage Nodes Configure the Storage Nodes. For more information, see Configuring the Storage Nodes. Installation Prerequisites Prerequisites for Master Server Requirement Description CPU Dual-core processor 64-bit Operating System Windows Windows 2008 R2 Service Pack (SP) 1 (64-bit) Windows 2012 Server (64-bit) Linux Ubuntu 12.04 (64-bit) Red Hat Enterprise Linux (RHEL) 6.3 (64-bit) RAM 8 GB 7
Network Card 10/100 Mbps Fast Ethernet Adapter Disk space 125 MB for installation Web browser Windows Internet Explorer 8 and later Mozilla Firefox 19 and later Safari 5.1 and later Google Chrome 25 and later MySQL MySQL database version 5 or later. Note: Druva recommends MySQL version 5.5.24 for an Ubuntu and Windows installation, and version 5.5 for a RHEL installation. Prerequisites for Storage Node Requirement Description CPU Quad-core processor 64-bit Operating System Windows Windows 2008 R2 SP1 (64-bit) Windows 2012 Server (64-bit) Linux Ubuntu 12.04 (64-bit) RHEL 6.3 (64-bit) 8
RAM 8 GB or 4 GB per TB of storage data, whichever is higher. The actual requirements might vary depending on your setup. Network Card 10/100 Mbps Fast Ethernet Adapter Disk space 125 MB for installation Note: To find out if your existing hardware is a good fit for your insync Private Cloud installation, contact Druva Support. Other Requirements Requirement Description Open Ports Keep the following ports open on both Master Server and Storage Node: 443: On the Master Server, this port is required to access the insync Admin Console and for Web restores. On the Storage Node, this port is required for Web restores. 6061: On both Master Server and Storage Nodes, this port is required for backups and communication with each other. IP Address or FQDN If you want to allow insync users to backup and restore data over WAN, decide on the WAN IP address or FQDN that they can use. The IP address can be configured through the insync Admin Console. For instructions on how to configure IP address or FQDN for insync 9
Server, see the insync Administrator Guide (Private Cloud 5.2). 10
Installing insync Master Server This section contains instructions for installing the Master Server on Windows or Linux operating systems. Installing Master Server on Windows Before you Begin Before you install the Master Server on a Windows computer, make sure that you complete the following tasks: Download the installer package on the computer on which you want to install the Master Server. Have administrative privileges on the computer on which you plan to install the Master Server. Appoint the first server administrator. Keep the user name, e-mail address, and password for this server administrator handy. Installation Procedure To install insync Master Server: 1. Double-click the Master Server installer. The installation wizard appears. 2. Click Next. The end-user license agreement (EULA) is displayed. 3. Accept the EULA and click Next. 4. In the Choose Destination Folder box, type or select the full path to the folder where you want to install the Master Server. 5. Create shortcuts to access the insync Master Management Console. 6. Click Install and then Finish. Next Steps: Clicking Finish launches the insync Master Management Console from which you can configure the Master Server. For information about configuring the Master Server, see Configuring Master Server for Windows. Copyright 2007-2013 Druva Inc. All Rights Reserved.
Installing Master Server on Linux Before you Begin Before you install the Master Server on a Linux computer, make sure that you complete the following tasks: Download the installer package on the computer on which you want to install the Master Server. Have root privileges on the computer on which you plan to install the Master Server. Appoint a first server administrator. Keep the user name, e-mail address, and password for this server administrator handy. Installation Procedure for Debian-based Linux To install insync Master Server: 1. Run the following commands on the Linux server: cd <directory> sudo dpkg -i <package_name> Note: <directory> is the path to the folder where the DEB package is located. <package_name> represents the file name and extension of the DEB package. For example, insync-cloudserver-installer-ver-5.2-r15103.i386.deb. Next Steps: Configure the Master Server. For more information about configuring the Master Server, see Configuring Master Server for Linux. Installation Procedure for Red Hat-based Linux To install insync Master Server: 1. Run the following commands on the Linux server: cd <directory> rpm -ivh <package_name> 12
Note: <directory> is the path to the folder where the RPM package is located. <package_name> represents the file name and extension of the RPM package. For example, insync-cloudserver-installer-ver-5.2-r15103.i386.rpm. Next Steps: Configure the Master Server. For more information about configuring the Master Server, see Configuring Master Server for Linux. Configuring the Master Server After installing the Master Server, you must configure it for use. As a part of this configuration, provide the MySQL authentication details. Additionally, assign the first administrator and define the port for accessing the insync Master Server Management Console. Configuring Master Server for Windows To configure insync Master Server: 2. From the Start menu, select All Programs > Druva insync Master > insync Master Server Management Console. The configuration wizard appears. 3. Click Next. 4. Enter the MySQL authentication details. For more information about the fields that appear on this page, see MySQL Authentication Details. 5. Enter the TCP port number and the first administrator details. For more information about the fields that appear on this page, see Web Console Details. 6. Click Next and then Finish. Configuring Master Server for Linux To configure insync Master Server: 1. On the Linux Terminal, run the following command: sudo insync-master-config.sh 2. When prompted, type the MySQL authentication details. For more information about the values that must be configured, see MySQL Authentication Details. 13
3. When prompted, type the TCP port number and administrator details. For more information, see Web Console Details. Note: To view the options available in insync-master-config.sh, run the command sudo insync-master-config.sh h To reconfigure an admin account, run the command sudo insync-master-config.sh -f Next Steps: If you assign somebody other than yourself the role of the first administrator, send an e- mail to that person with the following information: The MySQL user account details The IP address of the Master Server The TCP port assigned to the Master Server The e-mail address of the administrator The password for authenticating the administrator's e-mail With this information, the administrator can access the insync Master Management Console from any computer on your network. MySQL Authentication Details The following table lists the details required to configure the MySQL database that you want to connect to the insync Master Server. Information Required Description Hostname The IP address of the system where the MySQL database is installed. Port The port required to connect to the MySQL database. The default 14
value is 3306. Username The user name of the MySQL account. Make sure that ALL privilege is assigned to this user. Password The password used to access the MySQL user account. DB Name The name of the MySQL database instance that is created while installing the Master server. Web Console Details The following table lists the details required during the initial configuration of the Master Server. Information Required Description Web Console Service TCP Port Number This port is used to access the insync Admin Console. By default, insync Server uses port number 6061. Make sure that the TCP port you assign to insync is free. Note: Configuring the TCP port number is not required for Linux. Administrator Name The display name of the first administrator. E-mail address The e-mail ID of the first administrator. The administrator will need this ID to log on to the insync Admin Console. 15
Password The password for the first administrator. 16
Installing insync Storage Node This section contains instructions for installing the Storage Nodes on Windows or Linux operating systems. Installing Storage Node on Windows Before you Begin Before you install a Storage Node, make sure that you complete the following tasks: Download the installer package on the computer on which you want to install the Storage Node. Have administrative privileges on the computer on which you plan to install the Storage Node. Installation Procedure To install insync Storage Node: 1. Double-click the Storage Node installer. The installation wizard appears. 2. Click Next. The end-user license agreement (EULA) is displayed. 3. Accept the EULA and click Next. 4. In the Choose Destination Folder box, type or select the full path to the folder where you want to install the Storage Node. 5. Create shortcuts to access the insync Storage Node. 6. Click Install and then Finish. Next Steps: Configure your Storage Node to work with the Master Server. For more information, see Configuring the Storage Nodes. Copyright 2007-2013 Druva Inc. All Rights Reserved.
Installing Storage Nodes on Linux Before you Begin Before you install the Storage Node on a Linux computer, make sure that you complete the following tasks: Download the installer package on the computer on which you want to install the Storage Node. Have root privileges on the computer on which you plan to install the Storage Node. Installation Procedure for Debian-based Linux To install insync Storage Node: 1. On the Linux terminal, run the following command: cd <directory>. sudo dpkg -i <package_name> Note: <directory> is the path to the folder where the DEB package is located. <package_name> represents the file name and the file extension of the DEB package. For example, insync-storageserver-installer-ver-5.2-r15103.i386.deb. Next Steps: Configure the Storage Node to work with the Master Server. For more information, see Configuring the Storage Nodes. Installation Procedure for Red Hat-based Linux To install insync Storage Node: 1. On the Linux terminal, run the following command: cd <directory> rpm -ivh <package_name> 18
Note: <directory> is the path to the folder where the RPM package is located. <package_name> represents the file name and the file extension of the RPM package. For example, insync- StorageServer-Installer-ver-5.2-r15103.i386.rpm. Next Steps: Configure the Storage Node to work with the Master Server. For more information, see Configuring the Storage Nodes. Configuring the Storage Nodes To configure a Storage Node to work with the Master Server: 2. Generate a registration key for the Storage Node. For information, see Generating Storage Node Registration Key. 3. From the insync Admin Console, link the Storage Node to the Master Server. You must have an insync administrator account to perform this task. For more information, see the insync Administrator Guide (5.2 Private Cloud). 4. (Only for Storage Nodes create on Linux) Identify the directories to where insync administrators will create storages and set group and user permissions on these directories. For information, see Set Permissions on Storage Directories. Generating Storage Node Registration Key Generating Storage Node Registration Key on Windows To create a Storage Node registration key: 1. From the Start menu, click All Programs > Druva insync Storage Node. 2. The registration key for the Storage Node is displayed. Share this key with the insync administrator who will link the Storage Node to the Master Server on the insync Admin Console. Generating Storage Node Registration Key on Linux To create a Storage Node registration key: 1. Run the following command on the Linux Terminal: sudo insync-storagenodeconfig.sh -k 19
2. The registration key for the Storage Node is displayed. Share this key with the insync administrator who will link the Storage Node to the Master Server on the insync Admin Console. Set Permissions on Storage Directories This procedure is applicable only when you create a Storage Node on a Linux computer. You must create the folders for insync administrators to create storages and set appropriate permissions on them. To create and configure a directory for insync storage: 1. On the Linux Terminal, run the following command: sudo insync-storagenode-config.sh -s <path to the storage directory> Note: <path to the storage directory> refers to the folder that you want to create for insync storage. The command creates the folder and provide insyncserver group and owner permissions on the folder. Alternative method: To configure a directory for insync storage, you can create a folder and run the command: sudo chown insyncserver:insyncserver <path to the storage folder> 20
insync Log and Configuration Files Sometimes, when insync is not behaving as expected, it is helpful to go through its log and configuration files. While raising a support request on the Druva Support Website, it is good to attach the log and configuration files. By perusing the log and configuration files, the Druva Support team is able to diagnose the root cause of your issue and provide appropriate solutions. Therefore, you must know where the insync log and configuration files are stored. You must also know the name of the insync services. Sometimes, restarting the services can resolve the issue you are facing. insync Log Files The insync log files are available in the following locations. Log files for... On Windows OS On Linux OS Master Server C:\inSyncCloud\logs\CPortal.log C:\inSyncCloud\logs\inSyncCloudServer.log C:\inSyncCloud\logs\inSyncSyncServer.log C:\inSyncCloud\inSyncServer4\inSyncSharePanel.log /var/log/insynccloud/cportal.log /var/log/insynccloud/insynccloudserver.log /var/log/insynccloud/insyncsyncserver.log /var/log/insynccloud/insyncsharepanel.log Storage Nodes C:\inSyncCloud\logs\inSyncStorageServer.log /var/log/insynccloud/ insyncstorageserver.log The components generating the log files are as follows: insync Master Control Panel Service generates CPortal.log and insyncsharepanel.log insync Master Config Service generates insynccloudserver.log insync Master Sync Service generates insyncserver.log insync Storage Node Service generates insyncstorageserver.log Copyright 2007-2013 Druva Inc. All Rights Reserved.
insync Configuration Files Warning: Never change the configuration files manually. Always use the insync Admin Console to configure insync. In case of any problem, contact support@druva.com. The insync configuration files are available in the following locations. Configurat ion files On Windows OS On Linux OS Master Server C:\inSyncCloud\inSyncCloudServer.cfg C:\inSyncCloud\inSyncServer4\inSyncServer.cfg /etc/insynccloud/insynccloudserver.cfg /etc/insynccloud/insyncserver/insyncserver.cfg Storage Nodes C:\inSyncCloud\inSyncStorageServer.cfg C:\inSyncCloud\inSyncServer4\inSyncServerSto rage.cfg /etc/insynccloud/insyncstorageserver.cfg /etc/insynccloud/insyncserver/insyncserversto rage.cfg The information stored in the configuration files are as follows: insynccloudserver.cfg stores the configuration parameters for MySQL insyncserver.cfg stores configurations like SMTP settings, port numbers, and Server IP lists insyncstorageserver.cfg stores configurations like the node authentication key insyncserverstorage.cfg stores configurations like port numbers for web restore, sync, and so on insync Services Warning: Stopping the insync Services will stop synchronization and restores for all configured clients. insync Services for Windows The insync Services for Windows are as follows. 22
Name of the Service Location Description Druva insync Config Server Master Server insync Master config service Druva insync Sync Server Master Server insync Master sync service Druva insync Master Control Panel Master Server insync Master Control Panel service Druva insync Storage Node Storage Nodes insync Storage Node service insync Services for Linux The insync Services for Linux are as follows. Name of the Service Location Description insynccloudsrv /etc/init.d/insynccloudsrv on Master Server Responsible for Config Server and Sync Server processes insynccportal /etc/init.d/insynccportal on Master Server Responsible for insync Master Control Panel insyncstoragesrv /etc/init.d/insyncstoragesrv on the Storage Nodes Responsible for running the Storage Node 23
Upgrading insync Private Cloud This section contains information about upgrading insync Private Cloud (formerly known as insync Unlimited) to version 5.2.0. Upgrade Roadmap This topic contains the high-level steps for installing insync Private Cloud. To ensure that your installation completes successfully, follow the chronology of this roadmap. Step Task Description 1 Check prerequisites Make sure that the computers on which you plan to install the Master Server and Storage Nodes meet the system requirements. For information about the insync Private Cloud version from which you can upgrade, see Compatible insync Private Cloud Versions. For hardware and software requirements for upgrading Master Server, see Prerequisites for Master Server. For hardware and software requirements for upgrading, see Prerequisites for Storage Node. 2 Upgrade the Storage Nodes Upgrade all instances of Storage Nodes. For more information, see Upgrading the insync Storage Nodes. 3 Upgrade the Master Server Upgrade the Master Server. For more information, see Upgrading the insync Master Server. Copyright 2007-2013 Druva Inc. All Rights Reserved.
4 Modify insync Configuration To accommodate the changes to insync workflow, make changes to your insync configuration. For more information, see Post-upgrade Configurations. Upgrade Prerequisites Compatible insync Private Cloud Versions You can upgrade to insync Private Cloud 5.2 from versions 5.0.1 and later. insync Private Cloud was formerly known as insync Unlimited. Note: The insync Private Cloud 5.2 has a feature called High Availability. When you upgrade insync Private Cloud, this feature will not be available for those storages that were optimized for "Disk space savings". The High Availability feature will be available for all your storages that were optimized for "Performance". To know more about the High Availability feature, see the insync Release Notes. Hardware and Software Prerequisites For information about the hardware and software required for Master Server and Storage Nodes for insync Private Cloud 5.2, see Installation Prerequisites. Available Ports If you have the insync Master Server and an insync Storage Node on the same computer, check the sync port used by the Storage Node. If the Storage Node is using 6071 as the sync port, change it to any other available port, say 7071. The Master Server of insync Private Cloud uses the port 6071 and therefore, can cause conflict with the insync Storage Node. Upgrade Procedure Upgrading the insync Storage Nodes The upgrade procedure for the insync Storage Nodes is identical to the installation procedure. 25
Operating System Upgrade Instructions Windows Uninstall the older version of Storage Node and then install the current version. For uninstallation instructions, see Uninstalling the Storage Nodes. For installation instructions, see Installing Storage Node on Windows. Linux Uninstall the older version of Storage Node and then install the current version. For uninstallation instructions, see Uninstalling the Storage Nodes. For installation instructions, see Installing Storage Nodes on Linux. Upgrading the insync Master Server The upgrade procedure for the insync Master Server is identical to the installation procedure. Operating System Upgrade Instructions Windows Uninstall the older version of Master Server and then install the current version. For uninstallation instructions, see Uninstalling the Master Server. For installation instructions, see Installing Master Server on Windows. Linux Uninstall the older version of Master Server and then install the current version. For uninstallation instructions, see Uninstalling the Master Server. For installation instructions, see Installing Master Server on Linux. Notes: 1. To upgrade, you must first uninstall the Storage Node or the Master Server and then install the latest version. Uninstalling is necessary as the service names have been modified in the latest 26
version. Uninstallation will neither delete your backed up data nor affect your insync configuration. 2. In rare cases, while upgrading the insync Master Server on Windows, an error is displayed asking you to check the insyncsrvcfg.exe.log file. Click OK to ignore the error. 3. When upgrading to insync Private Cloud 5.2 on Ubuntu Linux, if the insync Master Server and one insync Storage Node is installed on the same computer, use the following command to install the Storage Node and the Master Server: sudo dpkg --force-overwrite -i <package name of Master Server/Storage Node> Post-upgrade Configurations With insync 5.2, some of the insync workflows have undergone changes. To align your setup to the changes, you will have to make some modifications to it. Modifying the Quota Assigned to Users In the earlier versions of insync, quota was the space allocated to a user on the insync storage. With every backup or sync operation from a user's device, incremental data was added to the storage till the user ran out of the allocated space. In insync 5.2, quota is calculated based on the native size of data that the user has selected for backup or sync from his or her devices. If users now reach their quota, they can reduce the data in their backed up locations, or their insync Share folder, to continue their backup or sync operations. To align with the new definition, the insync administrator may wish to reduce the quota allocated to each user. Installing an SSL Certificate for Restores With insync 5.2, requests from users to restore data are routed through insync Web. insync Web interacts with insync Server over a secure HTTP connection. To facilitate this secure interaction, a selfsigned certificate is used on insync Server. However, because a self-signed certificate is used, the users see a untrusted certificate message on their Web browser when they initiate a restore. 27
It is therefore recommended that the insync administrator install an SSL certificate signed a thirdparty Certificate Authority. For instructions on how to install an SSL certificate, see the insync Administrator Guide (5.2 Private Cloud). Alternatively, you can educate your end-users about the untrusted certificate message. Backing Up System and Application Settings insync 5.2 has the new Persona Backup function where insync administrators can also choose to back up system and application settings from user devices. When adding a new device, or replacing a device, users can choose to restore the system and application settings. Persona Backup is activated within the Profile and can only be set by an insync administrator. For instructions on how to activate system and application settings, see the insync Administrator Guide (5.2 Private Cloud). Configuring High Availability of Performance Optimized Storages With insync 5.2, the insync administrator can create a secondary storage and map it to one of your performance optimized storages. The secondary storage ensures that data backups and restores continue even when the primary storage is down. This high availability functionality is not available for disk space saving storages. Also, with insync 5.2, administrators can no longer create disk space saving storages. Save Storage Node Details If you have upgraded to insync Private Cloud 5.2 from insync Private Cloud 5.0.1, the insync administrator must manually save the port numbers defined for each Storage Node. For instructions, see Modifying the Storage Node Name or the Ports Used in the insync Administrator Guide (5.2 Private Cloud). The administrator need not make any change to the port numbers; just open the Edit Storage Node window and click Save. Define Time Zones for Administrators If you are upgrading to insync Private Cloud 5.2 from version 5.0.1 or 5.1, ask all administrators to define their time zones on the insync Admin Console. The time zone feature was introduced in insync Private Cloud 5.1.1 and enables administrators to view timestamps in the insync Admin Console interface per their local time zone settings. Administrators who do not configure their time zones, will 28
view all timestamps per UTC time. For instructions on defining the time zone, see Defining Your Time Zone in the insync Administrator Guide (5.2 Private Cloud). Restart the Config Server Service on insync Master Server If you are upgrading to insync Private Cloud 5.2 (installed on Windows OS) from version 5.0.1 or 5.1, and have created AD mappings on your existing installation, restart the Druva insync Config Server service through the Services Microsoft Management Console snap-in. 29
Uninstalling insync Private Cloud This section contains information about uninstalling insync Server. Uninstallation Roadmap This topic contains the high-level steps for uninstalling insync Private Cloud. To ensure that your installation completes successfully, follow the chronology of this roadmap. Step Task Description 1 Delete all Users, Storages, and Storage Nodes From the insync Private Cloud Admin Console, delete all Users, Storages, and Storage Nodes. For instructions, see the insync Administrator Guide (5.2 Private Cloud). 2 Uninstall all Storage Nodes Uninstall the Storage Nodes. For more information, see Uninstalling the Storage Nodes. 3 Uninstall the Master Server Uninstall the Master Server. For more information, see Uninstalling the Master Server. 4 Delete the configuration files for Master Server Delete the Master Server configuration files. For more information, see Deleting the Master Server Configuration Files. 30
Uninstalling the Storage Nodes Before You Begin Before you uninstall a Storage Node, make sure that the insync Private Cloud application is not running. Uninstallation Procedure for Windows To uninstall a Storage Node: 1. From the Start menu, select All Programs > Druva insync Storage Node > Uninstall Druva insync Storage Node. A dialog box requesting for your confirmation appears. 2. Click Yes. Uninstallation Procedure for Debian-based Linux To uninstall a Storage Node: On the Linux terminal, run the following command: sudo dpkg -r druva<version> Note: To know the version of the Storage Node installed, use the dpkg --get-selections grep druva command. Uninstallation Procedure for Red Hat-based Linux To uninstall a Storage Node: Run the following command: rpm -e <package_name> Note: In the above command, <package_name> represents the RPM package name of the Storage Node. For example, insync-storageserver-installer-ver-5.2-r15103.i386.rpm. To know the version of the Storage Node installed, use the dpkg --get-selections grep druva command. 31
Uninstalling the Master Server Before you Begin Before you uninstall the Master Server, make sure that the insync Private Cloud application is not running and the Storage Nodes have been uninstalled. Uninstallation Procedure for Windows To uninstall the Master Server: 1. From the Start menu, select All Programs > Druva insync Storage Node > Uninstall Druva insync Master. A dialog box requesting for your confirmation appears. 2. Click Yes. Uninstallation Procedure for Debian-based Linux To uninstall the Master Server: On the Linux terminal, run the following command: sudo dpkg -r druva<version> Note: Use the dpkg --get-selections grep druva command to know the version of the Master Server. Uninstallation Procedure for Red Hat-based Linux To uninstall the Master Server: On the Linux terminal, run the following command: rpm -e <package_name> Note: In the above command, <package_name> represents the RPM package name of the Master server installed. For example, insync-cloudserver-installer-ver-5.1.1- r15103.i386.rpm. Use the rpm -qa grep druva command to know the version of the Master Server. 32
Deleting the Master Server Configuration Files Before you Begin Before you delete the Master Server configuration files, make sure that the insync Master Server has been uninstalled. Deleting Configuration Files on Windows To complete the uninstallation, manually delete the following files on the computer where insync Master Server was installed: C:\inSyncCloud C:\Program Files (x86)\druva Deleting Configuration Files on Linux To complete the uninstallation, manually delete the following files on the computer where insync Master Server was installed: /etc/insynccloud /opt/druva /var/log/insync 33