Fix Boot of a Windows 2008 R2 after disktovhd STOP 0x0000007b Bare-metal

Source: http://terrytlslau.tls1.cc/2013/03/restore-windows-server-2008-r2-bare.html

Restore Windows Server 2008 R2 Bare-metal backup to a VM

Last month, My workmate needed to restore Windows Server 2008 R2 Bare-Metal backup to a VMware workstation environment. By default, Windows Server 2008 R2 Bare-Metal backup restore to a VM, Hyper-V or VMware workatation, it will show "STOP: 0x0000007B" error.

Then, I searched and read a useful post, Restoring a Win7 Complete PC image in Hyper-V. The forum users provided solutions for Hyper-V and VMware workstation. I tried to show you the steps which are provided by this forum.

For Hyper-V
Assuming that the Bare-Metal backup was restored to a VM and you get the "STOP: 0x0000007B".

1. Insert Windows Server 2008 R2 DVD.
2. Boot from DVD-Rom.
3. On "Install Windows" screen, click "Next".4. Click "Repair your computer".5. Select "Use recovery tools that can help fix problems starting Windows. Select an operating system to repair.".6. Click "Next".7. Select "Command Prompt".8. Perform "regedit" to start "Registry Editor".9. Select "HKEY_LOCAL_MACHINE".
10. On the menu, click "File > Load Hive".11. Navigate to "D:\Windows\System32\Config\SYSTEM".

  

Remark: Note that the restored Windows may be restored to another drive letter.

12. Click "Open".

13. Under "Key Name", type "Recovery".

 14. Click "OK".

15. Navigate to "HKEY_LOCAL_MACHINE\Recovery\ControlSet001\services\intelide".

16. Double-click "Start".

17. Change the "Value data" to "0".

18. Click "OK".

Remark: I tried to modify this setting and then the Windows Server 2008 R2 can boot up in Hyper-V environment. If the above setting doesn't work, please change the following registry settings.

HKLM/System/CurrentControlSet/Services/ and then the value of the "Start" parameter

Aliide = 3
Amdide =3
Atapi = 0
Cmdide = 3
iaStorV = 3
intelide = 0
msahci = 3
pciide = 3
viaide = 3

19. Navigate to "HKEY_LOCAL_MACHINE\Recovery".
20. On the menu, click "File > Unload Hive".21. On "Confirm Unload Hive" window, click "Yes". 22. Close "Registry Editor".23. On "System Recovery Options", click "Restart".

After restarted, the Windows Server 2008 R2 can boot up in a VM of Hyper-V.

Recovery of single or multiple Exchange 2003 mailbox using Recovery Storage Groups

Spanish keywords: Restaurar uno o múltiples buzones de Exchange 2003 utilizando Grupos de almacenamiento de recuperación
Source:
http://www.youtube.com/watch?v=pcCtJdRn79U (include errors not quickly fixed)
http://www.youtube.com/watch?v=odP4GqwRF-Q
http://www.youtube.com/watch?v=_j7Hv3nQIec (good video, steps missing, long and slow  introduction, and it copies not merge backup - so there is duplicity)


Types of backup

BACKUP FOR SYSTEM HARDWARE FAILURE
1. You need a backup (use ntbackup and make a full backup on sunday  - stopping exchange services with a script), call the file Exchange Full SysRecovery Backup.bkf

BACKUP FOR Recovery Storage Groups
2. You'll also need a full backup with Exchange services running.  It means "select checkboxes" on the side of "Exchange Information Store" when you select the scope of Ntbackup, call the file Exchange Full IS Backup.bkf

For use this instructions you need the second type of backup listed and at least Exchange 2003 SP2 installed

