R705-P35 Recovery File Size

I'd like to create a set of recovery files on a flash drive. How big are those files (i.e. what is the minimum flash drive size I will need)?

Kindly point out the page number where your User's Guide specifies 8 GB as the size required for a USB drive backup. I've read the applicable pages twice and can find no reference to actual size needed for either DVD's or USB Flash Drive. In fact, the instructions specifically say the size varies by computer model and will be shown when the Recovery Creator Utility is started.
C.B.
C.B.
Toshiba Sat. C75D-B7260 Win 8.1 64 Bit--Toshiba Sat. L775D-S7132 Win 7 HP SP1 64 Bit and Win 10 PRO Technical Preview--Toshiba Sat. L305-S5921 Win Vista SP2 32 Bit

Similar Messages

Recovery disk/files size

My notebook OS is Windows 7 Home Premium 64-bit.
I was going to run HP recovery manager and save the recovery files to a 16 GB USB flash drive.
To my surprise the recovery files size is over 19 GB!
I do not want to burn, carry and safeguard five DVDs all my life.
USB flash drive is much safer and portable.
Please provide detailed instructions on how to get this 19 GB down to 14 GB or less.
Any useful response will be much appreciated.

good idea in that hard drives are slightly better than DVDs from safety point of view.
but since laptop's hard drive is out of question (last time i needed the recovery disks because laptop's hard drive failed) i would have to find atleast two other hard drives and occupy about 20GB space on both and hope that both do not fail if and when the time comes.
i would still prefer USB flash drive or SDHC card.
is there no one in HP smart enough to reduce the size?
or is it such a cash cow that HP does not want to let it go?
i am sure if an option to choose what gets included is provided then the user can reduce the size substantially on his/her own.
or alternatively HP can provide an option to create the disks with bare minimum required to recover.
if user wants/needs then he/she can always download the rest from HP website later on.
all this just seems a very avoidable waste of so many people's time and effort.

R705-P35 - Create Recovery Problem

I bought a 16bg flash drive to create the recovery files for my R705-P35 laptop, but then ran into a problem.
1. After inserting the flash drive, and clicking "CREATE," I got the following message:
Format failed! (Note I had previously formatted the flash drive)
(Error Code: 040E2D-00-00000000)
... then ...
An Unexpected Error Occurred.
(Error Code: 040EAE-57-00000000)
... then the following message appeared in the recovery file creator window ...
"The creating process for all media has been cancelled." (my emphasis)
Any ideas or suggestions?

Portege R705-P35
I had previously formatted the flash drive
I'm only guessing here.
If you formatted it for the NTFS file system, try formatting it for FAT32.
-Jerry

What is impact to MDF file size if change database to simple recovery mode

Hi,
Currently I have a Database with 27GB MDF and 80GB LDF.
If I change from Full recovery to Simple recovery mode, would LDF information be transfered to MDF file and make
MDF file size exceed 100GB?

Hi
May I know how to perform point in time recovery? Currently the only backup we perform every 4 hours is the server OS snapshot.
Example :
1. Now is 6pm and some error transaction occurred.
2. We can perform 3pm server OS snapshot recovery on the mdf file. ( We would lost 3 hours data in this case )
3. Could we apply the ldf transaction log after OS snapshot recovery and roll it forward till 5:50pm?
You would be able to perform point in time recovery if you have
1. Database configured in full recovery mode
2. You were taking transaction log backups.(of course with full backup or may be differential)
In your scenario applying snapshot wont help you.What you have to do it you should have full backup in place .If you had full backup ,like full backup at 3 PM then you would have restored it with no recovery.After that suppose you took tansaction log backups
every on hour then restore 1 PM ,2 PM and 3 PM log backup all in nore covery.
Now i should have mentioned first but before restoring full backup you can also take tail log backup read this article
http://technet.microsoft.com/en-us/library/ms179314.aspx
So now after full and all log backups are applied with no recobery apply tail log backup with recovery and its quite possible that you might not have a data loss or in some scenario very small data loss( not 3 hrs as you would have with snapshot)
hope this helps
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

Recovered data show normal file size but icon is different and wont open

