Rubrik: Difference between revisions
No edit summary |
|||
(11 intermediate revisions by the same user not shown) | |||
Line 26: | Line 26: | ||
* Install the Rubrik backup agent on any physical servers you may wish to backup | * Install the Rubrik backup agent on any physical servers you may wish to backup | ||
* Create some SLA groups with the backup retention etc that meets your needs | * Create some SLA groups with the backup retention etc that meets your needs | ||
===Factory reset entire Rubrik=== | ===Factory reset entire Rubrik=== | ||
Line 60: | Line 61: | ||
Once you see this message you can reboot the Rubrik and start the setup process again, obviously if you have more than one Rubrik node you will need to repeat the above for each node. | Once you see this message you can reboot the Rubrik and start the setup process again, obviously if you have more than one Rubrik node you will need to repeat the above for each node. | ||
===Restarting a Rubrik cluster=== | |||
* SSH To any of the Rubrik nodes in the cluster using the admin account | |||
Example output: | |||
<pre style="color: silver; background: black; width: 800px"> | |||
ssh admin@10.10.10.10 | |||
</pre> | |||
* Enter admin password to access the Rubrik CLI prompt | |||
Example output: | |||
<pre style="color: silver; background: black; width: 800px"> | |||
~ host$ ssh admin@10.10.10.10 | |||
admin@10.10.10.10's password: | |||
Last login: Fri Feb 20 16:42:04 2019 from 10.242.100.1 | |||
</pre> | |||
* Type | |||
<pre>cluster reboot cluster</pre> | |||
===Shutting down a Rubrik cluster=== | |||
* SSH To any of the Rubrik nodes in the cluster using the admin account | |||
Example output: | |||
<pre style="color: silver; background: black; width: 800px"> | |||
ssh admin@10.10.10.10 | |||
</pre> | |||
* Enter admin password to access the Rubrik CLI prompt | |||
Example output: | |||
<pre style="color: silver; background: black; width: 800px"> | |||
~ host$ ssh admin@10.10.10.10 | |||
admin@10.10.10.10's password: | |||
Last login: Fri Feb 20 16:42:04 2019 from 10.242.100.1 | |||
</pre> | |||
* Type | |||
<pre>poweroff_cluster</pre> | |||
if this command doesnt work use: | |||
<pre>cluster poweroff_cluster</pre> | |||
Example output: | |||
<pre style="color: silver; background: black; width: 800px"> | |||
VRSTW4xxxx >> poweroff_cluster | |||
Warning: This operation will power off the entire cluster, any running jobs will be terminated!!! | |||
Type 'yes' to continue: | |||
4. Specify ‘yes’ at the prompt and then press ENTER to confirm the shutdown command. | |||
Type 'yes' to continue: yes | |||
Press Enter to shut down the local node | |||
VRSTW4xxxx >> | |||
Broadcast message from admin@VRSTW4xxxx | |||
(/dev/pts/2) at 17:42 ... | |||
The system is going down for power off NOW! | |||
Connection to 10.10.10.10 closed by remote host. | |||
Connection to 10.10.10.10 closed. | |||
</pre> | |||
==Useful Commands== | ==Useful Commands== | ||
Line 69: | Line 130: | ||
<pre>$Cred = Get-Credential</pre> | <pre>$Cred = Get-Credential</pre> | ||
<pre>Connect-Rubrik -Server x.x.x.x -Credential $Cred</pre> | <pre>Connect-Rubrik -Server x.x.x.x -Credential $Cred</pre> | ||
===Editing Enable storage array integration on all virtual machines=== | ===Editing Enable storage array integration on all virtual machines=== | ||
Line 80: | Line 142: | ||
Depending on how many virtual machines you are backing up this may take some time. | Depending on how many virtual machines you are backing up this may take some time. | ||
===Change/set sla of a virtual machine=== | ===Change/set sla of a virtual machine=== | ||
<pre>Get-RubrikVM -name <vm-name-here> | Protect-RubrikVM -SLA "<sla-name-here>"</pre> | <pre>Get-RubrikVM -name <vm-name-here> | Protect-RubrikVM -SLA "<sla-name-here>"</pre> | ||
===List all machines in an SLA group=== | ===List all machines in an SLA group=== | ||
<pre>Get-RubrikVM -SLA "<sla-name-here>" | Select -ExpandProperty name</pre> | <pre>Get-RubrikVM -SLA "<sla-name-here>" | Select -ExpandProperty name</pre> | ||
===Rubrik check for unassigned servers=== | |||
<pre>Get-RubrikVM -SLAAssignment "Unassigned" | Select -ExpandProperty name</pre> | |||
Example output: | |||
<pre style="color: white; background: #012456; width: 800px"> | |||
Server01 | |||
Domain12 | |||
FileServer02 | |||
</pre> | |||
==Adding more disks to Rubrik Edge (virtual Rubrik) on vmWare== | |||
Disks being added should be the same size as the original also it cannot exceed 30tb in total, however I have added disks of different sizes and it does work but probably not supported by Rubrik. | |||
* Shut down Rubrik Edge. | |||
* Launch vSphere Client or vSphere Web Client, and log in to the vCenter Server. | |||
* Open Manage > VM Hardware > Edit > New device > New Hard Disk. | |||
* Enter a size for the new hard disk. The size must match the original data disk size. | |||
* Click Add. | |||
* In the Edit Settings view, expand the ‘New Hard Disk’ row. | |||
* Set Disk Provisioning to ‘Thick provision lazy zeroed’ | |||
* Set Virtual Device Node to ‘SCSI controller’. | |||
* Select the highest SCSI controller number available. | |||
* Click OK to save the settings. | |||
* Power on Rubrik Edge. | |||
* Log in to the web UI for Rubrik Edge. | |||
* From the web UI Dashboard, click System. | |||
* In the System panel, click the name of the node. | |||
* In the HDD Status pane of the node management pane, click Set up disk. | |||
* Click Submit. | |||
It may take some time before you see the free disk space. | |||
[[Category:rubrik]] | [[Category:rubrik]] | ||
[[Category:backup]] | [[Category:backup]] | ||
<comments /> |
Latest revision as of 09:44, 8 June 2022
Rubrik
Setup
Rubrik install and setup process
Here are the steps for installing and setting up Rubrik backup devices.
- Go to the back of the Rubrik and you should see a serial number sticker with something along the lines of:
RVHM123456789.local
Make a note of this.
- Connect your laptop to the management port on the back of the Rubrik and wait for your laptop to get a DHCP address
- Once you have an IP address open a browser and browse to:
https://RVHM123456789.local
- This should take you to a Rubik setup page.
- You will have a "Welcome to Rubrik page" asking you for your email address and password. Enter these details and continue.
- The Rubrik will now search for other Rubrik nodes on the LAN.
- You will now see a screen asking you to setup IP information. First of all focus on the top section which will be the generic settings, i.e. cluster name, DNS, Gateway, subnet, ntp etc etc
- Now move down to the nodes section, you now need to add a management IP and a Idrac/ilo IP for each Rubrik node it has found. At this stage you can specify a VLAN for data traffic only, specify this if required.
- You will then get a "Setting up system" message followed by a "Setting up encryption" message, this will take some time.
- Once complete you should be able to browse to any of the management IP's and login using "admin" and the password you set at the beginning.
Once you have logged in you will need to:
- Add your vcenter to the Rubrik
- Assign a floating IP (optional)
- Add your storage array if it supports Rubrik storage array integration
- Add LDAP for domain login
- Install the Rubrik backup agent on any physical servers you may wish to backup
- Create some SLA groups with the backup retention etc that meets your needs
Factory reset entire Rubrik
Should you need to reset your Rubrik you can follow the steps below.
WARNING: THIS WILL COMPLETELY WIPE YOUR RUBRIK DEVICE AND THE BACKUPS STORED ON IT.!
- Using Putty SSH to the Rubrik node you wish to factory reset.
- Type:
reset
and press enter
- You will them be prompted with the below, if you still wish to continue type "yes" and press enter:
Warning: This operation will erase all the data on the filesystem!!! Type 'yes' to continue: yes
- You will then see a lot of messages similar to the below:
2019-07-11T12:01:13+0000 INFO <12973.MainThread> [reset_node.pyc] Starting sdreset 2019-07-11T12:01:13+0000 INFO <12973.MainThread> [reset_node.pyc] Running sdreset_internal 2019-07-11T12:01:20+0000 INFO <12973.MainThread> [reset_node.pyc] 2019-07-11T12:01:20+0000 INFO <12976.main> [sdreset_internal.sh] svscan is already running with pid 18986 2019-07-11T12:01:20+0000 INFO <12973.MainThread> [reset_node.pyc] 2019-07-11T12:01:20+0000 INFO <12976.main> [sdreset_internal.sh] Waiting for svc lock
Let these continue, you are waiting until you see the below message:
2019-07-11T12:03:43+0000 INFO <12973.MainThread> [reset_node.pyc] Ran sdreset successfully RVM123456789 >>
Once you see this message you can reboot the Rubrik and start the setup process again, obviously if you have more than one Rubrik node you will need to repeat the above for each node.
Restarting a Rubrik cluster
- SSH To any of the Rubrik nodes in the cluster using the admin account
Example output:
ssh admin@10.10.10.10
- Enter admin password to access the Rubrik CLI prompt
Example output:
~ host$ ssh admin@10.10.10.10 admin@10.10.10.10's password: Last login: Fri Feb 20 16:42:04 2019 from 10.242.100.1
- Type
cluster reboot cluster
Shutting down a Rubrik cluster
- SSH To any of the Rubrik nodes in the cluster using the admin account
Example output:
ssh admin@10.10.10.10
- Enter admin password to access the Rubrik CLI prompt
Example output:
~ host$ ssh admin@10.10.10.10 admin@10.10.10.10's password: Last login: Fri Feb 20 16:42:04 2019 from 10.242.100.1
- Type
poweroff_cluster
if this command doesnt work use:
cluster poweroff_cluster
Example output:
VRSTW4xxxx >> poweroff_cluster Warning: This operation will power off the entire cluster, any running jobs will be terminated!!! Type 'yes' to continue: 4. Specify ‘yes’ at the prompt and then press ENTER to confirm the shutdown command. Type 'yes' to continue: yes Press Enter to shut down the local node VRSTW4xxxx >> Broadcast message from admin@VRSTW4xxxx (/dev/pts/2) at 17:42 ... The system is going down for power off NOW! Connection to 10.10.10.10 closed by remote host. Connection to 10.10.10.10 closed.
Useful Commands
Connecting to Rubrik via Powershell
- Download and install the Rubrik PowerShell addon:
https://www.rubrik.com/blog/get-started-rubrik-powershell-module/
- Once downloaded, open PowerShell and connect to your Rubrik:
$Cred = Get-Credential
Connect-Rubrik -Server x.x.x.x -Credential $Cred
Editing Enable storage array integration on all virtual machines
Connect to the Rubrik run the command below to enable storage array integration on all virtual machines:
Get-RubrikVM | Set-RubrikVM -UseArrayIntegration 1
- If you wish to disable storage array integration on all virtual machine run the following command:
Get-RubrikVM | Set-RubrikVM -UseArrayIntegration 0
Depending on how many virtual machines you are backing up this may take some time.
Change/set sla of a virtual machine
Get-RubrikVM -name <vm-name-here> | Protect-RubrikVM -SLA "<sla-name-here>"
List all machines in an SLA group
Get-RubrikVM -SLA "<sla-name-here>" | Select -ExpandProperty name
Rubrik check for unassigned servers
Get-RubrikVM -SLAAssignment "Unassigned" | Select -ExpandProperty name
Example output:
Server01 Domain12 FileServer02
Adding more disks to Rubrik Edge (virtual Rubrik) on vmWare
Disks being added should be the same size as the original also it cannot exceed 30tb in total, however I have added disks of different sizes and it does work but probably not supported by Rubrik.
- Shut down Rubrik Edge.
- Launch vSphere Client or vSphere Web Client, and log in to the vCenter Server.
- Open Manage > VM Hardware > Edit > New device > New Hard Disk.
- Enter a size for the new hard disk. The size must match the original data disk size.
- Click Add.
- In the Edit Settings view, expand the ‘New Hard Disk’ row.
- Set Disk Provisioning to ‘Thick provision lazy zeroed’
- Set Virtual Device Node to ‘SCSI controller’.
- Select the highest SCSI controller number available.
- Click OK to save the settings.
- Power on Rubrik Edge.
- Log in to the web UI for Rubrik Edge.
- From the web UI Dashboard, click System.
- In the System panel, click the name of the node.
- In the HDD Status pane of the node management pane, click Set up disk.
- Click Submit.
It may take some time before you see the free disk space. <comments />