Steps:
1. Connect an USB or USB Hard disk drive with almost USB 2.0 and at least free same with the same size of priv1.edb or priv1.stm
2. Create a folder G:\Recovery
3. Start Exchange System Manager
4. Browse to Servers - ServerName - First Storage Group
5. Right Clic on First Storage Group and clic "New Recovery Storage Groups", go to General Tab and point both "Transaction Log Location" and "System Path Location" to G:\Recovery (USB)
6. Now clic on "Recovery Storage Group" and right clic to "Add Database to Recover", select your Database the default it's called "Mailbox Store"
7. Now go to "Database Tab" and be sure to have checked "The database can be overwritten by a restore"
8. Now open ntbackup.exe, go to Restore Tab, look for more recent Catalog file of "Exchange Full IS Backup", and check "Mailboxes and LogFiles", clic Start Restore. You'll be asked to select the "hostname" of your production server or a temporary server (more complex), create a second folder on drive G:\ called temp, so you can point the "Temporary location for log and..." to G:\temp
9. I've recomend to mark both checkboxes "Last restore set (Log File Replay)" and mount to finish.
10. Wait until restoration is Finished
11. Wait at least 5 minutes to see the "Recovery Storage GRoup" mounted and two subfolers "mailboxes and logon"
12. When you can access to Mailbox subfolder, you'll notice that all mailboxes are marked as "deleted" with a "Red X"
13. You right clic on one or select several mailboxes and you'll open a wizard of Exchange Tasks called "Recover Mailbox Data", clic on next, select the "Destination Storage Group\Database", clic next
14. Select Merge to copy only "missing items", if you chose Copy you'll create duplicates of all elements even if exist on the destination. Clic Next
15. You can schedule the task, or can clic next to start the process
16. That's all, only inexistent items will be restored, it could take more time than just copying but is better for the final user


Greetings

BADBOY

PS: If you have questions play the source videos, understand it and do your own tests.

 

Iomega Home Media Network Hard Drive (MHNDHD) file recovery after "Factory Self Erase"

Spanish keywords: recuperar archivos de un Iomega Home Media Network Hard Drive (MHNDHD) después de qué automáticamente retornó a su estado de fábrica

Tools:

• Standard Screwdriver

Hardware:

• Desktop PC with Windows 7 installed 
• an adittional free SATA connector
• Enough free space on drive C:

Software:

• Raise Data Recovery for SGI/XFS at http://www.ufsexplorer.com/rdr_xfs.php
• You need to buy the online serial via paypal to recover files greater tan 256KB

Objectives:

• Try to find a Iomega XFS Data Partition
• Try to restore overwrited XFS Data Partition by accidental factory reset
• Try to restore overwrited files on XFS Data Partition by "SELF factory reset"

Steps:

1. Warranty that you have 1 hard drives with enough space
2. Install Windows on drive in SATA 0 port
3. Shutdown computer

To dissasemble the drive

