Posts filed under ‘Backup and Recovery’
Windows server 2022 – Cannot extend C: partition
Those who are installing new Windows 2022 server , may realize that the C: drive cannot be extended . This is due to the recovery partition is created next to the C: drive.
Most of the google search references pointing out to use a 3rd party tool to modify the disk or delete the recovery partition via diskpart utility using the override switch and then extend the C: drive. However , This deletion will lead you to a situation you lose the recovery partition and unable to recover the server via the recovery media or similar methods. Thus I would recommend the below approach to safely transfer the recover partition to C: drive after deleting the original recovery partition.
Step1: Mount the Windows 2022 Image to the C:\Temp folder
DISM /Mount-image /imagefile:D:\sources\install.wim /Index:1 /MountDir:C:\temp/readonly /optimize
Step2: Transfer the recovery media to C: drive
robocopy /MIR C:\temp\Windows\System32\Recovery\ C:\Windows\System32\Recovery
Step3 : Set the recovery partition to C:\Windows\System32\Recovery
reagentc /setreimage /path C:\Windows\System32\Recovery
Step4: Unmount the Windows 2022 Image and verify the recovery partion status
Dism /Unmount-image /MountDir:C:\temp /discard
Run the command reagent /info to verify the Recovery partition Image
Exchange 2013 GRT Fails with Symantec Backup Exec 2014 SP1
Dear Folks
Recently we deployed Symantec Backup Exec 2014 V-Ray Edition and as per the Guidelines we installed the Agent on Exchange Server(Single Server) and configured all the prerequisites as below;
1) Add the BackupExec User to the below groups
-
Public Folder Management
-
Recipient Management
- Server Management
2) Enter the below commands in Powershell
new-RoleGroup -Name BackupExecRoles -Roles @(“Database Copies”, “Databases”, “Exchange Servers”, “Monitoring”, “Mail Recipient Creation”, “Mail Recipients”, “Recipient Policies”, “Mail Enabled Public Folders”, “Public Folders”)
Add-RoleGroupMember -Identity BackupExecRoles -Member BackupExecUser
3) This is for GRT
New-ManagementRole -Name “SymantecEWSImpersonationRole” -Parent ApplicationImpersonation
New-ManagementRoleAssignment -Role “SymantecEWSImpersonationRole” -User BackupExecUser -Name “BackupExecUser-EWSImpersonation”
New-ThrottlingPolicy -Name “SymantecEWSRestoreThrottlingPolicy” -EwsCutoffBalance Unlimited -EwsMaxBurst Unlimited -EwsMaxConcurrency Unlimited -ExchangeMaxCmdlets Unlimited -MessageRateLimit Unlimited -PowershellCutoffbalance Unlimited -PowershellMaxBurst Unlimited -PowershellMaxCmdlets Unlimited -PowershellMaxConcurrency Unlimited -PowershellMaxOperations Unlimited -RecipientRateLimit Unlimited -ThrottlingPolicyScope Regular
Set-Mailbox -Identity BackupExecUser -ThrottlingPolicy “SymantecEWSRestoreThrottlingPolicy
Set-ThrottlingPolicyAssociation -Identity BackupExecUser -ThrottlingPolicy “SymantecEWSRestoreThrottlingPolicy”
4) Test EWS Connectivity for the BackupExec User
test-webservicesconnectivity -MailboxCredential $(get-credential) -TrustAnySSLCertificate | FL
It will produce a logon prompt, enter the backup exec user credentials it will output some html tags without an error.You may face an error in the Powershell in Exchange 2013 and you need to run the command shown in the output and enter a password , thereafter if you run the original command it will not reproduce the error.
After all the above steps you may face the below error during the restore
Assuming if you have done all the prerequisites correctly , you must try the below
1) Restart both the Backup Exec and the Exchange Server
2) Reconfigure the Backup Exec Job credential for the Exchange Server as below (This worked for us)
Domain Name\BackupExec User
Good Luck !!!
Hope you like it.. 