We recently had an old lacie drive go bad. got dropped one too many times or whatever.. not our fault but its for an important client.. drive had 200 GB of files.. a lot of stuff.. we took it to recovery and returned 80GB.. not bad.. among the recovered files were the ones we wanted.. and more... more than half retained their full file name.. so we know... but usually the icon for audio file is two red and blue waves. when we saw the icons that we had tried to save on the main computer they were black and white. but they still portrayed
37.6 MB.. like a full normal file... on the recovered data we see the same file size, but the icon is a blank paper with the corner folded over.. we try to import it to pro tools but it wont import.. i think it was recorded in logic but i doubt that matters.. its just audio... im sure the proper info is in there but we have to get the applications to recognize it.. we tried opening it in different apps, but it simply wont.. is it an extension problem? will restore fix it? how should i do it? i appreciate any help!

i tried changing the extension. i changed the icon but it still wont open. the files are sd2f. apple info will not allow a test sounding. sample and bit rate are not displayed. i gotta get these to open up. what should i do?

Cannot open database due to incorrect file size

Hi,
we have a oracle database 8.0.5 and it crashed yesterday. now we cannot open the database (only mount readonly) due to an incorrect filesize of usr1orcl.ora. is there a simple way to open the database?

i'm sorry but it wasnt in archivelog mode.
the ora error codes are:
ORA-01122: datafile name - failed verification check
Cause: The information in the datafile is inconsistent with information from the control file. This could be for any of the following reasons:
The control file is from a time earlier than the datafiles.
The datafile size does not match the size specified in the control file.
The datafile is corrupted.
Action: Make certain that the datafiles and control files are the correct files for this database, then retry the operation.
ORA-01110: datafile name: str
Cause: This message reports the filename involved with other messages.
Action: See the associated messages for a description of the problem.
ORA-01200: actual file size of num is smaller than correct size of num blocks
Cause: The size of the file, as returned by the operating system, is smaller than the size of the file as indicated in the file header and the control file. Somehow the file has been truncated.
Action: Restore a good copy of the datafile from a backup and perform recovery as needed.

How to change archivelog file size in oracle 11g

Hello,
In my oracle 11g database inside flash recovery area how to increase each files size , now it 41 Mb per file iits name is o1_mf_1_161_8mfpwtbj_.arc how to change it to
the understandable name.
Thanks and regards

Hi,
As you know archived log is create when online log is switch. Archived log size might be maximum equal to online redo log size.
Because archived log size is copied from online redo log file, if you want change archived redo log size, then you must change online redo log size.
But you must think, what is advantages and disadvantages of change of online redo log size, it depends direct task LGWR process.
You can change archived redo log name with change LOG_ARCHIVE_FORMAT parameter.
See : http://docs.oracle.com/cd/B19306_01/server.102/b14237/initparams103.htm
Regards
Mahir M. Quluzade

Causes of ORA-01200: actual file size of x is smaller than correct size n ?

Hello everyone
We are running Oracle 11.2.0.3 64-bit E/E on Oracle Linux 6.2 with UEK R2 on X64.
Using Grid and ASM 11.2.0.3 and OMF names.
The database files are alll on SAN, the SAN vendor name not disclosed here to protect the innocent/guilty 8^)
I have a Test database MYDB (in NOARCHIVELOG mode) and after a normal server reboot, not a crash, the following error occured on Oracle database startup.
srvctl start database -d MYDB
PRCR-1079 : Failed to start resource ora.mydb.db
CRS-5017: The resource action "ora.mydb.db start" encountered the following error:
ORA-01122: database file 1 failed verification check
ORA-01110: data file 1: '+ASMDATA/mydb/datafile/system.256.787848913' <<<<<<<<<<---------------------------------------------------- Corrupt file on ASM disk, system tablespace this time
ORA-01200: actual file size of 94720 is smaller than correct size of 98560 blocks <<<<<<<<<<---------------------------------------------------- ERROR message
The ASM disks are all up and disk groups are mounted OK. The ASM protection level is EXTERNAL.
My understanding that the only proper recovery from the above error is to use RMAN Restore Database/File/Tablespace.etc (and then RMAN Recover, when in ArchiveLog mode).
I do have RMAN disk backups, so I don't need to "patch" the database to recover.
This is not my question at this point in time.
My Question is this : what are the most likely causes of such error?
Oracle Database bug? OS bug? Disk driver error? Server hardware failure (bus, memory, etc)? Or a SAN bug?
I expect that Oracle 11g R2 will always come up with the database "clean" if the server reboots or if server crashes (i.e. due to complete power failure) provided the actual storage is not physically damaged.
Our SAN vendor (no names!) says they are of the opinion that it's most likely Oracle database or Oracle Linux 6.x/UEK software bug, or probably Oracle ASM 11.2 bug.
We have opened a support call with Oracle.....
My personal experience dealing with similar database errors on more recent releases of Oracle (9i R2, 10g R2, 11g R2) and also MS-SQL 2005 and 2008 R2 suggests this kind of a problem is most likely related to errors/bugs in storage/drivers/firmware/BIOS and SAN and not likely to be a 'database' or O/S bug.
Perhaps you, good people on this forum, can share their experiences, as unbiased as you can?
Many thanks

