Home » Support » Common Issues » Support Documents » The LiveVault Essential Information Guide

Support DocumentsThe LiveVault Essential Information Guide

This guide will help you quickly install and configure a new LiveVault (LV) agent and create an initial backup policy. It is based on many years of installing and supporting the product and provides important guidance in the “Getting the Best out of LiveVault” section.

You should read this guide in conjunction with the:

• Quick Start Guide
• Environment Configuration Guide
• Release Notes

Together these guides provide full instructions on installing and configuring your LiveVault service.

Following these instructions will make your initial backup experience hassle-free and provide a robust environment going forward.

Pre-Install Checklist

The pre-install checklist is to ensure that your installation will go smoothly. If you require assistance please call 0800 0789 438. You will be asked to confirm that you are aware of all the following:

	I have discussed my backup requirements with Backup Direct’s consultant taking account of the software running on the server and data to be protected. There are no network drives to be protected.
	I have received my logon account details from Backup Direct.
	I have read the two supporting documents – Quick start and Environment Guides. (See links above)
	The server on which LiveVault is to be installed is running a supported OS and meets the minimum system requirements (see “Environment Configuration Guide” Page 9 for details).
	Consideration has been given to the required internet bandwidth and optimum time of day for the service to upload data to the data centres – both for the initial backup and regular incremental backups thereafter.
	The necessary amendments to the network infrastructure such as opening the relevant communication ports and other amendments to anti-virus/firewalls have been done (see Page 12 LiveVault Environment Configuration Guide for details).
	The backup strategy has been carefully considered – what data to protect, how often and when? I appreciate how to prepare and structure the backup policies (max. of 20 per server)
	I have the relevant user permissions to install the software.
	There are no other backup services running on the server to be protected. If there are, the backup times must not overlap. LiveVault folders in the Program Files and the LiveVaultData folder should not be backed up.
	Any anti-virus software is configured not to scan the Iron Mountain\Backup Engine folder in Program Files or the LiveVaultData directory.
	The server has sufficient disk space and memory to run the backup – The VSS service will require setting to the correct amount of storage space (see Page 15 Environment Configuration Guide).
	Exchange must have the appropriate Service Pack applied for Exchange aware policy to be available. (SP2 for Exchange 2003 or SP3 for Exchange 2007)
	The LiveVault system can send automated warning emails regarding connection and backup status. I will set these up with the appropriate recipients. (These are sent to the Administrator of the account automatically. You may have up to two email recipients).
	I am aware that the server will require a full reboot after the LV software is installed.
	I understand that the correct data retention period is selected on the backup policies, as per my Service Agreement. (Contact Service Team if you require assistance)
	None of the data to be protected is encrypted.

 

Getting the Best out of Live Vault

Network Infrastructure

• Open the following ports in your Firewall to allow LiveVault access to the Data vaults and the web server (WebUI). Port numbers 2144, 2145 & 443 must allow outbound TCP/IP communications. (Page 12 LiveVault Environmental Guide).
• Check the upload speed of your bandwidth so that you may calculate the best way to manage your first upload. We have a bandwidth calculator on our website at www.backupdirect.net/speedtest. A minimum upload speed of 100Kb/s is recommended for protecting small data volumes. 1Mb/s and above is recommended where there are large amounts of data changing each day.

First Backup Best Practices

• LiveVault needs an initial full backup of all your selected data before it can start the smaller, faster incremental backups. This can take several days to complete depending on your upstream bandwidth, the amount of data selected, and the policy schedules. Once underway, initial backups should be left to complete as incomplete initial backups will need to restart from scratch if it is edited whilst running.
• It is sensible to run a small policy initially to prove that the entire system and infrastructure is working.
• If you edit a policy during a backup, this will restart the policy from the beginning and re-send all the data. You can edit a policy that is not running without forcing a complete resend of all policy data.
• If using a custom backup schedule, you must select the option to allow the backup to “run beyond the scheduled time” otherwise the backup will stop at the end time and will restart from the beginning and potentially never complete the initial backup.
• Schedule a sensible time to initiate the first backup e.g. over the weekend and overnight.
• Start with a policy for your most critical data, then add new policies one after another as each one completes.

Policy Limits

