SCE Backup fail with Version 3.6.5 Build 489

Hello,
I upgraded my SCE 2020 and now can't do a subscriber backup on local Disk
Subscriber backup failed on SCE 2020 Version 3.6.5 Build 489:
sce#>conf
sce(config)#>interface LineCard 0
sce(config if)#>subscriber export csv-file subsback.csv
0 subscriber(s); 0 error(s)
sce(config if)#>
But I have 1298 subscribers !!!
sce#>show interface linecard 0 subscriber all-names
There are 1298 subscribers in the data-base:
N/A
subscriber1
subscriber2
subscriber3
subscriber1298
sce#>
(These commands worked well with old Firmare 3.5.0 Build 407).
Any idea about the problem ?  It's a new Bug ?
Thanks for comments.
Best regards.
Seb

Hi,
This is Shelley from Cisco TAC. I support the SCE.
This is a bug and was identified a few weeks ago. I would like you to open a TAC case so that we can track and monitor user affected by this bug. Once you open the case, we will provide you with the Bug ID as well (at this time it is internal hence cannot share)
Hope this answers your query.(Please mark complete if so and rate.)
Shelley Bhalla
CCIE #20002
Cisco TAC - Carrier services

Similar Messages

  • 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? 

  • 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.

  • TM Backup failed with error: 11 -  when copying Movie, image, music files

    TM giving backup errors (for a long time unsolved until I read forum entry about monitoring events with Console prog.) Recently upgraded from 10.5.4 to 10.5.6 with Combo package (attempts at upgrade to 10.5.5 failed with "unknown error")
    I narrowed down to the file types listed by excluding relevant erring folders. TM backup works OK now but without Movies, Photos, Music and small number of applications that appear to fail mainly on copying an image within appl.
    Using Console with "backupd" filter on LOG FILES/system.log (while executing TM backup) gives the following 4 samples of errors:
    1. Dec 21 02:20:03 Macintosh /System/Library/CoreServices/backupd[1627]: Starting standard backup
    Dec 21 02:20:05 Macintosh /System/Library/CoreServices/backupd[1627]: Backing up to: /Volumes/MacBook Backup/Backups.backupdb
    Dec 21 02:20:06 Macintosh /System/Library/CoreServices/backupd[1627]: Event store UUIDs don't match for volume: Macintosh HD
    Dec 21 02:20:06 Macintosh /System/Library/CoreServices/backupd[1627]: No pre-backup thinning needed: 64.44 GB requested (including padding), 129.33 GB available
    Dec 21 02:22:31 Macintosh /System/Library/CoreServices/backupd[1627]: Error: (-36) SrcErr:YES Copying /Users/xxxxx/Movies/iMovie Events.localized/New Event 07-04-2008 2/clip-2008-04-07 11;30;45.mov to (null)
    Dec 21 02:22:32 Macintosh /System/Library/CoreServices/backupd[1627]: Error: (-36) SrcErr:NO Copying /Users/xxxxx/Movies/iMovie Events.localized/New Event 07-04-2008 2/clip-2008-04-07 11;30;45.mov to /Volumes/MacBook Backup/Backups.backupdb/............
    2. Dec 21 02:25:23 Macintosh /System/Library/CoreServices/backupd[1627]: Starting standard backup
    Dec 21 02:25:23 Macintosh /System/Library/CoreServices/backupd[1627]: Backing up to: /Volumes/MacBook Backup/Backups.backupdb
    Dec 21 02:25:24 Macintosh /System/Library/CoreServices/backupd[1627]: Event store UUIDs don't match for volume: Macintosh HD
    Dec 21 02:25:24 Macintosh /System/Library/CoreServices/backupd[1627]: No pre-backup thinning needed: 64.44 GB requested (including padding), 126.79 GB available
    Dec 21 02:27:46 Macintosh /System/Library/CoreServices/backupd[1627]: Error: (-36) SrcErr:YES Copying /Users/xxxxx/Music/iTunes/iTunes Music/Duck Baker, Maggie Boyle and Ben Paley/The Expatriate Game--Traditional Irish & American Music/07 Rye Whiskey.m4a to (null)
    3.Dec 21 13:17:28 Macintosh /System/Library/CoreServices/backupd[1768]: No pre-backup thinning needed: 6.26 GB requested (including padding), 120.05 GB available
    Dec 21 13:21:11 Macintosh /System/Library/CoreServices/backupd[1768]: Error: (-36) SrcErr:YES Copying /Applications/AApplications Extra/Investor programs/StockXloader.app/Contents/Resources/StockXloaderName.tif to (null)
    Dec 21 13:22:03 Macintosh /System/Library/CoreServices/backupd[1768]: Error: (-36) SrcErr:YES Copying /Applications/AApplications Extra/Investor programs/Stox.app/Contents/MacOS/Stox to (null)
    Dec 21 13:22:31 Macintosh /System/Library/CoreServices/backupd[1768]: Error: (-36) SrcErr:YES Copying /Applications/AApplications Extra/Investor programs/Stox.app/Contents/Resources/help/Stox Manual_files/image002.png to (null)
    Dec 21 13:23:07 Macintosh /System/Library/CoreServices/backupd[1768]: Error: (-36) SrcErr:YES Copying /Applications/AApplications Extra/Investor programs/Stox.app/Contents/Resources/help/Stox Manual_files/image033.png to (null)
    Dec 21 13:23:31 Macintosh /System/Library/CoreServices/backupd[1768]: Error: (-36) SrcErr:YES Copying /Applications/AApplications Extra/Investor programs/Stox.app/Contents/Resources/help/Stox Manual_files/image060.png to (null)
    Dec 21 13:24:09 Macintosh /System/Library/CoreServices/backupd[1768]: Error: (-36) SrcErr:YES Copying /Applications/AApplications Extra/Investor programs/Stox.app/Contents/Resources/help/Stox Manual_files/image120.png to (null)
    Dec 21 13:27:29 Macintosh /System/Library/CoreServices/backupd[1768]: Error: (-36) SrcErr:YES Copying /Applications/AApplications Extra/Unproven /EyeTV.app/Contents/MacOS/EyeTV to (null)
    Dec 21 13:27:53 Macintosh /System/Library/CoreServices/backupd[1768]: Error: (-36) SrcErr:YES Copying /Applications/AApplications Extra/Unproven /EyeTV.app/Contents/Resources/authopen to (null)
    Dec 21 13:28:17 Macintosh /System/Library/CoreServices/backupd[1768]: Error: (-36) SrcErr:YES Copying /Applications/AApplications Extra/Unproven /EyeTV.app/Contents/Resources/Device Pictures/CinergyDTXS.png to (null)
    Dec 21 13:28:42 Macintosh /System/Library/CoreServices/backupd[1768]: Error: (-36) SrcErr:YES Copying /Applications/AApplications Extra/Unproven /EyeTV.app/Contents/Resources/Device Pictures/CinergyTExpress.fscaled.png to (null)
    Dec 21 13:29:07 Macintosh /System/Library/CoreServices/backupd[1768]: Error: (-36) SrcErr:YES Copying /Applications/AApplications Extra/Unproven /EyeTV.app/Contents/Resources/Device Pictures/ElgatoDiversity.fscaled.png to (null)
    4. Dec 21 14:44:46 Macintosh /System/Library/CoreServices/backupd[1858]: Starting standard backup
    Dec 21 14:44:48 Macintosh /System/Library/CoreServices/backupd[1858]: Backing up to: /Volumes/MacBook Backup/Backups.backupdb
    Dec 21 14:45:50 Macintosh /System/Library/CoreServices/backupd[1858]: No pre-backup thinning needed: 2.11 GB requested (including padding), 116.67 GB available
    Dec 21 14:46:18 Macintosh /System/Library/CoreServices/backupd[1858]: Error: (-36) SrcErr:YES Copying /Applications/iWork '08/Keynote.app/Contents/Frameworks/BGCompatibility.framework/Versions/A/BGComp atibility to (null)
    Dec 21 14:46:18 Macintosh /System/Library/CoreServices/backupd[1858]: Error: (-36) SrcErr:NO Copying /Applications/iWork '08/Keynote.app/Contents/Frameworks/BGCompatibility.framework/Versions/A/BGComp atibility to /Volumes/MacBook Backup/Backups.backupdb/xxxxxxx’s MacBook/2008-12-21-131514.inProgress/58F99FC2-7474-42C9-8DCA-5C99F724CE6E/Macin tosh HD/Applications/iWork '08/Keynote.app/Contents/Frameworks/BGCompatibility.framework/Versions/A
    Dec 21 14:46:18 Macintosh /System/Library/CoreServices/backupd[1858]: Stopping backup.
    Dec 21 14:46:18 Macintosh /System/Library/CoreServices/backupd[1858]: Error: (-8062) SrcErr:NO Copying /Applications/iWork '08/Keynote.app/Contents/Frameworks/BGCompatibility.framework/Versions/A/BGComp atibility to /Volumes/MacBook Backup/Backups.backupdb/xxxxxx’s MacBook/2008-12-21-131514.inProgress/58F99FC2-7474-42C9-8DCA-5C99F724CE6E/Macin tosh HD/Applications/iWork '08/Keynote.app/Contents/Frameworks/BGCompatibility.framework/Versions/A
    Dec 21 14:46:18 Macintosh /System/Library/CoreServices/backupd[1858]: Copied 52 files (26.7 MB) from volume Macintosh HD.
    Dec 21 14:46:18 Macintosh /System/Library/CoreServices/backupd[1858]: Copy stage failed with error:11
    Dec 21 14:46:24 Macintosh /System/Library/CoreServices/backupd[1858]: Backup failed with error: 11

    solongpc wrote:
    Regardless if this is a general problem or not, does anyone know of any documentation/release notes for common/generic TM error codes? That would be helpful.
    Yeah, many of us would love it! But no such thing exists, at least not that us mere mortals can find.
    There might be another variable that I don't understand right now but at least it is consistent.
    Could it be something funky in the name of one of the folders? Or could the folder object itself be corrupt? Or have some odd extended attribute?
    All I can suggest is calling AppleCare, and/or reporting it as a bug:
    *_Submitting a +Bug Report+ to Apple._*
    |
    This requires a membership in the +Apple Developer Connection,+ but you can get one for free.
    Register here: http://developer.apple.com/programs/start/register/create.php
    Once you receive the confirmation, go to: https://bugreport.apple.com and login.
    Click +New Problem+ at the top.
    Click Help at the top, and/or any of the items underlined in blue for more information.
    Provide as much specific detail as possible, and attach a log, screenshot, etc., as appropriate in the lower section.
    When done, click Submit at the bottom.

  • 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

  • Online Backup Failed with error-BR0268E Asynchronous execution of program..

    Hi,
    We are using DB13 for Online backup.But from few days it failing with below error.
    BR0268E Asynchronous execution of program interrupted, exit status: c0000094
    BR0267E Asynchronous execution of program failed
    BR0278E Command output of 'F:\usr\sap\QE2\SYS\exe\uc\NTAMD64\mkszip -c F:\ORACLE\QE2\SAPDATA4\SR3_22\SR3.DATA22 >
    Can someone please help on this issue? Thanks in advance.
    Regards,
    Kiran M

    Hi,
    Check below threads.
    BRbackup problem on new system
    Offline backup failed with BR0253E errno 13: Permission denied
    BR0268E Asynchronous execution of program interrupted, exit status: c000009
    Thanks,
    Sushil
    Edited by: Sushil Suryawanshi on May 28, 2009 8:16 PM

  • Backup failed with error: 11 -Error: (-41) SrcErr:NO Copying

    Like many of you, I was unlucky to get the famous TimeMachine error message: "The backup was not performed because an error occurred while copying files to the backup disk". I started to get as much help as I could from Google and all your forum posts.
    Until recently I could not get an easy answer and it seemed that various people had success by:
    - renaming their machine to remove say extraneous characters (such as apostrophe)
    - delete the last "in progress" backup
    - reset the TM
    - etc.
    I did all of that plus reformatting my new WD HDD but nothing changed. After 2 days of frustration with this piece of software (Time Machine), the good news for me is that I can consistently reproduce the error as well succeed in performing a backup. The solution for me seems to make sure that I +*do not have a source directory structure deeper than 15 levels*+. As soon as I have a file that is 16 levels deep from the root of the HDD that I try to backup, I get this error:
    +*Error: (-41) SrcErr:NO Copying /Volumes/<HDD to Backup>/<Deep Directory Structure>... to*+
    +*/Volumes/<Your TM Drive>/Backups.backupdb/<Your Machine>/<Timestamp>.inProgress/<AutoGenerated-GUID>/<HDD to Backup>/<Deep Directory Structure>...*+
    +*Copy stage failed with error:11*+
    +*Backup failed with error: 11*+
    The Console app shows the system log with the path to the file that failed during backup. I tried to make the pathname shorter than 255 characters to make sure this is not an 8bit limitation of some string length in the code. Even if I have a path shorter than 255 characters, TM fails with the above error when the source files are at least 16 levels deep in the directory structure.
    What is most frustrating about this is not the careless and uninformative error message or this apparently non-sense limitation of 15 levels - it might be something historical in Apple's code - but the lack of documentation. In the absence of proper logging and error handling in this piece of code, wouldn't be nice to have some explanation from Apple with regards to what this error #11 means or perhaps what caused this "Error (-41) SrcErr:NO Copying"? I guess most of us would be just fine to know that as per release notes, Apple has this limitation of 15 levels for the source directory structure.

    solongpc wrote:
    Regardless if this is a general problem or not, does anyone know of any documentation/release notes for common/generic TM error codes? That would be helpful.
    Yeah, many of us would love it! But no such thing exists, at least not that us mere mortals can find.
    There might be another variable that I don't understand right now but at least it is consistent.
    Could it be something funky in the name of one of the folders? Or could the folder object itself be corrupt? Or have some odd extended attribute?
    All I can suggest is calling AppleCare, and/or reporting it as a bug:
    *_Submitting a +Bug Report+ to Apple._*
    |
    This requires a membership in the +Apple Developer Connection,+ but you can get one for free.
    Register here: http://developer.apple.com/programs/start/register/create.php
    Once you receive the confirmation, go to: https://bugreport.apple.com and login.
    Click +New Problem+ at the top.
    Click Help at the top, and/or any of the items underlined in blue for more information.
    Provide as much specific detail as possible, and attach a log, screenshot, etc., as appropriate in the lower section.
    When done, click Submit at the bottom.

  • Backups fail with Insufficient privileges error

    Oracle 9.2.0.5 database
    Solaris Operating Sysstem
    I needed to recreate one database recently from the backup. I used DUPLICATE TARGET DATABASE comamand to recreate database. And once client confirmed I removed old database and copied this new database to original location and recreated controlfile.
    But the tape backups are failing ever since then.
    Is it because of password file problems ? This is a a totally new database and also DBID is different . But database name is same and created from backups of old database.
    Backups fail with this error.
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    ORA-01031: insufficient privileges
    But the RMANUSER has the same privileges as in other databases on this server.
    SQL> select username,sysdba,sysoper from v$pwfile_users;
    USERNAME SYSDB SYSOP
    SYS TRUE TRUE
    RMANUSER TRUE FALSE
    SQL> select privilege from dba_sys_privs where grantee='RMANUSER';
    PRIVILEGE
    CREATE SESSION
    UNLIMITED TABLESPACE
    How to resolve this issue ?

    I actually recreated the password file using orapwd utility. But when checked the V$PWFILE_USERS it showed no users. Not even SYS
    And I tired to grant SYSDBA to RMANUSER. It failed with the following error.
    ERROR at line 1:
    ORA-01999: password file mode has changed from 'exclusive' to 'shared'
    But the show parameter REMOTE showed that remote_login_passwordfile is still EXCLUSIVE. And database uses an INIT file, not SPFILE.
    I had to move back the copy of Old password file and now it shows two users (SYS and RMANUSER) again.

  • Backups failing with error 19: the backup disk could not be resolved, or there was a problem mounting it

    Hello all,
    Doubt this issue relates to a recent and ugly issue but sharing anyways (resolved thanks to a user here: LaPastenague)
    Time Capsule won't backup if Modem (Motorola SB6121) attached
    This was on Feb 10th resolved. Few days later I upgraded to Yosemite.  Backups were working fine since.  
    Yesterday I happen to notice my last backup was 5 days ago.  I looked in the console logs and saw:
    2/25/15 3:55:06.127 PM com.apple.backupd[2777]: Attempting to mount network destination URL: afp://Paul;AUTH=SRP@Time%20Capsule._afpovertcp._tcp.local./Data
    2/25/15 3:55:17.778 PM com.apple.backupd[2777]: NAConnectToServerSync failed with error: 2 (No such file or directory) for url: afp://Paul;AUTH=SRP@Time%20Capsule._afpovertcp._tcp.local./Data
    2/25/15 3:55:17.792 PM com.apple.backupd[2777]: Backup failed with error 19: The backup disk could not be resolved, or there was a problem mounting it.
    2/25/15 3:57:18.808 PM com.apple.prefs.backup.remoteservice[2021]: Attempt to use XPC with a MachService that has HideUntilCheckIn set. This will result in unpredictable behavior: com.apple.backupd.status.xpc
    I called Apple.  Their front line was clueless. He suggested resetting the TC (latest "tower" model btw") which then a backup kicked off YEAH
    But the next hour it failed
    Called Apple again, this time to Sr Advisor.  He suggested factory reset of the TC and set up again.  Also first backup worked then rest failed
    Third call to Apple useless also.  He was asking questions I didn't feel relevant.  He also was asking me to reset the TC which I told him was done 2 hours prior. He asked me to reboot which I could NOT at that time.
    I begged him to collect data to submit to engineering, which will take days to get a reply.
    So I thought I would throw this out to the community....
    TC Is NEW (replaced from last issue).  Mac is 8 months old (iMac 27"), Os is Yosemite,  TC also new (latest model)
    Thanks...

    Yosemite is problematic on two fronts.. Networking and Time Machine.. so the combo of doing both with a Time Capsule is like bugs on bugs.
    Here is my standard list.. but your problem maybe difficult to resolve.. and my suggestion is simple.. until Apple get their act together and fix TM.. buy Carbon Copy Cloner and use that for your backup. It is solid and reliable.. even better if you use USB drive plugged into the computer and do a bootable clone.. because then you have a backup that is able to be tested for full functionality 2min after the end of the backup.
    This also starts from a factory reset.. but the reason for it is to change the configuration which is much more easily handled with factory reset to begin.. the instructions are there.. because this is my standard reply.. this is not uncommon!!
    Factory reset universal
    Power off the TC.. ie pull the power cord or power off at the wall.. wait 10sec.. hold in the reset button.. be gentle.. power on again still holding in reset.. and keep holding it in for another 10sec. You may need some help as it is hard to both hold in reset and apply power. It will show success by rapidly blinking the front led. Release the reset.. and wait a couple of min for the TC to reset and come back with factory settings. If the front LED doesn’t blink rapidly you missed it and simply try again. The reset is fairly fragile in these.. press it so you feel it just click and no more.. I have seen people bend the lever or even break it. I use a toothpick as tool.
    N.B. None of your files on the hard disk of the TC are deleted.. this simply clears out the router settings of the TC.
    Setup the TC again.
    ie Start from a factory reset. No files are lost on the hard disk doing this.
    Then redo the setup from the computer with Yosemite.
    1. Use very short names.. NOT APPLE RECOMMENDED names. No spaces and pure alphanumerics.
    eg TCgen5 and TCwifi for basestation and wireless respectively.
    Even better if the issue is more wireless use TC24ghz and TC5ghz with fixed channels as this also seems to help stop the nonsense. But this can be tried in the second round.
    2. Use all passwords that also comply but can be a bit longer. ie 8-20 characters mixed case and numbers.. no non-alphanumerics.
    3. Ensure the TC always takes the same IP address.. you will need to do this on the main router using dhcp reservation.. or a bit more complex setup using static IP in the TC. But this is important.. having IP drift all over the place when Yosemite cannot remember its own name for 5 min after a reboot makes for poor networking. If the TC is main router it will not be an issue.
    4. Check your share name on the computer is not changing.. make sure it also complies with the above.. short no spaces and pure alphanumeric.. but this change will mess up your TM backup.. so be prepared to do a new full backup. Sorry.. keep this one for second round if you want to avoid a new backup.
    5. Mount the TC disk in the computer manually.
    In Finder, Go, Connect to server from the top menu,
    Type in SMB://192.168.0.254 (or whatever the TC ip is which you have now made static. As a router by default it is 10.0.1.1 and I encourage people to stick with that unless you know what you are doing).
    You can use name.. SMB://TCgen5.local where you replace TCgen5 with your TC name.. local is the default domain of the TC and doesn't change.
    However names are not so easy as IP address.. nor as reliable. At least not in Yosemite they aren't. The domain can also be an issue if you are not plugged or wireless directly to the TC.
    6. Make sure IPv6 is set to link-local only in the computer. For example wireless open the network preferences, wireless and advanced / TCP/IP.. and fix the IPv6. to link-local only.
    There is a lot more jiggery pokery you can try but the above is a good start.. if you find it still unreliable.. don't be surprised.
    You might need to do some more work on the Mac itself. eg Reset the PRAM.. has helped some people. Clean install of the OS is also helpful if you upgrade installed.
    Tell us how you go.
    Someone posted a solution.. See this thread.
    Macbook can't find Time Capsule anymore
    Start from the bottom and work up.. What I list here is good network practice changes but I have avoided Yosemites bug heaven.
    This user has had success and a few others as well.
    RáNdÓm GéÉzÁ
    Yosemite has serious DNS bug in the networking application.. here is the lets say more arcane method of fixing it by doing a network transplant from mavericks.
    http://arstechnica.com/apple/2015/01/why-dns-in-os-x-10-10-is-broken-and-what-yo u-can-do-to-fix-it/

  • Backup fails with System writer error

    Hi,
    We have a networker backup solution in place. Backup fails on one of the windows 2012 server. Event log below. I am not sure how to resolve this issue. Can someone please help?
    Log Name:      Application
    Source:        VSS
    Date:          6/17/2014 5:01:41 PM
    Event ID:      8193
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      ---
    Description:
    Volume Shadow Copy Service error: Unexpected error calling routine GetVolumeNameForVolumeMountPoint is now failing on the volume, winerror 0x00000005. .  hr = 0x80070005, Access is denied.
    Operation:
       PrepareForSnapshot Event
    Context:
       Execution Context: Writer
       Writer Class Id: {e8132975-6f93-4464-a53e-1050253ae220}
       Writer Name: System Writer
       Writer Instance ID: {13f27935-f32a-4e30-bdb6-d87894cecf12}
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="VSS" />
        <EventID Qualifiers="0">8193</EventID>
        <Level>2</Level>
        <Task>0</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2014-06-17T15:01:41.000000000Z" />
        <EventRecordID>4864</EventRecordID>
        <Channel>Application</Channel>
        <Computer>
        <Security />
      </System>
      <EventData>
        <Data>GetVolumeNameForVolumeMountPoint is now failing on the volume, winerror 0x00000005. </Data>
        <Data>0x80070005, Access is denied.
    </Data>
        <Data>
    Operation:
       PrepareForSnapshot Event
    Context:
       Execution Context: Writer
       Writer Class Id: {e8132975-6f93-4464-a53e-1050253ae220}
       Writer Name: System Writer
       Writer Instance ID: {13f27935-f32a-4e30-bdb6-d87894cecf12}</Data>
        <Binary>2D20436F64653A20565353415049435030303030313131332D2043616C6C3A20565353415049435030303030313035372D205049443A202030303030303434302D205449443A202030303030313539362D20434D443A2020433A5C57696E646F77735C73797374656D33325C737663686F73742E657865202D6B204E6574776F726B53657276696365202020202020202D20557365723A204E616D653A204E5420415554484F524954595C4E4554574F524B20534552564943452C205349443A532D312D352D3230</Binary>
      </EventData>
    </Event>

    Hi,
    in my case, I didn't have "System Writer" shown in the Writers list. I tried everything to put it up and running, but without any luck. I even tried re-registering writers, which was a bit risky, but that didn't help either.
    Then I have found this hotfix, installed it, and it worked after it.
    Anyway, you can find here on technet few topics about this particular issue. For the others, something else worked. Please, take a look:
    http://social.technet.microsoft.com/Forums/windowsserver/en-US/f4c7fb5b-162a-4c75-994c-b75fbd1dece7/vss-system-writer-is-missing
    http://social.technet.microsoft.com/Forums/windowsserver/en-US/4458947a-623e-45c1-b8e4-868aad1e93b0/missing-vss-system-writer-and-capi2-error-in-event-log?forum=winserverfiles
    https://kb.acronis.com/content/45776#Win2008 - pay attention what is for 2003 and what for 2008, you can end up with broken system
    http://social.technet.microsoft.com/Forums/windowsserver/en-US/764791ff-ecb5-4716-9f1c-9e22852e0f6b/resolved-backup-failing-on-server-2008-r2-system-writer-missing?forum=windowsbackup
    http://social.technet.microsoft.com/wiki/contents/articles/7309.backup-fails-with-error-message-writer-missing-or-failed-or-timed-out-or-waiting-for-completion-in-vssadmin.aspx
    You can try all of this (I did), but this hotfix saved my day in the end.
    Hope this helps.
    If this helped you resolve your issue, please mark it Answered, thanks! Kind regards

  • What to do about Backup failed with error: The target volume is read-only

    This is a weird story. My wife has a PowerBook G4/1.33 GHz that she uses in clamshell mode with a 20" Cinema Display. One day under OS X 10.5.6, her Time Machine backups (to a networked 500 GB Time Capsule) failed with the error: Backup failed with error: The target volume is read-only. So I upgraded her to 10.5.7 and erased the sparseimage file, starting a new Time Machine backup. And it just happened again. Any idea how this sort of problem arises? My wife was doing something at her computer when the Time Machine error occurred.
    Please don't advise us to upgrade to 10.5.8, because her PowerBook freezes not infrequently with any OS later than 10.5.6, and I was just about to downgrade her from 10.5.7 to 10.5.6.

    Pondini wrote:
    odysseus wrote:
    This is a weird story. My wife has a PowerBook G4/1.33 GHz that she uses in clamshell mode with a 20" Cinema Display. One day under OS X 10.5.6, her Time Machine backups (to a networked 500 GB Time Capsule) failed with the error: Backup failed with error: The target volume is read-only. So I upgraded her to 10.5.7 and erased the sparseimage file, starting a new Time Machine backup. And it just happened again.
    Try repairing the sparse bundle, per #A5 of the Time Machine - Troubleshooting *User Tip,* also at the top of this forum.
    I've tried this before, but it can't be repaired, because it can't be mounted.
    Any idea how this sort of problem arises? My wife was doing something at her computer when the Time Machine error occurred.
    One possibility is, the HD in the Time Capsule is beginning to fail (all HDs fail, sooner or later).
    I'm backing up to my own sparseimage bundle just fine.
    Please don't advise us to upgrade to 10.5.8, because her PowerBook freezes not infrequently with any OS later than 10.5.6, and I was just about to downgrade her from 10.5.7 to 10.5.6.
    Those two things may be related. Whatever's going wrong may very well be what's corrupting the backups.
    I'd recommend finding out what's wrong with the Powerbook. It's impossible to tell, of course, but that may be the root of the problem.
    There's a problem with PowerBooks and Cinema Displays. I've posted a lot about this. Even after a motherboard replacement, my PowerBook G4/1.67 GHz had freezes, and eventually Apple gave me a MacBook Pro, but I think there's a failure involving hardware/software design.
    If you haven't yet, I'd start by dong a +*Verify Disk+* on it's internal HD (also per #A5);
    That checks out fine.
    if there are no errors, or they're fixed and the problem continues, run the +Apple Hardware Test+ from the disc that came with the Mac. (One of the discs should have that, and instructions for running it, printed in tiny type on the label).
    If still no help, I'd be inclined to do an +Archive & Install, preserving users & settings,+ of Leopard, then download & install the appropriate "combo" update. That's a combination (thus the clever name) of all the updates to Leopard since it was first released, so installing it should fix anything that's gone wrong since then, such as with one of the normal "point" updates. Info and download available at: http://support.apple.com/downloads/MacOS_X_10_5_8_ComboUpdate (change the last "8" to the desired number). Be sure to do a +Repair Permissions+ via Disk Utility (in your Applications/Utilities folder) afterwards.

  • Time Machine Backup Failed with error: 2

    I have been doing unattended continuous backups to a 1 TB drive for about 4 months via Time Machine. In the last 2 months I have been getting a dialog box with this message: "Unable to complete backup. An error occurred while creating the backup directory." In each case I have gone to Disk Utility to repair the disk, and each time have had to reboot to get the Repair Disk function to work, since without a reboot, the backup disk won't unmount. After repair, the backups resume, but the frequency of the failures is beginning to worry me. I never had problems with scheduled SuperDuper backups and am thinking of returning to that approach, albeit different.
    Below is what is listed in in the system log after the backup failure. It lists "error: 2", whatever that is.
    The backup disk has over 400GB space remaining.
    Can anyone help me with this?
    May 2 19:34:17 Macintosh /System/Library/CoreServices/backupd[12497]: Backup requested by user
    May 2 19:34:17 Macintosh /System/Library/CoreServices/backupd[12497]: Starting standard backup
    May 2 19:34:26 Macintosh /System/Library/CoreServices/backupd[12497]: Backing up to: /Volumes/WD1TB Backup Disk/Backups.backupdb
    May 2 19:34:28 Macintosh /System/Library/CoreServices/backupd[12497]: Error: (-50) Creating directory 2008-05-02-193428.inProgress
    May 2 19:34:28 Macintosh /System/Library/CoreServices/backupd[12497]: Failed to make snapshot container.
    May 2 19:34:28 Macintosh /System/Library/CoreServices/backupd[12497]: Backup failed with error: 2
    Thanks,
    Art

    Betty - actually, no. Rebooting alone didn't resolve the problem. Time Machine still wouldn't resume backups.
    Once the directory was rebuilt via Disk Utility, it is up and running again, at least for a while.

  • Time Machine. Backup failed with error code: 21

    Hi,
    I recently upgraded to Leopard 10.5.4 mainly for the time machine backup. I'm using a DNS-323 in a RAID1 configuration as the TM backup drive. Also I have the DNS-323 connected to my Airport Extreme through the ethernet to give NAS ability to my home network.
    After much hunting around the forums I got the sparsebundle created and copied to the DNS-323 share volume. See http://www.flokru.org/2008/02/29/time-machine-backups-on-network-shares-in-leopa rd/ My thanks to flokru.
    However, TM is still not working. The console messages have the following:
    Network mountpoint /Volume/Volume_1 not owned by backupd... remounting
    Network volume mounted at /Volume/Volume11
    Failed to mount disk image /Volume/Volume1_1/MacBook001b6334c307.sparebundle
    Backup failed with error: 21
    It would appear this error lies in the way TM is trying to mount the volume, specifically that Volume_1, the DNS-323 volume name, is not owned by TM. TM then tries to create a new volume, Volume11 and stick the sparebundle on it.
    Is there a way of making TM "own" the volume, Volume_1?
    Has anybody else seen this error or better yet, got a fix for it?

    James,
    It would appear this error lies in the way TM is trying to mount the volume, specifically that Volume_1, the DNS-323 volume name, is not owned by TM. TM then tries to create a new volume, Volume11 and stick the sparebundle on it.
    Is there a way of making TM "own" the volume, Volume_1?
    Actually, it is not TMs failure to mount the volume that is causing your failure to backup. I have received the same Console message using a Time Capsule. However, Time Machines' attempt to 'remount' the volume always succeeds and the backup goes through. That appears not to be your experience, but it is NOT because the volume is not being mounted. It is.
    *Mount Point Conflict (TMDisk-1)*
    NOTE: the following distinguishes “network drive” (the physical hard disk) from “disk image” (the sparsebundle file TM uses to backup to).
    First of all, I am convinced that the second mount point that is created (in your case Volume11) is due to the fact that you already had the network drive mounted on your desktop at the time of the attempted backup. Was that the case?
    When you manually mount a network drive the system creates a mount point in the /Volumes folder (Let’s call it TMDisk ). While that exists any attempt by Time Machine to mount the same disk will created a second mount point ( TMDisk-1 )
    Nevertheless, as I have observed, this doesn't seem to prevent backups from taking place successfully, at least on the Time Capsule. And according to your Console logs it appears that your volume is being ‘remounted’ successfully.
    *”The Backup Disk Image Could Not Be Mounted”*
    The real issue is Time Machines' failure to mount the disk image (sparsebundle) contained on your network drive.
    +Failed to mount disk image /Volume/Volume1_1/MacBook001b6334c307.sparebundle+
    +Backup failed with error: 21+
    More often than not this is due to having the Time Machine backup disk image (sparsebundle) mounted on your desktop during a backup attempt.
    Eject the backup disk image (sparsebundle) by either clicking the little Eject icon to the right of the disk image in the Finders’ Sidebar, or Ctrl-Click the drive icon on the desktop and select “Eject” from the contextual menu. Now try backing up again or launching Time Machine to view previous backups.
    For more information, see an article on this here:
    [http://discussions.apple.com/thread.jspa?threadID=1715977]
    Alternatively, a backup disk image can fail to mount if there is a problem with your computer name.
    *Proper Computer Name* #
    Make sure your computer has a proper name. Go to System Preferences --> Sharing. Time Machine needs to differentiate your computer from others on your network (i.e. "Bills MacBook" or "Office iMac"). If the "Computer Name" field is blank, create a name. Realize that if this step is necessary, you will likely have to start the Time Machine backup process over again and do another full initial backup.
    According to THIS article [http://support.apple.com/kb/TS1760], Time Machine may experience problems if your computer name includes certain characters. Make sure the computer name only includes ASCII characters from the following set.
    (0123456789abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ)
    Once a change in the computer name occurs, you should stop and restart Sharing on the affected computer. Uncheck and then recheck Sharing in the Services list on the left.
    Let me know if any of this helps.
    Cheers!

  • Time Machine backup failed with error 11 (RAID Slice)

    Disk Utility Verified OK and I have erased and started again. I'm still getting intermittent failed errors with my RAID set up (it's been happening more often as the weeks progressed). Is it possible one my Time Machine drives (shown below) are just going bad?
    Here's the Console log report:
    3/5/14 3:15:00 PM
    com.apple.backupd[1073]
    Starting standard backup
    3/5/14 3:15:00 PM
    com.apple.backupd[1073]
    Backing up to: /Volumes/PGXRAID-02/Backups.backupdb
    3/5/14 3:15:28 PM
    com.apple.backupd[1073]
    No pre-backup thinning needed: 879.0 MB requested (including padding), 845.06 GB available
    3/5/14 3:15:28 PM
    com.apple.backupd[1073]
    Waiting for index to be ready (100)
    3/5/14 3:15:41 PM
    com.apple.backupd[1073]
    Copied 633 files (15 KB) from volume Photo-Grafix.
    3/5/14 3:15:57 PM
    Typinator[212]
    re-enabling tap: -2, times=(0.000, 0.000, 0.000, 0.000, 0.000)
    3/5/14 3:16:13 PM
    com.apple.backupd[1073]
    Error: (-36) SrcErr:NO Copying /Users/macprouser01/.dropbox/sigstore.dbx to /Volumes/PGXRAID-02/Backups.backupdb/MacProAdmin’s Mac Pro/2014-03-05-083503.inProgress/0D116102-5F8A-47C0-9D79-C4C78E2B1EF8/Mecca/Use rs/macprouser01/.dropbox
    3/5/14 3:16:13 PM
    com.apple.backupd[1073]
    Stopping backup.
    3/5/14 3:16:13 PM
    com.apple.backupd[1073]
    Error: (-8062) SrcErr:NO Copying /Users/macprouser01/.dropbox/sigstore.dbx to /Volumes/PGXRAID-02/Backups.backupdb/MacProAdmin’s Mac Pro/2014-03-05-083503.inProgress/0D116102-5F8A-47C0-9D79-C4C78E2B1EF8/Mecca/Use rs/macprouser01/.dropbox
    3/5/14 3:16:13 PM
    com.apple.backupd[1073]
    Copied 1508 files (109.3 MB) from volume Mecca.
    3/5/14 3:16:13 PM
    com.apple.backupd[1073]
    Copy stage failed with error:11
    3/5/14 3:16:19 PM
    com.apple.backupd[1073]
    Backup failed with error: 11

    Still backing up since last night...But seems some errors crept up and TM retried. Another error#11 and a -36
    3/5/14 10:35:03 PM
    com.apple.backupd[5200]
    Copied 413.6 GB of 1793.4 GB, 1517098 of 2656716 items
    3/5/14 11:35:04 PM
    com.apple.backupd[5200]
    Copied 489.6 GB of 1793.4 GB, 1628446 of 2656716 items
    3/6/14 12:35:04 AM
    com.apple.backupd[5200]
    Copied 607.3 GB of 1793.4 GB, 1637474 of 2656716 items
    3/6/14 1:21:57 AM
    com.apple.backupd[5200]
    Copied 1645192 files (689.3 GB) from volume Mecca.
    3/6/14 1:21:59 AM
    com.apple.backupd[5200]
    Waiting for index to be ready (100)
    3/6/14 1:22:59 AM
    com.apple.backupd[5200]
    Waiting for index to be ready (100)
    3/6/14 1:23:59 AM
    com.apple.backupd[5200]
    Waiting for index to be ready (100)
    3/6/14 1:24:59 AM
    com.apple.backupd[5200]
    Waiting for index to be ready (100)
    3/6/14 1:35:05 AM
    com.apple.backupd[5200]
    Copied 708.0 GB of 1793.4 GB, 1647783 of 2656716 items
    3/6/14 2:35:05 AM
    com.apple.backupd[5200]
    Copied 826.2 GB of 1793.4 GB, 1661209 of 2656716 items
    3/6/14 3:18:04 AM
    com.apple.backupd[5200]
    Error: (-36) SrcErr:NO Copying /Volumes/Maryam/HVR/9003-Creatista/2012/05-Approved/2012-08-Caitlin-5728.tif to /Volumes/PGX-RAID-03/Backups.backupdb/MacProAdmin’s Mac Pro/2014-03-05-173408.inProgress/D6CBF0C7-550B-4138-938C-DA5E18C8E65D/Maryam/HV R/9003-Creatista/2012/05-Approved
    3/6/14 3:18:05 AM
    com.apple.backupd[5200]
    Stopping backup.
    3/6/14 3:18:05 AM
    com.apple.backupd[5200]
    Error: (-8062) SrcErr:NO Copying /Volumes/Maryam/HVR/9003-Creatista/2012/05-Approved/2012-08-Caitlin-5728.tif to /Volumes/PGX-RAID-03/Backups.backupdb/MacProAdmin’s Mac Pro/2014-03-05-173408.inProgress/D6CBF0C7-550B-4138-938C-DA5E18C8E65D/Maryam/HV R/9003-Creatista/2012/05-Approved
    3/6/14 3:18:06 AM
    com.apple.backupd[5200]
    Copied 1662808 files (914.3 GB) from volume Maryam.
    3/6/14 3:18:06 AM
    com.apple.backupd[5200]
    Copy stage failed with error:11
    3/6/14 3:18:11 AM
    com.apple.backupd[5200]
    Backup failed with error: 11
    3/6/14 3:33:47 AM
    com.apple.backupd[5200]
    Starting standard backup
    3/6/14 3:33:47 AM
    com.apple.backupd[5200]
    Backing up to: /Volumes/PGX-RAID-03/Backups.backupdb
    3/6/14 3:33:56 AM
    com.apple.backupd[5200]
    No pre-backup thinning needed: 1.04 TB requested (including padding), 1.82 TB available
    3/6/14 3:34:00 AM
    com.apple.backupd[5200]
    Copied 17 files (0 bytes) from volume Photo-Grafix.
    3/6/14 3:34:10 AM
    com.apple.backupd[5200]
    Copied 30 files (153 bytes) from volume Mecca.
    3/6/14 4:33:57 AM
    com.apple.backupd[5200]
    Copied 192.4 GB of 883.7 GB, 2174 of 2656716 items
    3/6/14 5:33:58 AM
    com.apple.backupd[5200]
    Copied 383.7 GB of 883.7 GB, 10318 of 2656716 items
    3/6/14 6:33:59 AM
    com.apple.backupd[5200]
    Copied 578.0 GB of 883.7 GB, 11527 of 2656716 items

Maybe you are looking for