Installation guide for DataCove Archiver Virtual Machines Hypervisor type: Hyper-V 2012 R2 December 20, 2015 Revision 1.0

Transcription

1 Installation guide for DataCove Archiver Virtual Machines Hypervisor type: Hyper-V 2012 R2 December 20, 2015 Revision 1.0 Introduction: Hello, and thank you for your decision to utilize the DataCove Archiver! In this document, you'll find information on how to download and import the DataCove Virtual Machine base image, as well as how to configure it for both 'standard' and 'enhanced' levels of performance, dependant on your local hardware resources. As always, if there are any questions beyond the scope of this document, please contact Tangent's DataCove support team at x5 or via at Qualifying hardware resources needed for your model of DataCove: The DataCove Archiver requires different resource allocations depending on the model, which can greatly impact its performance in both volume processed daily as well as how fast search results are returned to the requester. The recommended resource amounts are provided in the below table. Allocation of lesser quantities can still allow the system to function, but at greatly reduced performance levels. DataCove VM Model Processing Cores Memory Disk Space Ethernet Interface DataCove GB 590GB 1x Gigabit DataCove GB 1.1TB 1x Gigabit DataCove GB 2.2TB 1x Gigabit DataCove GB 4.4TB 1x Gigabit DataCove GB 6.7TB 1x Gigabit DataCove GB 8.9TB 1x Gigabit If additional resources are available or increased performance is desired, enhancing DataCove's resource allotment is recommended and can be done according to the below table. An explanation of how different resources are used with DataCove and which would be optimal for your objective is also include further down. As always, gracefully shut down the system before making hardware changes, as the system will not recognize new hardware until reboot.

2 DataCove VM Model Processing Cores Memory Disk Space Ethernet Interface DataCove GB 590GB 1x Gigabit DataCove GB 1.1TB 1x Gigabit DataCove GB 2.2TB 1x Gigabit DataCove GB 4.4TB 1x Gigabit DataCove GB 6.7TB 1x Gigabit DataCove GB 8.9TB 1x Gigabit DataCove uses the hardware granted to it for different primary purposes, with some significant overlap between them in goals. Processors: The number and speed of processing cores assigned to DataCove dictate how many different processing queues can be spawned on the system for parallel workloads. Increasing the quantity of cores assigned to the VM will allow DataCove to "process" more s per day and allow for additional fetching in high volume environments. processing includes how quickly DataCove can pull data in from a remote location ( server or network share for data upload), its deduplication and compression of data, as well as preparation of the s into broken down data sets for the Indexing process to work on. Memory: As the most important resource on DataCove, the amount and speed of the memory available to DataCove determines how many indices can be cached in high speed memory for quick searches, how quickly the Indexing processes can read and catalog all of the data in an , and how many simultaneous operations can be conducted. In both high volume environments or heavy use environments (i.e. end user access), granting additional memory to the DataCove can be the single most beneficial action taken in dealing with vast swathes of incoming s, either from daily loads or when importing existing historical s. The additional elbow room it provides for large index caches can improve search performance for systems with many millions of s on them and for sites granting out end user access to the DataCove for their own archive search and restorations. Memory on DataCove should always be a static memory assignment, and not dynamically allocated, as DataCove will consume all memory it sees.

3 Storage: DataCove's storage needs can be defined in two senses: the sheer amount of space required and the IOPS (Input/Output operations per second) needed for efficient operation. First and foremost, DataCove is an archival device, and its primary consumption of resources is tilted towards disk space. This space is used to provide 'actual value' storage in the sense that a DataCove 500 model provides exactly 500GB of usable space, and any additional space is used for Operating System functions that would otherwise utilize perfectly good archival space instead. Space provided or 'extended' beyond what the virtual machine itself comes with is not used by the system (usable space is determined by the model purchased). The second, and far more important factor, is the IOPS required per system. Traditionally, any Datacove will provide a sufficient level of performance with about 1000 IOPS, but providing higher tiered storage (especially high RPM disks, SSD Cached or even pure SSD volumes) can dynamize the system into an extremely high volume and even more responsive system. It is highly recommended to place DataCove on Tier 0/1 storage whenever possible. All search, fetching and even system level functions such as automated retention policy purges are heavily reliant on disk speed for their own rate limits. The volume on which DataCove is placed can have a significant impact on it as well. Parity based RAID volumes like RAID 5 and RAID 6 (as well RAID 50 and 60) have a write performance penalty that are at odds with DataCove's 96% write/4% read profile, and can lead to lessened performance in terms of volume handled. RAID 10 volumes are the recommended storage type whenever possible. Disk space allocated to DataCove from the base virtual machine is by default Dynamic. While this does have a minor performance penalty, it traditionally is not a bottleneck to the system's performance even in high volume environments. Networking: Networking on DataCove is limited to a single Gigabit network adapter. A single paravirtualized interface comes with the virtual machine as is, and should be assigned to a 'server' designated network. This network should be able to access the following locations: Internet (for KeyServer subscription updates and access to hosted , such as Office 365 or Google Apps) Internal Mail Server (for new fetching, if mail server is onsite) Internal File Server (for backups) Desktop network, for end user access DHCP is desirable to have for initial system installation, but is not required. Adding additional network adapters will not provide teaming, link aggregation or any other benefits to DataCove, and can cause unsupported behaviors.

