booting from a cloned hard on a laptop
Hi, I cloned a linux CentOS hard drive of a server PC which included a LVM. Then I connected my external hard to the usb port of my laptop. I wanted to boot my laptop from the CentOS of external hard so i could use the programs which were installed on PC.So I restarted the laptop and press F11 button to select the desired OS. I can see the CentOS of external hard but when select it the following message appears: ========================================= Booting 'CentOS (2.6.18-308.24.1.e15)' root (hd0,0) Filesystem type is ext2fs, partition type 0x83 kernel /vmlinuz-2.6.18-308.24.1.e15 ro root=/dev/VolGroup00/LogVol00 rhgb quiet [Linux-bzImage, setup=0x1e00, size=0x1cf514] initrd /initrd 0 0x37e62000, 0x18d36e bytes] Memory for crash kernel (0x0 to 0x0) notwithin permissible range Red Hat nash version 5.1.19.6 starting unable to access resume device (/dev/VolGroop00/LogVol101) mount: could not find filesystem '/dev/root' setuproot: moving /dev failed: No such file or directory setuproot: error mounting /proc: No such file or directory setuproot: error mounting /sys: No such file or directory switchroot: mount failed: No such file or directory kernel panic - not syncing: Attempted to kill init! ============================================ by the way, when i log in to windows of my laptop and use Virtual Box, i can mount both boot and lvm partition of external hard and i can see the content of lvm and the programs of my interest.but i cant run the programs. Thanks in advance
BACKUPEXEC 2010 Backing up VMWARE 2003 OS backs up too much data.
Hello I am backing up a VMWARE server 2003 with backupexec 2010. I have done it twice. the second time I backed it up activating hardware or software compression. the VM was powered off the backup is backup to disk (no tape) VMWARE reports the used space of the server to be under 1.7 GB but allocated is 50 GB (available but unused). The backup takes 48 minutes over 10/100 network and backs up 26 GB. 1) is this normal that it saves 26 GB when the actual space used is less than 3 GB? Any way to change a setting to shrink this? thank you The size of the 2003 OS is listed from VMWARE at
Backup Exec 2010 or BESR 2010
We are in the middle of implementing our first VMware servers. 1 server with 3 VM's using ESXi 4.1 (Essentials Edition). We own both BESR 2010 and BE 2010 which we currently use to backup our physical servers (which will be replaced by the VM's) My question is whether to purchase the VMware Virtual Sever license for BE 2010 or the Virtual Server license for BESR 2010. Both allow for unlimited VM backups on a single host so is there an advantage of using one over the other? Can I do everthing with BESR that I can do with BE or should I use both? Is the only advantage of using BE 2010 is the ability to use tape? Can I do bare metal restores of VM's with BE 2010 or only BESR 2010? Thanks in advance ..
BESR 2010 scheduled VMware conversion jobs fail due the numerical name change in the .v21 files
I have two physical servers, each runs on ESX4, one holds my VMGuest OS Windows 2008 R2 Fileserver/Domain Controller and the other holds my VMGuest Windows 2008 R2 Exchange 2010 Server. I have a third server running Windows 2008 R2 Server that runs the following processes/apps: VCenter server, VMware client and VM Host update server, Backup Exec 12.5 for tape backups and BESR 2010 server for image backups and VM Conversions. The VM'd OS servers each also have BESR 2010 installed and configured. Each of the physical servers are configured with their datastore exally portioned that allows either physical machine to run both VM'd OS's (FileSrv and ExchSrv) so with this in mind we are making a nightly full Image backup of each of the VM'd servers off to a storage point on the VCenter server each night and then in turn each is to be converted to ESX bootable VMDK files over to it's own opposite server physical server so that should either server encounter physical problems then both VM'd OS's would be able to run on the remaining good server as of last bood image backup. We have made this process work previously and so it should work now. We have found that the nightly scheduled VM Conversion which should run based solely on the .sv2i file created each night will not run because of the numerical name change that happens to the .v2i files each night an new image backup is completed for either the FileSrv or ExchSrv VM'd guests... Error reported in the BESR 2010 log: Error EC8F1F48: The 'Vmware VMDK' conversion process could not be completed. Error EC8F1FDB: Unable to create virtual disk. This could be due to one of the following reasons: - Destination path does not exist. - Insufficient disk space. - Invalid credential or permissions on destination path. - Network errors. (UMI:V-281-3215-8008) Details: Source: Backup Exec System Recovery The UMI:V-281-3215-8008 error takes me to a page where Symantec reports that they're "Working" on the problem...! Anyone have any ideas or info?BESR 2010 scheduled VMware conversion jobs fail due the numerical name change in the .v21 files
I have two physical servers, each runs on ESX4, one holds my VMGuest OS Windows 2008 R2 Fileserver/Domain Controller and the other holds my VMGuest Windows 2008 R2 Exchange 2010 Server. I have a third server running Windows 2008 R2 Server that runs the following processes/apps: VCenter server, VMware client and VM Host update server, Backup Exec 12.5 for tape backups and BESR 2010 server for image backups and VM Conversions. The VM'd OS servers each also have BESR 2010 installed and configured. Each of the physical servers are configured with their datastore exally portioned that allows either physical machine to run both VM'd OS's (FileSrv and ExchSrv) so with this in mind we are making a nightly full Image backup of each of the VM'd servers off to a storage point on the VCenter server each night and then in turn each is to be converted to ESX bootable VMDK files over to it's own opposite server physical server so that should either server encounter physical problems then both VM'd OS's would be able to run on the remaining good server as of last bood image backup. We have made this process work previously and so it should work now. We have found that the nightly scheduled VM Conversion which should run based solely on the .sv2i file created each night will not run because of the numerical name change that happens to the .v2i files each night an new image backup is completed for either the FileSrv or ExchSrv VM'd guests... Error reported in the BESR 2010 log: Error EC8F1F48: The 'Vmware VMDK' conversion process could not be completed. Error EC8F1FDB: Unable to create virtual disk. This could be due to one of the following reasons: - Destination path does not exist. - Insufficient disk space. - Invalid credential or permissions on destination path. - Network errors. (UMI:V-281-3215-8008) Details: Source: Backup Exec System Recovery The UMI:V-281-3215-8008 error takes me to a page where Symantec reports that they're "Working" on the problem...! Anyone have any ideas or info?BESR 8.5 Scheduled Conversion to ESX VMDK
Hi We have BESR 8.5 backing up a full recovery point once a week of out SBS 2008 server. For the rest of the week we have incrementals taken once a night. We would like to begin scheduling a nightly conversion to ESX VMDK so that if the primary server fails we can bring the virtual machine online with less than a day of data loss. My question is: How does the scheduled conversion work? Does it re-create the VMDK from scratch each time a conversion job is run? Or does BESR have the ability to update the VMDK with only the incremental changes after the nightly incremental? The reason I ask is that our SBS server has over 1TB of data and I'm worried that a restore time may take several days if we need to start from scratch. If anyone has experience or knows of a faster way to restore to a VM (maybe with the recovery CD?) I would be very interesting in hearing about your experiences Any assistance here would be greatly appreciated Adzee