• Aim to limit each policy sizes to 50-60GB and no more than about 100GB.
• Do not create more than 20 policies on a single server.
• If possible, avoid having a policy which spans data across multiple volumes.
• Group similar sets of data in separate policies e.g. have one policy for User Profiles and one for Office files etc.
• If you select the System State backup option, LiveVault will create a separate System State Policy that runs no more than once every 24 hours.

Using Different Scheduling Methods

• You can create different schedules for different policies. e.g. set a system state backup to run over the weekend and SQL data policy to backup continuously.

Using Continuous Data Protection

• You can use the “Continuous” backup schedule to backup your data every 15 minutes for critical data
• Suitable for large amounts of daily data changes as it spreads the load during the day rather than sending a day’s worth or changes in the evening.

Bandwidth Throttling

• To suit any bandwidth constraints (such as not reducing user’s internet access performance during the working day) you can limit the amount of bandwidth LiveVault will use by using a timed throttle on each server.
• Consider setting a bandwidth limit during working hours and no limit overnight or at the weekend when there will be less demand on your network. Be aware this may affect the frequency of your backups.

Exclusions and Software Interaction

• Refer to the list of recommended exclusions to prevent any problematic conflicts (See Appendix A (Page 19) of the LiveVault Environment Guide).
• Exclude the LiveVault folders from any Antivirus scans and do not schedule disk defragmentation during the backup schedule (See Page 15 & 16 LiveVault Environment Guide)

Microsoft Exchange Policies

• Create a separate backup policy for Exchange installations
• The method for backing up Exchange may differ depending on version and service pack.
• If you are using Microsoft Exchange 2003 SP2 or Microsoft Exchange 2007 SP2 (or SP3 if on SBS2008) you can create an Exchange Aware Policy, which will automatically detect the Exchange databases for easy selection of Exchange information. For Exchange 2003 you may also need to enable the Exchange VSS Writers in order for LiveVault to perform an ‘aware’ backup. (see http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q838183 )
• Ensure that you also back up the System State as this is required for a full Exchange server recovery.
• For Microsoft Exchange 2010 backup please contact Service Team for details.

SQL Policies

LiveVault is able to perform an application ‘aware’ backup of SQL 2005/2008 databases:

• Select the ‘Add New SQL Server Backup Policy
• LiveVault will detect the presence of SQL and offers the SQL-aware backup policy option. You may now select the individual databases you wish to backup.
• On the Options tab you may choose whether or not LiveVault will perform SQL log truncation (N.B. use this option if you do not have log truncation being performed by another application).

For SQL 2000, please follow the following steps:

• Create a separate policy for the SQL data.
• Ensure that you select the folder(s) with the SQL data, transaction logs and application files.
• LiveVault does not truncate or remove the SQL logs so you will need to set up SQL maintenance to truncate the transactions logs or set database recovery model to Simple. Other considerations:
• Exclude SQL backup files, as this will consume a significant amount of storage space and bandwidth.
• Ensure that you also back up the System State as this is required for a full SQL server recovery.

Using a Restore-Only Client

• You can setup another server to act as a stand-by restore machine saving you time in the event that you need to recover data to a different computer.
• Data can be restored to another server by doing a Redirected Restore (see LiveVault Help).
• As LiveVault performs an incremental restore as well as backup, if similar data resides on the restore-only machine the restore will be incremental and therefore this could greatly increase the restore speed of large data sets.
• LiveVault needs be installed and provisioned on this server and the encryption keys from the backed up machine(s) must be imported to the restore-only agent.
• Dependent upon purpose of the restore, this machine ideally would be of a similar build (hardware and software) level to original machine. Reports
• The reports tab in the LiveVault Web Portal will allow you to generate reports to check the status of the backup, network usage and restores.
• Additionally, you can receive a combined report detailing each server and policy set on a daily or weekly basis.

Email Notifications

There are a number of LiveVault email notifications that will update you with the status of the backup the most common are shown below:

• Data Retention, Versions and LiveVault
• Database Backup with LiveVault
• Disaster Recovery (Bare Metal) using LiveVault
• DR Sites and Turbo Restore Appliances
• Backing Up Sage Correctly
• The LiveVault Essential Information Guide
• Backing Up Digita Correctly
• Backing Up QuickBooks Correctly
• Backing up Microsoft Outlook Password protected PST files
• Backup Direct Professional Backup Guide

Contact Backup Direct