• Unplug LAN and Power Cord and Carefully Disasembly Iomega Hard Drive, take out the two screws on the back, BE EXTREMLY CAREFUL the disk could slide out and crash, take out the "fan connector" just the white connector, if you pull from cable you'll broke the fan plug.  Later take out the four screws from the side of the internal sata disk
• A dissasembly video from Geek Street is on YouTube (http://www.youtube.com/watch?v=RLAGPBaixbw)

1. Install the internal SATA on your Desktop computer on port SATA 1 (don't use SATA-to-USB adapters these are extremely slow if you need to recover a bunch of files)
2. Click NO if Windows Ask to format a "x: drive" letter
3. Just don't try to browse the partitions from Windows.  Run compmgmt.msc to open "Disk Management" to see if the drive appears, again Click NO if Windows ask to initialize disk or "Reactivate Disk", just check that you see your C:\ drive and a second disk with three partitions (two small and one large)
4. Install and actívate the Raise Data Recovery for XFS
5. Open the program and right clic on "the biggest XFS partition" that you found on the secondary disk, and clic "Recover", don't forget to check "Intelligent RAW" checkbox
6. Once you see the file tree on Raise Data Recovery Program, restore on drive C:\ or a network share.  The recovery chances is 100% but the recovery of filenames is only about 80%, so you will need to rename several or hundred of files.  (install msoffice, adobe , etc) you'll have a lot of time to spent putting the right name on files.
7. To get the initial FileTree will take about 8 hours on a 50% used 1TB hard drive.
8. Later you could have a 24 hour wait for total recovery of the files.

Good Luck

Captions soon
 

Zimbra 7 Failed to start slapd bdb_db_close: database "": txn_checkpoint failed: Invalid argument (22).

Problema provocado por apagados bruscos o incorrectos de zimbra. USEN UN UPS Y APRENDAN A APAGAR SU SERVIDOR! !!!!!!!

Y sino tengan un backup que funcione.....



login as: root
root@mail.dominio.com's password:
Last login: Tue Sep  4 15:01:41 2012 from mail.infa.gob.ec
[root@mail zimbra]# su zimbra
[zimbra@mail ~]$ zmcontrol start
Host mail.dominio.com
        Starting ldap...Done.
Failed.
Failed to start slapd.  Attempting debug start to determine error.
bdb_db_close: database "": txn_checkpoint failed: Invalid argument (22).
backend_startup_one (type=hdb, suffix=""): bi_db_open failed! (22)
bdb_db_close: database "": alock_close failed

[zimbra@mail ~]$ zmcontrol stop
Host mail.dominio.com
        Stopping stats...Done.
        Stopping mta...Done.
        Stopping spell...Done.
        Stopping snmp...Done.
        Stopping cbpolicyd...Done.
        Stopping archiving...Done.
        Stopping antivirus...Done.
        Stopping antispam...Done.
        Stopping imapproxy...Done.
        Stopping memcached...Done.
        Stopping mailbox...Done.
        Stopping logger...Done.
        Stopping zmconfigd...Done.
        Stopping ldap...Done.
[zimbra@mail ~]$ cd /
[zimbra@mail /]$ cd opt
[zimbra@mail opt]$ cd zimbra
[zimbra@mail ~]$ cd data
[zimbra@mail data]$ cd ldap
[zimbra@mail ldap]$ cd hdb
[zimbra@mail hdb]$ cd db
[zimbra@mail db]$ ls
alock            dn2id.bdb        zimbraDomainName.bdb
cn.bdb           entryCSN.bdb     zimbraForeignPrincipal.bdb
__db.001         entryUUID.bdb    zimbraId.bdb
__db.002         givenName.bdb    zimbraMailAlias.bdb
__db.003         id2entry.bdb     zimbraMailCatchAllAddress.bdb
__db.004         mail.bdb         zimbraMailDeliveryAddress.bdb
__db.005         objectClass.bdb  zimbraMailForwardingAddress.bdb
__db.006         sn.bdb           zimbraMailHost.bdb
DB_CONFIG        uid.bdb          zimbraMailTransport.bdb
displayName.bdb  zimbraACE.bdb    zimbraVirtualHostname.bdb
[zimbra@mail db]$ /opt/zimbra/bdb  (aquí hay doble tab para ver la versión)
bdb/          bdb-4.7.25.4/
[zimbra@mail db]$ /opt/zimbra/bdb-4.7.25.4/bin/db_recover -vv
Finding last valid log LSN: file: 47 offset 4632342
Recovery starting from [47][4632197]
Recovery complete at Tue Sep  4 16:36:33 2012
Maximum transaction ID 80000002 Recovery checkpoint [47][4632342]
[zimbra@mail db]$ ls  (noten los db.000x eliminados automáticamente)
alock            id2entry.bdb                zimbraId.bdb
cn.bdb           mail.bdb                    zimbraMailAlias.bdb
DB_CONFIG        objectClass.bdb             zimbraMailCatchAllAddress.bdb
displayName.bdb  sn.bdb                      zimbraMailDeliveryAddress.bdb
dn2id.bdb        uid.bdb                     zimbraMailForwardingAddress.bdb
entryCSN.bdb     zimbraACE.bdb               zimbraMailHost.bdb
entryUUID.bdb    zimbraDomainName.bdb        zimbraMailTransport.bdb
givenName.bdb    zimbraForeignPrincipal.bdb  zimbraVirtualHostname.bdb
[zimbra@mail ldap]$ cd /
[zimbra@mail /]$ zmcontrol start
Host mail.dominio.com
        Starting ldap...Done.
        Starting zmconfigd...Done.
        Starting logger...Done.
        Starting mailbox...Done.
        Starting spell...Done.
        Starting mta...Done.
        Starting stats...Done.
[zimbra@mail /]$ zmcontrol status
Host mail.dominio.com
        ldap                    Running
        logger                  Running
        mailbox                 Running
        mta                     Running
        spell                   Running
        stats                   Running
        zmconfigd               Running

Otras fuentes: http://www.ecualug.org/2010/03/15/forums/problemas_con_zimbra
 

How to move Exchange 2000 to new hardware and keep the same server name

Basado en: http://support.microsoft.com/kb/297289

NO SIRVE PARA CONTROLADORES DE DOMINIO, SOLO PARA SERVIDORES DE EXCHANGE INDEPENDIENTES

1. To move Exchange 2000 to new hardware:
   Verify that the databases are in a "Clean Shutdown" state. To do this, type the following command at a command prompt:
   eseutil /mh database name.edb
   Make an offline backup copy of the .edb files and the .stm files for each database. You can then copy these files into the same locations on the new server after the new server is built.


2. Document the existing locations of databases and transaction logs. You will have to re-create these locations on the new system.


3. Take the existing server offline. o añade un disco duro nuevo


4. Reset the machine account for the Exchange 2000 server:
   Start Active Directory Users and Computers.
   Locate the Exchange 2000 server machine account, right-click the machine account, and then click Reset Account. (saca un system state del domain controller para deshacer cualquier cosa que falle)


5. Bring the new server online and use the same server name. (instala en otra partición u otro disco duro), configura la tarjeta de red apuntando al dns correctamente y el sufijo en el registro de dns igualmente


6. Use an Exchange 2000 Full Administrator account to log on to the new server. (o sea unele al dominio)


7. Install any components that Exchange 2000 requires, such as Internet Information Services (IIS) and the appropriate Microsoft Windows 2000 Server service packs. Note After you install the SMTP service, set the SMTP service to disabled until the Exchange installation is complete. This will prevent this server from receiving mail until Exchange is functioning properly. (cierra el puerto en el firewall o en el antispam) en brightmail Consola - Administration - Host Name - clic en Pause message scanning and delivery. Instala el service pack mas actual y si tienes tiempo el rollup y los demas updates criticos y de seguirdad, pon el antivirus con proteccion de red preferible


8. Use an Exchange 2000 Full Administrator account to log on to the new server.


9. Run Exchange 2000 Setup with the following parameter:
   Setup /disasterrecovery Make sure that you click Action-Disaster Recovery for the Messaging and Collaboration services and the Exchange System Management Tools.


10. When Setup is complete, install the Exchange 2000 service pack that was installed on the existing server by using the update.exe /disasterrecovery switch.


11. (this section is useless)
    If the following registry key does not already exist, add a DWORD value and the following registry string based on the service pack value:
    HKEY_LOCAL_MACHINE\Software\Microsoft\Exchange\Setup
    DWORD value name: ServicePackBuildHexadecimal value: number
    The number varies based on the service pack:
    The hexadecimal number for the retail, released version without a service pack is 1141.
    The hexadecimal number for Service Pack 1 is 1268.
    The hexadecimal number for Service Pack 2 is 1682.
    The hexadecimal number for Service Pack 3 is 1869.
    


12. Install any Exchange 2000 post-service pack hotfixes that were installed on the existing server.
13. Remove all transaction log files that were created during the installation of Exchange. For example, remove E00xxxxx.log and E00.log. Then, restore or copy the files that you backed up in step 1.
14. Just copy mdbdata to the new server use the original location, to replay all unconfirmed transactions.
    
15. Mount all of the stores after the restoration is complete. Make sure that clients can connect and that mail can flow. Edit "Unmount settings"
    

More reading.

1. 296788 (http://support.microsoft.com/kb/296788/ ) Offline backup and restoration procedures for Exchange