Ive seen Ora-1200 twice I think over the years, both times there was disk problems which led to write issues which caused file problems, youve reported no such issues on your side though so if thats actually true, Im thinking bug.

Deleting the C:\System Recovery Files folder

In 2012 someone already posted this and I have the same problem. Can't anyone solve this? How about someone from HP or Microsoft. Problem deleting the C:\System Recovery Files folder ‎01-08-2012 10:37 AM My computer, a HP-Pavillion desktop, model RK575AA-ABA a1740n running Windows Vista Home Premium, was getting more and more sluggish. One morning, when booting, I pressed F11 and clicked on "Backup and Recovery". The process took a while and resulted in a MINWINPC folder on my backup drive containing my C: drive in compressed form. The rest of the process was to take the computer back to its previous capabilities: formatting, installating the factory image of the system and installating my programs. Once this was completed, I decompressed the MINWINPC and it deposited all of the files from my previous C: drive into a "System Recovery Files" folder on my C: drive. From that folder, I copied and pasted the users data.
The C:\System Recovery Files folder is still on my C: drive, it has served its purpose and is not needed any longer. I tried to delete it. I took administrator priviledges and right-clicked the folder and selected the "Delete" command. Surprise! Access was denied and I cancelled the command. I tried a lot of tricks gathered by a search on the Web (take ownership from the virtual menu properties and Security panel, use TakeOwnership and Unlocker) to no avail though I had very little problem deleting users data and all the files resulting from the installation of applications. Deleting the AppData folder required more patience but there was no way to delete sub-folders of Program Files containing Window programs (Internet Explorer, Microsoft Security Client, Windows Calendar, ...). An attempt to use Unlocker even resulted in a BSOD indicating a last ditch effort by Windows to save its integrity.
What can I do?

Unless this folder is excessive in size, why be worried? If you absolutely have to remove the folder, you could do it outside of Windows, since windows will not let it be done. My choice is to get a Linux Live, make the CD to load it and then reboot to the Linux by booting to the Linux Live CD. It will not alter the Windows install but will allow the user to remove or write whatever they want to the hard drive. I have done this many times. To use a user friendly Distro look for Linux Mint or Ubuntu.Be cautioned that bad things can happen to any other files if any are accidentally altered or deleted will using this method. The risk however is yours, depending on how much this Recovery file folder is annoying to you.

Increase redolog file size - Merits and Demerits

Hi
Currently, we are in 9.2.0.7.0 oralce version and having redolog file sizes (Mirrlog and origlog) of 100MB.
Now we are planning to increase the size to 200 MB so that we could reduce the number of archive log files.
Can you please let me know what would be the demerits of bigger size in redolog files?
And also let me know the step by step process how to increase the size of redolog files?
Thank you

> I understand what you are saying but in our situation our backup policy is one time online backup and one time offline backup in a week.....Online backup is on Thu and Offline backup is on Sunday.......
>
> In case of system crash if needed we would need to apply archive log files; If we have lesser number of archive logs; recover database would be faster.......correct me if am wrong.
You are wrong.
Ok, let's see an example:
You took your backup on sunday midnight and your DB needs recovery on wednesday.
Meanwhile you created say, 800 M worth of redolog data per day.
That sums up to (monday, tuesday, wednesday) 3x800 M = 2400 M that need to be recovered.
Going with your current setup (100 M redolog size) the largest archivelog file can be 100 M, makes 24 files to restore and recover.
After changing the redologsize to, say 200 M, you only have 12 files to restore and recover.
But know what? It's still 2400 M of data.
Since you will likely not put every archivelog file to its own tape, but rather change the tape each day (just an assumption) or maybe don't use manually operated tapes at all, the little latency overhead in handling tapes doesn't count in to your overall recovery time.
All in all you still need to feed the same amount of data to the recovery process.
Apart from this:
if you're discussing short recovery times, than you'd never perform just two data backups a week.
You'd make online backups every day - maybe incremental ones.
You' d use the flashback recovery area.
An additional thing often overlooked: in many cases the ultimate performance killer for a restore/recovery scenario is not the technology in use.
It's that when the case is there, the DBA is not sure anymore, what do to.
He wonders:
Where the good backups are.
How to get them back from the 3rd party backup tool.
How to check them.
Where to get a different storage system because the original one is broken.
How to figure out what needs recovery
How the tools work
By ensuring that you always master the theory and the how to of restore and recovery - that's how you make it quick and painless (and dataloss-less).
regards,
Lars

How to avoid db_recover "file size not a multiple of the pagesize" error?

I am writing some backup and recovery scripts for a Berkeley DB application. I'm using the Oracle supplied db_hotbackup.exe and db_recover.exe executables (DB 4.5.20). My very first recovery unit test has resulted in the following error from db_recover:
"file size not a multiple of the pagesize"
What is the cause of this error, and how do I create my backup files to avoid this problem?

This error message indicates that a file that should be made up of pages of a certain size is not a multiple of that size. For example, if a database file configured with 4KB pages was found in a 10KB file, you would get this error message.
Can you check that however the scripts manipulate the database files, they don't add or remove any bytes from the end?
Regards,
Michael Cahill, Oracle.

Camera Raw file size

I have accidently noticed that Camera Raw's files size nearly doubled between 6.4 and 6.5. Not that I care about a few megs of lost disk space, but what little secrets are there hidden? I don't remember any major new features being added.
P.S. I have not been around for a good couple of months, so maybe I missed something.

No, I said "no new features" in ACR 6.5, but a big jump in file size.
Camera Raw.8bi is 11.9 MB for version 6.4
Camera Raw.8bi is 19.0 MB for version 6.5
Remember how ACR 5.7 had no UI for editing PV2010 adjustments, but could interpret it to assure some compatibility of the old Photoshop CS4 with the new process? At first, I thought maybe it's the same thing here: there's some code in ACR 6.5 for PV2012 interpretation. But seems a bit unlikely, given that it was released about 5 month ago and PV2012 is still considered unfinished in LR4.
Then I thought it has something to do with fixing the dreaded "hue shift when using Recovery" issue. But that was fixed in 6.4 already. (BTW, how come this went unnoticed, without any mention of it in release notes? This was a huge problem for some images and fixing also caused a major difference in rendering of some images, thus braking backward compatibility.)
But I don't believe that the sudden doubling of ACR file size is an accident either.

Unable to set max log file size to unlimited

