DPM 2012 R2 All backups fail with recovery point volume not available after resizing OS disk

I resized the C drive partition of my DPM server (the data is on a separate dedicated array) and everything failed. I put it back but everything is still failing with the same problem as here:
DPM 2007: The recovery point volume is not available?
I've run chkdsk for a couple and both have given the following after doing 3 stages:
Windows has scanned the file system and found no problems.
No further action is required.
The backups still fail and the only error information I can find in the event logs is:
Backup job for datasource: Online\<VM name> on production server: <host FQDN> failed.
How can I find out what the problem actually is?
Is it possible to resize the C drive containing a DPM install? If so what can it be safely resized to? It easily met the minimum requirements and I don't know of anything in the documentation that says resizing the OS disk may cause issues.
Preparing your environment for System Center 2012 R2 Data Protection Manager (DPM)

Hi,
Resizing the boot partition (usually C:) should not effect DPM in any way. DPM writes directly to it's volumes contained in the storage pool and not through the mount points on the C: drive. So is the DPM UI showing
missing volume next to some data sources ? Try doing a DPM disk rescan and see if that removes the missing volume flag.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This
posting is provided "AS IS" with no warranties, and confers no rights.

Similar Messages

Job failed with error tempdb is not available

HI All,
Backup job failed with error 'Unable to determine if the owner () of job backup_all_user_db_full has server access (reason: The log for database 'tempdb' is not available. [SQLSTATE HY000] (Error 9001)).'
I checked in errorlog
LogWriter: Operating system error 1784(The supplied user buffer is not valid for the requested operation.) encountered.
    Write error during log flush. Shutting down server
2014-09-09 07:46:25.90 spid52    Error: 9001, Severity: 21, State: 1
2014-09-09 07:46:25.90 spid52    The log for database 'tempdb' is not available..
2014-09-09 07:46:25.92 spid51    Error: 9001, Severity: 21, State: 1
Can anyone suggest to why it is happening

From the error message, it looks like the drive on which the tempdb log file is residing is having issues.
Please involve your storage admin to look into the disk subsystem

IWork free with new purchase but not available after time machine restore

