it consultant collaboration

8 Topics

How to migrate email archiving to Exchange mailboxes (cross-forest) without archiving?
I need information about how to migrate or move the email archiving EV to mailboxes in Exchange 2013 without archiving in cross-forest topology. The versions of EV they are varied EV8 and EV11. I can use Transvault Migrator tool but I dont know if it's posible that the target mailbox this is a mailbox without archiving, and if it's posible in cross-forest topology.
Solved
Roberto_Fernand
10 years ago Place Enterprise Vault
1.5KViews
0likes
7Comments
The Enterprise Vault Storage Service service could not be stopped.
Hi all, We have scheduled a job to run on every thursday to restart EV services Enterprise vault task controller service, Enterprise vault storage service Enterprise vault directory service, Enterprise vault indexing service, Enterprise vault Admin service, This scheduled job will first stop the services and then it will start the services. While stopping the task from "Task controller to Admin service", I am getting error in Storage service while stopping as "The Enterprise Vault Storage Service service could not be stopped". But while i monitoring event in server the "Enterprise vault storage" service was stopped successfully but in log file am getting this error message. could you please assist me to solve this issue.
Solved
vinoth_SR
10 years ago Place Enterprise Vault
1.9KViews
0likes
5Comments
Enterprise Valut
Symantec Vault facing problem while deleting mail of journaling database it is saying error "you are no authorized
Solved
Mohankumar_K
14 years ago Place Enterprise Vault
922Views
0likes
3Comments
EV Design Question with Exchange 2010 DAG running over MAN
Hi guys, would like some feedback (pros/cons) of a design I'm putting together for a customer who's going to be having Exchange 2010 run in two geographical locations. They have two physical locations for Exchange 2010 connected by a high-speed MAN (Metro Area Network). Each site has 4 Exchange mailbox servers for a total of 8 servers - all of which are in the same DAG. They want to be able to fail an Exchange DB from any server to any other server, even over the MAN. I had originally designed the EV environment with two completely separate directories, one in each location, to archive just the 4 local Exchange servers, and thus generate no traffic over the MAN from archiving or journaling. The plan was to set up an archiving task for each Exchange server in the local site, but also an archiving task for each Exchange server in the remote site in case a local Exchange database were to fail over the MAN to a remote Exchange server, we could still archive/restore from it. I then went through the "Setting up Exchange Server Archiving" guide, and saw a blurb in there that all members of a DAG must be archived by EV servers in one EV site. I wanted to know if we carefully provisioned users in each EV directory (based on their Exchange database), so that no users would be accidentally archived by the remote EV servers in the other directory if it failed over, if we can in fact use two separate directories to process the one DAG that spans the MAN. I'm concerned that I may be missing or not thinking of a side effect of doing this. Just wanted to find out why we need to use one EV site as per the guide, as in this case, it will generate a LOT of network traffic if we do have just one EV site processing both the local and remote Exchange servers. I'd also like to make sure I'm not designing something that won't be supported by Symantec Support. Any and all advice is appreciated. Thanks Dan
Solved
Pending_Shortcu
14 years ago Place Enterprise Vault
761Views
0likes
2Comments
File Cluster Instance Failover takes more than 5 minutes after installing placeholder service
File Cluster Instance Failover takes more than 5 minutes after installing (case 414-736-536) - customer has a windows 2008 2-node (active-active) file cluster - there are several instances on the cluster - moving an instance normally takes approx. 30 seconds - after installing the fsa agent and creating the resources, move takes about 8 minutes - in cluster administration we see the placeholder service keeps running, after 8 minutes it is (forcefully by the system??) shut down - checked http://www.symantec.com/business/support/index?page=content&id=TECH135458&actp=search&viewlocale=en_US&searchid=1306156703078 --> we do not have any GPT disks in the cluster we do not see any event viewer entries no entries in cluster log any ideas? has anyone see this before?
fho
14 years ago Place Enterprise Vault
875Views
0likes
6Comments
EV9 - Move Archive and Vault Cache sync
All, We have just concluded a large PST migratio project in which we added a number of additional EV servers to help with the ingestion of PST files. We now want to move the archives back to the original EV servers. We are using EV 9.0.2 and determined that there is no vault store migration available. If we use 'Move Archive' then we have to go through numerous steps listed in the forum posts to get the vault cache to sync again. Would these 2 options below be the best that we can do as of now? 1. Move the vault store partition to the original server by modifying the storage service entry, partition root path entries and index volume locations? 2. Use USL to decommission the extra servers and change the DNS and perform a recovery on the original servers to now host vault stores, storage and index services. Thanks
Solved
Mark_Clardy-USA
14 years ago Place Enterprise Vault
566Views
0likes
1Comment
Migrating Placeholders
Notes: Migrating off a celerra to a netapp filer 36 mil placeholders on celerra, need to avoid recall 20tb of other customer data identity swap between the source and the destination need the smallest possible migration window hoping fsautility can perform incremental/differential copy (for a small cutover window) A customer is looking to migrate off of a celerra to a netapp filer. We are considering the fsautility for this, however, we are concerned about the items listed above. Can someone comment on how fsa would address any of these concerns and if there are guides & best practice notes available online? Thank you Questions -do we have the ability to perform a incremental/differential with fsautility? -does the fsautility have to modify the placeholder and the ev database to migrate -how do customers typically go about migrating these, is there mandatory (lengthy) outage window or are there tricks to doing it right? -if the ev server is just pointing to the celerra storage via a drive letter, does this migration become much easier? Is it just a matter of replicating the placeholders to a new drive letter and upon cutover, assign the old drive letter to the new storage? Thanks in advance if anyone can assist ;) -daniel
dpesposito
14 years ago Place Enterprise Vault
754Views
0likes
3Comments
Move archive problem between two EV 9.0.1 MS cluster servers in same site
If I try to move archive over Move Archive Task from store on one MS cluster EV 9.0.1 to store on second MS cluster 9.0.1 in same site is visible follow error message: Could not create the destination archive. Enterprise Vault will try again later unless the retry count has been reached. Exception: Exception thrown while creating/getting the destination archive. The move will not occur. CM API error code: 0x80040306. CM API error: An internal failure occurred. Internal Error: 'Catastrophic failure [0x8000ffff]'.. Inner storage error code: 0x8000ffff. Inner storage error description: Catastrophic failure . If I try move archive on first cluster but to new store on this cluster is all without any problem.
Solved
Ivos
14 years ago Place Enterprise Vault
603Views
0likes
2Comments