Posts Tagged Symantec

Solution for Symantec Enterprise Vault when Unable to see the EV Toolbar in MS Outlook


Solution for Symantec Enterprise Vault when Unable to see the EV Toolbar in MS Outlook

Issue:

Unable to see the EV Toolbar in the Outlook after the Mailbox moved within Exchange Database Findings & Cause: -Found Event ID 3357 This mailbox cannot be processed until the Exchange provisioning task has processed the corresponding user’s details. Ensure that a provisioning group includes this user and run the provisioning task. To disable these warnings, set the ‘HideMissingPolicyInfoErrors’ registry value to 1.

–It appears Hidden message is corrupted in the Mailbox

Resolution:

– EV server Version 9.0.2

Zaped user mailbox as per articlehttp://www.symantec.com/docs/TECH35614

[Directory] DirectoryComputerName = evserver.Domain.com Sitename =  EV Site [Mailbox] DistinguishedName =  /o=OrganizationName/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=MailBoxName [Folder] Name = Mailboxroot Zap = True

Run the EVPM tool in the command prompt.

Run Enterprise Vault Policy Manager (EVPM) from \Program Files\Enterprise Vault (or \Program Files (x86)\Enterprise Vault) on the EV server logged on as the Vault Service Account (VSA). The syntax for EVPM follows:

Symantec EVPM2

 
 
 
 
 
 
 
  • – Enabled Mailbox to be provisioned for Archiving.
  • – EV tool bar is appears now but VC sync button not available
  • -Checked Mailbox log, Mailbox is running in online mode not cached mode
  • -Enabled Mailbox Cache Mode [pre-request for Vault Cache]
  • -Restarted Outlook, Sync button appears now.
Advertisements

, , , , , , , ,

Leave a comment

Backing Up Symantec Enterprise Vault with Veeam Backup & Replication


Hello Once Again,

I found the solution to backup Symantec Enterprise Vault 9.0.2.1061 with Veeam Backup and Replication 6.1.0.205.

Every environment is differ to another with regards to the Veeam Setup and Symantec Enterprise Vault Setup and Configuration.

When Symantec Enterprise Vault is configured with the Site and Storage Groups “Vaults”, there is a PowerShell script automatically will generate the Transform Backup Scripts for your environment. The Transform-Backup.PS1 script is located under C:\Program Files (x86)\Enterprise Vault\Reports\Templates.

Once the script runs, it will generate an HTML file which will have all the PowerShell cmdlet to set he Enterprise Vault/Site/Vaults ‘Storage Groups’ into Backup Mode and scripts to Exit/Clear the IndexLocation and Vault ‘Storage Groups’.

Out of this you will have to create two scripts or more, in my environment with my basic knowledge of scripting, I have created four scripts, two PowerShell and two Windows Batch files that calls the powerShell scripts.

Note: You have to install the Enterprise Vault Console on the Veeam Backup & Replication Server in order to invoke and run the scripts.
Note: Permission you will require to run the Veeam Job and the Enterprise Vault Console. If the Veeam Services runs under Service Account, this service account need to be granted permission as Local Administrator on the Enterprise Vault Server and as a Power Administrator “Or create a new Authorization Group under that have definition of;
EVT Manage Index Location Backup Mode
EVT Manage Vault Store Backup Mode
Then add the user to the newly group created. And configure the Task Schduler to run the task under this user which manages the Veeam Services “Veeam”
This KB from Symantec can help you out with the permission: http://www.symantec.com/business/support/index?page=content&id=TECH67812
Note: The PowerShell has to run on the 32bit; c:\Windows\SysWOW64\WindowsPowerShell\v1.0\powershell.exe
Note: Do not configure the Schduler on Veeam Backup Job, let the Task Scheduler handle this instead.

Pre Script:
This script will include the Power cmdlet which will set the Enterprise Vault in backup Mode and will invoke the Veeam Backup Job to run.

#Pre-job to set the Symantec Enterprise Server and Site into Backup Mode.
#Reset ArchiveBit on the Store Vaults.

DEL “\\EVServer\EVPartition01cc55b2dc699b70$\IgnoreArchiveBitTrigger.old”
DEL “\\EVServer\EVPartition01cc55b2753ddd30$\IgnoreArchiveBitTrigger.old”
DEL “\\EVServer\EVPartition01cc55b34882a450$\IgnoreArchiveBitTrigger.old”
DEL “\\EVServer\EVPartition01cc55b3725ff520$\IgnoreArchiveBitTrigger.old”

#Site: EV Site

#Set backup mode on site
c:\Windows\SysWOW64\WindowsPowerShell\v1.0\powershell.exe -psconsolefile “C:\Program Files (x86)\Enterprise Vault\EVShell.psc1” -command “& {Set-VaultStoreBackupMode -Name ‘EV Site’ -EVServerName evserver -EVObjectType Site}”