4 Downloading the DataCove virtual machine image: The DataCove virtual machines are pre-created VM's which exist in a ready-to-import configuration, with all hardware already allocated in a baseline configuration (usually 4-8 cores and 8GB-16GB of RAM). This configuration allows for sites using the DataCove in a low-impact mode to still take advantage of all of its archiving benefits without tying up large quantities of resources if they are not required. The prior explanation of how resources are used on the system can help guide a system administrator into tailoring what is needed most for their organization. The DataCove virtual machine images for Hyper-V can be found here: ftp://dcftp.datacovehosted.com/datacove%20vm%20base%20images/datacove%20images%20hyper-v/ On this FTP, you'll find each model of DataCove listed by its prefix. DCTvi-1000 equates to a the DataCove 1000 model, as an example. Our naming convention determines the model, hypervisor type it is designed for, and OS version for quick review. Once you have located the DataCove model you have purchased, click on the appropriate hyperlink for it to begin download. Once download has completed, decompress the file to find the folders containing the actual virtual machine template. We are now ready to begin importation of the virtual machine into Hyper-V!

5 Importing the virtual machine: The newly decompressed folder will contain multiple subfolders. Once the data has been emplaced into either a network share or uploaded directly to the Hyper-V host, open the Hyper-V Manager and click on Import Virtual Machine: When importing the virtual machine into Hyper-V, be sure to select the Virtual Machines folder:

6 When choosing the Import Type, it is usually best to Copy the Virtual machine and create a new unique ID for it. Other options may leave the virtual machine where it was placed instead of in the proper default locations for virtual machines or, when using multiple DataCove's in concert, may cause non-unique identifiers in Hyper-V to cause management problems. If any file storage locations need to be changed manually, they can be adjusted on later screens. Once all storage options are set according to your site's needs, the Import Wizard will prompt for a network to attach the virtual machine to. As per the Networking instructions above, please attach to this a server zoned network which will be able to reach the mail server or mail hosting service, as well as be accessible by the end users.

7 After importation of the virtual machine is complete, right click on it in Hyper-V Manager and select Settings. Be sure to adjust the memory and processor assignments to the virtual machine as per the recommendations above for your model size of DataCove. Other site specific settings in Hyper-V can be adjusted from here, but are usually not necessary. At this point, we have fully configured the basic properties about the VM and can now boot!

8 Initial system setup: Network configuration of DataCove: Once the virtual machine has been started, you'll see a lot of Linux operating system drivers loading and verifying themselves. Shortly before allowing log in the system, the DataCove will attempt to obtain an IP address via DHCP. If DHCP is present on the network, it will accept an IP from the DHCP server. If one is not present, the system will wait for approximately one minute before letting the DHCP request time out and continuing to boot without network assignment. Once boot is complete, the following login screen will appear: The login to the low level system configuration menu is as follows: Username: cliadmin Password: ChangeMe

9 Once authenticated, the system will present its configuration and diagnostic menu. Start by selecting Option 1, View Current Network Settings. This will display the network configuration of the DataCove, and will be showing us all of the fields we'll need to populate when assigning a static IP address. For quick reference, the following addresses are needed (simple example below): IP address of DataCove: Subnet mask: Gateway: Fully Qualified Domain Name: DataCove.domainname.com DNS Server: (add a space between DNS server IP's when adding multiple) It's best to select which IP the system will be bound to prior to beginning the static IP setup. Once an IP and other network details are figured out, use Option 0 (return to main menu), and then select Option 3 to begin the static IP setup. The first step is to bind the static IP to the right Ethernet interface, which should display as the one and only ETH0 on DataCove.

10 From here, simply follow the prompts and fill in the appropriate information for each field. If the information in the field is also accurate, press Enter to retain it and move on to the next field. After all fields have been populated, the system will ask to confirm the information and then prompt to reboot. If the information is accurate, proceed with the reboot. If it isn't, press N for no, and it will send you back to the main menu to start again. Applying the DataCove Maintenance Key: NOTE: The following step is typically performed with a DataCove installation technician on the phone and is not necessary to execute prior to your normal setup appointment. If you'd like to get a step ahead, please follow the below instructions. After the DataCove has rebooted, you'll be able to access the web interface at the assigned static IP address. Launch a web browser and type the DataCove IP address (if a DNS entry was already made, type in the hostname) into the address bar. You should wind up at the DataCove login page, as seen in the below picture:

11 The login information here is a little different than that of the console login: Username: admin Password: ChangeMe Upon login, the DataCove End User License Agreement will appear. Please take a moment to review it in its entirety before clicking Accept (if the agreement is declined, cease use of the system straight away and contact your sales representative). After the EULA, the system will send you to the Search interface.

12 The Search section will be covered by your Installation Technician; for our setup purposes, please click on the Maintenance header, and then click on the Maintenance Key on the left hand side: The system will now be prompting for the Maintenance Key used to uniquely identify your DataCove, as well as track whether new product updates are available for it and the status of its service subscription. This 30 character alphanumeric key can only be provided by Tangent support personnel when a new DataCove VM is purchased. If you have not received your key, please contact Tangent support at x5 or via at Support@tangent.com. Once you have received your Maintenance Key, enter it into the specified field. Dashes are required for this key entry. With the key added, the system is now fully ready for archiving. It is suggested to update the system via the Update Now link on the left hand menu (requires system registration, which can performed via a call to Tangent support, an to Support@tangent.com or registration can also be handled online with the use of the Maintenance Key.

13 DataCove System Configuration and beyond: With the Maintenance key added, your DataCove VM setup is complete and the regular system configuration guide and/or your installation technician will be able to guide you through all other steps. As always, if there are any questions, problems or concerns that go beyond the scope of this document, please contact us right away! Tangent prides itself on a knowledgeable and highly responsive support team, and we are always excited at the possibility of being able to assist you. To contact Tangent Support: By phone: x5 By Support@tangent.com Support hours: 6:30am -3:30pm Pacific Standard Time, weekdays. Enterprise Support hours: 24/7/365. Please contact your Sales Representative on how to obtain Enterprise Support if extended support services are desired.