This guide covers how to setup Arcserve UDP backups within your environment. This involves installing at least one RPS server, this is where the backup data is stored. The console will also be installed on the RPS typically, allowing you to centrally manage backups. The agent will be pushed out to other servers in your environment from the RPS.
 

Installing Arcserve UDP

Requirements: The RPS/Console server requires the Microsoft .NET Framework 3.5 SP1 to be installed first. This needs to be installed first through server manager, select the ".NET Framework 3.5 Features" feature through the add roles and features wizard provided by server manager and install these first.
  1. First you need to install the UDP console onto your designated arcserve backup server. The console is used to install the agent remotely on all of your other servers. Download the software here: http://www.arcserve.com/us/lpg/arcserve-software-downloads-instructions.aspx by selecting Arcserve UDP Premium Plus Edition.
  2. Once the download has completed, extract the "Arcserve_Unified_Data_Protection_with_update_3" file from the download and run it. This may take some time as it's quite large.
  3. Read through the license agreement, once you reach the bottom you will be able to accept it and click Next to proceed.


     
  4. On the next screen we are given the option to only install the agent, or install a full copy. We will deploy the agent from the RPS/Console server later, so for now we are only concerned with installing the full copy, which contains the console, RPS, and agent.


     
  5. Select where you want to install this, the default is usually fine however if you have a different disk for installing programs select that instead.


     
  6. For the configuration it is recommended to set the protocol to HTTPS as this is more secure. Leave the ports as default, and provide an administrator account and password for the installation process.


     
  7. Set the database settings, in most cases it's fine to use the included Microsoft SQL Server 2008 R2 Express that is included, otherwise you can specify another SQL server if you have one and would prefer to use it.

    Note: At this step you may receive a warning if you do not have .NET 3.5 SP1 installed as this is required for SQL 2008 R2 Express which will be installed. If this is the case you will need to install this first through server manager as noted at the top of this page in the requirements, you will then be able to proceed with the Arcserve installation.


     
  8. The next screen will advise the windows firewall rule exceptions that will be created for the backup process, click Install to proceed.


     
  9. The installation process will then begin.


     
  10. Once installation has completed, you can optionally check online for latest updates which is recommended. After this you will be prompted to reboot the server to complete the process, perform the reboot to proceed with configuration.

Configuring Arcserve UDP

Now that we have completed the installation, it's time to do some basic configuration tasks and add a server to be backed up.
 
  1. From start, open the "arcserve UDP console". This will open https://localhost:8015/ in a browser window. You may need to use Internet Explorer, we have had some issues with Firefox.


     
  2. Log in with your administrator account at the login screen.


     
  3. First you need to configure a data store, a location on the RPS where backup data will be stored. Typically it is a good idea to add a large secondary disk to the server for this, rather than storing the backup data on C drive with the operating system.

    Select the "Resources" tab, followed by "Recovery Point Servers" which is found under "Destinations" in the left hand menu. You should see this console/RPS listed. Right click it and select "Add a Data Store..."


     
  4. Give the datastore a name. Select a folder where backups will go. Select the amount of concurrent backups to run at any given time. Select if you want to encrypt the stored data and if so provide a password (it is very important that you do not lose this or you will not be able to restore data). It is recommended that you deduplicate data as this will save a lot of space, in this case we have separate folders on our secondary disk for the data, index, and hash destinations. Allocate some of your RAM to be used as hash memory, and finally select the deduplication block size to use. Click the "Save" button up the top right when complete.


     
  5. Now that a datastore has been defined, we can add servers to backup. From the "Resources" tab, select Nodes > All Nodes. As this is a new server you will only see the RPS itself there as the only node. Click to add a node, and add another server to be backed up. You will need to specify credentials for the server. If successful, the arcserve agent should be installed on it, this may prompt for a reboot if required. In order for the RPS to connect to the node the appropriate firewall rules must be in place, for details on these see the firewall rule section toward the bottom of this page.



    Once you have entered the credentials in for the node, click the Add to List button, it will then appear on the right hand side. Then click the Save button to complete the process.
     
  6. Now to actually protect the nodes added we need to create a plan that specifies to back these servers up to the datastore we have created at a time specified. From the Resources tab, select All Plans under Plans, and click Add a Plan.


     
  7. Give the plan a name, in this case the plan is named "Daily-Backup-Plan". Select the task type, we have selected Backup: Agent-Based Windows, as we are backing up Windows servers in this plan. Select the "Add Nodes" button, and add the servers that you want to back up, in this example we add the server we previously added.


     
  8. Now that the Source tab has been completed, select the Destination tab. Select where the selected nodes will backup to, here we select the RPS and datastore we created earlier. Create a session password that you will remember.


     
  9. Once you have filled out the Destination tab, select the Schedule tab, this is where we define when the backup plan runs and how many backups are held. In the default settings below we have a daily task set to run at 10pm each day, which will hold 7 days worth of backups.


     
  10. After the schedule has been created, optionally fill out the advanced settings in the next tab. The most useful option here is to tick the "Enable Email Alerts" box, once you configure an SMTP server you will receive alerts for failed/successful jobs. You can also set resource alerts and reports to be mailed out.
     
  11. Once you are done creating the plan, click the Save button toward the top right hand side of the screen. If this is your first plan and your nodes do not yet have the agent installed, you will receive options on how you want to install the agent as shown below.


     
  12. Once the plan has deployed, the agent installed, and the server rebooted, you can either run a backup manually or let the plan run at your scheduled time.

Firewall rules

In order for the console server to connect to the other servers remotely, ports most be opened between the two in both directions. You would do this through both CloudPlatform as requried, and in Windows firewall or iptables on Linux as needed.
 

Add Feedback