Hetzner is a hosting company in Germany where you can rent dedicated root servers per month. Using their KVM-over-IP setup, it is possible to install operating systems that are not available by default, such as XenServer by Citrix. With the machine, you get four public IP addresses. One of these addresses is given to you when the machine is assigned to you, the other three are assigned to you on request.

There is a problem with the public IP addresses Hetzner gives you. Within the Hetzner network, there is a hard connection between the MAC address of your machine and the IP addresses you have been given. This is a problem for virtual machines that are bridged onto the network by the host machine. These virtual machines have their own MAC address and the Hetzner network will drop packets from these unknown MAC addresses.

There is a solution to this problem: have the host machine route IP packets from the virtual machines to the network and vice versa. We will use the following addresses in the example below:

IP addresses	188.40.109.204 (host), 188.40.109.250 (VM)
Netmask	255.255.255.192
Gateway	188.40.109.193 (host)
DNS	213.133.100.100

We start with the configuration of the host machine (running XenServer). The first file is the configuration file of eth0: /etc/sysconfig/network-scripts/ifcfg-eth0

XEMANAGED=yes
DEVICE=eth0
ONBOOT=no
TYPE=Ethernet
HWADDR=40:61:86:be:ce:88 (replace with MAC address of host)
BRIDGE=xenbr0

Notice that this file does not contain any IP configuration. The second file is the configuration file of xenbr0: /etc/sysconfig/network-scripts/ifcfg-xenbr0

XEMANAGED=yes
DEVICE=xenbr0
ONBOOT=no
TYPE=Bridge
DELAY=0
STP=off
PIFDEV=eth0
BOOTPROTO=none
IPADDR=188.40.109.204 (replace with IP address of host)
NETMASK=255.255.255.192
GATEWAY=188.40.109.193 (replace with gateway of host)
DNS1=213.133.100.100
DNS2=213.133.99.99
DNS3=213.133.98.98

Now we need to enable IP forwarding on the host machine. We start with the sysctl configuration file: /etc/sysctl.conf

net.ipv4.ip_forward=1
net.ipv4.conf.all.send_redirects=0
net.ipv4.conf.default.send_redirects=0
net.ipv4.conf.lo.send_redirects=0
net.ipv4.conf.xenbr0.send_redirects=0

The first line tells the machine to perform IP forwarding. The four lines after that tell the machine to disable sending ICMP redirects. The last file we need to edit is the firewall configuration file: /etc/sysconfig/iptables. Add this text below the line -A RH-Firewall-1-INPUT -i lo -j ACCEPT:

-A RH-Firewall-1-INPUT -i xenbr0 -o xenbr0 -j ACCEPT

Now reboot the machine and continue with the IP configuration of the virtual machine running on XenServer. There is only one file we need to edit here, which is the configuration file of eth0: /etc/sysconfig/network-scripts/ifcfg-eth0

DEVICE=eth0
BOOTPROTO=none
ONBOOT=yes
HWADDR=8e:35:1e:3b:12:aa (replace with MAC address of VM)
IPADDR=188.40.109.250 (replace with IP address of VM)
NETMASK=255.255.255.192
GATEWAY=188.40.109.204 (replace with IP address of host)

The gateway in this configuration is crucial: it needs to be the IP address of the host itself, not the gateway of the host.

Source:-http://www.jansipke.nl

When you boot Novell server, you may encounter the following error message during the bootup process:

“Volume does not exist”

After getting this error message, when you run vrepair to check for any disk data structures related problems, the process does not complete and no message gets displayed.

This problem occurs with every Novell volume. In such critical situations, the volume becomes completely inaccessible. Your precious data stored on a particular Novell volume could not be accessed and you experience serious data loss due to such system behavior. To revive the lost data in the Novell server hard drive, you should opt for novell recovery software.

Grounds of the issue

This behavior might be the possible result of damaged, corrupted or lost hard drive logical structure like file system. A Novell volume becomes inaccessible, unmountable or invisible mainly in case of file system corruption.

