Forum Discussion

Corako's avatar
Corako
Level 2
9 years ago

Move Archive - Failing

Hello,

 

I'm running EV version 10 and I'm trying to move some archives from one vault store to another. As part of my testing, I am trying to move some inactive users to validate the process. Everything seemed to be going pretty smoothly until yesterday (we did need to reconfigure and test some backup settings for the new vault store). Everything is now failing during any step of the process (I have archives in each step 1 through 5). New test move archive operations also fail on all copy operations when I start it until the process fails after 50 attempts.

The archive logs are not helpful, this is the error description.

An internal failure occurred. Internal Error: 'Unspecified error  (0x80004005)'.

Error code: 80040306

My initial thought was maybe something was stuck in backup mode, but I checked everything and that is not the case. I also re-created the move archive with the following process (keep in mind these are not active users, so there is no new writes going to the 'new' archive').

1. After the move archive operation fails, I delete the operation.

2. I Delete the 'new archive'

3. Rename the original archive (remove the date appended to the end)

4. Create new move archive operation  

Would someone be able to point me where I should look next? I seem to be out of options and I'm really stumped as to why this is all failing now.

 

  • Think I may have found the culprit, but it's just a theory for now.

    EV is running on W2K8R2 and has virtual hardware version 7. I added the disks the same day as the new vault stores were created while the system was online. At somepoint I believe the disks went offline due to the policy in the following article:

    http://www.happysysadm.com/2010/11/disk-is-offline-because-of-policy-set.html

    I'm not able to confirm if the disks were offline prior to the reboot because I never looked. I only noticed that the disks were offline following the most recent reboot.

     

5 Replies

  • i found a couple previous posts on the same topic. can you see if they help?

    https://www-secure.symantec.com/connect/forums/how-tell-ev-move-archive-not-be-fussy-when-moving

    https://www-secure.symantec.com/connect/forums/problems-error-when-moving-archive

    https://www-secure.symantec.com/connect/forums/ev-move-between-sites-failes

  • I found an option to run a trace against the Move Archive process, a snippet of which I have copied below. It looks like it can't find the file it's trying to copy? When I manually go into the directory, I am able to find the file.

    182    13:55:45.898     [3376]    (StorageOnlineOpns)    <10276>    EV:M    Reading part from: \\<Removed>\backup\<Removed>\EV\Enterprise Vault Stores\Exchange Ptn3\2014\12-04\0\08E\008E3D5E4E16D4CF48325D38BFBB55D1.DVS
    183    13:55:45.898     [3376]    (StorageOnlineOpns)    <10276>    EV:L    {EVCommandExecutor::ExecuteCommand} (Entry)
    184    13:55:45.898     [3376]    (StorageOnlineOpns)    <10276>    EV:L    {OpenStreamOnFileCommand::Execute} (Entry)
    185    13:55:45.898     [3376]    (StorageOnlineOpns)    <10276>    EV:H    {CEVByteStream::OpenStreamOnFile:#139} _com_error exception: [The specified network name is no longer available.  (0x80070040)]
    186    13:55:45.899     [3376]    (StorageOnlineOpns)    <10276>    EV:H    {OpenStreamOnFileCommand::Execute:#250} _com_error exception: [The specified network name is no longer available.  (0x80070040)]
    187    13:55:45.899     [3376]    (StorageOnlineOpns)    <10276>    EV:H    {OpenStreamOnFileCommand::Execute} (Exit) Status: [The specified network name is no longer available.  (0x80070040)]
    188    13:55:45.899     [3376]    (StorageOnlineOpns)    <10276>    EV:L    {EVCommandExecutor::ExecuteRecoverWithRetry} (Entry)
    189    13:55:45.899     [3376]    (StorageOnlineOpns)    <10276>    EV:L    {EVCommandExecutor::ExecuteRecoverWithRetry} (Exit) Status: [Success]
    190    13:55:46.149     [3376]    (StorageOnlineOpns)    <10276>    EV:L    {StorageCommandExecutor::Sleep:#29} Sleep 250 milliseconds.
    191    13:55:46.149     [3376]    (StorageOnlineOpns)    <10276>    EV:L    {OpenStreamOnFileCommand::Execute} (Entry)
    192    13:55:46.149     [3376]    (StorageOnlineOpns)    <10276>    EV:H    {CEVByteStream::OpenStreamOnFile:#139} _com_error exception: [The specified network name is no longer available.  (0x80070040)]
    193    13:55:46.149     [3376]    (StorageOnlineOpns)    <10276>    EV:H    {OpenStreamOnFileCommand::Execute:#250} _com_error exception: [The specified network name is no longer available.  (0x80070040)]
    194    13:55:46.149     [3376]    (StorageOnlineOpns)    <10276>    EV:H    {OpenStreamOnFileCommand::Execute} (Exit) Status: [The specified network name is no longer available.  (0x80070040)]
    195    13:55:46.150     [3376]    (StorageOnlineOpns)    <10276>    EV:L    {EVCommandExecutor::ExecuteRecoverWithRetry} (Entry)
    196    13:55:46.150     [3376]    (StorageOnlineOpns)    <10276>    EV:L    {EVCommandExecutor::ExecuteRecoverWithRetry} (Exit) Status: [Success]
    197    13:55:46.400     [3376]    (StorageOnlineOpns)    <10276>    EV:L    {StorageCommandExecutor::Sleep:#29} Sleep 250 milliseconds.
    198    13:55:46.400     [3376]    (StorageOnlineOpns)    <10276>    EV:L    {OpenStreamOnFileCommand::Execute} (Entry)

  • what changes exactly did you make to the system before it stopped working?

  • Hi,

    This ended up affecting everything on the EV server, so it wasn't just my migrations. EV stopped being able to access its storage (which is up and running fine, we have other hosts accessing it).

    I added a new vault store group and vault store (this would have also created databases). The error is temporarily resolved by rebooting the EV server.

    Here's what's strange:

    The system returns the error:

    \\<systename>\backup\company\EV\Enterprise Vault Stores\Exchange Ptn3\2014\07-20\0\166"

    Reason: The specified network name is no longer available.  (0x80070040)   Operation: READ   Reference: CVaultStoreVolume::OnOffLineStatus     

    If I try to access that same file on my machine, it works. If I manually browse to the file on the EV server it also works only if I start at the root (\\<systemname>).

    My only theory now is that it is something during the migration process. The memory and CPU are being heavily utilized (90%+). Reviewing the event logs shows that it suddenly starts. I guess I'll try rebooting again and adding more resources.

     

  • Think I may have found the culprit, but it's just a theory for now.

    EV is running on W2K8R2 and has virtual hardware version 7. I added the disks the same day as the new vault stores were created while the system was online. At somepoint I believe the disks went offline due to the policy in the following article:

    http://www.happysysadm.com/2010/11/disk-is-offline-because-of-policy-set.html

    I'm not able to confirm if the disks were offline prior to the reboot because I never looked. I only noticed that the disks were offline following the most recent reboot.