Rick_Krieger_-_
Level 3
Joined 19 years ago
User Profile
User Widgets
Contributions
Re: archive and backup scheduling
No problem... everyone is entitled to an opinion.. ;) re: Safety copies and pending shortcuts... I understand the issue with users seeing pending shortcuts but if the backup strategy is designed and managed properly (mentioned previously - backup Exchange, Archive, Backup Enterprise Vault and this occurs during typical off-hours)... then users should not see pending shortcuts - unless they are working in the middle of the night or something like that.857Views0likes0CommentsRe: archive and backup scheduling
Provides more/better recovery options... - After Exchange backup... if you have failure of EV, restore EV. - After archiving run (with safety copies) ...if you have failure of EV, restore EV and perform another archiving run. - After archiving run (without safety copies)... if you have failure of EV, restore Exchange, restore EV, then perform another archiving run. IMHO... I would choose options that involve 'not' having to restore my real time messaging environment. Also... adding safety copies does not delay moving the data from Exchange to the Vault... during the archive run EV will copy these items to the vault. With safety copies enabled it will only delay when it will actually delete them from Exchange and create the shortcuts in their place. (i.e. after the vault store is backed up.) Also... the way I see it... you don't have multiple copies of the mailbox in the scenario we are discussing... you would have one... the most recent exchange backup... (unless you were doing a brick level backup or something like that as well as an IS backup.) If you have the resources and backup window then... why not configure your vault stores to use safety copies? Throw in Centera as your primary storage device as your primary storage that you have to replicate (instead of backing up) or implement snapshots of your EV data then safety copies becomes more important. If you don't have the resources/backup window, don't see the risk of losing EV in that short time window as a likely/significant risk (which, admitedly is marginal) and/or still think safety copes are dumb.. then rock on.859Views0likes0CommentsRe: archive and backup scheduling
What Tony said... plus I would add the following commentary... The new scheme you mentioned would be the better way to go... Configure your Vault Stores to remove 'Safety Copies... 'After Backup' and... configure your overall schedule so you Backup Exchange, then archive, then backup the archive data (as you mentioned.) Doing it in this order (with safety copies) ensures that you have multiple copies of data before things are deleted and gives you more recovery options. IMHO I would do all of this as 'Full' backups every night (if possible) to simply the restore process. Also, make sure you are doing the 'backup the archive data' part properly... which should contain at the very very minimum... 3 things... EV databases in SQL, indexes and vault stores. All three should be backed up while the storage service is in read only mode. You should also be backing up things like program files, MSMQ, registry/system state, PST Holding Temp, Shopping, etc. Refer to the backup in the Admin Guide as Tony suggested for more info.859Views0likes0CommentsRe: Vault Rights
On a fresh install of EV... even the vault service account (VSA) doesn't have permissions to search other archives... (i.e. if you are logged into the ev server and you right click a user archive under archives... you won't see the "search archives" item at the top of the context menu unless you go to 'permissions' first and add the VSA and give it at least read permissions. Maybe you have a policy where everyone has reviewer permissions on everyones calendar? if so then everyone would have access to some portion of everyones archve (i.e. the calendar data.) so... the would show up in the list. If you can see other peoples archives right off the bat then something else is going on.176Views0likes0CommentsRe: Vault Store - reporting
Make sure the short name and fqdn for each of the following are added to the trusted sites in the Local Intranet Zone on each EV Server in the environment: EV Server (i.e. ev1 and ev1.yourdomain.com) Vault alias (i.e. vault1 and vault1.yourdomain.com) Vault site alias (i.e. vaultsite1 and vaultsite1.yourdomain.com) so... if you have one EV server in your environment it would be 6 entries per EV server...if you have 2 EV servers... it would be 10 entries per EV server. Hope this helps, Rick105Views0likes0CommentsRe: Exchange 2000 OWA Extension Install Problem (2147217895)
Couple quick things to try... Make sure you have a replica of the schema-root in a public folder on the exchange server you are running the script on (or at least on a server in your admin group / site.) Run the script with just the /dnsdomain:nthp.org switch. Run the script with nothing specified.1.2KViews0likes0CommentsRe: EV System Mailbox
One EV System Mailbox per Exchange Server you are archiving from. Don't use it for anything else Don't mailbox enable the vault service account and use it as an EV system mailbox Best bet is to create them manually. It's a requirement and not sure if there is a way around it... but since MS is not charging by the mailbox I wouldn't worry about it too much. :) Rick208Views0likes0CommentsRe: NTFS to Centera migrator
Your license key requires an "FTC" license item which would look something like this: # Component: OSL Legacy Migrator FEATURE FTC ............... I just did some digging around and confirmed that this is now bundled/included with the base EV 6.0 product. Just tell your sales rep that you need an "OSL Legacy Migrator" license key and that it is now part of the product (was a separate charge in EV 5.0) If you and/or your sales rep are in a bind then you could probably get by with a temp key (which includes the OSL Legacy Migrator license item) but I'd recommend getting a permanent key in case your migration activities go beyond the temp key period. Hope this helps, Rick216Views0likes0Comments