11-26-2009 10:53 AM
11-27-2009 01:43 AM
11-27-2009 06:24 AM
Thanks for your response.
Checking my jobs NO Advanced Open File option is not enabled.
I think that the problem is indeed as you have pointed out, that I have created the RSG, on a different group. Where I suppose I was (am) confused is that I did create a RSG on the NEW server in the "OLD" storae group but could not restore to it.
The answer that Im slowly coming to is that if you are physically on the NEW server and create a RSG on the OLD group its not actually storing the files on the NEW server but back on the OLD server, which in my case does not have enough space. (thus it fails) I thought that if I created the RSG on the NEW server in the OLD GROUP through the Exchange Sys Mang. that it would put the files on the NEW SERVER. The added proof of this is that if I create the RSG on the NEW SERVER in the OLD group and then right click on the RSG and click on it and select properties and click Browse I get an error.
This option is available only if the Exchange System Manager runs on the server on which the files are located. ID no: c1038af4, Exchange System Manager
Which I think means that I cant access the files because they are not physically on the computer that Im currently on.
I have asked elseware and they have confirmed that if you create a RSG that it resides on the computer that has the original "production" db. At lease this seems to be true.
Can anyone confirm this?
My alternative is to add a spare drive to the production system and then point the RSG to that drive since the production system does not have enough space for 27 gigs of the RSG.
So one of my added question is, why does Backup exec talk about redirecting a RSG when you really cant do it, or at least why would you?
11-27-2009 07:18 AM
RSG's are usually used in order to get back a small number of lost mailboxes or messages - an RSG is not used for recovery of a complete server.
Microsoft (I believe) came up with the RSG concept as before RSGs were available to restore one message or mailbox - you had to build a complete offline Exchange server to do it - which from experience (with Exchnage 5.5) was a real pain as you also had to have a copy of your Domain and a backup server in the offline environment to do the restore.
Brick Level backups were also possible (but could be exceedingly slow) that allowed you to get at mailbox content. and restore it. As well as being slow you also had to run an information store backup separately as the Brick Level backup was difficult to use in a DR situation wher you have lost the whole server..
BackuP Exec 9.1 supported both Brick Level and RSG processes.
Symantec (in newer versions of Backup Exec) then came up with a Granular Restore Technology (GRT) that allowed you to do ONLY an Information Store backup, but restore individual mail messages or mailboxes as needed. If you are trying to formulate a recovery scenario I would suggest you actually consider updating your spftware to use the GRT ability (especially as 9.1 is no longer subject to support or development. Bear in mind that GRT works best if disk storage is used for the BackuP Media (with duplication to tape if you need offsite storage)
With regards the RSG itself - the Microsoft artilces that I linked earlier do seem to imply that you can create an RSG on a different server (but in the same administrative group) and restore to it - unfortunately I have not seen anyone try this with any version of Backup Exec.
I have seen an RSG process work with Backup Exec where the RSG iis on the original mail server.
11-27-2009 08:21 AM
Job ended: November 27, 2009 at 10:34:36 AM Completed status: Failed Final error: 0xa0008488 - Access is denied. Final error category: Security Errors Restore - \\EXCHANGE\Microsoft Information Store\First Storage Group
Access denied to database Mailbox Store (EXCHANGE). Error writing file data. Access denied to database Mailbox Store (EXCHANGE). Error writing file data. In the restore the Resource Credentials of the job the System logon account is the account used. This is the administrator. The error thankfully is obvious, the resolving it a little more cryptic for me.