Advance work

Available in Classic and VPC

Advance work describes what to do before creating resources.

The cases where you need to do some advance works and the advance work accordingly are as follows:

• The case where you use Windows server to create resources: Windows setup
• The case where you cannot use the root/Administrator accounts to install the agent: set up server ID
• The case where you use the server created by the image of the server with the agent installed or the server with the previously installed agent: end backup process and delete related directory

You can create resources immediately without going through other processes when you are not under any cases mentioned above. For more information about resource creation, see resource creation.

Windows setup

To create resources through Windows servers, follow these steps:

• Setting a fixed port for WMI (mandatory)
• Enable remote registry service (mandatory)
• Setting ACG (mandatory)
• Enable ADMIN$ shares (optional)

Setting a fixed port for WMI (mandatory)

To set a Windows Management Instrumentation (WMI) fixed port 24158, follow these steps:

1. Press [Windows] + [R], and enable the Run command.

2. Type cmd and [Ctrl] + [Shift] + [Enter] together.

   • The cmd window with the administrator authority opens.

3. Enter the following commands and enable the WMI service automatically:

   # winmgmt -standalonehost
   

4. Enter the following commands and stop the WMI service and restart it.

   # net stop Windows Management Instrumentation
   # net start Windows Management Instrumentation
   

5. Enter the following commands and add the outbound rule for Windows firewall.

   // the rule to allow for the access to the port 24158
   # netsh firewall add portopening TCP 24158 WMIFixedPort
   

   <example>
   

Enable remote registry service (mandatory)

To enable remote registry service, follow these steps:

1. Press [Windows] + [R], and enable the Run command.
2. Type control and press [Enter].
3. When Control Panel window appears, click System and Security > Administrative Tools > Services in order and enable Services.
4. Double-click Remote Registry to open Remote Registry Properties (Local Computer) window.
   • Also, you can click Remote Registry with the right button on the mouse and then click Properties.
5. Select Automatic from Startup type dropdown menu.
6. Click the [OK] button.
7. Click in the top of Services page to enable Services.
   
   • Remote Registry services are enabled.

Setting ACG (mandatory)

When you use Backup services in Classic, see setting ACG and set up the ACG rule as follows:

• Protocol: TCP
• Access source (IP range): 10.0.0.0/8
• Allowed ports: 135, 139, 445, and 24158

Enable ADMIN$ shares (optional)

While managing the server remotely, view whether ADMIN$ shares as the currently used resource are enabled and enable it.

Viewing whether ADMIN$ shares are enabled

To view whether ADMIN$ shares are enabled, follow these steps:

1. Press [Windows] + [R], and enable the Run command.
2. Type cmd and [Ctrl] + [Shift] + [Enter] together.
   • The cmd window with the administrator authority opens.
3. Enable net share to view whether ADMIN$ shares are enabled.
   

Enable ADMIN$ shares

To enable ADMIN$ shares, follow these steps:

1. Press [Windows] + [R], and enable the Run command.
2. Type regedit and press [Enter].
   • Registry Editor opens.
3. Move to the HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanServer\Parameters route.
4. Click Registry Editor window with the right button on the mouse and click New > DWORD (32-bit) Value in order.
5. Type AutoShareServer and press [Enter].
   • Add AutoShareWks in the same way.
6. Double-click AutoShareServer.
   • Also, you can click AutoShareServer with the right button on the mouse and then click Modify.
7. When the popup window comes up, enter 1 into Value data and click the [OK] button.
   • Set up AutoShareWKS in the same way.
     
8. Reboot the server.

Set up server ID

To install the agent through servers, use the root account for Linux and the Administrator account for Windows. When you cannot use the root/Administrator accounts, create an account for the agent installation and assign the root/Administrator authority to use it. However, after the completion of the agent installation, remove the root/Administrator authority from the account.

Linux

To create an account for the agent installation and assign the root authority to the account, follow these steps:

1. Access the server with the root account.

   • See server access (VPC) or server access (Classic) based on the environment you are using from NAVER Cloud Platform.

2. To create an account for agent installation, enter the following commands:

   • When you have an existing account for the agent installation, you do not need to create an account.

   adduser {account name}
   // example
   // adduser test01
   

