Create backup
cp -vr /vz/private/101 /vz/backup/
or
rsync -vaP /vz/private/101/ /vz/backup/101
Restore backup
tar -cvzf backup/101.tar.gz backup/101
scp backup/101.tar.gz host:
No. If you have not purchased additional, multiple IP addresses, you must not change the IP address. If you have purchased additional, multiple IP addresses for your account, you must exercise great care when you change an IP Address. In all cases, if you specify an IP address other than one which is assigned to you, your private server will not function. This is true of any other IP address than the those your private server was assigned at the time of provisioning. Even the address you might see displayed as unused IP address for the subnet of your private server might cause your private server to cease functioning. You will also be unable to see information about any aspect of the data traffic associated with any other IP address or VPS account. The Red Hat Enterprise Linux (RHEL) operating system supports a standard, UNIX/Linux command which enables you to see the status of network interfaces for your private server. Use the command for diagnostic and configuration tasks only. For example, if you issue the ifconfig command without any additional argument, all of the currently active interfaces are displayed. If you issue the command with the additional argument of –a, all of the interfaces, including inactive ones are displayed. Beyond the simple display of interfaces, the command includes additional argument s which enable you to specify an IP address for each network interface. If you do specify another address in error, the remedy is to log into your private server as root and use the ifconfig command to specify the correct IP address. For more details about the ifconfig command, refer to the RHEL operating system Man Pages
Not necessarily. Our provisioning system and ARIN requirements do not allow us to guarantee contiguous IP address blocks. When you purchase additional IP addresses, the next available addresses will automatically be assigned to your account/server.
By default, your account comes with a single dedicated IP address and is not enabled to have additional ones. However, you can purchase additional, multiple IP addresses and configure your account to utilize them.
Your private server account is designed with the goal to emulate the behavior of a dedicated Linux server in a shared environment. Because of this, account will operate and function as a dedicated Linux server does. One of the key limitations of account is that, because of the shared environment, the private server root user does not have the ability to modify kernel or hardware-related configurations. It is significant to note, however, that any of the system files not specifically changed by the private server administrator will continue to be maintained and updated by our staff. While many of the utilities are extended to your private server account, the multi-user environment makes application management slightly different.
The following examples describe practical applications of your private server account:
Your private server account represents a highly refined step in server virtualization technology. The technology partitions a single physical server into isolated virtual hosts. Each virtual host operates as a real, networked server.
You can install most Web–based applications, software, and utilities within the virtual host without any modifications. Widely tested and utilized open–source and commercial applications run successfully on your private server account. Applications and services do not have to be aware of private server technology. However, direct access to hardware is not available.
private server technology creates isolated, secure virtual environments on a single physical server (sometimes referred to as a sandbox). private server technology enables better server utilization and ensures applications do not conflict. your private server performs and executes your requests as a stand–alone server. You can reboot your private server account independently and configure root access, users, files, applications, system libraries, and configuration files. your private server behaves as a stand–alone Linux server. It uses standard startup scripts and software from multiple vendors. You can change any configuration file and you can install additional software. The file system and processes are fully isolated from any other account. your private server includes its own IP address. Traffic snooping is not possible. Resource management controls the amount of resources available to your server. This enables the quality of service to meet the service level agreements associated with your server.
The following examples of the features enhanced or added for Linux VPS:
Note: Many Java applications consume significant CPU and memory resources and may not be appropriate for use on a VPS.
Following are examples of how to use your private server: