---
title: "Preliminary tasks"
slug: "backup-advance"
updated: 2026-09-17T09:18:06Z
published: 2026-09-17T09:18:06Z
canonical: "guide.ncloud-docs.com/backup-advance"
stale: true
---

> ## Documentation Index
> Fetch the complete documentation index at: https://guide.ncloud-docs.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Preliminary tasks

Available in Classic and VPC

You may need to perform certain preliminary tasks before creating resources.

The cases where you need to perform preliminary tasks and the tasks that should be performed depending on the circumstances are as follows:

- When you use Windows server to create resources: [Set Windows](/docs/en/backup-advance#Windows%EC%84%A4%EC%A0%95)
- When you cannot use the root/Administrator accounts to install the agent: [Set server ID](/docs/en/backup-advance#%EC%84%9C%EB%B2%84%EC%95%84%EC%9D%B4%EB%94%94%EC%84%A4%EC%A0%95)
- When you use the server created from a server image with the agent installed or the server with the previously installed agent: [End backup process and delete related directory](/docs/en/backup-advance#%EB%B0%B1%EC%97%85%ED%94%84%EB%A1%9C%EC%84%B8%EC%8A%A4%EC%A2%85%EB%A3%8C%EB%B0%8F%EA%B4%80%EB%A0%A8%EB%94%94%EB%A0%89%ED%84%B0%EB%A6%AC%EC%82%AD%EC%A0%9C)

If the above cases do not apply, you can create the resource immediately without performing any additional tasks. For more information about how to create a resource, see [Create resource](/docs/en/backup-backupresource#%EB%A6%AC%EC%86%8C%EC%8A%A4%EC%83%9D%EC%84%B1).

## Set Windows

To create resources on Windows servers, perform the following tasks:

- [Set fixed port for WMI (required)](/docs/en/backup-advance#WMI%EA%B3%A0%EC%A0%95%ED%8F%AC%ED%8A%B8%EC%84%A4%EC%A0%95%ED%95%84%EC%88%98)
- [Enable Remote Registry (required)](/docs/en/backup-advance#RemoteRegistry%ED%99%9C%EC%84%B1%ED%99%94%ED%95%84%EC%88%98)
- [Set ACG rule (required)](/docs/en/backup-advance#ACG%EA%B7%9C%EC%B9%99%EC%84%A4%EC%A0%95%ED%95%84%EC%88%98)
- [Enable ADMIN$ share (required)](/docs/en/backup-advance#ADMIN%EA%B3%B5%EC%9C%A0%ED%99%9C%EC%84%B1%ED%99%94%ED%95%84%EC%88%98)

### Set fixed port for WMI (required)

To set a Windows Management Instrumentation (WMI) fixed port 24158:

1. Press **[Windows]** + **[R]** keys, and enable the Run command.
2. Enter cmd and press **[Ctrl]** + **[Shift]** + **[Enter]** keys.
  - The cmd window opens with administrator permissions.
3. Enter the following commands and run 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:

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

Example:  

![resource_agent_1](https://cdn.document360.io/6998976f-9d95-4df8-b847-d375892b92c2/Images/Documentation/resource_agent_1.png?sv=2026-02-06&spr=https&st=2026-10-27T19%3A56%3A10Z&se=2026-10-27T20%3A56%3A10Z&sr=c&sp=r&sig=yNpy8jv%2FCSw51POVD9%2FxhUZVhNyWpc8nMvp5Mn1dwyE%3D)

### Enable Remote Registry (required)

To enable Remote Registry:

1. Press **[Windows]** + **[R]** keys, and enable the Run command.
2. Enter control and press the **[Enter]** key.
3. When the Control Panel window appears, navigate to **System and Security > Administrative Tools > Services** to run Services.
4. Double-click **Remote Registry** to open the Remote Registry Properties (Local Computer) window.
  - You can also right-click **Remote Registry** and click **Properties**.
5. Select **Automatic** from the **Startup type** dropdown menu.
6. Click **[OK]**.
7. Click ![i-backup_running](https://cdn.document360.io/6998976f-9d95-4df8-b847-d375892b92c2/Images/Documentation/i-backup_running.png?sv=2026-02-06&spr=https&st=2026-10-27T19%3A56%3A10Z&se=2026-10-27T20%3A56%3A10Z&sr=c&sp=r&sig=yNpy8jv%2FCSw51POVD9%2FxhUZVhNyWpc8nMvp5Mn1dwyE%3D) at the top of Services page to run Services.  

![resource_agent_4](https://cdn.document360.io/6998976f-9d95-4df8-b847-d375892b92c2/Images/Documentation/resource_agent_4.png?sv=2026-02-06&spr=https&st=2026-10-27T19%3A56%3A10Z&se=2026-10-27T20%3A56%3A10Z&sr=c&sp=r&sig=yNpy8jv%2FCSw51POVD9%2FxhUZVhNyWpc8nMvp5Mn1dwyE%3D)
  - Remote Registry service is enabled.

              Note

              

To prevent Remote Registry from being disabled again, edit the registry as follows:

1. Press **[Windows]** + **[R]** keys, and enable the Run command.
2. Enter regedit and press the **[Enter]** key.
  - Registry Editor opens.
3. Go to the `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\RemoteRegistry` path.
4. Double-click **DisableIdleStop**.
  - You can also right-click **DisableIdleStop** and click **Modify**.
5. When the popup window appears, enter 1 into **Value Data** and click **[OK]**.

### Set ACG rule (required)

When you use Backup services in Classic, see [Set ACG](/docs/en/server-acg-classic#acg%EC%84%A4%EC%A0%95) and set up the ACG rule as follows: ![backup-advance_acg_ko](https://cdn.document360.io/6998976f-9d95-4df8-b847-d375892b92c2/Images/Documentation/backup-advance_acg_en.png?sv=2026-02-06&spr=https&st=2026-10-27T19%3A56%3A10Z&se=2026-10-27T20%3A56%3A10Z&sr=c&sp=r&sig=yNpy8jv%2FCSw51POVD9%2FxhUZVhNyWpc8nMvp5Mn1dwyE%3D)

- Protocol: TCP
- Access source (IP range): 10.0.0.0/8
- Allowed port: 135, 139, 445, 24158

### Enable ADMIN$ share (required)

While managing the server remotely, view whether ADMIN$ share, the currently used resource, is enabled and enable it.

**View whether ADMIN$ share is enabled**

To view whether ADMIN$ share is enabled:

1. Press **[Windows]** + **[R]** keys, and enable the Run command.
2. Enter cmd and press **[Ctrl]** + **[Shift]** + **[Enter]** keys.
  - The cmd window opens with administrator permissions.
3. Run `net share` to view whether ADMIN$ share is enabled.  

![resource_agent_2](https://cdn.document360.io/6998976f-9d95-4df8-b847-d375892b92c2/Images/Documentation/resource_agent_2.png?sv=2026-02-06&spr=https&st=2026-10-27T19%3A56%3A10Z&se=2026-10-27T20%3A56%3A10Z&sr=c&sp=r&sig=yNpy8jv%2FCSw51POVD9%2FxhUZVhNyWpc8nMvp5Mn1dwyE%3D)

**Enable ADMIN$ share**

To enable ADMIN$ share:

1. Press **[Windows]** + **[R]** keys, and enable the Run command.
2. Enter regedit and press the **[Enter]** key.
  - Registry Editor opens.
3. Go to the `HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanServer\Parameters` path.
4. Right-click Registry Editor window and navigate to **New > DWORD (32-bit) Value**.
5. Enter AutoShareServer and press the **[Enter]** key.
  - Add AutoShareWks in the same way.
6. Double-click **AutoShareServer**.
  - You can also right-click **AutoShareServer** and click **Modify**.
7. When the popup window appears, enter 1 into **Value data** and click **[OK]**.
  - Set **AutoShareWKS** in the same way.  

![resource_agent_3](https://cdn.document360.io/6998976f-9d95-4df8-b847-d375892b92c2/Images/Documentation/resource_agent_3.png?sv=2026-02-06&spr=https&st=2026-10-27T19%3A56%3A10Z&se=2026-10-27T20%3A56%3A10Z&sr=c&sp=r&sig=yNpy8jv%2FCSw51POVD9%2FxhUZVhNyWpc8nMvp5Mn1dwyE%3D)
8. Reboot the server.

## Set server ID

To install the agent on 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 permissions to use it. However, after the completion of the agent installation, remove the root/Administrator permissions from the account.

### Linux

To create an account for the agent installation and assign the root permissions to the account:

1. Access the server with the root account.
  - See [Access server (VPC)](/docs/en/server-access-vpc#linux%EC%84%9C%EB%B2%84%EC%A0%91%EC%86%8D) or [Access server (Classic)](/docs/en/server-access-classic#linux%EC%84%9C%EB%B2%84%EC%A0%91%EC%86%8D) depending on the environment you are using on NAVER Cloud Platform.
2. To create an account for agent installation, enter the following commands:

```
adduser {account name}
Example:
// adduser test01
```
  - When you have an existing account for the agent installation, you do not need to create an account.
3. Run the following commands:

```
vi /etc/sudoers
```
4. Enter the content below to assign the root permissions 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 at step 4 to remove the root permissions.

### Windows

To assign the administrator permissions to the account for agent installation:

1. Access the server.
  - See [Access server (VPC)](/docs/en/server-access-vpc#windows%EC%84%9C%EB%B2%84%EC%A0%91%EC%86%8D) or [Access server (Classic)](/docs/en/server-access-classic#windows%EC%84%9C%EB%B2%84%EC%A0%91%EC%86%8D) depending on the environment you are using on NAVER Cloud Platform.
2. Press **[Windows]** + **[R]** keys, and enable the Run command.
3. Enter netplwiz and press the **[Enter]** key.
4. When the popup window appears, click the account for the agent installation and click **[Properties]**.
  - If you do not have any accounts for agent installation, click **[Add]** to create a new account.
5. When the popup window of Properties appears, click the **[Group Membership]** tab.
6. Select **Administrator** and click **[OK]**.
  - After the completion of the agent installation, delete the account or change the permissions of the account back to **Standard user**.

## End backup process and delete related directory

If the server intended for resource creation meets all of the following conditions, you must end the currently running backup process and delete the directory related to the agent stored on the server:

- A server created from a server image with the agent installed.
- A server that has a history of agent installation and still contains agent-related files.

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

### Linux

When you create the resource in the Linux server with the existing backup agent installed, perform the following tasks:

1. Access the Linux server you will use to create resources.
  - See [Access server (VPC)](/docs/en/server-access-vpc#linux%EC%84%9C%EB%B2%84%EC%A0%91%EC%86%8D) or [Access server (Classic)](/docs/en/server-access-classic#linux%EC%84%9C%EB%B2%84%EC%A0%91%EC%86%8D) depending on the environment you are using on NAVER Cloud Platform.
2. Enter the following commands with the root permissions and end the backup process installed on the server:

```
commvault stop -all
Redirecting stopping service for Instance001 to systemd ...
Running "systemctl stop commvault.Instance001.service" ...
Stopping Commvault services for Instance001 ...
All services stopped.
```
  - When the commands do not work, exit the backup process by following step 4.
3. Enter the following commands to check for any remaining backup processes on the server:

```
ps -ef | grep -i "cvlaunchd|cvd|cvfwd|ClMgrS"
```
  - Backup process you need to check: cvlaunchd, cvd, cvfwd, ClMgrS
4. Use kill commands to exit the backup process.
  - When the commands do not work at step 1 or the backup process continues running afterward, perform the above step.
5. View the following path and delete the directory related to the agent:

              Note

              

When the agent has not been installed in the default path, 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 path is as follows:

  - Default path: /home/ncloud/commvault
  - Log path: /home/ncloud/var/log/commvault
  - Registry path: /home/ncloud/CommVaultRegistry
  - Default path: Folders starting with commvault in /opt
    - Example: /opt/commvault, /opt/commvault1, /opt/commvault2, etc.
  - Log path: Folders starting with commvault in /var/log
    - Example: //var/log/commvault, /var/log/commvault1, /var/log/commvault2, etc.
  - Registry path: Folders starting with /etc/CommVaultRegistry
    - Example: /etc/CommVaultRegistry, /etc/CommVaultRegistry1, /etc/CommVaultRegistry2, etc.

### Windows

When you create the resource on the Windows server with the existing backup agent installed, perform the following preliminary tasks:

              Caution

              

When deleting the directories related to the agent, you have to follow the procedure. If directories are deleted individually, they may not be completely removed, which can cause issues during resource creation.

1. Access the Windows server you will use to create resources.
  - See [Access server (VPC)](/docs/en/server-access-vpc#windows%EC%84%9C%EB%B2%84%EC%A0%91%EC%86%8D) or [Access server (Classic)](/docs/en/server-access-classic#windows%EC%84%9C%EB%B2%84%EC%A0%91%EC%86%8D) depending on the environment you are using on NAVER Cloud Platform.
2. Search for Commvault Process Manager in the taskbar and run Process Manager.
3. Click the **[Services]** tab.
4. Click **All Services** from the tree menu and click ![i-backup_stop](https://cdn.document360.io/6998976f-9d95-4df8-b847-d375892b92c2/Images/Documentation/i-backup_stop.png?sv=2026-02-06&spr=https&st=2026-10-27T19%3A56%3A10Z&se=2026-10-27T20%3A56%3A10Z&sr=c&sp=r&sig=yNpy8jv%2FCSw51POVD9%2FxhUZVhNyWpc8nMvp5Mn1dwyE%3D).
  - You can also right-click **All Services** and click **Stop**.
5. If there are any running backup processes, end them individually.
  - Click the backup process that is still running and click ![i-backup_stop](https://cdn.document360.io/6998976f-9d95-4df8-b847-d375892b92c2/Images/Documentation/i-backup_stop.png?sv=2026-02-06&spr=https&st=2026-10-27T19%3A56%3A10Z&se=2026-10-27T20%3A56%3A10Z&sr=c&sp=r&sig=yNpy8jv%2FCSw51POVD9%2FxhUZVhNyWpc8nMvp5Mn1dwyE%3D), or right-click the process and click **Stop**.
6. Search for Add or remove programs in the taskbar and run it.
7. After clicking **Commvault ContentStore**, click **[Uninstall]**.
8. After viewing the popup window, click **[Uninstall]**.
9. When the COMMVAULT popup window appears, click and select **Uninstall all packages in the instance** and press the **[Enter]** key.
10. View the content you want to delete and press the **[Enter]** key.