3. Run the following commands.

   vi /etc/sudoers
   

4. Enter the content below to assign the root authority to the account for agent installation.

   "The name of account for the agent installation" ALL=(ALL) NOPASSWD: ALL
   

   <example>

   [root@backup-linux01 ~]# vi /etc/sudoers
   ## Allow root to run any commands anywhere
   root    ALL=(ALL)       ALL
   test01  ALL=(ALL) NOPASSWD:   ALL
   

5. After the completion of agent installation, delete the content that was entered into at the fourth step to remove the root authority.

Windows

To assign the Administrator authority to the account for agent installation, follow these steps:

1. Access the server.
   • See server access (VPC) or server access (Classic) based on the environment you are using from NAVER Cloud Platform.
2. Press [Windows] + [R], and enable the Run command.
3. Type netplwiz and Press [Enter].
4. When the popup window comes up, click the account for the agent installation and then click [Properties] afterward.
   • When you do not have any accounts or agent installation, click [Add] button to create a new account.
5. When the popup window of Properties comes up, click the [Group Membership] tab.
6. Select the Administrator and click the [OK] button.
   • After the completion of the agent installation, remove the account or change the authority status of the account into Standard User.

End backup process and delete related directory

When the server you will use to create resources is under the category below, you have to end the currently running backup process and delete the directory related to the agent installed in the server.

• The server created by the image of the server with the agent installed
• A server that previously had installed and therefore still agent-related files

Before creating resources, perform the advance work according to the OS of the server you will use to create resources.

Linux

To create resources by reusing Linux server, follow these steps:

1. Access the Linux server you will use to create resources.

   • See server access (VPC) or server access (Classic) based on the environment you are using from NAVER Cloud Platform.

2. Type the following commands with the root authority and end the backup process installed in the server:

   • When the commands do not work, exit the backup process by following the fourth step.

   commvault stop -all ()
   Redirecting stopping service for Instance001 to systemd ...
   Running "systemctl stop commvault.Instance001.service" ...
   Stopping Commvault services for Instance001 ...
   All services stopped.
   

3. Type the following commands to view the leftover backup processes in the server:

   • Backup processes you have to view: cvlaunchd, cvd, cvfwd, and ClMgrS

   ps -ef | grep -i "cvlaunchd|cvd|cvfwd|ClMgrS"
   

4. Use kill commands to exit the backup process.

   • When the commands do not work at the first step or the backup process does not end after the commands input, follow these steps:

5. View the following route and delete the directory related to the agent:

   • Default route: folders starting with /opt and commvault
     • <example> /opt/commvault, /opt/commvault1, /opt/commvault2...
   • Logging route: folders starting with /var/log and commvault
     • <example> /var/log/commvault, /var/log/commvault1, /var/log/commvault2...
   • Registry route: /etc/CommVaultRegistry (single folder)
   Note

   When the agent has not been installed in the default route, delete the home directory of the account used for installation.

   <example>

When the agent is installed in the ncloud directory, its location is under /home/ncloud/ and the route is as follows.

• Default route: /home/ncloud/commvault
• Logging route: /home/ncloud/var/log/commvault
• Registry route: /home/ncloud/CommVaultRegistry

:::

Windows

When creating resources by reusing Windows server, the required advance works are as follows:

1. Access the Windows server you will use to create resources.
   • See server access (VPC) or server access (Classic) based on the environment you are using from NAVER Cloud Platform.
2. Search for Commvault Process Manager at the search bar and run Process Manager.
3. Click [Services] tab.
4. Click All Services from the tree menu and then click .
   • Also, you can click All Services with the right button on the mouse and then click Stop.
5. When you have ongoing backup processes left, end them separately.
   • Click leftover backup processes, and click or the right button on the mouth to click Stop.
6. Search for Add or remove programs at the task bar and run it.
7. After clicking Commvault ContrntStore, click [Uninstall] button.
8. After viewing the popup window, click [Uninstall] button.
9. When the COMMVAULT popup window comes up, click and select Uninstall all packages in the instance and press [Enter].
10. View the content you want to delete, and press [Enter].