#SiteIndexLocations:  EV Site

#Set backup mode on indexes in site
c:\Windows\SysWOW64\WindowsPowerShell\v1.0\powershell.exe -psconsolefile “C:\Program Files (x86)\Enterprise Vault\EVShell.psc1” -command “& {Set-IndexLocationBackupMode -EVServerName evserver -EVSiteName ‘EV Site’}”

#Start Veeam Backup Job

Add-PSSnapin VeeamPSSnapin

# Add the name of the backup jobs to be included here. The order in which they are entered is the order in which they will run

$chainedjobs = (“SymantecEV”)

foreach ($jobname in $chainedjobs){
$job = Get-VBRJob -name $jobname
$jobtry = 0
start-VBRJob -job $job

$job.GetLastResult()
if($job.GetLastResult() -eq “Failed”){
do{
Start-Sleep 480
Start-VBRJob -job $job -RetryBackup
$jobtry++
}
while(($jobtry -lt 3) -and ($job.GetLastResult() -eq “Failed”))
}
}

The GetVBR-Job script it will start and it will loop through for 3 times as RetryJob till it gets the result Success/Warning other than Failed.
Call this script in the Task Scheduler either using PowerShell.PS1 or you can create a Windows Batch file to call the script

PowerShell.exe G:\Script\PreJob.ps1

Then in the Veeam Backup Job configuration in the Storage Section -> Advanced Settings you have to put the Post-Job Script under the Post Job Activity Section.

Post-Job Script:
This script will include the Power cmdlet which will clear the Enterprise Vault from backup Mode once the Veeam Job Succeeded.

#Post-job to Clear the Backup Mode on the Enterprise Site and EVServer.
#Create IgnoreArchiveBitTrigger.txtecho “Enterprise Vault Trigger File”> “\\EVServer\EVPartition01cc55b2dc699b70$\IgnoreArchiveBitTrigger.txt”
echo “Enterprise Vault Trigger File”> “\\EVServer\EVPartition01cc55b2753ddd30$\IgnoreArchiveBitTrigger.txt”
echo “Enterprise Vault Trigger File”> “\\EVServer\EVPartition01cc55b34882a450$\IgnoreArchiveBitTrigger.txt”
echo “Enterprise Vault Trigger File”> “\\EVServer\EVPartition01cc55b3725ff520$\IgnoreArchiveBitTrigger.txt”

#Clear backup mode from site

c:\Windows\SysWOW64\WindowsPowerShell\v1.0\powershell.exe -psconsolefile “C:\Program Files (x86)\Enterprise Vault\EVShell.psc1” -command “& {Clear-VaultStoreBackupMode -Name ‘EV Site’ -EVServerName evserver -EVObjectType Site}”

#Clear backup mode from indexes in sitec:\Windows\SysWOW64\WindowsPowerShell\v1.0\powershell.exe -psconsolefile “C:\Program Files (x86)\Enterprise Vault\EVShell.psc1” -command “& {Clear-IndexLocationBackupMode -EVServerName evserver -EVSiteName ‘EV Site’}”

When the Pre-Job Script runs, you will notice on the Enterprise Vault Server that an Event IDs will be generated which indicates that the Enterprise Vault Server is Set for Backup Mode and all the Storage Groups;

Successfully set Backup Mode on all the Vault Stores that are managed by the Storage Service on this computer. Event ID 7060
Computer Name: evserver.domain.com
Successfully set Backup Mode on all the Vault Stores in the Vault Store Group that are managed by the Storage Service on this computer.  Event ID 7059
Disabling additions, deletions, and updates to the following index locations because they are in backup mode: Event ID 7319

E:\Index\index1
E:\Index\index2
E:\Index\index3
E:\Index\index4
E:\Index\index5
E:\Index\index6
E:\Index\index7
E:\Index\index8

Status: Success  (0)

Once the Backup Job in Veeam Server finished, the Post-Script will be triggered and will clear out the Backup Mode and Symantec Enterprise Vault will generate an Event IDs
as successful cleared Backup Mode for all the Storage Groups Vault.
Successfully cleared Backup Mode from Vault Store. Event ID 7079

, , ,

10 Comments

Integration Veeam Backup with Symantec Backup Exec 2010


Integration Veeam Backup with Symantec Backup Exec 2010

Introduction:

This document highlights some necessary steps required to setup a successful Veeam Backup and Symantec Backup Exec 2010 for tape integration and off-site storage.

Steps to a successful integration:

Veeam B& R v6.0.0.181 is installed on a Virtual Machine running guest operating system Windows 2008 R2 64bit with 8 GB of Ram and 2 Virtual vCPU Sockets and 4 Cores for each socket. The Veeam resources it depends on the environments and workload that put on the backup during backup operation.