A file system may get damaged due to a number of reasons such as user errors, extensive fragmentation, virus infection etc. Due to file system corruption, operating system could not find the necessary information about the affected volume and thus won’t be able to access it.

After the occurrence of such errors, the ultimate result would be the loss of your mission critical data. Novell server stores a massive amount of significant business data as employee databases, project related information, knowledge resources etc. Loss of such critical information could be really daunting and it can bring your current work routine to a standstill.

In such severe data loss situations, you need to fix the file system corruption and retrieve your data at the earliest. The delay in recovery process may harm in terms of decreased revenue, customer faith and market value. Also, you should ensure that you do not reuse the affected disk to ensure that it does not get overwritten. Once a disk is overwritten or erased using proper erasure techniques, the data recovery becomes impossible.

The only solution to fix file system corruption is to format the hard drive and go for clean operating system reinstall. By formatting the drive you remove all the as related to the file system. It will lead to an error free hard drive that will be free from logical errors only, as hardware errors can also cause data loss and storage media malfunction.

Although, formatting a hard drive is helpful for fixing logical errors, but it also has a downside. The format operation erases all the data from the selected volume (in case of a single volume, whole hard drive). It causes complete data loss. So, you need to go for high-quality Novell Recovery solutions to reclaim your lost data stored in the server.

At this point of time, you need to perform novell partition recovery to recover your lost novell volumes and data from them. Novell server and workstation level recovery is potential through novell recovery software. Such tools are powerful and easy-to-use third party utilities, which perform complete and smooth Novell Recovery in all possible scenarios of data loss.

Stellar Phoenix Novell data recovery suite is the most promising novell recovery solution for all your Novell data loss problems. You can choose from Stellar Phoenix Novell NWFS Data Recovery or Stellar Phoenix Novell NSS Data Recovery software. The software supports NWFS (Netware File System) and NSS (Novell Storage System) file systems.

Author:-K MADHAV

Exchange Server provides an inbuilt utility (Eseutil) to fix the database corruption problems. But sometimes when you perform hard recovery, it may not complete and you need to carry out EDB recoveryto sort out the problem.

While performing hard database recovery, you may encounter -1019 error messages. The error message shows that EDB file is severely corrupted and it can not be repaired. After these errors, the recovery process gets halted and last transaction log file which is replayed, gets modified and damaged.

In this case, when you see the Application Event Log of Exchange Server, you may find the underwritten events:

Event ID: 0 Source: ESE97 Type: Error Category: Performance Description: (252) Unexpected Win32 error: 0x3E6

Event ID: 122 Source: ESE97 Type: Error Category: Logging/Recovery Description: (252) Unable to read the log. Error -1022.

Event Id: 0 Source: ESE97 Type: Error Category: Logging/Recovery Description: (252) -1019

After these error messages, your important data in the Exchange Server becomes inaccessible and you have to figure out the cause of this issue and use EDB repair solutions to reclaim the lost data.

Grounds of this issue

You may encounter these error messages due to EDB file corruption. Such corruption could be the possible result of improper server shutdown, file header corruption, application malfunction, virus infection and other similar reasons. In all these situations, your data becomes inaccessible and unusable, thus you need to sort out this problem to reclaim your inaccessible data.

How to fix this problem

You can overcome the corruption scenarios by repairing the corrupted EDB file using EDB recovery software. These are third party applications that are uniquely designed to thoroughly scan the corrupted EDB file and extract inaccessible and lost data from it.

These software come equipped with interactive user interface and does not demand sound technical knowledge to achieve efficient repair and restoration of data. They are able to recover all EDB objects including e-mails, notes, contacts, journals, calendar entries and tasks.

With read-only design, these software carry out safe and original EDB repair in almost all the EDB corruption scenarios. To ensure safe, quick and effective recovery, you should opt for result-oriented and time-tested exchange data recovery software.

Stellar Phoenix mailbox exchange recovery is the most reliable EDB recovery application for all software caused Exchange Server corruption. The software supports Microsoft Exchange Server 2003, 2000 and 5.5. It is compatible with Microsoft Windows XP, 2003 and 2000.

Author:-K MADHAV