LogoLogo
EBR DocsHelp
Zmanda Classic
Zmanda Classic
  • Welcome to Zmanda Documentation
    • Zmanda Video Walkthrough
    • Zmanda 5.1 Release Notes
      • Zmanda 5.1.1 Release Notes
      • Zmanda 5.1.2 Release Notes
      • Zmanda 5.1.3 Release Notes
      • Zmanda 5.1.4 Release Notes
      • Zmanda 5.1.5 release notes
    • Zmanda 5.0 Release Notes
      • Zmanda Patch 5.0.0.7 Release Notes
      • Zmanda Patch 5.0.1.0 Release Notes
    • Zmanda 4.3 Release Notes
    • Zmanda 4.2 Release Notes
    • Zmanda 4.1 Release Notes
  • Getting Started With Zmanda
    • Terms, Concepts, and Best Practices
    • Cloud-Based Trial Environment
  • Installation & Configuration
    • Step 1: Install Zmanda Server
      • Dependencies & System Requirements
      • Zmanda Backup Appliance Installation
      • Oracle Cloud Marketplace Installation
      • AWS Marketplace Installation
      • Azure Marketplace Installation
      • Linux Binary Installation
      • Client-side Deduplication Documentation
      • Add Backup Servers in the ZMC
    • Step 2: Add Storage
      • Zmanda Cloud Storage
      • Simple Disk
      • NAS & SAN
      • Tape
      • Cloud Storage
    • Step 3: Add Sources
      • Prerequisite: Initialize a Backup Set
      • Windows
        • Installation
          • ZWC Silent Installation Guide
        • Configuration
      • Linux
        • Installation
        • Configuration
      • VMware and Hyper-V
      • File Shares
      • Databases and Applications
        • Oracle DB's - Linux
        • Oracle DB's - Windows
        • PostgreSQL Server - Linux
        • Microsoft SQL Server
        • Microsoft Exchange
        • Microsoft SharePoint
      • Mac OS
    • Step 4: Run a Backup
    • Step 5: Run a Restore
      • VMs Restore Process
      • PostgreSQL Restore Process
    • Step X: Intelligent Scheduling
    • Troubleshooting
  • Information
    • Backup Overview
      • Storage
      • Backup Sets
      • Sources
        • Large and complex data sources
      • Schedule Plan
    • Restore Overview
    • Disaster Recovery
      • Disaster Recovery with Zmanda: A Comprehensive Guide
    • Reports
    • Data Integrity
    • Custom Reports
    • Audit
    • License Info
    • Comprehensive Guide to Downloading Zmanda EBR 5.1 License
  • CUSTOMIZATION
    • How to Customize Your Zmanda Deployment
      • Vaulting
      • User Management
        • Single Sign-On Integration
        • LDAP Integration in Zmanda
        • Custom Roles and Policies
      • Enabling Email Notifications
      • Bulk Deployment of Zmanda Linux Clients
      • Bulk Deployment of Zmanda Windows Clients
      • Bulk Automation Guide
      • Immutable Backups
      • Global Exclusion Policy for Linux and Windows Clients
      • Client Triggered Oracle Backups
      • Archive to AWS Glacier Tiers
      • Comprehensive Guide to Setting Up Zmanda in AWS
      • Comprehensive Guide to Setting Up Zmanda in Azure
  • Product Lifecycle
    • Explore product lifecycle
Powered by GitBook
LogoLogo

Quick Links

  • Amanda Community Wiki
  • Amanda Community Downloads
  • Share Feedback

About

  • About Us
  • Customer Testimonials

Terms

  • Terms of Use
  • Privacy Policy

Contact Info

  • Denver, CO, USA
  • 888-496-2632 (US)
  • 408-732-3208 (INT)

2025 © Zmanda, A BETSOL Company

On this page

Was this helpful?

Export as PDF
  1. Installation & Configuration
  2. Step 1: Install Zmanda Server

Oracle Cloud Marketplace Installation

Zmanda + The next-generation cloud. Protect your data for less.

PreviousZmanda Backup Appliance InstallationNextAWS Marketplace Installation

Last updated 1 year ago

Was this helpful?

Building Zmanda on Oracle Cloud Infrastructure (OCI) enables you to deploy a backup server in any geography in minutes. It is also ideal if your workloads are hosted on OCI, or if you are using OCI Object Storage as a target. Let's get started:

Steps

  1. Login to your OCI account, select the region you would like to deploy your Zmanda Server in, and navigate to Instances. Click Create instance

  2. Give the instance a name and complete the Compartment, Placement, and Security fields as desired

  3. In the Image and shape box, click Change image

  4. Click Marketplace, type "Zmanda" in the search bar, check the appropriate boxes, and click Select Image

  1. Change the shape as desired. For minimum system requirements, see here.

  2. In the Primary VNIC information section, select the appropriate virtual cloud network (VCN) and subnet.

You must configure ingress rules that allow TCP traffic on ports 8008, 8002, 10080, 10081, and 22 (if using ssh to connect).

To do this, you can go to Networking>Virtual Cloud Networks>Click on your VCN>Click on the default subnet or create a new subnet>Click on the default security list or create a new security list>Add the appropriate Ingress rules.

See this OCI documentation for more information.

  1. Configure the rest of the settings as desired including SSH. If you do not enable SSH, you will only be able to connect through a Cloud Shell Connection. When finished, click Create

  2. You will be taken to the Instance page where you can see info about the instance. You can connect to the instance using the SSH keys or through a Cloud Shell Connection

  3. Once connected, reset the admin password for Zmanda using the following command:

sudo /opt/zmanda/amanda/bin/reset-admin-password

//Requirements
length should be at least 8
Password should have at least one numeral
Password should have at least one uppercase letter
Password should have at least one of the symbols $,@,#,%,^,&,*,~
  1. Type admin for the username, and input a password that meets the above criteria.

  2. Run setup-aee and setup-zmc to make sure that all services are running.

  1. Run sudo setup-zmc unseal

  1. Go to network.zmanda.com and download any patches that are available. Untar them and find and execute the patch executable.

  1. You can now log in to the ZMC console by opening any browser in your internal network and typing the following in the address bar:

https://<VM’s Public IP>:8008

The credentials will be the username (admin) and the password you set in step 10