All backup repositories’ are mapped through iSCSI Initiator with MPIO. The sizing of the repositories also it depends on each environment and how much data needs to be restored from disk and for how long. Again, this retention period plays a big role in the repository storage and how big your storage is.

In my environments, I have multiple targets;

No

Repository Target

Size

1. IBM iSCSI – DS3500 2.0 TB
2. IBM iSCSI – DS3500 745 GB
3. EMC iSCSI – AX4-5i 800 GB
4. OpenFiler iSCSI 2.3 1.4 TB
5. IBM iSCSI – DS3500 2.0 TB
Total 6.9 TB

Veeam Backup Configuration:

All the above repositories are added to the Veeam Backup & Replication v.6.0.0.181. Backup jobs configured for each VM to one of the above repositories.

Due to lack of disk space in the repositories and which limits the number of days  ofbacked up VMs should remain on disk, all the backup jobs are configured as follows;

Categorizing the backup jobs based on roles of the Virtual Machines helps a lot from backing up static Virtual Machines which doesn’t change very often.

No

Backup Category

Descriptions

1. Critical Virtual Machines Virtual machines are changing dynamically, such as Mail Server, file Server, Archive Server, Sharepoint, etc..
2. Non-Critical Virtual Machines Virtual machines are not changing on a daily basis, such as AntiVirus, Proxy Servers, WSUS, Deployment Serves

Critical Virtual Machines Job Settings:

Since those Virtual Machines are changing dynamically and daily, weekly and monthly backup requires for them backup job settings are configured based on the disk space and how long we can restore from disk.

Restore points to keep on disk: = 5

Deleted VMs data retention period: = 5

Backup Mode set as Incremental and Weekly Friday Active Full Backup. And schedule backup Sunday through Friday.

This settings result 1 Full Backup on Friday .vbk file and Sunday through Thursday is incremental which will gives 5 .vibs files.

Note: Since the Deleted VMs data retention period set to 5, CheckDataValue() when it reaches to 5 days, the full last backup chain will be deleted from disk and will have a new .vib file changed with last .vbk file.

Example:

Full Backup runs on 27th April, 2012 it will have a chain of Sunday through Thursday.

Week#1

No

Backup Date

Day

Backup Mode

1. 04/27/2012  02:43 VM001012012-04-27T143033.vbk Friday Full
2. 04/29/2012  02:37 VM001012012-04-29T143033.vib Sunday Incremental
3. 04/30/2012  09:42 VM001012012-04-30T093346.vib Monday Incremental
4. 05/01/2012  02:37 VM001012012-05-01T143039.vib Tuesday Incremental
5. 05/02/2012  02:37 VM001012012-05-02T143047.vib Wednesday Incremental
6. 05/03/2012  02:38 VM001012012-05-03T143029.vib Thursday Incremental

Week #2

No

Backup Date

Day

Backup Mode

1. 05/05/2012  11:18 VM001012012-05-04T143026.vbk Friday Full
2. 05/06/2012  02:36 VM001012012-05-06T143052.vib Sunday Incremental
3. 05/07/2012  02:36 VM001012012-05-07T143038.vib Monday Incremental
4. 05/08/2012  02:36 VM001012012-05-06T143052.vib Tuesday Incremental
5. CheckDateValue()
6.

When CheckDateValue() reach next week Wednesday, the previous backup chain will be deleted entirely.

Non-Critical Virtual Machines:

The same applies to the non-critical virtual machines backup jobs, except those backup jobs are set to 1 for both values, Restore points to keep on disk:= 1 && Deleted VMs data retention period:= 1.

This will allow only one restore point on disk.

Symantec Backup Exec 2010 Configuration:

All traditional backup software, the well-known backup methods are Full, Incremental or Differential. With Symantec Backup Exec 2010 and Veeam Integration there is a caution in here to select which backup methods to use when you Backup the Veeam Images *.VBK or *.VIB files.

In Symantec when Full Backup is configured to backup Veeam Images it will Backup everything on the drive and will reset the file Archive Bits.

When Veeam Backup runs again and created a VIB file or VBK file and again Symantec Runs as Incremental against veeam files, only the last changed files will be backed up.

But, when Symantec Full backup runs against Veeam, it will backup everything on the drive, means all Full *.VBK Files along with all *.VIB files. This increase the possibility of taking long time to finish the backup as well as doubling the backup twice.

The best option in here to backup Veeam Image using Symantec is to set all the backup methods as Incremental with Reset-Archive-Bit including Daily, weekly and Monthly Backup.

Also, Since Veeam Backup & Replication doesn’t have the option to set a monthly Backup, the last Wednesday of Last Week in the month can be considered as monthly backup and again the Backup Method has to be Copy otherwise backup will not backup anything to tapes because the Archive-Bit has been reset already.

In my example, Wednesday is my CheckDateValue() that configured on the Veeam backup jobs. So, all previous chain will be deleted.


, , , , ,

12 Comments