Posts Tagged ‘recovery’
YUMI (Your Universal Multiboot Installer), is the successor to MultibootISOs. It can be used to create a Multiboot USB Flash Drive containing multiple operating systems, antivirus utilities, disc cloning, diagnostic tools, and more. Contrary to MultiBootISO’s which used grub to boot ISO files directly from USB, YUMI uses syslinux to boot extracted distributions stored on the USB device, and reverts to using grub to Boot Multiple ISO files from USB, if necessary.
Aside from a few distributions, all files are stored within the Multiboot folder, making for a nicely organized Multiboot Drive that can still be used for other storage purposes.
Creating a YUMI Multiboot MultiSystem USB Flash Drive
YUMI works much like Universal USB Installer, except it can be used to install more than one distribution to run from your USB. Distributions can also be uninstalled using the same tool!
YUMI’s Main Multiboot Boot Menu
How to Create a MultiBoot USB Flash Drive
- Run* YUMI-0.0.2.9.exe following the onscreen instructions
- Run the tool again to Add More ISOs/Distributions to your Drive
- Restart your PC setting it to boot from the USB device
- Select a distribution to Boot from the Menu and enjoy!
That’s all there is to it. You should now be booting your favorite distributions from your custom Multi-Boot USB device!
How It Works: YUMI (Your Universal Multiboot Installer) enables each user to create their own custom Multiboot UFD containing only the distributions they want, in the order by which they are installed. A new distribution can be added to the UFD each time the tool is run.
If you run YUMI from the same location you store ISO downloads, they should be auto-detected (*See Known Issues Below), eliminating the need to browse for each ISO.
VERY IMPORTANT: Windows Vista or 7 Installers will cause Ubuntu or any remix based on Ubuntu (I.E. Linux Mint) to hang during boot. A quick fix is to temporarily rename the Windows SOURCES folder found at the root of the USB device.
Other Notes: If MultibootISOs was previously used, you must reformat the drive and start over. YUMI uses Syslinux directly, and chainloads to grub only if necessary, so it is not compatible with the older Multiboot ISO tool. Although I do plan to add back the capabilities of MultibootISOs as time permits.
The distro uninstaller works great, but unlisted ISO’s that have been added must currently be manually removed!
With a good backup in hand and Exchange databases and logfiles on different hard drives, it is no problem to recover from an Exchange disaster.Just restore the data from backup and initiate a roll forward of the transaction logs. Well done, the Exchange information store goes online.
But what should you do when your backup isn’t readable or you don’t have a backup? Here’s how these tools come to play.
Before you start:
- Make sure that the databases are really not startable
- Check the Application log for Exchange events that can tell you the cause of the failure
- Make a backup of the database
- Restart the server so that a soft recovery can be done
ESEUTIL /P parameters
ESEUTIL /p repairs a corrupted or damaged database. Ensure that you have a minimum of 20% free disc capacity in association to the Exchange database size.
ESEUTIL /P „c:\program files\exchsrvr\mdbdata\priv1.edb“ /Se:\exchsrvr\mdbdata\priv1.stm /Te:\tempdb.edb
This command will repair the database PRIV1.EDB. If you have no .STM file, you can create one with ESEUTIL /CREATESTM. Read more about this here.
After running ESEUTIL, you can open a detailled logfile called >database<.integ.raw to see the results.
As a last Step run ISINTEG –fix -test alltests. You can read more about ISINTEG later in this article.
Note: Sometimes you must run the fix over and over again till it fix all problems. Its like a defrag of a harddrive