SharePoint backup size estimation

How to estimate the size of the database that need to be backup? I read some reference that the size is about 2.5*content database.
How about the backup size using back-spfarm? Is there any compression when backup as bak files? How to set the compression ratio?
So, is the full backup size calculated as 2.5*content database*compress ratio? And what is the differential backup size estimation?
Overall, I need to plan the space required for a weekly full and 5-6 differential backup.
Thanks for providing any ideas that I am not clear.

Hi, we are using a powershell script to calculate the SPSite size in MOSS 2007, same script could work in 2010 and 2013. The result from this + 6 % will return you the ruff size of the backup: It is working for us. Cheers
function Site-Space ($sitecola)
[reflection.assembly]::LoadWithPartialName("Microsoft.SharePoint") | out-null
$sitea = [Microsoft.SharePoint.SPSite]($sitecola)
[int]$sitespacesite = $sitea.Usage.Storage /1MB
$siterecyclebin = $sitea.RecycleBin | Where {$_.ItemState.ToString() -eq 'SecondStageRecycleBin'}
If ($siterecyclebin -ne $null)
ForEach($recycleitem in $siterecyclebin)
[int]$recyclesize = $recyclesize + ($recycleitem.Size /1MB)
$sitespace += ($sitespacesite + $recyclesize)
Else
$sitespace = $sitespacesite
return $sitespace

Similar Messages

  • Estimated Backup size

    Hi,
    I'm tryin to use TM for the first time to backup my internal disc of my MacBook Pro to a newly bought external one.
    The internal drive (the source for the backup) has a total capacity of 232,9 GB (250.059.350.016 Bytes) according to Disk Utility of which 98,0 GB (105.187.246.080 Bytes) are used.
    Time Machine however claim for the initial backup it is to backing up 422.42 GB which is about 4.3 times the amount of data on my drive!
    Is this normal? Why is it that far off the weeds?
    This actually doesn't give me a very good feeling regarding the reliability of Time Machine.
    Needles to say the initial backup runs endless....
    BTW: Forgot to mention: This 10.5.8 and the external drive is 1.5 TB, USB 2.0

    I don't use File Vault, and it does some strange things vs. Time Machine. As I understand it, you should have both a normal home folder and a sparse image (the encrypted version). That's the "horst" volume in the second UUID message.
    Right. That's what I found out in the meantime.
    Your "normal" home folder should have been excluded automatically. If you now exclude it manually, however, it doesn't sound like that will get to the correct size.
    It was, when I checked initially, but now it no longer isn't
    And yes, it's FileVault confusing not only Time Machine but rather the entire system:
    When I select my home folder in Finder's sidebar and do a Get Info on it, the Finder tells me my home folder is has a capacity of 465.13 GB of which 330.56 GB are used (which is entire crap since my entire hard disk only is about 233 GB and the amount of dat in my home folder is about 48 GB).
    But then it sums up fairly well: 330 GB (of assumed data) plus 98 GB actual data on disk are about the estimated backup size, TM is reporting.
    The Unix command df reports the same false data, so there obviously is something wrong in Leopard's calculation of FileVault sizes:
    Horsts-MBP:~ horst$ df
    Filesystem 512-blocks Used Available Capacity Mounted on
    /dev/disk0s2 487725344 204928248 282285096 43% /
    devfs 218 218 0 100% /dev
    fdesc 2 2 0 100% /dev
    map -hosts 0 0 0 100% /net
    map auto_home 0 0 0 100% /home
    /dev/disk1s2 975450624 693231064 282219560 72% /Users/horst
    /dev/disk2s2 2929605344 249137376 2680467968 9% /Volumes/Time Machine Backups
    Do you really need your entire home folder encrypted? It's not going to play well with TM, even under the best of circumstances. You won't be able to see the details of what was backed-up, and I don't believe you can restore individual items. Plus, TM will only back it up when you log out, not on it's normal hourly schedule.
    What I tried but after logging out, the previous backup stopped. I see TimeMachine and FileVault aren't really good friends, possibly even mutually exclusive. If I have to choose I'll stick to FikeVault because seemless data encryption for me is currently more important than hourly backups.
    Maybe I'll have to investigate in a different backup strategy

  • Estimating the backup size before running the RMAN

    DB Version : 11.2
    OS : Oracle Solaris 10
    I need to take an ad-hoc RMAN cold backup of a 200GB DB to Local Disk. Using RMAN, is there any way I could check how much the backup size would be before I take the cold backup ?

    Read the metalink How to estimate the size of an RMAN database backup [ID 1274720.1].

  • Estimating the backup size for full database backup?

    How to estimate the backup file size for the following backup command?
    Oracle 10g R2 on HPUX
    BACKUP INCREMENTAL LEVEL 0 DATABASE;
    Thank you,
    Smith

    Depends on the number of used blocks, block size etc. You could probably get a rough formula for backup size based on the contents of dba_tab_statistics (subtract empty_blocks), dba_ind_statistics etc.

  • Backup size too large??

    I have been using an external drive for my TM backup for a long time.
    Recently I did a reinstall of Snow Leopard on my iMac, then the problem arises.
    TM gives the warning of too large backups and not enough disk space in my external drive.
    I have tried to erase my TM drive but the problem still exists.
    I can see from the TM preferences->option that the "Estimated backup size" is 644 GB
    and my TM external drive has 750GB empty space, but the warning msg said I need 775GB of empty space on the ext.
    How could it be?? I just have around 600GB of used space on my internal drive to backup!
    Can somebody help??

    Your backup drive is too small.
    It varies greatly, depending on how you use your Mac, but Time Machine usually needs 2-3 times the space of the data it's backing-up to keep a few months of backups for you.
    The immediate problem is, Time Machine adds about 20% to the estimated size of the backup, for workspace, as mentioned in the message.
    Short term, you can "squeeze" your backups onto that drive by temporarily excluding some large items, per #10 in [Time Machine - Frequently Asked Questions|http://web.me.com/pondini/Time_Machine/FAQ.html] (or use the link in *User Tips* at the top of this forum). Then remove the exclusions, and run another backup. Since the 20% will be added to a much smaller backup, it should fit.
    Longer term, you need a much larger disk, preferably 1.5 TB or larger.

  • Time Machine gives different full backup sizes

    After this recent Time Machine update I am no longer able to back up. When Time Machine computes the backup it tells me that it is 320GB, which is larger than my backup drive, so it can't back up. However, when I go into the Time Machine preferences it computes the estimated backup size as 272.52GB. Before this Time Machine update was applied my backups were happening with no issues.

    Mark Trolley wrote:
    Thank you. They must have changed the amount of extra space required with this latest patch
    It's been 20% since the early days of Leopard.
    because it was working fine up until that point.
    It may be a combination of things: the drive is clearly too small; while it varies widely depending on how you use your Mac, our general "rule of thumb" is that TM needs at least twice the space of the data it's backing-up.
    If you're like most of us, the amount of data on your system has been growing.
    And apparently Time Machine is doing a full backup, so it just got beyond the capacity of the disk to hold it all.
    Looks like I need a larger Time Machine disk.
    Yup. The good thing is, they continue to get less and less expensive.

  • Backup Size Oddity

    I have an internal drive showing 120GB used. I have set up exclusions and under the exclusions list (in which the excluded items add up to 50GB), the estimated full backup size shows as 70GB as I'd expect. However, after my initial backup, the Time Machine drive shows 3GB used not the 70GB I was expecting. Any suggestions as to why it's only backing up this small amount?

    Time Machine does automatically exclude some things, such as system work files, most caches and logs, trash, etc. Usually those don't add up to more than a few GBs, though.
    So there are two possibilities: you have about 67 GB of that sort of stuff; or there's a problem with Time Machine.
    What have you excluded? It's usually not a good idea to exclude much, as it can make recovery after a hard drive or other failure much more difficult. See #11 in [Time Machine - Frequently Asked Questions|http://web.me.com/pondini/Time_Machine/FAQ.html] (or use the link in *User Tips* at the top of this forum).
    You can use the "Star Wars" display per #15 in the FAQ to see what was backed-up; you may want to spot-check what you expect to be there. If such things aren't there, the preferences file (where the exclusions are stored) may be corrupted. Try a "full reset" of Time Machine, per #A4 of [Time Machine - Troubleshooting|http://web.me.com/pondini/Time_Machine/Troubleshooting.html] (or use the link in *User Tips* at the top of this forum).
    If that doesn't fix it, add-up the sizes of the visible folders on your system; that should be fairly close to the 120 GB that's shown as used on your internal HD. If you have multiple users, log on as each one to see the size of that user's home folder, as one user, even an Admin user, won't see the actual size of another user's stuff.
    There are some hidden system folders, so the total won't be 120 GB. But it should be within 10 or 20 GB or so.
    Post back with your results, and we'll dig a bit deeper if necessary.

  • I am trying to update my time machine backup on time capsule, but time machine keeps trying to create an entirely new backup (evidenced by the 200GB backup size). How can I get time machine to modify my old backup rather than create a new one?

    I am trying to update my time machine backup on time capsule, but time machine keeps trying to create an entirely new backup (evidenced by the 200GB backup size). How can I get time machine to modify my old backup rather than create a new one?

    It must have found the old backup corrupt.. so you will more than likely have little choice. You can archive off the old backup if it is still useful.
    You can also verify it. See A5 http://pondini.org/TM/Troubleshooting.html
    He also has some info on this problem. eg C13.

  • Backup size says 2.0 GB, but I have all backup options turned off. Why is my backup size still 2.0 GB?

    I had an iPhone 4 updated to the iOS 7.1.2 version, and I recently purchased an iPhone 5s. When I got the 5s, I transferred all of my camera roll pictures from my 4 to my PC in a file folder and deleted all the photos from my 4 camera roll. I also turned off the "camera roll" backup option in my iCloud storage settings. However, my backup size still said I had a large backup size, so I turned off all the apps in the backup options under the iCloud storage tab. Along with all the apps, I turned off the backup for the Mail, Contacts, Calendars, Reminders, etc. Yet, my backup size on my 4 still said 2.0 GB, and my 5s needs more backup storage without purchasing any extra storage.
    I'm not sure if I should completely delete my 4 backup or if there is a solution without completely deleting its backup. If there is a possible solution to decrease my backup size without deleting the backup, what is that solution? If deleting the 4 backup is the best option, what are the "risks" of deleting the backup? Like would I lose anything I restored onto my 5s from the 4 backup, etc.? 

    Hi girdster,
    Thanks for using Apple Support Communities. Based on what you stated, it sounds like you need to manage your iCloud storage. I would recommend that you read this article, This tells you how to manage and how to delete a backup. 
    Manage your iCloud storage - Apple Support
    Cheers,
    Mario

  • Limiting Time Machine backup Size with WD MyBookLive and 10.8

    I cannot take credit for the any part of this solution; merely for merging and clarifying how the solutions discovered by 2 Apple Support Communities contributors much smarter than I (namely “Pondini” – Florida and  “himynameismarek”) - worked perfectly for my situation. All cudo’s to these two!
    I have about average or better PC skills, but am an absolute newbie with Apple. This week I got a new iMac. Having a number of home PC’s all sharing files and back up space on a Western Digital MyBookLive (“WD MBL”) 3TB network drive (NAS), naturally I wanted to use it to backup the new Mac rather than rushing out to buy an Apple Time Capsule.
    There are hundreds of threads on limiting size of a Time Machine (“TM”) backup, many of which required entries in “Terminal” or were devised on older versions of OSX. I’m running OSX Mountain Lion 10.8, so was concerned they may not work.
    The issues I wanted to resolve were:
    Time Machine will use up all of the space on my WD MBL if left to it’s own devices.
    The WD MBL is compatible with Mac and PC’s… which is good… but unlike a back up in Windows 7 Pro which will allow you to make backups in a mapped “share” you create yourself, Apple TM Backups will not; they end up in a hidden folder on the NAS (much like PC backups done with WD Smartware)
    At first I thought maybe I could limit the size of a share created in the MBL, but not possible, at least not that I've seen and I have searched for days.
    The solutions:
    First make sure you have the latest firmware for the WD MBL as of today it is MyBookLive 02.11.09-053. From what I’ve read Western Digital fixed the compatibility issues with 10.8 Mountain Lion just recently.
    Next you need to start TM so that it starts to create a back up. You can stop the back up once you see files being copied. Do this before you walk thru the video tutorial by my Marek below. WD MBL will create the hidden folder you need to find for TM Backups. This folder is called “TimeMachine” but it is not visible even in the “MBL_NAME-backup” folder in Finder.
    Open safari and type “ afp://xxx.xxx.x.xxx ” but use your own ip address of your MBL. Mine was 192.168.1.120, yours will be different.
    It will ask how you want to connect. CHOOSE AS A GUEST even if your MBL is protected… I’m not sure why it works but it does. Then a window will come up asking which share you’d like to mount. You will see all of your own shares plus one called software and now one called “TimeMachine”. Choose that one.
    Now in “Finder” you will see a mounted shared item called “YOUR_MBL_NAME-“ (the same as the one that is probably already there but with a dash(-) at the end). You’ll also see a new “device” in the device list called “Time Machine Backups” (If you already have watched the video tutorial by Marek, you’d know you are looking for a file called “YOUR_MACHINE_NAME.sparsebundle”. Well if you browse the folder “Backups.backupdb” in the Time Machine Backups device you won’t find it… again I don’t know why but you won’t. It resides in the hidden folder called “TimeMachine” that is now visible in the thing you just mounted in step 4)
    NOW watch this video tutorial http://youtu.be/Nq7mSizqUSI and follow it step by step.
    Voila... issues resolved. Thank you Pondini and Marek!

    Try Use Terminal to limit Time Machine sparcebundle size on timecapsule,
    should work to limit Time Machine backup size on any NAS or external disk (or not...)
    sudo defaults write /Library/Preferences/com.apple.TimeMachine MaxSize 500000
    to return to ilimited
    sudo defaults delete /Library/Preferences/com.apple.TimeMachine MaxSize
    if you want to reclame deleted files space shrink it use
    hdiutil resize -size 500g -shrinkonly /Volumes/TimeMachineYOURNAME/YOURNAME.sparsebundle/
    Regards

  • HT4847 I am only backing up camera roll and a my media app which are 890 MB and 414 MB, i backup everynight why is it full it says my backup size is 4.7 GB when I only have those 2 things?

    I am only backing up camera roll and a my media app which are 890 MB and 414 MB, i backup everynight why is it full it says my backup size is 4.7 GB when I only have those 2 things?

    The back up is supposed to be a rolling back up and therefore may still contain data from previous back ups. To free up space you may wish to delete the back up and start again.

  • Big increase in backup size after upgrade

    Hello
    I've upgraded my database from 10.2.0.4 SE on win2003-SP2 to 11.2.0.1.0 SE on win2008-R2-SP1 64-bit, by doing exp/imp
    The databasefiles size sums up to about 150gb on each server
    But when I do a normal RMAN database backup of the datafiles on the new database (backup device type disk database;) I get a backupset that is 78 gb in size .
    On the old database the backup size was only 36 gb
    The data in the two database is about the same, and I dont believe I'm using compression on  any of the database backups. I've listet the RMAN  paramaters below
    Can anybody tell me why I'm seeing this huge increase in backup size?
    Best regards
    Klaus Mogensen
    10g RMAN parameter settings:
    CONFIGURE RETENTION POLICY TO REDUNDANCY 2;
    CONFIGURE BACKUP OPTIMIZATION OFF; # default
    CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
    CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO COMPRESSED BACKUPSET PARALLELISM 1;
    CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT   'C:\backup\vtrack\backupset\ora_df_%Y_%M_%D_%T_%t_s%s_s%p.bkp';
    CONFIGURE MAXSETSIZE TO UNLIMITED; # default
    CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
    CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
    CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO 'D:\ORACLE\PRODUCT\10.2.0\DB_1\DATABASE\SNCFVTRACK.ORA'; # default
    11g RMAN parameter settings:
    CONFIGURE RETENTION POLICY TO REDUNDANCY 2;
    CONFIGURE BACKUP OPTIMIZATION OFF; # default
    CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
    CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
    CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE MAXSETSIZE TO UNLIMITED; # default
    CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
    CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
    CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default
    CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO 'E:\ORACLE\PRODUCT\11.2.0\DBHOME_1\DATABASE\SNCFVTRACK.ORA'; # default

    This is why,
    Your 10g channel device configuration:
    CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO COMPRESSED BACKUPSET PARALLELISM 1
    Your 11g channel device configuration:
    CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
    Your 10g backups were being compressed, the 11g are not.

  • How to get Systemstate Backup size using PowerShell command in Windows 2008 R2

    Hi,
    We using WBSummary command to get completed backup status.
    I need to find how much data is backed up  using powerShell command .
    Is there any way to get the details , i can see the GUI but no in command.
    Please advise
    Regards Gopi K

    Hi,
    You mentioned that you can see the system state backup size in the GUI. Does the backup size mean the amount of date transferred?
    It seems that there is no such a PowerShell to get Systemstate Backup size. You may need to you need a PowerShell scripts to do this work.
    http://social.technet.microsoft.com/Forums/windowsserver/en-US/home?forum=ITCG
    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.

  • Backup size is increased after resync catalog

    Hi everyone,
    I have describe my problem, if anyone have a solution please provide me.
    Rman catalog database version : 10.2.0.1.0, OS : red hat linux
    Target database version : 10.2.0.5.0, OS : solaris 10
    rman catalog database space is full, then i move my example tablespace to another location, but i forgot to change the ownership of new file.
    And I have no backup of my rman catalog database. so i offline the datafile first for opening the rman catalog database after opening the database I have offline the whole example tablespace and this tablespace cannot contain any thing related the catalog.
    after that I used the command : crosscheck archivelog all;
    DELETE EXPIRED ARCHIVELOG ALL
    then i run the command : CROSSCHECK BACKUP;
    DELETE EXPIRED BACKUP;
    then i run the command : report obsolete;
    delete obsolete;
    then i run the command : RESYNC CATALOG;
    then i run the command : change archivelog all validate;
    after doing all the thing when I am taking a backup of archive log by using following command :
    run {allocate channel c1 device type disk format '/appl2/prodback_rman/prod_fullbackup/ARCH_%d_%s.bak';
    backup archivelog all;
    before performing all the above thing my archive backup of whole day is around 5gb but after the above thing my archive backup of one day is around : 126gb
    and my level0 backup is alright after and before the above thing and the size is around : 139gb
    the script for the full backup is :
    run {allocate channel c1 device type disk format '/appl2/prodback_rman/prod_fullbackup/FULL_%d_%s_%c.bak';
    backup incremental level 0 database skip offline;
    after that I have perform the incremental level 1 backup by using the following script :
    run {allocate channel c1 device type disk format '/appl2/prodback_rman/prod_fullbackup/INC1_%d_%s_%c.bak';
    backup incremental level 1 database;
    before the above activity the size of incremental backup is around : 4.5gb but after performing the above activity the incremental backup size is around : 120gb
    it is very critical for me, if any one have the solution please provide me as early as possible.
    Thanks & Regards
    Rakesh Kumar

    Hi Hemant K Chitale,
    you said that I am using the COMPRESSED BACKUPSETs till 22-Jan, so I am posting
    the rman configuration here that is used before all this happening and same
    configuration is used right now.
    but before resync catalog the archivelog is generated only one location then I used to archive log
    dest for archive log generation then after 5 month I will resync my catalog. may be it is the
    reason.
    because there are no compressed backupset is defined in the rman configuration.
    RMAN> show all;
    RMAN configuration parameters are:
    CONFIGURE RETENTION POLICY TO REDUNDANCY 2;
    CONFIGURE BACKUP OPTIMIZATION ON;
    CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/appl2/prodback_rman/prod_fullbackup/ctrl_%F';
    CONFIGURE DEVICE TYPE DISK PARALLELISM 2;
    CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE CHANNEL 1 DEVICE TYPE DISK FORMAT '/appl2/prodback_rman/prod_fullbackup/prod_%d_%s_%c.bak', '/appl2/prodback_rman/usb/prod_%d_%s_%c.bak';
    CONFIGURE MAXSETSIZE TO 20 G;
    CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
    CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
    CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/appl2/prodback_rman/prod_fullbackup/snapcf_PROD.f';
    Archive log generation log on the daily basis.
    SQL> select trunc(COMPLETION_TIME,'DD') Day, thread#,
    round(sum(BLOCKS*BLOCK_SIZE)/1048576) MB,
    count(*) Archives_Generated from v$archived_log
    group by trunc(COMPLETION_TIME,'DD'),thread# order by 1;
    DAY THREAD# MB ARCHIVES_GENERATED
    04-FEB-13 1 2776 37
    05-FEB-13 1 16767 220
    06-FEB-13 1 16545 216
    07-FEB-13 1 15772 208
    08-FEB-13 1 15056 198
    09-FEB-13 1 18486 244
    10-FEB-13 1 17591 232
    11-FEB-13 1 18163 238
    12-FEB-13 1 15062 198
    13-FEB-13 1 26383 342
    14-FEB-13 1 36279 462
    DAY THREAD# MB ARCHIVES_GENERATED
    15-FEB-13 1 34010 432
    16-FEB-13 1 32230 413
    17-FEB-13 1 31904 408
    18-FEB-13 1 33448 426
    19-FEB-13 1 34639 444
    20-FEB-13 1 36684 468
    21-FEB-13 1 27547 352
    right know the archive log backup size by rman is around 19gb per day.
    so tell me how we reduce the size of my archive log backup according to
    my rman configuration and how can i reduce the archive log generation on
    my production server on daily basis.
    Thanks & Regards
    Rakesh Kumar

  • DB read_only backup size increase

    Hi Experts,
    Have below 3 queries. Kindly enough throw some light
    1) I have 1 database which is read_only. tlog backup size daily fluctuates how this is possible please...
    2)another question related to another problem
    backupset table of 1 database shows 65 MB full readonly database backup(named: abcd)  daily. here i am somply taking backup from litespeed.
    when i run backup database abcd to disk="c:\abcd.bak" with copy_only,checksum,init (in read only mode) it shows size of 57 MB only. Why there's gap as database is in read_only mode.
    3) buffercount and maxtransfersize are safe if i have x64bit machine and 100 GB RAM. restore verify completed successfully.
    Regards
    Manish

    1) Why are you taking a backup of a read only database every day ?
    Since nothing is changing just stick with the backup you already have. As for fluctuations you may be taking a backup that's added on the latest backup so it'll increase over time.
    2) There is no direct correspondence between size in BAK and MDF/LDF. You could have compressed tables or compressed backup, empty space etc etc
    3) Changing buffercount and maxtransfersize are safe to change. But first measure for what you gain from changing them since increasing them will have a higher impact on cpu time.
    Here are some benchmarks on those:
    http://www.mssqltips.com/sqlservertip/2539/options-to-improve-sql-server-backup-performance/
    "If there's nothing wrong with me, maybe there's something wrong with the universe!"

Maybe you are looking for