Upgrading 7.0 systems protecting Oracle and SharePoint Applications

SUMMARY

Upgrading 7.0 systems protecting Oracle and SharePoint Applications

ISSUE

Purpose

This KB article is to provide instructions for upgrading from a pre-7.4 system. The KB includes information about upgrading 7.0 systems protecting Oracle and SharePoint Applications.

Description

Additional Steps when upgrading from a pre-7.4 version

These additional requirements and considerations apply only when upgrading from a pre-7.4 version.

Requirement for
Pre-7.4 Upgrade

Description

Windows backups

Run new full Windows file-level backups after upgrading the backup system and Windows agent to version 8.0. This is required to:

  • Use the Windows integrated bare metal recovery feature.
  • Protect Windows 2012 clients that have Windows deduplication enabled.
  • Take advantage of significant reliability and performance enhancements.

VMware backups of ESX(i) 3.x no longer supported

Unitrends no longer supports agentless data protection of ESX(i) 3.x hypervisor versions. You must do one of the following before upgrading:

Oracle and SharePoint backups on Version 7.0

To upgrade a Unitrends version 7.0 system that is running Oracle or SharePoint backups, follow the instructions in KB 1779 after upgrading to version 8.0.

Hyper-V backups

After upgrading to 8.0, Hyper-V backups will run concurrently rather than sequentially. It’s a good idea to visit your schedules to see if they should be staggered for optimum performance.

For Hyper-V and VMware backups running on a Unitrends 32-bit appliance

If you are performing Hyper-V or VMware backups and have not run fulls since version 7.1.0-4, you must run full Hyper-V and/or VMware backups after upgrading to version 8.0. For a list of Unitrends 32-bit appliances, see KB 1321.

For protection of Oracle 11g on Linux and Oracle 11g on Solaris

If you are currently running Oracle backups, you must do the following after you upgrade the backup system: upgrade the Linux or Solaris agent on the Oracle client to 8.0, set up new Oracle credentials, then run new Oracle full backups. (8.0 is the latest agent release for Linux and Solaris.)

Versions prior to 6.0

If you are running a pre-6.0 version, contact Support for assistance in upgrading.

If you are currently running SharePoint or Oracle backups of any Windows client on a Unitrends version 7.0 system, you must do the following after upgrading to the Unitrends appliance to version 8.0:

1       Upgrade to the 8.0 Windows agent as described in Upgrading Client Software on page 6.

2       Set up the client so the Unitrends system can detect the Oracle or SharePoint application. (See Display of Oracle application in the backup system and Display of SharePoint agent in the backup system from the Unitrends Administrator's Guide

3       Set up credentials if required.

  • For SharePoint, credentials are required. Set them up as described in Creating Credentials for SharePoint on page 14.
  • For Oracle, see Credentials for Oracle on Windows below to determine whether credentials are needed.

Setting up the Oracle and SharePoint Applications

Perform the following after upgrading to the 8.0 windows agent so the system can detect the Oracle or SharePoint application.

1       Select Settings > Clients, Networking, and Notifications > Clients.

2       Select the desired client.

3       Click Setup.

Credentials for Oracle on Windows

If you are upgrading to Unitrends version 8.0 and are currently running Oracle backups, you may need to set up Oracle credentials after the upgrade. Credentials are required to perform Oracle backup and restore jobs. In general, credentials can be set at the instance level or client level in the Unitrends system:

  • Client-level credentials are set on the Add Client page. These credentials are required to access certain client types (such as VMware and Cisco UCS), are optional for Windows clients, and are not used for all other client types.
  • Instance-level credentials are required to access certain application instances, including Oracle instances.
  • To ensure sufficient privileges, the Oracle credential user must be a member of the ora_dba group.
  • For Oracle on Windows, if both instance-level and client-level credentials have been set, the system uses instance-level credentials for Oracle backups and restores. If instance-level credentials are incorrect, the backup fails without attempting to use any client-level credential.
  • If no credentials are available, or if credentials are incorrect, the backup fails with a TNS permission denied error.

See the following to determine whether Oracle instance-level credentials are needed in your environment:

  • If the Windows NT AUTHORITY\SYSTEM user is a member of the ora_dba group, you do not need to add Oracle credentials. Oracle backups and restores are performed using the NT AUTHORITY\SYSTEM account.
  • If you have set up client-level administrative credentials on the Add Client page to enable push installations and this Windows credential user is a member of the ora_dba group, the system can use this client-level credential for Oracle protection as well. If not, you must also add instance-level credentials for each Oracle instance you wish to protect.
  • If the cases above do not apply, add instance-level credentials for each Oracle instance you wish to protect.

To create a new credential for an Oracle database, follow these instructions:

1       Select the Oracle instance in the Navigation pane and click Backup.

2       On the 1-Time Backup or Schedule Backup tab, databases display in the Select Items list. To refresh the list, click the Reload icon in the bottom right.

3       Click the Credential icon to the right of the desired database.

4       In the Set Credentials for the Listed Items window, click New Credential and enter the following:

Field

Description

Credential Name

Name associated with the credential. This is optional.

Administrative Username

User must be a member of the ora_dba group for Windows clients.

Password

Password associated with the username you supplied.

Confirm Password

Enter the password again to confirm.

Domain

Name of the Windows domain associated with this credential. This is optional.

Set as Default

Check this box to set the credential as default for the system. This is optional.

 

5       Click Create and Set Credential.
The credential is created and applied to the selected database.

Note: If you are running Oracle on Windows, you must run a new Oracle full backup after upgrading.

Creating Credentials for SharePoint

If you are upgrading to 8.0 and are running SharePoint backups, you must upgrade the Windows agent on the SharePoint server to 8.0 and set up SharePoint database credentials.

Trust credentials are needed for the Unitrends system to back up the SharePoint farm database. These credentials must be set at the database instance level as described below. To ensure sufficient privilege, it is recommended that the credential user be a member of the administrators group on the local computer for each member of the farm, and a member of the farm administrator’s SharePoint group. In addition, you may also wish to define client-level trust credentials to enable push install of the Unitrends agent. These client-level trust credentials are not used to back up the SharePoint instance. You must define instance-level credentials for backups to run successfully.

If you experience backup errors using new credentials, see the following KnowledgeBase articles for more information: KB 1181, KB 1183, KB 1184, KB 1185, KB 1186, and KB 1187.

To create a new credential for a SharePoint database:

1       Select the SharePoint farm instance in the Navigation pane and click Backup.

2       On the 1-Time Backup or Schedule Backup tab, databases display in the Select Items list. To refresh the list, click the Reload icon in the bottom right.

3       Click the Credential icon to the right of the farm database.

4       In the Set Credentials for the listed Items window, click New Credential and enter the following:

Field

Description

Credential Name

Name associated with the credential. This is optional.

Administrative Username

User must be a member of the administrators group on the local computer for each member of the farm, and a member of the farm administrator’s SharePoint group.

Password

Password associated with the username you supplied.

Confirm Password

Enter the password again to confirm.

Domain

Name of the Windows domain associated with this credential. This is optional.

Set as Default

Check this box to set the credential as default for the system. This is optional.

     Click Create and Set Credential. The credential is created and applied to the selected tab.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Contact us