Backup error with 8320

Just restore info from an 8310 to a used 8320.  Everything went fine.  Trying to update Blackberry software through the desktop program but says there is a backup error and to check that device is connected, which it is.  Then I just tried to backup info without updating the software and I get the same error.  I really need to be able to back up my phone.  I do not use the internet on it at all at this point.
Help asap
Thanks

Reboot the PC.
Do a simple reboot on the BlackBerry in this manner: With the BlackBerry device POWERED ON, remove the battery for a minute, and then reinsert the battery to reboot.
Now, connect again to USB cable to the PC and run the BlackBerry Desktop Software > Backup.
You might also try using the USB cable to connected to another main rear USB port on the PC, not a front USB and not a USB hub.
1. If any post helps you please click the below the post(s) that helped you.
2. Please resolve your thread by marking the post "Solution?" which solved it for you!
3. Install free BlackBerry Protect today for backups of contacts and data.
4. Guide to Unlocking your BlackBerry & Unlock Codes
Join our BBM Channels (Beta)
BlackBerry Support Forums Channel
PIN: C0001B7B4   Display/Scan Bar Code
Knowledge Base Updates
PIN: C0005A9AA   Display/Scan Bar Code

Similar Messages

  • Backup error with 6300, verify a .nbu file.

    Hi,
    I had a backup error when backing up my 6300 over USB using Nokia PC Suite (v. 6.84.10.3). Is there any way to examine a .nbu backup file to verify what has been backuped? I am worried the conatacts on my SIM did not be backed up properly. Otherwise how do I resolve or determine what the error was and what specifically did not get backed up?
    Many thanks.
    PS. Using Win 2000 (fully up to date with all SPs, etc).
    ..Message Edited by mattstan on 01-Aug-200710:21 PM

    when the backup finished, there's a log file describes the categories saved to pc.
    pc suite doesn't save those contacts on sim card. you can copy them to smart phonebook in flash then re-backup.
    to inspect the content of the .nbu, you can try noki (this thread: /discussions/board/message?board.id=pcsuite&message.id=13911).
    What's the law of the jungle?

  • N97 MINI V12 Backup error with Nokia Maps Beta 3.0...

    After installation nokia maps 3.06 beta on my fresh hardware reset n97 mini v12 is not possible to make backup from mobile to Memory card from File manager. Phone memory on C: is 220 MB.
    With nokia maps 3.04 backup is ok, with 3.06 error: Memory full, operation canceled (kind)
    I think firmware upgrade from v12 to v20 delay, the reason nokia maps 3.06 is not perfectly integred full functionaly in new firmware.

    have the same problem. I think its a bug in SW 12.. , after a hard reset it worked well until I installed some programs (incl. Maps 3.06). Backup only with PC or Ovi Suite able to do.
    Nokia N9 Black

  • RMAN Backup error with Symantec Backup Tool

    Hi
    My Environment
    OS Windows server 2003 R2
    Oracle 10G R2 10.2.03 2 node RAC
    When i am taking backup maually in the command prompt with RMAN, it is successful, but when we are trying from Symantec Backup tool we are getting errors like
    RMAN 03002 failur of Backup lus archivelog is problem,
    RMAN 10015 error compiling PL/SQL programme
    RMAN 10033 error during compilation of job step2
    Ora 00603 Oracle server session terminate by fatal error.
    Ora 004030 out of process memory when trying to allocate 4120 bytes(pl/sql) MPCODE,BAMMA, BAM Buffer)
    So please tell me why its giving the error with Symatntec and why when i am doing manually it is successfull.
    What could be the solution, please we are taking daily and weekly backups with Symantec on HP tape library. Please suggest me to the needful.
    Immediate reply highly apperciated
    Thanks
    Edited by: 873393 on Apr 17, 2012 10:09 AM

    Hello,
    Ora 00603 Oracle server session terminate by fatal error.
    Ora 004030 out of process memory when trying to allocate 4120 bytes(pl/sql) MPCODE,BAMMA, BAM Buffer) The ORA-04030 error message is interesting. It means that the OS doesn't have enough memory for Oracle.
    So you may monitore the Memory usage of the Server during the Symantec Backup, and check for any activity. May be the Symantec Backup runs when other Batch Jobs use already a lot of memory . You may also have to extend the RAM of the Server.
    Also, check for the RMAN script used by Symantec and compare with the "manual" script. May be, some options are used with Symantec and consume more resources on the Server.
    Hope this help.
    Best regards,
    Jean-Valentin

  • Db13 backup error with mssql as database

    Hi
    While scheduling the backup through db13 i got the following error msg.i mdoing the backup on disk
    Task information ***********                               
    Jobname:                                                               
    SAP CCMS Full DB Backup of DEV,master,msdb [20090825163455]            
    Taskname:  Step1                                                       
    Type:      TSQL                                                        
    DB-Name:   DEV                                                         
    Lastrun:   20090826 07:00:01                                           
    Nextrun:   not scheduled                                               
    Created:   2009-08-25 16:34:55.                                        
    Command:    dev.sap_backup_databases                                   
                 @dblist="DEV,master,msdb",@r3db="DEV",@bdev="db1          
               3 backup",@unload=0,@verify=0,@jobname= "SAP CCMS           
               Full DB Backup of DEV,master,msdb [20090825163455]          
    Descript: SAP CCMS JOB                                                                               
    Task history information ***********                       
    For run:   20090826 07:00:00                                           
    Status:    0          (failure)   (see DB error log)                   
    Message:   156                                                         
    Severity:  15                                                          
    Duration:  0 hours, 0 minutes, 0 seconds                               
    Duration:  0 hours, 0 minutes, 0 seconds                               
    Last msg:  Executed as user: NT AUTHORITY\SYSTEM. DBCC execut          
               ion completed. If DBCC printed error messages, con          
               tact your system administrator. [SQLSTATE 01000] (          
               Message 2528)  Incorrect syntax near the keyword '          
               WITH'. [SQLSTATE 42000] (Error 156).  The step failed.      
    i have set the  backup device name as db13 backup. is that the problem.                                                
    Plz help me

    Hi Pranav,
    Could you please tell us what was the issue so that if any body face the issue again then he will get help from this thread.
    Regards
    Ashok Dalai

  • Backup error with networker

    we have an error as below. does anyone know any clue for this?
    18594:nsrsapsv:/usr/sap/RMA/SYS/exe/run/brbackup is not a SAP Brtools command.
    18573:nsrsapsv:Running backup process as user rmaadm
    18560:nsrsapsv:spawning /usr/sap/RMA/SYS/exe/run/brbackup process as user rmaadm
    ld.so.1: brbackup: fatal: /oracle/client/10x_64/instantclient/libclntsh.so.10.1:
    Permission denied

    seems ok:
    -rwsr-srwx   1 orarma   dba      5361656 Oct 26  2006 brarchive
    -rwsr-srwx   1 orarma   dba      5521800 Oct 26  2006 brbackup
    -rwsrwxr-x   1 orarma   dba      7165688 Oct 26  2006 brconnect
    -rwxrwxr-x   1 orarma   dba      5854504 Oct 26  2006 brrecover
    -rwxrwxr-x   1 orarma   dba      2208576 Oct 21  2006 brrestore
    -rwxrwxr-x   1 orarma   dba      7381728 Oct 26  2006 brspace
    -rwsrwxr-x   1 orarma   dba      3158576 Oct 26  2006 brtools
    oracle client also seems to be ok..
    but i am still wondering about the error "brbackup is not BRtool".

  • TS1550 Time Machine backup error with LaCie hard drive

    When trying to backup in Time Machine to a new LaCie external hard drive, I get "Time Machine couldn’t complete the backup to “LaCie". The backup disk image “/Volumes/LaCie/(owner's name’s) MacBook Pro.sparsebundle” could not be accessed (error -1)."  Can anyone tell me what I need to do to fix this?  Do I need to erase and re-partition the LaCie hard drive?  Thanks.

    Hello,
    See if this from the late/great Pondini helps...
    http://pondini.org/TM/C17.html

  • Errors with Time Machine (not completing backup, and needing to erase the ".inProgress" package)

    I have in a previous discussion been talking about errors with my Time Machine backup.  The errors were with a problem with Indexing a file, it fails and stops the whole backup.  Each time it attemps another backup, it fills my ".inProgress" package with a (nearly) whole backup, filling my Time Machine hard drive, and thus errasing my previous good backups.  The error occurs after about 95% completion.
    In my last post of a similar disscussion, the problem was indexing the Preference Pane files and this caused the whole backup to fail.  This was my last post there:  (below in some additional info of my situation)
    I did exclude the MobileMe.prefPane.  And I got:
    12/16/11 9:24:50.468 PM com.apple.backupd: Starting standard backup
    12/16/11 9:24:50.556 PM com.apple.backupd: Backing up to: /Volumes/3 TB GoFlex Drive/Backups.backupdb
    12/16/11 9:25:14.418 PM com.apple.backupd: Waiting for index to be ready (101)
    12/16/11 9:27:02.366 PM com.apple.backupd: Deep event scan at path:/ reason:must scan subdirs|
    12/16/11 9:27:02.366 PM com.apple.backupd: Finished scan
    12/16/11 9:33:37.119 PM com.apple.backupd: Deep event scan at path:/Volumes/Mac OS Lion GM reason:must scan subdirs|
    12/16/11 9:33:37.119 PM com.apple.backupd: Finished scan
    12/16/11 9:36:15.650 PM com.apple.backupd: 758.92 GB required (including padding), 830.32 GB available
    12/16/11 10:25:14.873 PM com.apple.backupd: Copied 22.8 GB of 630.5 GB, 782749 of 2357620 items
    12/16/11 11:25:15.335 PM com.apple.backupd: Copied 86.6 GB of 630.5 GB, 1167675 of 2357620 items
    12/17/11 12:25:16.227 AM com.apple.backupd: Copied 152.2 GB of 630.5 GB, 1393795 of 2357620 items
    Dec 17 01:25:16 Thomas-P-Kellys-iMac com.apple.backupd[99858]: Copied 305.2 GB of 630.5 GB, 1413946 of 2357620 items
    Dec 17 02:25:16 Thomas-P-Kellys-iMac com.apple.backupd[99858]: Copied 457.1 GB of 630.5 GB, 1419190 of 2357620 items
    Dec 17 03:19:07 Thomas-P-Kellys-iMac com.apple.backupd[99858]: Copied 1736865 files (568.3 GB) from volume Macintosh HD.
    Dec 17 03:25:16 Thomas-P-Kellys-iMac com.apple.backupd[99858]: Copied 572.1 GB of 630.5 GB, 1848939 of 2357620 items
    Dec 17 03:40:33 Thomas-P-Kellys-iMac com.apple.backupd[99858]: Indexing a file failed. Returned 200 for: /Volumes/Mac OS Lion GM/System/Library/PreferencePanes/Mouse.prefPane, /Volumes/3 TB GoFlex Drive/Backups.backupdb/Tom iMac/2011-12-14-171406.inProgress/7DB524DD-EFB9-42A6-8A21-0A2A312EDA6D/Mac OS Lion GM/System/Library/PreferencePanes/Mouse.prefPane
    Dec 17 03:40:33 Thomas-P-Kellys-iMac com.apple.backupd[99858]: Aborting backup because indexing a file failed.
    Dec 17 03:40:33 Thomas-P-Kellys-iMac com.apple.backupd[99858]: Stopping backup.
    Dec 17 03:40:33 Thomas-P-Kellys-iMac com.apple.backupd[99858]: Copied 2164998 files (581.1 GB) from volume Mac OS Lion GM.
    Dec 17 03:40:33 Thomas-P-Kellys-iMac com.apple.backupd[99858]: Copy stage failed with error:11
    Dec 17 03:40:50 Thomas-P-Kellys-iMac com.apple.backupd[99858]: Backup failed with error: 11
    This time it was the Mouse.prefPane that caused the error.  I'd like to exclude the entire PreferencePanes directory.
    This was my error message this time:
    I just realized this was on my small Developers partition.  Perhaps there is an error with the build, OR an error with the initial restore.  I'd like to perhaps exclude the entire /Volumes/Mac OS Lion GM.  I expect that Time Machine is working fine with my main partition and the error happens when it's almost done with the Mac OS Lion GM partition.
    The problem now is that I only have 265 GB of 3 TB available on my Time Machine HDD.  If attempt another backup, it'll surely erase about 410 GB of my past saved backups.  I've already lost 6 months, and I only have two months left of backups.  I need to erase the ".inProgress" package again.  That'll take time, and it's impossible to do from this main partition, even at root access.  This ".inProgress" has a total of two (nearly) full backups; it didn't cleanup the first full backup attempt while starting the second,perhaps it would have had it finished.  But I fear even if I exclude the whole "Mac OS Lion GM" partition,  It'll create a third full backup before cleanup and erase ~400 GB of previous good backups.  Then, I'll have a total of 4 (nearly) full backups!  3 TB is just enough without any past backups.
    Maybe I'll just copy my documentations of my 'errasing the ".inProgress" package'  last time (from the Mac OS Lion GM partition) and do a full restore of just that partition.  Thus erasing the errors all together.  If it doesn't fix the errors then this could be a bug in the build that doesn't allow Time Machine to work.  I've always included this partition in Time Machine before, even with other Lion builds, so I suspect that it was an error in the initial restore.  (I may be answering my own questions, and that the inital restore (of the small partition) is the problem, and I just need to re-restore the small partition)
    Again, I'm going to have to erase the ".inProgress" file to regain 1.53 TB of space before proceeding.
    Also, I gave myself permission to read the ".Backup.345781513.887697.log", the log that was created last night when I first started Time Machine this last time.  It was interesting, but didn't show the error I could see from the console.
    Right now, mds and mdworker appear to be going crazy even after I just now turned off Time Machine.  I think I'll let it go for the rest of the night.  Then I'll work on erasing the ".inProgress" package from the other partition boot up.
    That was my entire last post.  To add some information, I have two OS X partitons, both Mac OS X Lion.  One is my large main partition, the other is one I don't mind testing with.  I recently replaced my internal hard drive in my iMac and restored from Time Machine both partitions.  This appeared to go smoothly.  But I have yet to create a single successful Time Machine backup since.  At first it was doing a Full Backup, which I didn't like, but now it just aborts around 95% completion.  Each, time, it tries it fills the Time Machine hard drive with duplicate (nearly) full backups errasing my older good backups.  I would like to erase the ".inProgress" file to save space.
    My main question in this new discussion is does anyone know of a good way of erasing the ".inProgress" file? This is so I can preseerve my previous backups.  ACLs and other permissions seem to make it impossible to erase from this startup partition, the one I'm running Time Machine from.  Even at root level, if I give myself permission to change permissions or delete a file, it'll say Operation not Permitted instead of Permission Denied.  I have been able to delete this ".inProgress" package before when booting from the other  partition, but with great difficulty.  I have had much help from another Member in this Support Community when it comes to solving my Time Machine problems.  I think I have found the problem (indexing files in my small OS X partition), as stated in my copy& pasted post above, but I really need to delete this inProgress package first to save space before continuing!

    Pondini wrote:
    Gator TPK wrote:
    Now I'll have to fix the small partition?  How's the best way to do this?  There could be thousands of files that won't index fine.
    See if there's anything you haven't done, that applies, in the pink box of #C3 in Time Machine - Troubleshooting
    Otherwise, since most (or all?) of the indexing errors are in OSX, you might want to just reinstall it.  Something may have gone wrong sometime, that damaged those files.
    I reviewed #C3 in Time Machine - Troubleshooting and I have already done most of those things.  I have just learned something new though:
    When I included my Main OS X partition again, I got an indexing error for the first time for that partition.  I might be interesting to note that the _spotlight process was running, and it's running again (the magnifying glass has a dot and it generically says "Indexing Tom's iMac").  mdworker, mds and backupd processes really are working hard, one moment they used over 500% of my CPU.  It's nice to know for once quad core is good for something other than video encoding.  (Now if they could just get the Finder to do more than 100.1%, only 1 thread is doing 100%, I'd like to see file size calculations 8 times quicker!)
    I never got an indexing error once in the past 2 weeks for that large Mac OS X v10.7.2 main volume, and it had appeared to finish that partition backup before running into problems with my smaller test partition.  Also, I had just updated the smaller test partition with a later build of Mac OS X.  But It appears that the beta builds are clearly not the problem.  I thought I could just restore again (from the December 4th backup) the small partition and both would be fine.
    I'll finish reviewing all the suggestions on Time Machine - Troubleshooting and go from there.  Hopefully, the _spotlight indexing simutaniously was the only problem.  It's strange that the indexing hasn't happened since the original restore last week untill I finally got a good clean complete partial Time Machine backup.  Why would the first Time Machine backup trigger indexing again?
    For now, I'm going to exclude the Main Partition again, and let another good backup run.  And try your suggestions.  (And wait till mds, mdworker, etc. to finish!)
    I have the logs of the first two sucsessful backups and the last two failed backups from the last 3 hours, if that would help.?

  • Windows 2008 R2 backup fails with event 521 error code 2155348001

    Windows Server 2008 R2 SP1.  Hyper-V role installed. 
    OS on drive C.  All VMs stored on Drive D.
    I am attempting to run a Bare Metal backup of the host system to a network share. 
    Drive D is not included in the backup job.  I am getting the following error:
    Log Name:      Application
    Source:        Microsoft-Windows-Backup
    Date:          1/10/2014 11:28:52 PM
    Event ID:      521
    Task Category: None
    Level:         Error
    Keywords:     
    User:          SYSTEM
    Computer:      SHAQTUS.scdl.local
    Description:
    The backup operation that started at '‎2014‎-‎01‎-‎11T04:08:50.683000000Z' has failed because the Volume Shadow Copy Service operation to create a shadow copy of the volumes being backed up failed with following error code '2155348001'. Please review the event
    details for a solution, and then rerun the backup operation once the issue is resolved.
    Reviewing event details, as suggested, does not offer any solution.
    I have tried the suggested solutions in other similar threads of increasing the timeout value with the registry entry. 
    This does not work.
    I have not tried reregistering the VSS writers manually, as the only links I have found are for server 2003/2008 (not R2) and explicitly state that they won’t work on higher versions of the OS, since they now utilize manifests and the manual procedure could
    cause problems for those servers. Haven't found similar procedures for 2008 R2.
    I have been able to narrow this down a bit.
    A Windows 2008 R2 SP1 server with Hyper-V installed – backup to a network share is successful;
    Install the DPM 2012 agent – same backup fails with the 2155348001 error.
    We use DPM 2012 to backup VMs, but DPM cannot perform a bare metal backup/restore of server and the 2012 version no longer has the DPMSRT feature. 
    I prefer to run Bare Metal Backup to a file server share.
    Stuck on this one.
    Rick

    Hi, 
    The issue is related to DPM, I would suggest you ask for help from DPM forums:
    http://social.technet.microsoft.com/Forums/en-US/home?forum=dataprotectionmanager
    Regards, 
    Mandy
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • BMR-SS backup fails with error "the specified network name is no longer available"

    We are running DPM 2012 SP1 on a Windows Server 2008 R2 system, backing up a Windows Server 2012 system that is a DC.  The agent version is 4.1.3417.0.  Both the DPM server and the DC are physical systems - brand new HP Proliant 360's.
    When creating the replicas for the 2012 server the first time, the backups work fine, and then for a day or so after that.  After a couple of days, the BMR-SS backups fail with the error "the specified network name is no longer available".  
    I can watch the backup happening in the Windows Server Backup console on the protected server - the BMR backup goes up to 99% and then fails.  BMR backups on all the other servers are working - we have a mix of Win2008R2 and Win2012. 
    Here is what I have tried:
    I can connect to the UNC path on the backup server without a problem during and after the backup is happening. 
    Tried reinstalling the DPM agent.
    Tried backing up directly from the protected server to another server's network share, which worked.
    I can copy multiple gigabyte files directly from the protected server to the DPM file share without a problem (the same one that DPM uses for the replica)
    Tried turning off the SCEP real-time protection during the backup.
    Any help would be appreciated - thanks.
    KW

    llo Boudewijn
    I followed Boudewijn's suggestion. 
    The Windows 2012R2 servers had no recovery partition in disk C. I created one (400MB) following http://support.microsoft.com/kb/2930294/en-us and
     DPM system restore worked. But just once. 
    So this is not the solution to the problem......
    Is no one else having issues with DPM bare metal protection of Windows 2012R2 servers? 

  • MAXDB backup failed with error: end of file reached -917

    Hi I am performing a complete data backup for a database which is about 230 GB.
    Previously it had run successfully for many days, but since yesterday, I began to receive such error:
    Error: end of file reached(-917)
    The backup stopped itself after running for 1 hour, and from backup history I just saw above error message.
    I also had a look at the logs, and found below, could someone help me look into this issue?
    Appreciate your kind help in advance!
    2008-11-25 22:08:09      0xBE4 ERR 52012 SAVE     error occured, basis_err 5750
    2008-11-25 22:08:09      0xBE4 ERR     3 Backup   Data backup failed
    2008-11-25 22:08:09      0xBE4 ERR     1 Backup    +   Backupmedium #1 (F:\Dbbackup\QAS_data_01) end of file reached
    2008-11-25 22:08:09      0xBE4 ERR     6 KernelCo  +   Backup error occured, Error code 5750 "write_task_crash"
    2008-11-25 04:00:27     0x16A0     52024 SAVE     30462712 pages -> "F:\DBbackup\QAS_DATA"
    2008-11-25 04:00:28     0x1BE4     19626 IO       Async I/O thread stopped, 'F:\DBbackup\QAS_DATA'
    2008-11-25 04:00:28     0x1FC4     19626 IO       Async I/O thread stopped, 'E:\sapdb\QAS\DAT_0001'
    2008-11-25 04:00:28     0x1688     19626 IO       Async I/O thread stopped, 'E:\sapdb\QAS\DAT_0002'
    2008-11-25 04:00:28     0x15D4     19626 IO       Async I/O thread stopped, 'E:\sapdb\QAS\DAT_0003'
    2008-11-25 04:00:28      0xAEC     19626 IO       Async I/O thread stopped, 'E:\sapdb\QAS\DAT_0004'
    2008-11-25 04:00:28     0x179C     19626 IO       Async I/O thread stopped, 'E:\sapdb\QAS\DAT_0005'
    2008-11-25 04:00:28      0xDD4     19626 IO       Async I/O thread stopped, 'E:\sapdb\QAS\DAT_0006'
    2008-11-25 04:00:28     0x1AE8     19626 IO       Async I/O thread stopped, 'E:\sapdb\QAS\DAT_0007'
    2008-11-25 04:00:28     0x176C     19626 IO       Async I/O thread stopped, 'E:\sapdb\QAS\DAT_0008'
    2008-11-25 04:00:28     0x11B8     19626 IO       Async I/O thread stopped, 'G:\sapdb\QAS\DAT_0009'
    2008-11-25 04:00:28     0x1B4C     19626 IO       Async I/O thread stopped, 'G:\sapdb\QAS\DAT_0010'
    2008-11-25 04:00:28     0x1F60     19626 IO       Async I/O thread stopped, 'G:\sapdb\QAS\DAT_0011'
    2008-11-25 04:00:35      0xB8C     52012 SAVE     ready
    2008-11-25 04:00:35      0xB8C     19651 CONNECT  Connection released, T113
    Thanks,
    vivian

    Hello Shaun,
    Thank you so much for your reply. But I've checked that my F drive still have more than 480GB free space, so the space should not be the problem.
    And I've just run the backup once again, this time it keeps running for 2 hours, and then failed again with the same error.
    Is there other possible reasons of this error?
    Thanks a lot,
    Vivian

  • Backup fail with VSSwriter error

    Hello,
    we currently are using Symantec Backup on tape and Windows Server Backup to make two differents backups on a SBS 2008.
    We are getting failed backup randomly during the week for both. Sometimes one is succeed and not the others.
    We have found several post about the VSS issues and how to fix it but nothing has changed.
    What we have done:
    - check the VSS writer and all is in "no error" state
    - check the settings of the backups
    - restart the VSS services
    - Configure the Shadow Copy on the drives
    - reboot the server
    - Tried several solutions from forums
    What we can see in the event viewer
    ID 12289
    "Volume Shadow Copy Service error: Unexpected error VSS_E_WRITER_STATUS_NOT_AVAILABLE. An older active writer session state is being overwritten by a newer session. The most common cause is that the number of parallel backups has exceeded the maximum
    supported limit.  hr = 0x80042409. 
    Operation:
       Aborting Writer
    ID 7001
    VssAdmin: Unable to create a shadow copy: The shadow copy provider had an error. Please see the system and application event logs for more information. 
    Command-line: 'C:\Windows\system32\vssadmin.exe Create Shadow /AutoRetry=15 /For=C:\'. "
    ID 12341
    Volume Shadow Copy Warning: VSS spent 75 seconds trying to flush and hold the volume \\?\Volume{c22d5d46-0540-11e0-9496-806e6f6e6963}\.  This might cause problems when other volumes in the shadow-copy set timeout waiting for the release-writes phase,
    and it can cause  the shadow-copy creation to fail.  Trying again when disk activity is lower may solve this problem. 
    Operation:
       Executing Asynchronous Operation
    Context:
       Current State: flush-and-hold writes
       Volume Name: \\?\Volume{c22d5d46-0540-11e0-9496-806e6f6e6963}\"
    Some will post the link of "how to troubleshoot VSSwriter issue": we have already used it.
    Does someone have a fresh idea about this issue ?
    Thanks in advance

    Hi Nerea,
    Before going further, would you please let me confirm if temporarily disable either of the two backup, will
    another backup operation run smoothly? In other words, if temporarily disable Symantec Backup, will Windows Server Backup always run successfully? Or if disable Windows Server Backup, will Symantec Backup always run successfully? Please check if Windows Server
    Backup conflicts with Symantec Backup.
    Based on the error message, please run
    chkdsk command and check if there is any issue in the disk. Then use
    Vssadmin resize shadowstorage to resizes the maximum amount of storage space that can be used for shadow copy storage. And check if this issue still persists.
    In addition, would you please let me know whether re-register Volume VSS components? If this issue still persists,
    please re-register and monitor the result.
    From command prompt:
    cd windows\system32
    Net stop vss
    Net stop swprv
    regsvr32 ole32.dll
    regsvr32 vss_ps.dll
    Vssvc /Register
    regsvr32 /i swprv.dll
    regsvr32 /i eventcls.dll
    regsvr32 es.dll
    regsvr32 stdprov.dll
    regsvr32 vssui.dll
    regsvr32 msxml.dll
    regsvr32 msxml3.dll
    regsvr32 msxml4.dll
    net start swprv
    net start vss
    By the way, did the Symantec Backup and Windows Server Backup run at the same time? Or before one backup finished,
    had another backup started?
    Hope this helps.
    Best regards,
    Justin Gu

  • Backup failed with Error: (-50) Creating Directory

    Repeats ad nauseum.
    This is backing up to a second internal drive that is an exact duplicate (in terms of HD model and size).
    Does anyone know what Error -50 means? Lack of permissions? Invalid name (doesn't seem like it)?
    8/30/08 9:06:37 AM /System/Library/CoreServices/backupd Starting standard backup
    8/30/08 9:06:37 AM /System/Library/CoreServices/backupd Backing up to: /Volumes/Sliffy Time/Backups.backupdb
    8/30/08 9:06:58 AM /System/Library/CoreServices/backupd Error: (-50) Creating directory 2008-08-30-090658.inProgress
    8/30/08 9:06:58 AM /System/Library/CoreServices/backupd Failed to make snapshot container.
    8/30/08 9:07:03 AM /System/Library/CoreServices/backupd Backup failed with error: 2

    Hi Glenn,
    Thanks for the suggestion. Nope, it's not listed. The only thing listed is my Time Machine volume.
    After a reboot, Time Machine seems to be working. It's making backups on schedule and the logs look good, not reporting any strangeness.
    A bit bummed about these phantom errors that go away on reboot. I'll keep on eye on the error/reboot frequency.
    Rob

  • Backup Fails with Invalid RECID Error

    Hi All,
    Please help me to understand Caution -section
    below text is from
    [http://download.oracle.com/docs/cd/B10501_01/server.920/a96566/rcmtroub.htm#447765]
    Backup Fails with Invalid RECID Error: Solution 2
    This solution is more difficult than solution 1:
    To create the control file with SQL*Plus:
       1. Connect to the target database with SQL*Plus. For example, enter:
          % sqlplus 'SYS/oracle@trgt AS SYSDBA'
       2. Mount the database if it is not already mounted:
          SQL> ALTER DATABASE MOUNT;
       3. Back up the control file to a trace file:
          SQL> ALTER DATABASE BACKUP CONTROLFILE TO TRACE;
       4. Edit the trace file as necessary. The relevant section of the trace file looks something like the following:
          # The following commands will create a new control file and use it
          # to open the database.
          # Data used by the recovery manager will be lost. Additional logs may
          # be required for media recovery of offline data files. Use this
          # only if the current version of all online logs are available.
          STARTUP NOMOUNT
          CREATE CONTROLFILE REUSE DATABASE "TRGT" NORESETLOGS  ARCHIVELOG
          --  STANDBY DATABASE CLUSTER CONSISTENT AND UNPROTECTED
              MAXLOGFILES 32
              MAXLOGMEMBERS 2
              MAXDATAFILES 32
              MAXINSTANCES 1
              MAXLOGHISTORY 226
          LOGFILE
            GROUP 1 '/oracle/oradata/trgt/redo01.log'  SIZE 25M,
            GROUP 2 '/oracle/oradata/trgt/redo02.log'  SIZE 25M,
            GROUP 3 '/oracle/oradata/trgt/redo03.log'  SIZE 500K
          -- STANDBY LOGFILE
          DATAFILE
            '/oracle/oradata/trgt/system01.dbf',
            '/oracle/oradata/trgt/undotbs01.dbf',
            '/oracle/oradata/trgt/cwmlite01.dbf',
            '/oracle/oradata/trgt/drsys01.dbf',
            '/oracle/oradata/trgt/example01.dbf',
            '/oracle/oradata/trgt/indx01.dbf',
            '/oracle/oradata/trgt/tools01.dbf',
            '/oracle/oradata/trgt/users01.dbf'
          CHARACTER SET WE8DEC
          # Take files offline to match current control file.
          ALTER DATABASE DATAFILE '/oracle/oradata/trgt/tools01.dbf' OFFLINE;
          ALTER DATABASE DATAFILE '/oracle/oradata/trgt/users01.dbf' OFFLINE;
          # Configure RMAN configuration record 1
          VARIABLE RECNO NUMBER;
          EXECUTE :RECNO := SYS.DBMS_BACKUP_RESTORE.SETCONFIG('CHANNEL','DEVICE TYPE DISK
          DEBUG 255');
          # Recovery is required if any of the datafiles are restored backups,
          # or if the last shutdown was not normal or immediate.
          RECOVER DATABASE
          # All logs need archiving and a log switch is needed.
          ALTER SYSTEM ARCHIVE LOG ALL;
          # Database can now be opened normally.
          ALTER DATABASE OPEN;
          # Commands to add tempfiles to temporary tablespaces.
          # Online tempfiles have complete space information.
          # Other tempfiles may require adjustment.
          ALTER TABLESPACE TEMP ADD TEMPFILE '/oracle/oradata/trgt/temp01.dbf' REUSE;
          # End of tempfile additions.
       5. Shut down the database:
          SHUTDOWN IMMEDIATE
       6. Execute the script to create the control file, recover (if necessary), archive the logs, and open the database:
          STARTUP NOMOUNT
          CREATE CONTROLFILE ...;
          EXECUTE ...;
          RECOVER DATABASE
          ALTER SYSTEM ARCHIVE LOG CURRENT;
          ALTER DATABASE OPEN ...;
    Caution:
          If you do not open with the RESETLOGS option,
    then two copies of an archived redo log for a given log sequence number may
    exist--even though these two copies have completely different contents.
    For example, one log may have been created on the original host and the other on the new host.
    If you accidentally confuse the logs during a media recovery,
    then the database will be corrupted but Oracle and RMAN cannot detect the problem.

    Please help me to understand Caution -section
    Caution:
    If you do not open with the RESETLOGS option,
    then two copies of an archived redo log for a given log sequence number may
    exist--even though these two copies have completely different contents.
    For example, one log may have been created on the original host and the other on the new host.
    If you accidentally confuse the logs during a media recovery,
    then the database will be corrupted but Oracle and RMAN cannot detect the problem.As per my understanding it says. If you don't open database with RESETLOGS option then there may be archived logs with log sequence number which is already archived on the source host. This may happen due to difference in RECIDs. Now when the database needs media recovery for this particular log sequence, you may provide any of them. So in this case, RMAN and Oracle will not be able to differentiate the two files and can accept any of the archived log files during recovery. Since the contents of two archived logs are different, because they are generated at different times and they contains different transactions. So, internally it corrupts your database.
    Rgds.

  • Bare metal restore of full server backup fails with RPC error 0x800706BA (server 2012)

    With Windows Server 2012, after creating a successful windows server backup (full server), I am unable to do a bare metal restore of the system.
    EFI System Partition, C:, D: are the volumes on a single array (Raid 5).
    Loading WinRE and launching re-image, the full server restore stops after completing the C: restore just after beginning the D: drive restore (data volume) with the error with the message about RPC error 0x800706BA, unavailable.
    The system will not boot as a result of the failure. 
    What may be causing this?
    [edit]
    I think I have two things working against me here... one, Volume Shadow Copy service wasn't running in WinPE and two.. the D: volume contains data deduplication.
    I think this is causing some of my problems.
    Is there an additional service that I need to start in WinPE to get a volume that was deduplicated restored perhaps using wbadmin?

    Hi,
    Thanks for the reply Shaon.
    The hardware system is identical; however, I am increasing storage capacity from 12TB to 16TB.  Basically, the system is the same, just new hard drives (4x4TB versus 4x3TB).  Drives are all identical enterprise class drives and I am actually using
    the same system (backup, swap drives then restore).
    I tried both using the WinRE restore (re-image) with the backup set, and tried using wbadmin.  Both produce same RPC unavailable messages (although using the GUI based tool via WinRE provides the additional error code #).
    I do not have any idea what to look at to try to figure this one out.
    [edit]
    I was just informed of this posting:
    http://social.technet.microsoft.com/Forums/windowsserver/en-US/147efccc-e0e9-4458-852e-c3a44ae5cb64/the-system-image-restore-failed-error-details-he-rpc-server-is-unavailable-0x800706ba?forum=windowsbackup
    and in my case, this lab server does in fact act also as a DC as well as a file server...  do I need to spin up a secondary controller (perhaps in a VM on another machine) to do this restore?

Maybe you are looking for