Hi all,
Hoping someone can give me an explanation of an oddity I've had. I have a series of fairly large databases. I wanted the make the database log files 8GB in size with 8GB growth increments with
unlimited maximum file size. So, I wrote the script below. It seems to have worked but the database max size doesn't show as unlimited, it shows as 2,097,152MB and cannot be set to unlimited using a script or in SSMS by clicking on the unlimited radio button.
2TB is effectively unlimited anyway but why show that rather than actually setting it to unlimited?
USE
[master]
GO
--- Note: this only works for SIMPLE RECOVERY MODE. FOR FULL / BULK RECOVERY modes you need to backup the transaction log instead of a CHECKPOINT.
DECLARE
@debug
varchar(1)
SET @debug =
'Y'
DECLARE
@database
varchar(255)
DECLARE
@logicalname
varchar(255)
DECLARE
@command
varchar(8000)
DECLARE
database_cursor
CURSOR LOCAL
FAST_FORWARD FOR
select
DB_NAME(database_id)
as DatabaseName
name
as LogicalName
from
master.sys.master_files
where
file_id
= 2
AND type_desc
= 'LOG'
AND physical_name
LIKE '%_log.ldf'
AND
DB_NAME(database_id)
NOT IN('master','model','msdb','tempdb')
OPEN
database_cursor
FETCH
NEXT FROM database_cursor
into @database,@logicalname
WHILE
@@FETCH_STATUS
= 0
BEGIN
SET
@command
= '
USE ['
+ @database
+ ']
CHECKPOINT
DBCC SHRINKFILE('''
+ @logicalname
+ ''', TRUNCATEONLY)
IF
(@debug='Y')
BEGIN
PRINT
@command
END
exec
(@command)
SET
@command
= '
USE master
ALTER DATABASE ['
+ @database
+ ']
MODIFY FILE
( NAME = '''
+ @logicalname
+ '''
, SIZE = 8000MB
ALTER DATABASE ['
+ @database
+ ']
MODIFY FILE
( NAME = '''
+ @logicalname
+ '''
, MAXSIZE = UNLIMITED
, FILEGROWTH = 8000MB
IF
(@debug='Y')
BEGIN
PRINT
@command
END
exec
(@command)
FETCH
NEXT FROM database_cursor
INTO @database,@logicalname
END
CLOSE
database_cursor
DEALLOCATE
database_cursor

Hi,
http://technet.microsoft.com/en-us/library/ms143432.aspx
File size (data)
16 terabytes
16 terabytes
File size (log)
2 terabytes
2 terabytes
Thanks, Andrew
My blog...

ORA-19510: failed to set size with ORA-27059: could not reduce file size

Hi,
I have RMAN backup implemented and getting below error.
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on c1 channel at 01/12/2014 04:28:37
ORA-19510: failed to set size of 12839996 blocks for file "/home/oracle/DBBACKUP/Oracle10g1/Full_Backup/DB_Backup_201401128366598241" (blocksize=16384)
ORA-27059: could not reduce file size
Linux Error: 28: no space left on device
Additional information: 2
I have checked with following scenarios:
1. taking backup by setting the MAXSETSIZE parameter value greater than the maximum size of tablespace.
2. taking compressed incremental backup with maxsetsize as unlimited.
3. taking compressed incremental backup with maxpiecesize value as 20G/40G/80G/120G and maxsetsize as unlimited.
Following is the RMAN backup script:
RMAN> run
2> {
3> allocate channel c1 device type disk maxpiecesize 120G
4> format '/home/oracle/DBBACKUP/Oracle10g1/Full_Backup/DB_Backup_%Y%M%D%t%p';
5> backup incremental level 0 as compressed backupset database plus archivelog delete input;
6> crosscheck backup of database;
7> crosscheck backup of controlfile;
8> crosscheck archivelog all;
9> delete noprompt expired backup of database;
10> delete noprompt expired backup of controlfile;
11> delete noprompt obsolete recovery window of 15 days;
12> release channel c1;
13> }
14> exit;
Oracle database version is 10.2.0.1.
The database is on Linux system and we are taking the RMAN backup on mounted Windows NTFS disk.
The remaining space on NTFS system 1.7TB and the total database size 850GB. Used size by database is 500GB.
Regards,
Yogesh.

Hi,
First get the backup piece size its trying to allocate for file "/home/oracle/DBBACKUP/Oracle10g1/Full_Backup/DB_Backup_201401128366598241"
= 12839996*16384
= 210370494464/1024/1024/1024
=195.9GB
Its trying to allocate ~196GB for the file.
1. Make sure the RMAN backup piece won’t exceed the O/S permitted filesize limit.
2. But we can restrict the RMAN backup piece using the MAXPIECESIZE option.
You restricted it to 120GB but actual requirement to allocate backup piece file is ~196GB.
I think you need to change the MAXPIECESIZE and give it a try.
Please update if it succeeded or failed.
Thanks & Regards,
Gayu

FAST_START_MTTR_TARGET - Optimal File Size

I have set Fast_Start_MTTR_Target to 3600 (1 hour)...when I query v$instance_recovery view it says that 17929 MB is my suggested log file size. They are now sized at 300MB. This can't be correct, can it? I can't have a 17GB log file. This is Oracle JD Edwards though....but what else should I look at? I know 300MB is too small.

kirkladb wrote:
I have set Fast_Start_MTTR_Target to 3600 (1 hour)...when I query v$instance_recovery view it says that 17929 MB is my suggested log file size. They are now sized at 300MB. This can't be correct, can it? I can't have a 17GB log file. This is Oracle JD Edwards though....but what else should I look at? I know 300MB is too small. I Beleieve you have to FSMT to too high value i.e 1hr. I dont think you will wait your database to startup after instance crash for 1hr?????? This is i believe is not a gud settings. I would rather go with default value initially
Now you have set FSMT to 1hr and oracle would think that it has to do incremental checkpoint after 1hr (to flush dirty block from buffer cache to disk) . So due to this configuration you are seeing too high value in v$instance_recovery i.e 17929.
Please be notes that value of Optimal_logfile_size is very dynamic in nature and changes its value depending upon the load on system. So you cannot basically rely on this value if your system experience dynamic load.
Looking upon Load in database and amount of redolog file switches per sec/min, If they happen to be too frequent for example 2-3logfile switches per 20 mins, then its considered to be overswitching. Oracle recommends for optimal performance every logfile switch should not happen before 15-20 mins.
So good approach is to first see your alert.log and find out that how many log switches are happening then take a decision to increase the logfile size.
Please check with your organization what they suggest how much time they need to wait while instance do its recovery and then change value from default to higher.
Edited by: 909592 on Mar 29, 2012 11:45 AM

R705-P35 Recovery File Size

Similar Messages

Maybe you are looking for