Netbackup: Import Disk Based images

This is the procedure I used to import Netbackup disk based images from a failed media server.  This is a 2 phased method that uses the NBU Admin console.  Phase 1 initiates the import process by locating the path to the images to be imported and the second phases imports the images into the database.  The disk images must be present on a local disk. In my experience network importing from a network share did not work.

Phase 1
Importing NetBackup disk images
First, run the "phase 1 import".
1. Start the NetBackup Administration Console and go to the Catalog section.
2. From the menu select Actions > Initiate Import and a dialog box will appear.
3. Check the "The images to be imported are on disk" radio button and enter a disk path to import images from.
4. Check the Activity Monitor for progress of the phase one import.

Phase 2
Once the "phase 1 import" completes, run the "phase 2 import".
1. Start the NetBackup Administration Console and go to the Catalog section.
2. Under Pathname:, enter the disk path used for the phase 2 import.
3. Select a date range for the images to import and click the Search button.
4. Select Backup IDs to import from the search results.
5. From the menu select Actions > Import to begin the phase 2 import.
6. Check the Activity Monitor for progress of the phase 2 import.

Once the phase 2 import completes successfully, the disk images will be available for restores.


Documentation

VDR: Remove Damaged Restore Points

Remove Damaged Restore Points

Corrupt restore points, which are identified during integrity checks, should be removed. Restore points may be identified as damaged during transient connection failures. If transient connection failures are possible, check if damaged restore point issues are resolved after connections are restored.

Prerequisites
Before you can remove damaged restore points, you must have restore points in a functioning Data Recovery
deployment.

Procedure
1 In the vSphere Client, select Home > Solutions and Applications > VMware Data Recovery.
2 Click the Reports tab and double-click the integrity check that failed.

The Operations Log for the event opens in a separate window. Note which restore points triggered the
failure.

3 Close the Operations Log and click the Restore tab.

4 From the Filter dropdown list, select Damaged Restore Points.
Available restore points are filtered to display only the virtual machines with damaged restore points. It
may be necessary to expand a virtual machine's node to display the damaged restore point.

5 Select damaged restore points for removal and click Mark for Delete.

6 Initiate an integrity check.
Completing an integrity check causes all restore points marked for deletion to be removed.

7 Review the results of the integrity check to ensure no damaged restore points remain.


VMware Data Recovery Administration Guide
28

Exchange 2007: Fowad all Mail

This is the Procedure to forward all mail from one Exchange 2007 mailbox to another mailbox without leaving a copy on the original recipient mailbox. 

Exchange management Shell:

Set-Mailbox -Identity "John Smith" -ForwardingAddress "sara@contoso.com"

Use following ccmlet to forward all mail while leaving a copy on the original recipient mailbox. 

Set-Mailbox -Identity "John Smith" -ForwardingAddress "sara@contoso.com" -DeliverToMailboxAndForward $true

Exchange Management Console:

1.   In the console tree, expand Recipient Configuration, and then click Mailbox.

2.  In the result pane, right-click the mailbox for which you want to configure mail forwarding and click Properties.

3.  In <Mailbox> Properties, on the Mail Flow Settings tab, click Delivery Options, and then click Properties.

4.  Click the Forward to check box. This enables the Browse button.

5.  Click Browse to open the Select Recipient dialog box. Select the recipient to whom you want to forward messages, and then click OK.

6.  If you want incoming messages to be delivered to the mailbox as well as to the forwarding address configured, select the Deliver message to both forwarding address and mailbox check box. Clear this check box to forward all incoming messages without retaining copies in the mailbox.

7.  Click OK to return to <Mailbox> Properties.

8.  Click OK.

PowerShell Script: Protect OUs from Acidental Deletion

Quick Powershell script to protect all OUs from acidental delition.

Run the following script from the Active Directory Module  to finda all unprotected OUS

Get-ADOrganizationalUnit -filter * -Properties ProtectedFromAccidentalDeletion | where {$_.ProtectedFromAccidentalDeletion -eq $false} | ft


Run the following script from the Active Directory Module to protect all the OUs listed in output from obove scripts.

