Home > netapp > Basic’s on how to back up NetApp with Backup Exec (Linux focused)

Basic’s on how to back up NetApp with Backup Exec (Linux focused)

    • Log in as the administrator for Backup Exec. The details for this operation depend on the specific operating system on which Backup Exec is running. For example, on Linux, log in as user “root” and execute

      cd /opt/VRTSralus/bin

    • Identify the name of the NetApp device you want to use from the operating system’s point of view, and make a note of the name. The details for this operation depend on the specific operating system on which Backup Exec is running.

      For example, on Linux, execute

      mount

      and search for the line corresponding to the NetApp device in the output of “mount.” The result should be a mount point for a filesystem residing on the device, such as “/media/netAppFS3.” Consult with your system administrator if the choice is not obvious.

    • Start RALUS, the configuration interface for Backup Exec. The details for this operation depend on the specific operating system on which Backup Exec is running. For example, on Linux, execute

      ./ralus

    • Click “Media” on the RALUS navigation bar. Click “All media” to display all the available options. Select the NetApp device using the name you obtained for it in Step 2. Click “Media tasks,” then click “Associate with media set.” Select the media set to which this device should belong. Click “OK.” The new device is ready to be used in future backups.

Advertisements
Categories: netapp Tags: , ,
  1. No comments yet.
  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: