Insufficient free space in the database during upgrademodule General checks

we are upgrading SAP R/3 Enterprise 470 110 to ECC6 on Oracle/Windows.
During PREPARE module: General checks the file CHECKS.LOG show the following information:
   #====================================================#
Requests and information for module General checks #
   #====================================================#
INFO> The following values may be preliminary because of
      free space consumption during productive operation and
      additional free space requests derived in a later stage.
      Conversions of modified tables can require additional space.
      Please use the largest free space request printed,
      which are the values at the very end of this file.
ERROR> Insufficient free space in the database as follows:
Create TABLESPACE PSAPDIMD             with 102 MB
Create TABLESPACE PSAPDIMI             with 102 MB
Create TABLESPACE PSAPODSD             with 112 MB
Create TABLESPACE PSAPODSI             with 112 MB
Create TABLESPACE PSAPFACTD            with 102 MB
Create TABLESPACE PSAPFACTI            with 102 MB
INFO> To adjust the size of your tablespaces, you may use the commands
      in file 'C:\usr\sap\put\log\ORATBSXT.LST' using the 'brspace' utility.
      Please copy the file before making changes, as it may be
      overwritten in subsequent upgrade phases.
INFO> During the upgrade, the new SAP kernel
      will be installed. All files and subdirectories
      in directory C:\usr\sap\CTD\SYS\exe\run which are not used
      in Release 700 will be removed.
      The files from "dbclient.lst" in the kernel directory are kept.
      Files and subdirectories can be protected from deletion
      if they appear in a file "protect.lst" in the same directory
      (each protected name in a separate line).
      For security reasons, directory C:\usr\sap\CTD\SYS\exe\run
      should be saved in a backup.
INFO> You already installed kernel extensions.
      Please unpack the archive(s)
      RFC.CAR
      after the upgrade has finished.
      You can find these archives on the CD "Presentation".
      Do  n o t  unpack the archives now, the software
      is only compatible with the new SAP kernel.
INFO> It is possible to upgrade the frontend software before
      you start SAPup!
   #===========================================================#
PREPARE module General checks finished with status failed #
   #===========================================================#
#====================================================
Execution of all selected PREPARE modules finished.
#====================================================
Now, we have the new tablespace layout and as says the upgrade general note: Note 819655 - Add. info.: Upgrade to SAP NW 2004s ABAP ORACLE we do not have to create tablespaces as saied in PREPARE; so I have adjusted tables DDART,    TAORA, IAORA: with the entry
DDIM     STD     Dimension Tables in BW
DFACT     STD     Facts Table in BW
DODS     STD     ODS Tables in BW
Then J have repeated the module: GENERAL CHECK but in the file CHECKS.LOG I noted always the same error.
Any HELPS?????
Edited by: Raffaele Pezone on Dec 1, 2009 4:25 PM
Edited by: Raffaele Pezone on Dec 1, 2009 4:34 PM

As mentioned in sap note: Note 541542 - Upgrade phase INIT_CNTRANS: Container inconsistency
we don't have standard layout:
Standard layout: TABART: TAORA-TABSPACE, IAORA-TABSPACE
SSDEF:  PSAPES<rel>D,   PSAPES<rel>I
SSEXC:  PSAPES<rel>D,   PSAPES<rel>I
SLDEF:  PSAPEL<rel>D,   PSAPEL<rel>I
SLEXC:  PSAPEL<rel>D,   PSAPEL<rel>I
APPL0:  PSAPSTABD,      PSAPSTABI
USER :  PSAPUSER1D,     PSAPUSER1I
<...>:  PSAP<.....>D,   PSAP<.....>I
but
MCOD Layout (new layout)
SSDEF:  PSAP<sid><rel>, PSAP<sid><rel>
SSEXC:  PSAP<sid><rel>, PSAP<sid><rel>
SLDEF:  PSAP<sid><rel>, PSAP<sid><rel>
SLEXC:  PSAP<sid><rel>, PSAP<sid><rel>
APPL0:  PSAP<sid>USR,   PSAP<sid>USR
USER :  PSAP<sid>USR,   PSAP<sid>USR
<...>:  PSAP<sid>, PSAP<sid>
but we don't use Multiple component in one Database. We have only one instance in one DB.
in fact we have following tablespaces:
PSAPSID   
PSAPSID620
PSAPSID700
PSAPSIDUSR
PSAPTEMP  
PSAPUNDO  
SYSAUX    
SYSTEM
I have just created PSAPSID700 as  PREPARE says.

Similar Messages

  • Insufficient free space in the database

    Hello,
    Good day.
    Would just like to ask if anyone has encountered this problem during their EHP4 upgrade.
    We currently run the preprocessing steps of the EHP4 so we could check the possible problems that we may encounter.
    Rigth now,we encountered an error:
    Extend Tablespace PSAP<sid>
    Create Tablespace PSAP<sid>701
    First on extension of tablespace - I think this is possible, we just need to add disk space on one of our drive so we could extend the said tablespace.
    Second on creation of Tablespace - how could we perform this one, we have an existing Tablespace PSAP<sid>700 and I think this has been created during we install the system. How can we create this new tablespace? can we do it via brspace?
    Thanks in advance on your responses.

    Hello,
    That's correct.
    You have to create the table space PSAPSR3701 yourself with brtools.
    Check the brtools manual for your operating system/database to see how you can create this NEW table space.
    After creation of this new tablespace with brtools/brspace you can continue with EHPinst, EHPinst will then check if you have allocated enough space.
    After installation of EHP4 the old tablespace PSAPSR3700 can be dropped, this can also be done with brtools.
    This is a small example that we have used on UNIX with an Oracle database.
    Creation of tablespace PSAPSR3701 with brtools/brcheck results in following Oracle commands:
    1/
    create tablespace PSAPSR3701 extent management local uniform size 1M segment space management auto datafile '/oracle/GP2/sapdata1/sr3701_1/sr3701.data1' size 10000M autoextend on next 1024M maxsize 20000M
    2/
    alter tablespace PSAPSR3701 add datafile '/oracle/GP2/sapdata2/sr3701_2/sr3701.data2' size 10000M autoextend on next 1024M maxsize 20000M, '/oracle/GP2/sapdata3/sr3701_3/sr3701.data3' size 10000M autoextend on next 1024M maxsize 20000M, '/oracle/GP2/sapdata4/sr3701_4/sr3701.data4' size 10000M autoextend on next 1024M maxsize 20000M
    After installation of EHP4 in the post processing steps:
    BR0280I BRSPACE time stamp: 2009-08-29 03.02.49
    BR0657I Input menu 310 - please check/enter input values
    Options for dropping of tablespace PSAPSR3700
    1 * Number of files in tablespace (files) . [16]
    2 * Total tablespace size in MB (size) .... [81420]
    3 - Force tablespace drop (force) ......... [no]
    4 - SQL command (command) ................. [drop tablespace PSAPSR3700]
    I hope you can use this as a starting point.
    Success.
    Wim
    Edited by: Wim Van den Wyngaert on Oct 16, 2009 7:09 PM

  • Determining the used and free space on the database

    Hi,
    I am trying to analyse the total used and free space on all the tablespaces in a database. The query which I am using is as below:
    SELECT /* + RULE */ df.tablespace_name "Tablespace",
    df.bytes / (1024 * 1024) "Size (MB)",
    SUM(fs.bytes) / (1024 * 1024) "Free (MB)",
    Nvl(Round(SUM(fs.bytes) * 100 / df.bytes),1) "% Free",
    Round((df.bytes - SUM(fs.bytes)) * 100 / df.bytes) "% Used"
    FROM dba_free_space fs,
    (SELECT tablespace_name,SUM(bytes) bytes
    FROM dba_data_files
    GROUP BY tablespace_name) df
    WHERE fs.tablespace_name (+) = df.tablespace_name
    GROUP BY df.tablespace_name,df.bytes
    UNION ALL
    SELECT /* + RULE */ df.tablespace_name tspace,
    fs.bytes / (1024 * 1024),
    SUM(df.bytes_free) / (1024 * 1024),
    Nvl(Round((SUM(fs.bytes) - df.bytes_used) * 100 / fs.bytes), 1),
    Round((SUM(fs.bytes) - df.bytes_free) * 100 / fs.bytes)
    FROM dba_temp_files fs,
    (SELECT tablespace_name,bytes_free,bytes_used
    FROM v$temp_space_header
    GROUP BY tablespace_name,bytes_free,bytes_used) df
    WHERE fs.tablespace_name (+) = df.tablespace_name
    GROUP BY df.tablespace_name,fs.bytes,df.bytes_free,df.bytes_used
    ORDER BY 4 DESC;
    Is this query alright? Or are any changes required in it?
    Thanks in advance.

    SET LINESIZE 85
    SET PAGESIZE 200
    column tablespace_name format a18
    column file_name format a25
    column Allocated_kb format 999,999,999
    column free_kb format 999,999,999
    column Percent_Free format 999
    SELECT
    df.tablespace_name,
    df.file_name,
    df.bytes/1024 Allocated_kb,
    free.free_kb,
    Round(free.free_kb/(df.bytes/1024)*100) Percent_Free
    FROM
    dba_data_files df,
    (SELECT file_id, SUM(bytes)/1024 free_kb
    FROM dba_free_space GROUP BY file_id) free
    WHERE
    df.file_id=free.file_id
    ORDER BY
    Percent_Free;

  • Insufficient free space error

    Hello.
    I try to install EHP4 on ERP 6.0
    I have x86_64 windows server with two partitions: drive c: and large drive mounted to c:\oracle\SID
    Installation interrupts at PREP_GENCHECKS/SPACECHK_OPT with message
    ERROR> Insufficient free space in the database as follows:
    Create TABLESPACE PSAPSR3701           with 64637 MB
    - it cannot find enough free space on drive c:
    But tablespace should be created under c:\oracle\SID, and there is a lot of free space.
    Can I skip this delirious check of c:\ ?

    Hi,
    Please ensure your brtools is at the latest
    version as per note 12741.
    If the problem still persists, you can set the trace level for brspace
    to 11 as per note 29321 and re-run the phase.
    Usually in sap upgrade this is related to Oracle dba_free_space not the
    system free space, same theory should apply to EHP install. If you have
    an Oracle dba you may ask him to check the data dictionary view
    dba_free_space and available extents for each tablespace.
    Also please review carefully points within Note 716377 - Problem
    analysis in the upgrade: SPACECHK phases ?
    Regards,
    Aidan

  • Error: There is insufficient free space on disk volume

    Hello All,
    I am trying to add Appset and getting this error:
    Error message:There is insufficient free space on disk volume 'E:\' to create the database. The database requires XXXXX additional free bytes, while only yyyyy bytes are available.
    My question is :
    Why I get this message although I didn't check the data or any other option when trying to copy my production AppSet?
    XXXX required is the size of my production AppSet DB.
    Can anyone please help?
    Best regards,
    Mahmoud

    Hi Santosh,
    Thanks for your answer.
    I am sorry I don't understand well what did you mean.
    What I wanted to say is that DataBase creation failed so AppSet copy has failed and this is due to lack of disk space as mentioned in the error message.
    If this would be clearer my question would be :
    - What is the minimum free disk space needed to create an "empty" AppSet? Empty means no options checked in the copy Appset wizard.
    FYI: I use BPC 7.0 SP8 SQLServer 2008
    Thank you for your help.
    Best Regards
    Mahmoud

  • What actually happens @Completed filling free space info for database

    Hello,
    i see some strange thing with my 15.7 Ase server
    Earlier for a very big db of around 1TB the recovery time would be around 15Mins( i mean for the 1TB db to come online).
    Now its taking only seconds to come up.
    so wanted to check what actually happens in this stage.
    Started filling free space info for database 'xxx'
    Completed filling free space info for database 'xxx'
    The difference is that we have created new server and bcpd the data into it.
    Please can someone explain.
    Thanks

    ASE keeps counters in memory of the amount of free space available on devices and segments.  When ASE is shutdown cleanly (aka "politely"), these values are flushed to disk and used to initialize the in-memory counters on reboot.  If ASE is shutdown abruptly, the values have to be recalculated, a process which involves either reading every OAM page in the database or every Allocation page.

  • How do you create additional free space on the volume containing the iPhoto library?  I have plenty of HD space.

    How do you create additional free space on the volume containing the iPhoto library?  When attempting to import images from a CD I get an "Insufficient Disk Space" message albeit there is plaenty of additional space on the hard drive.

    How much free space do you have on your hard drive?  Try the following:
    1 - delete the iPhoto preference file, com.apple.iPhoto.plist, that resides in your
         User/Home/Library/ Preferences folder.
    2 - delete iPhoto's cache file, Cache.db, that is located in your
    User/Home/Library/Caches/com.apple.iPhoto folder (Snow Leopard and Earlier).
    or with Mt. Lion from the User/Library/Containers/com.apple.iPhoto/
    Data/Library/Caches/com.apple.iPhoto folder
    3 - launch iPhoto and try again.
    NOTE: If you're moved your library from its default location in your Home/Pictures folder you will have to point iPhoto to its new location when you next open iPhoto by holding down the Option key when launching iPhoto.  You'll also have to reset the iPhoto's various preferences.
    NOTE 2:  In Lion and Mountain Lion the Library folder is now invisible. To make it permanently visible enter the following in the Terminal application window: chflags nohidden ~/Library and hit the Enter button - 10.7: Un-hide the User Library folder.

  • ASE - Started filling free space info for database

    Hi All
    I have an ASE db that is in a RECOVERY state.
    This the last communication in the log: Started filling free space info for database 'BWP'
    Does anyone know what this means?
    There is a SAP BW running on ASE 15.7.
    I am an SAP consultant working onsite at a client and the environment is down due to the DB being in this state.
    Any ideas?
    00:0002:00000:00014:2014/07/03 10:27:18.04 server  Recovering database 'BWP'.
    00:0002:00000:00014:2014/07/03 10:27:18.05 server  Started estimating recovery log boundaries for database 'BWP'.
    00:0002:00000:00014:2014/07/03 10:27:18.07 server  Database 'BWP', checkpoint=(249429512, 203), first=(249429512, 203), last=(249429513, 46).
    00:0002:00000:00014:2014/07/03 10:27:18.07 server  Completed estimating recovery log boundaries for database 'BWP'.
    00:0002:00000:00014:2014/07/03 10:27:18.07 server  Started ANALYSIS pass for database 'BWP'.
    00:0002:00000:00014:2014/07/03 10:27:18.07 server  Completed ANALYSIS pass for database 'BWP'.
    00:0002:00000:00014:2014/07/03 10:27:18.07 server  Log contains all committed transactions until 2014/07/03 10:19:12.65 for database BWP.
    00:0002:00000:00014:2014/07/03 10:27:18.07 server  Started REDO pass for database 'BWP'. The total number of log records to process is 81.
    00:0002:00000:00014:2014/07/03 10:27:18.14 server  Completed REDO pass for database 'BWP'.
    00:0002:00000:00014:2014/07/03 10:27:18.14 server  Timestamp for database 'BWP' is (0x0004, 0xd609797b).
    00:0002:00000:00014:2014/07/03 10:27:18.14 server  Recovery of database 'BWP' will undo incomplete nested top actions.
    00:0002:00000:00014:2014/07/03 10:27:18.14 server  Started recovery checkpoint for database 'BWP'.
    00:0002:00000:00014:2014/07/03 10:27:18.14 server  Completed recovery checkpoint for database 'BWP'.
    00:0002:00000:00014:2014/07/03 10:27:18.14 server  Started filling free space info for database 'BWP'.
    ASE VERSION:
    Adaptive Server Enterprise/15.7/EBF 22779 SMP SP122 /P/x86_64/Enterprise Linux/ase157sp12x/3662/64-bit/FBO/Sat Apr 19 05:48:19 2014
    Any suggestions on what to do?
    J

    ASE tracks the free space available on each segment in memory.
    If the server is shut down politely, ASE can store the current values on disk and retrieve them at startup.  However, if the server is shutdown abruptly (shutdown with nowait, crash, power failure, kill -9, etc.) the free space figures don't get written out.  In that case ASE has to recalculate the free space values by reading all the allocation pages or OAM pages in the database.  On a big database, that can take time.
    Your main choices are to
    1) wait it out
    2) set the "no freespace accounting" database option and reboot
    Disabling free-space accounting for data segments
    While recovery will be much faster with freespace accounting turned off, there are side effects such as unexpected 1105 errors (no free space...) and thresholds not firing as expected.  In general I'd advise waiting it out and trying to avoid the use of "shutdown with nowait" going forward (which may or may not be what brought the server down, but it is the main cause you can control).
    -bret

  • Tmpfs free space versus the "free" command

    I've always thought this possible, so today I tried it:
    I have 2 gigs of physical RAM, and no swap partitions, so my memory limit is a hard 2 gigs.
    I made 2 1-gig tmpfs mounts; nothing complained.
    I filled them up one at a time, and kept checking both free memory (with free) and free space on the tmpfs mounts -- as I started to get near the limit of my system's RAM, free still showed plenty of RAM free in the +/- row.
    Neither free nor df gave me any indication that the system was dangerously low on memory. (I assume from a bit of Googling  that "free" considers the size of tmpfs's to be part of the "cached" column, as nothing else was big enough to contain them.)
    Anyhow, I added a few more files to the tmpfs and the system locked up for a while... After about 3 minutes of hard drive thrashing (which was a bit distressing, but since my files look OK I guess it was desperately running sync again and again to try to free RAM for the tmpfs), a couple programs died and everything went back to normal.
    So, in an effort to have that not happen again (since I use tmpfs heavily; it's a nice way to screw around with big files without waiting on hard drives), I wrote this little shell script:
    #!/bin/bash
    #prints worst-case free memory, from /proc/meminfo
    total=`grep MemTotal /proc/meminfo | gawk '{print $2}'`
    used=`grep Committed_AS /proc/meminfo | gawk '{print $2}'`
    echo "Free RAM in the worst case: " $(($total - $used)) "kB"
    and put this in my .bashrc:
    alias free='free; wcfree'
    alias df='df; wcfree'
    ~Felix.
    PS: If it's not possible to make stuff crash with only a single tmpfs, please let me know -- that would be good knowledge, and make me feel silly for writing this :P

    The advice I got was to shrink the database and reexpand it. And reindex all tables because of defragmentation.
    I don't know if it works, and I would be hesitant to try it, because I believe there is an issue with DBCC SHRINKFILE being awfully slow when there is LOB data.
    I like to believe that your odds would be better if you used varbinary(MAX), and given how easier varbinary(MAX) is to work with your life would be happier two. But I don't know how that would work with your merge-replication scheme. And if you use READ/WRITE/UPDATETEXT
    you need to change that code.
    You say you cannot create a new table and copy data over because of merge replication. Would it be possible to create a new column, copy data over, drop the old column and rename? I have no experience with merge replication myself, so I don't know of
    the repercussions. If you do this, you need to run DBCC CLEANTABLE to get rid of the space.
    For that matter you could try DBCC CLEANTABLE in the state you have now. Not that it should help from you have told me, but you never know...
    Erland Sommarskog, SQL Server MVP, [email protected]

  • Ut 4000 photos in my iphotos; iPhoto cannot import your photos because there is not enough free space on the volume containing your iPhoto library.

    I keep getting the following error message despite only having about 4000 pics in my iphotos; iPhoto cannot import your photos because there is not enough free space on the volume containing your iPhoto library. I have tried moving my iphotos library to an external Hard Drive and starting a new library but still it will not allow any more to be loaded.

    What version of iPhoto?
    try Back up your iPhoto library, Depress and hold the option (alt) and command keys and launch iPhoto - rebuild your iPhoto library database
    LN

  • IPhoto cannot import your photos because there is not enough free space on the volume containing your iPhoto library.

    iPhoto cannot import your photos because there is not enough free space on the volume containing your iPhoto library. I have .999.35 T left. 3.18 gigs used in photo storage. How do I fix this?

    iphoto insufficient disk space
    iphoto insufficient disk space on volume

  • Why am i getting this warning? iPhoto cannot import your photos because there is not enough free space on the volume containing your iPhoto library.

    I can no longer import photos from my PC because I get this message:  iPhoto cannot import your photos because there is not enough free space on the volume containing your iPhoto library.  How can I fix this problem?

    Option 1
    Back Up and try rebuild the library: hold down the command and option (or alt) keys while launching iPhoto. Use the resulting dialogue to rebuild. Choose to Rebuild iPhoto Library Database from automatic backup.
    If that fails:
    Option 2
    Download iPhoto Library Manager and use its rebuild function. This will create a new library based on data in the albumdata.xml file. Not everything will be brought over - no slideshows, books or calendars, for instance - but it should get all your albums and keywords back.
    Because this process creates an entirely new library and leaves your old one untouched, it is non-destructive, and if you're not happy with the results you can simply return to your old one. .
    Regards
    TD

  • I have IPhoto version 9.5.1. I cannot export pictures, the following message appears: "iPhoto cannot import your photos because there is not enough free space on the volume containing your iPhoto library." What am I suppose to do? I have a Mac mini.

    I have IPhoto version 9.5.1. I cannot export pictures since the following message appears: "iPhoto cannot import your photos because there is not enough free space on the volume containing your iPhoto library." What am I suppose to do? I have a Mac mini which properly used can perform any reasonable task, the problem is I do not know what to do.
    Any help will be appreciated.

    Hmm... that was labelled:
    As a Test:
    In bold and all
    Try repair the main Library:
    Option 1
    Back Up and try rebuild the library: hold down the command and option (or alt) keys while launching iPhoto. Use the resulting dialogue to rebuild. Choose to Repair Database. If that doesn't help, then try again, this time using Rebuild Database.
    If that fails:
    Option 2
    Download iPhoto Library Manager and use its rebuild function. (In early versions of Library Manager it's the File -> Rebuild command. In later versions it's under the Library menu.)
    This will create an entirely new library. It will then copy (or try to) your photos and all the associated metadata and versions to this new Library, and arrange it as close as it can to what you had in the damaged Library. It does this based on information it finds in the iPhoto sharing mechanism - but that means that things not shared won't be there, so no slideshows, books or calendars, for instance - but it should get all your events, albums and keywords, faces and places back.
    Because this process creates an entirely new library and leaves your old one untouched, it is non-destructive, and if you're not happy with the results you can simply return to your old one.  
    Regards
    TD

  • May I run "shrink DB/truncate free space from the end of file" at PROD?

    We have a SAP/MSS production system.
    The disk is full.
    We want to truncate the log file by:
    "shrink DB/truncate free space from the end of file"
    on the log file.
    How risk is it? Can we do it during production is running?
    Thanks! Points!

    Backup the log file (to save the data and keep a consistent backup) Then shrink the file. Its normal for the log not to shrink down to the size you want. Do not shrink past 1GB.
    DO NOT TRUNCATE - you are losing/dropping data and recovery will only be possible to the last on-line, or on-line plus last log/s.
    You can avoid a full log file by setting a 9002 trap - this will trigger a backup (like oraarch when you back up based on % full). Else you need to change the frequency of the backups for the logs to ensure the system never fills ups.
    You can Also add a second log file on a separate F/S if this occurs regular - which it shouldn't if you have a correct backup strategy.

  • WBAdmin BMR backup says "There is not enough free space on the backup storage location to back up the data."

    We're doing nightly BMR backups of a small 2012 R2 Hyper-V host via wbadmin to 2TB USB disks, via
      wbadmin start backup -backupTarget:z: -quiet -noverify -vssFull -include:e:,c: -allCritical
    (where E: contains the sole VM).
    We are using the same backup system on other similar Hyper-V hosts running 2008 R2 and 2012, with no problems. However, with this 2012 R2 host, after a few months of no problems the backups started failing with:
      There is not enough free space on the backup storage location to back up the data.
    This made no sense, and continues to make no sense:
    The 2TB backup disks are only half full (>1TB free), with 600GB of unallocated shadowstorage.
    There should be room for many more backups on these disks. Each currently contains 11 to 13 backups, with the initial full backup having required about 600GB and each subsequent backup only requiring another 20GB to 40GB.
    There is over 40GB free on the C: drive and 300GB free on the E: drive; free space on the host volumes is not an issue.
    Increasing the shadowstorage limit on the backup disks to unbounded doesn't resolve the issue.
    This is not a problem of a RECOVERY partition that's too small, and SystemState backups always complete successfully.
    The first workaround we found was to temporarily reduce (not increase) the shadowstorage allocation on the E: drive (containing the VM) and then increase it back (with the end result of deleting old shadow copies).
    This worked reliably, but looking for a root cause led us to uninstall the Windows Updates installed mid-September (in particular the Aug 2014 and Sep 2014 roll-ups), which preceded the start of this problem. But instead of resolving the problem the uninstalls
    made it worse, in that our workaround stopped working.
    We reinstalled the Windows Updates, and then tried setting backup performance to normal, in case the problem was related to VSS on the host volumes, but the errors continued.
    At this point the only way we've found to work around the error is to delete 1 or 2 of the oldest backups on the destination disk, via
      wbadmin delete backup -backupTarget:z: -deleteOldest
    after which the new backup will succeed.
    But, again, this makes no sense, as the destination disks are only half full, and even if space was an issue wbadmin should delete old backups as required. And this same system is working fine on 2008 R2 and 2012.
    Any suggestions?
    Thanks,
    John

    Hi John,
    Please check run the command below to check if the space required to complete the backup causes the snapshot storage space to become less than 1/8 of the target size.
    vssadmin list shadows /for=x: will list the shadow copies on x: and creation time.
    WSB will not shrink the diff area to less than 1/8 of Target volume size as we do not want to lose all past backups just to accommodate this one.
    For more detailed information, please refer to the article below:
    Windows Server Backup automatic disk usage management
    http://blogs.technet.com/b/filecab/archive/2011/03/14/windows-server-backup-automatic-disk-usage-management.aspx
    V. Backup, Restore and Disaster Recovery
    http://social.technet.microsoft.com/wiki/contents/articles/1846.v-backup-restore-and-disaster-recovery.aspx?Sort=MostUseful&PageIndex=1
    Best 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.

Maybe you are looking for