Get-ADOrganizationalUnit -filter * -Properties ProtectedFromAccidentalDeletion | where {$_.ProtectedFromAccidentalDeletion -eq $false} | Set-ADOrganizationalUnit -ProtectedFromAccidentalDeletion $true

TechNet Article

OCS 2007 r2: 3 Way IM Conferencing

A few days ago I got a call from the Helpdesk technicians reporting OCS issues.  It turns out that 3 way IM conference sessions stopped working.  My first thought was to check the status of the OCS services, but they all appeared to be running.  The error displayed in the logs was 3098 which after research turned out to be related to certificate issue.  After I looked at my certificate store I found out that the Certificate was expired.

After reissuing the certificate I continued to get errors (3097) relating to a downed or disabled MCU.  I continued to read many, many forums until I found one which seemed to have the my same issue.  The forum poster had called Microsoft and after a long troubleshooting session they found out that the IM Conferencing Service was being run by the RTCComponentServer rather than the RTCService.  Everything started working after I made the change.

I am still wondering why this stopped working, given that this configuration was set up since the initial setup of OCS 2007 r2.

LCSCMD commands to activate and Deactivate the IM Conferencing on OCS 2007 r2

Activate:
LCSCmd.exe /MCU /Action:deactivate /Role:IMMCU

Deactivate:
LCSCmd.exe /MCU /Action:Activate /Role:IMMCU /Pool01  /Password:OptimusPrime
No need to issue /username if you are logged on with an account that can perform this action.

I these are some post that I rread in my effort to fix the issue.

http://blogs.technet.com/b/daveh/archive/2009/03/30/error-joining-im-livemeeting-conferences-in-office-communications-server-2007.aspx

http://techiefixation.blogspot.com/2009/01/office-communicator-2007-3-party.html

http://cmcgreanor.wordpress.com/2009/09/02/ocs-2007-r2-mcu-factory-issue/

http://ocsguy.com/2010/01/13/a-certificate-gotcha-that-got-me-again/

PowerShell Scripts Change User Attributes

Just a note on how to search and modify user attributes.  I recently had to use these cmlets to modify the Manager and Company field in AD.  

Modify Attributes for all users risiding in a particular OU. Start listing the OU. In this case all user in PayRoll OU will have Optimus Prime as Manager.

Get-ADUser -Filter * -SearchBase "OU=PayRoll,OU=Accounting,DC=YourDomain,DC=com" | Set-ADUser -Manager "Optimus Prime"

Copying one user’s group memberships to a second user. In this case all group memberships of the user Optimus Prime will get duplicated to MegaTron.

Get-ADPrincipalGroupMembership -Identity OptimusPrime | % {Add-ADPrincipalGroupMembership -Identity MegaTron -MemberOf $_}

Reporting on user accounts with non expiring Passwords.  Format teh output to display any properties.

Search-ADAccount -PasswordNeverExpires | FT Name, ObjectClass, UserPrincipalName

Thanks to the TechRepublic

Netbackup Device Mappings

Use the bellow process to update/install the Netbackup Device mappings.

1. Download and extract the new mappings file package to a temporary folder.  This will create three files in the temporary location:

    * Readme.txt
    * external_types.txt
    * external_robotics.txt

2. Copy the external_types.txt file from the temporary location to C:\Program Files\VERITAS\NetBackup\var\global\ on the Master Server or  EMM Server.

3. Copy the external_robotics.txt file from the temporary location to C:\Program Files\VERITAS\NetBackup\var\global\ on the master server, EMM Server, each media server that controls a robot, and each media server from which robot inventories will be run.

4. Bring up a command window with Start -> Run -> Type "cmd". Enter the following commands in that command window.

5. Update the NetBackup Enterprise Media Manager database with the new device mappings version. This only needs to be done once and must be run from the Master Server or the EMM Server.  Use the command format below that corresponds to the installed version of NetBackup:

NetBackup 6.5/7.0/7.1:  C:\Program Files\VERITAS\Volmgr\bin\tpext -loadEMM

7. Restart Device Manager (ltid) on each Media Server.

8. Verify that the version that is now stored in the Enterprise Media Manager database is the same as what is in the file stored on the Media Server:

C:\Program Files\VERITAS\Volmgr\bin\tpext -get_dev_mappings_ver


Device Mappings_V195.zip