Tried to find the best place to put this and this is the best I can surmise.
iWork is now supposedly free with the purchase of a new Mac. I received a new MacBook Pro 2 days ago. The problem is, I wanted to keep all my old settings/apps/features/files without spending 2 weeks resetting everything back up, so I used time machine to restore my machine to the state of my old MacBook Air. Unfortunately, it does not look like any iWork apps remained in the Applications folder (makes sense), but now I go to the App store and Pages, Numbers, and Keynote are all listed as $19.99.
I only assume that my time machine restore was the issue (I don't know if the apps were ever in the Applications folder at all), but since time machine is a feature Apple supports I would assume they support some way to make this work as well. How do I go about getting iWork without paying $60?
Thanks

There are several reasons why the updates don't show as free for those who already have iWork '09 installed.
1. You must have iWork '09 apps installed & they must be updated to the x.3 version. You can also download the standalone updater from this page.
2. If you are not using English as the primary language for your Mac, change to English & run Software Update. You can then switch back to your preferred language.
3. Go to Mac App Store (MAS) > Click on Store > Check for Unfinished Downloads. You will need to individually click into each application > Click update > enter in your Apple ID & password and then it will start updating.
4. Open App Store on your Mac & look at the buttons under Keynote, Pages & Numbers. If it does not say “Update” click Account under Quick Links, enter your password & click “View Account.” Next, click the “Reset” button to the right of “Reset all warnings for buying and downloading” at the bottom of this page, & click Done. Check your updates tab & iWork & iLife updates should now appear.
These are the ones I've seen work for others.

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.

Time Machine backup fails with error 2

trying to run a backup for the first time on a new external hard-drive but backup fails to complete. Any suggestions?
Starting standard backup
Backing up to: /Volumes/FreeAgent GoFlex Drive/Backups.backupdb
Failed to create progress log file at path:/Volumes/FreeAgent GoFlex Drive/Backups.backupdb/Jones’s iMac (3)/2011-11-24-170759.inProgress/.Backup.343882684.814583.log.
Event store UUIDs don't match for volume: Macintosh HD
Error: (-50) Creating directory 6A3DF5C4-679A-4FBE-A116-218CE389908A
Failed to make snapshot.
Backup failed with error: 2

I too am having multiple problems with time machine for a couple of weeks now, however this is not my first backup. I have been using TM for over 2 years, and these are new problems. This is the last error message:
Starting standard backup
Backing up to: /Volumes/OWC Mercury Elite AL Pro/Backups.backupdb
Failed to create progress log file at path:/Volumes/OWC Mercury Elite AL Pro/Backups.backupdb/LM Home/2011-11-25-200420.inProgress/.Backup.344169198.317667.log.
Event store UUIDs don't match for volume: Mac 2
Event store UUIDs don't match for volume: Mac 1
Error: (-50) Creating directory 0A89DB49-A127-4ECE-8E98-65C5393BC268
Failed to make snapshot.
Backup failed with error: 2
The above came after permissions repair & disk repair. Before the messages were mostly:
Error: (-50) SrcErr:NO Copying /Applications/Font Book.app to /Volumes/OWC Mercury Elite AL Pro/Backups.backupdb/LM Home/2011-11-25-200420.inProgress/E0326568-C860-4A3F-888D-9840DFF72832/Mac 1/Applications
Error: (-50) SrcErr:NO Copying /Applications/Front Row.app to /Volumes/OWC Mercury Elite AL Pro/Backups.backupdb/LM Home/2011-11-25-200420.inProgress/E0326568-C860-4A3F-888D-9840DFF72832/Mac 1/Applications
Error: (-50) SrcErr:NO Copying /Applications/Full Key Codes to /Volumes/OWC Mercury Elite AL Pro/Backups.backupdb/LM Home/2011-11-25-
With a whole string of different applications with the same error, then ending with:
Error: (-43) SrcErr:NO Copying /User Guides And Information to (null)
Error writing to backup log. NSFileHandleOperationException:*** -[NSConcreteFileHandle writeData:]: Invalid argument
Error: (-1407) SrcErr:NO Copying /Users to (null)
Error writing to backup log. NSFileHandleOperationException:*** -[NSConcreteFileHandle writeData:]: Invalid argument
Error: (-43) SrcErr:NO Copying /usr to (null)
Error writing to backup log. NSFileHandleOperationException:*** -[NSConcreteFileHandle writeData:]: Invalid argument
Error: (-1407) SrcErr:NO Copying /Volumes to (null)
Formulating crash report for process backupd[960]
Any help/suggestions out there ??

DPM 2012 R2 long backup to tape job randomly fail after installing SCCM 2012 Client

Hello,
I'm managing a two nodes 2012 R2 file server cluster that contains a 16To CSV. I'm using DPM 2012 R2 to backup this entire shared volume directly to LTO 4 tapes, the job last about 55h.
Since SCCM 2012 client has been installed(I don't manage it), the tape jobs are failing ramdomly after several hours with the error:
Type: Tape backup
Status: Failed
Description: The DPM service was unable to communicate with the protection agent on serverX.xxxx.xxx . (ID 52 Details: The semaphore timeout period has expired (0x80070079))
More information
End time: 19/07/2014 03:11:06
Start time: 18/07/2014 22:00:00
Time elapsed: 05:11:05
Data transferred: 768 289,56 MB
Cluster node serverX.xxxx.xxx
Source details: G:\
Protection group members: 1
Details
Protection group: File Server Tape Protection
Library: Quantum PX500 Series Medium Changer
Tape Label (Barcode): File Server Tape Protection-00000230 (000043L4)
If I uninstall SCCM 2012 client, no more issue, backups succeed. I've asked our SCCM team, no specific task has been scheduled or deployed in SCCM.
I can't see anything abnormal in logs.
Any idea?

I have disabled "Configuration Manager Maintenance" and I have also tried to set the registry value HKLM\Software\Microsoft\CCM\CcmEval\NotifyOnly to TRUE and still the same issue.
I can't find any correlated errors in the Windows event logs, task scheduler history neither in the DPM logs.
I've increased the log level of DPM by following the following procedure
http://blogs.msdn.com/b/george_bethanis/archive/2013/11/04/how-to-collect-dpm-verbose-logs.aspx
Now i'm suspecting the maintenance job of Windows 2012 R2, i'll try to disabled this task. But the fact is that I don't have this backup issue if SCCM 2012 client is not installed.
I'm waiting for next logs and will keep you informed

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?

DPM 2012 R2 UR4 - DPM could not set security permissions on the replica or recovery point volume that was created.

Hi All,
I am running a fresh install of SCDPM 2012 R2 with a protection group that is backing up the 'C:\', Bare Metal and System State of some VMs. If i add any additional servers to the group since the first creation it returns the following error:
Modify protection group: System State & Bare Metal Recovery failed:
Error 419: DPM could not set security permissions on the replica or recovery point volume that was created.
Error details: The process cannot access the file because it is being used by another process
Recommended action: Review the error details, take appropriate action and retry the operation.
If i re-create the whole protection group it works fine.
Could any one advise any further diagnostics I can do to try and locate the reason behind not being able to modify the group after the first creation? I can add new servers to other PGs without any issues.
Thanks in advance,
Dan

If you are protecting any of the system state/BMR protection. Can you stop protection by deleting the older recovery points and then recreate the protection group.
This thread mentions this to be a hardware issue, albeit with less information on what exact hardware issue:
https://social.technet.microsoft.com/Forums/en-US/480679c2-1079-4847-ab38-5cc8f454ef86/error-419-dpm-could-not-set-security-permissions-on-the-replica-or-recovery-point-volume-that-was?forum=dataprotectionmanager
Regards, Trinadh [MSFT] This posting is provided AS IS with no warranties, and confers no rights. If you found the reply helpful, please MARK IT AS ANSWER. Looking for source of information for DPM? http://blogs.technet.com/b/dpm/ http://technet.microsoft.com/en-in/library/hh758173.aspx

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.

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

Understanding replica volume and recovery point volume usage with SQL Express Full Backup

I am running some trials to test DPM 2012 R2's suitability for protection a set of SQL Server databases and I am trying to understand what happens when I create a recovery point with Express Full Backup.
The databases use simple recovery model and in the tests I have made so far I have loaded more data into the databases between recovery points since that will be a typical scenario - the databases will grow over time. The database files are set to autogrowth
by 10%
I have been looking at the change in USED space in the replica volume and in the recovery point volume after new recovery points and have a hard time understanding it.
After the first test where data was loaded into the database and an Express Full Backup recovery point was created, I saw an increase in used space in the replica volume of 85 Gb and 29 GB in the recovery point volume. That is somewhat more than I think
the database grew (I realize that should have monitored that, but did not), but anyway it is not completely far out.
In the next test I did the same thing except I loaded twice as much data into the database.
Here is where it gets odd: This causes zero increased usage in the replica volume and 33 GB increased use in the recovery point volume.
I do not understand why the replica volume use increases with some recovery points and not with others.
Note that I am only discussing increased usage in the volumes - not actual volume growth. The volumes are still their original size.
I have been using 3-4 days on the test and the retention period is set to 12 days, so nothing should be expired yet.

Hi,
The replica volume usage represents the physical database file(s) size. The database file size on the replica should be equal to the database file size on the protected server. This is both .mdf and .ldf files. If when you load data
into the database and you overwrite current tables versus adding new ones, or if there is white space in the database files and the load simply uses that white space, then there will not be any increase in the file size, so there will not be any increase
in the replica used space.
The recovery point volume will only contain delta changes applied to the database files. As the changed blocks overwrite the files on the replica during express full backup, VSS (volsnap.sys) driver copies the old blocks about to be overwritten
to the recovery point volume before allowing the change to be applied to the file on the replica.
Hope this helps explain what you are seeing.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.

All crawl jobs are failing with errors, Query server not responding.

Hi All,
I'm facing issue with search service , one of the Query server not responding and all the crawl jobs are throwing errors.
Errors:
"The SharePoint item being crawled returned an error when requesting data from the web service. ( Error from SharePoint site )"
"The object was not found. ( Error from SharePoint site: HttpStatusCode NotFound The request failed with HTTP status 404: Not Found. )"
Please suggest some resolutions.
Pavan

Hi Pavan,
1. First verify as given in this article - https://support.microsoft.com/en-us/kb/2323206?wa=wsignin1.0
2. If not 1 resolves issue then try to disable the anonymous access on the default zone web application(in content source)
3. Also check this article if above two steps does not resolve the issue - http://www.sharepointtechs.com/the-sharepoint-item-being-crawled-returned-an-error-when-requesting-data-from-the-web-service-error-from-sharepoint-site-value-does-not-fall-within-the-expected-range
4. If none of the above works then install this CU update http://support.microsoft.com/kb/2596505 and
then re-run you SP Configuration Wizard and restart your SharePoint Server. But before installing this CU on your SharePoint Server ensure your have the latest backup.
4. If all above does not work then remove
the anonymous access (if enabled) and restore the site collection to a new new site.
Please remember to click 'Mark as Answer' if the reply answers your query or 'Upvote' if it helps you.

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 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/

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.

DPM 2012 R2 All backups fail with recovery point volume not available after resizing OS disk

Similar Messages

Maybe you are looking for