Backup with tandberg type
i want backup oracle
using tandberg type
with rman
i donnot know how to do it
details:
oracle runs 24/7
Does anyone have the idea?
If the backup you're trying to restore from is encrypted, you will not be able to use that backup if you can't remember the encrypted backup passcode.
If on a Mac, & you elected to save the passcode to your Keychain, you can recover the passcode from your Keychain. Otherwise, your data is unrecoverable.
While you can continue to sync/backup, if you can't remember it & want to remove it, you'll have to delete your existing backups & restore the phone as a new device. Your data will be unrecoverable.
You delete your existing backups here: iTunes>Preferences>Devices.
Similar Messages
-
Required to take backup with out TSM in PROD server.
Dear all,
I required to take backup with out using TSM .
we have got error in TSM . so that i am getting error .
Prod server backup is working automated through TSM .
now i need to take Online backup with out using TSM like DEV and QA (Manual backup) .
For DEV and QA server backup is manual . i am simply moved the tape to tape library and fired the online backup as well same QA also .
Now my query is reqiured to take backup with out the help of TSM in PROD server . Is it possible ?
2 profiles are configured for Online backup and offline backup .
pls check the below profiles .
initSIDdaily.sap -
> Online backup .
initSIDweekly.sap -
> Offline backup
is there any parameter i need to change ?
Kindly adviseDear all ,
I have initialised the Tape IRPB01 , after i have try to tkae backup , i got below error .
BR0051I BRBACKUP 7.00 (48)
BR0055I Start of database backup: bedqreyq.ant 2010-07-12 13.19.44
BR0484I BRBACKUP log file: /oracle/IRP/sapbackup/bedqreyq.ant
BR0477I Oracle pfile /oracle/IRP/102_64/dbs/initIRP.ora created from spfile /ora
cle/IRP/102_64/dbs/spfileIRP.ora
BR0280I BRBACKUP time stamp: 2010-07-12 13.19.45
BR0319I Control file copy created: /oracle/IRP/sapbackup/cntrlIRP.dbf 15122432
BR0280I BRBACKUP time stamp: 2010-07-12 13.19.46
BR0057I Backup of database: IRP
BR0058I BRBACKUP action ID: bedqreyq
BR0059I BRBACKUP function ID: ant
BR0110I Backup mode: ALL
BR0077I Database file for backup: /oracle/IRP/sapbackup/cntrlIRP.dbf
BR0061I 42 files found for backup, total size 158434.742 MB
BR0143I Backup type: online
BR0112I Files will not be compressed
BR0130I Backup device type: tape
BR0102I Following backup device will be used: /dev/rmt0.1
BR0103I Following backup volume will be used: IRPB01
BR0280I BRBACKUP time stamp: 2010-07-12 13.19.46
BR0256I Enter 'c[ont]' to continue, 's[top]' to cancel BRBACKUP:
c
BR0280I BRBACKUP time stamp: 2010-07-12 13.19.52
BR0257I Your reply: 'c'
BR0259I Program execution will be continued...
BR0208I Volume with name IRPB01 required in device /dev/rmt0.1
BR0210I Please mount BRBACKUP volume, if you have not already done so
BR0280I BRBACKUP time stamp: 2010-07-12 13.19.52
BR0256I Enter 'c[ont]' to continue, 's[top]' to cancel BRBACKUP:
c
BR0280I BRBACKUP time stamp: 2010-07-12 13.19.55
BR0257I Your reply: 'c'
BR0259I Program execution will be continued...
BR0280I BRBACKUP time stamp: 2010-07-12 13.19.55
BR0226I Rewinding tape volume in device /dev/rmt0 ...
BR0351I Restoring /oracle/IRP/sapbackup/.tape.hdr0
BR0355I from /dev/rmt0.1 ...
BR0241I Checking label on volume in device /dev/rmt0.1
BR0280I BRBACKUP time stamp: 2010-07-12 13.19.55
BR0226I Rewinding tape volume in device /dev/rmt0 ...
BR0202I Saving /oracle/IRP/sapbackup/.tape.hdr0
BR0203I to /dev/rmt0.1 ...
BR0209I Volume in device /dev/rmt0.1 has name IRPB01
BR0202I Saving init_ora
BR0203I to /dev/rmt0.1 ...
BR0202I Saving /oracle/IRP/102_64/dbs/initIRPdaily.sap
BR0203I to /dev/rmt0.1 ...
BR0280I BRBACKUP time stamp: 2010-07-12 13.19.59
BR0198I Profiles saved successfully
BR0280I BRBACKUP time stamp: 2010-07-12 13.20.00
BR0315I 'Alter tablespace PSAPSR3 begin backup' successful
BR0202I Saving /oracle/IRP/sapdata1/sr3_1/sr3.data1
BR0203I to /dev/rmt0.1 ...
BR0278E Command output of 'LANG=C dd obs=64k bs=64k if=/oracle/IRP/sapdata1/sr3_
1/sr3.data1 of=/dev/rmt0.1':
dd: /oracle/IRP/sapdata1/sr3_1/sr3.data1: Invalid argument
BR0280I BRBACKUP time stamp: 2010-07-12 13.20.00
BR0279E Return code from 'LANG=C dd obs=64k bs=64k if=/oracle/IRP/sapdata1/sr3_1
/sr3.data1 of=/dev/rmt0.1': 2
BR0222E Copying /oracle/IRP/sapdata1/sr3_1/sr3.data1 to/from /dev/rmt0.1 failed
due to previous errors
BR0280I BRBACKUP time stamp: 2010-07-12 13.20.02
BR0317I 'Alter tablespace PSAPSR3 end backup' successful
BR0056I End of database backup: bedqreyq.ant 2010-07-12 13.20.00
BR0280I BRBACKUP time stamp: 2010-07-12 13.20.02
BR0054I BRBACKUP terminated with errors
BR0292I Execution of BRBACKUP finished with return code 5
BR0668I Warnings or errors occurred - you can continue to ignore them or go back
to repeat the last action
BR0280I BRTOOLS time stamp: 2010-07-12 13.20.02
BR0670I Enter 'c[ont]' to continue, 'b[ack]' to go back, 's[top]' to abort:
Kindly Advise -
After upgrading to Mountain Lion, I repeatedly get this message: "There was a problem connecting to the server. URLs with the type "file:" are not supported.
Why?
What can be done to eliminate it?Open the Time Machine pane in System Preferences. If it shows that Time Machine is ON, click the padlock icon in the lower left corner, if necessary, to unlock it. Scroll to the bottom of the list of backup drives and click Add or Remove Backup Disk. Remove all the disks, then add them back. Quit System Preferences. Test.
-
Backup with retention policy to recovery window of N days
Hello,
I've issued command to create database incremental backup with configuration:
run
configure retention policy to recovery window of 14 days;
backup incremental level 1 cumulative
tag daily_incr_14_days
database
plus archivelog delete all input;
All parameters are set to their default values and database backups goes to FRA. I've got recovery catalog connected and all RC_ views at my disposal.
1) Is there any way to find out, what recovery window was used for backup from any command in rman or query from RC_ views or local database views (information from control file)?
2) If I use other recovery window setting with configure command what would rman crosscheck or report commands do?
BR
Patrycjusz.TenakaKhan wrote:
Mahir,
thanks for answer - this means that recovery window should be used mainly for maintenance purposes (crosscheck, delete obsolete, report need backup etc.) and it's not related to actual retention period with backup pieces like 'keep until' clause for backup ... database command (this information are saved with backup as I could check in rc_backup_set view from recovery catalog)?
Yes it is.
Maintaining RMAN Backups and Repository Records
keepOption
backup retention policy
A user-defined policy for determining how long backups and archived logs must be retained for media recovery. You can define a retention policy in terms of backup redundancy or a recovery window.
RMAN retains the data file backups required to satisfy the current retention policy, and any archived redo logs required for complete recovery of those data file backups.
recovery window
A recovery window is one type of RMAN backup retention policy, in which the DBA specifies a period of time and RMAN ensures retention of backups and archived redo logs required for point-in-time recovery to any time during the recovery window.
The interval always ends with the current time and extends back in time for the number of days specified by the user. For example, if the retention policy is set for a recovery window of seven days, and the current time is 11:00 AM on Tuesday,
RMAN retains the backups required to allow point-in-time recovery back to 11:00 AM on the previous Tuesday.
Regards
Mahir M. Quluzade -
new macbook pro receving this message: There was a problem connecting to the server. URLs with the type "file:" are not supported. What is causing this and how do
Open the Time Machine pane in System Preferences. If it shows that Time Machine is ON, click the padlock icon in the lower left corner, if necessary, to unlock it. Scroll to the bottom of the list of backup drives and click Add or Remove Backup Disk. Remove all the disks, then add them back. Quit System Preferences. Test.
-
I have just upgraded to Mountain Lion from Leopard, but now I keep getting this message when I open some web-pages and every time I wake the Mac up after going to sleep. For some odd reason I get it in Swedish sometimes (installed language) and some times in English...
There was a problem connecting to the server.
URLs with the type "file:" are not supported.
OK
What is this and how can I get rid of it. I use Firefox and have updated to latest version.Open the Time Machine pane in System Preferences. If it shows that Time Machine is ON, click the padlock icon in the lower left corner, if necessary, to unlock it. Scroll to the bottom of the list of backup drives and click Add or Remove Backup Disk. Remove all the disks, then add them back. Quit System Preferences. Test.
-
I keep getting an error message saying "There was a problem connecting to the server. URLs with the type "file:" are not supported" Can someone help me locate and get rid of this error.
Open the Time Machine pane in System Preferences. If it shows that Time Machine is ON, click the padlock icon in the lower left corner, if necessary, to unlock it. Scroll to the bottom of the list of backup drives and click Add or Remove Backup Disk. Remove all the disks, then add them back. Quit System Preferences. Test.
-
My Mac suddenly started getting a pop up message saying "There was a problem conecting to the server. URLs with the type "file" are not supported." My internet is working fine,no problem connecting. I just keep getting this message which I click off and continue working.
Open the Time Machine pane in System Preferences. If it shows that Time Machine is ON, click the padlock icon in the lower left corner, if necessary, to unlock it. Scroll to the bottom of the list of backup drives and click Add or Remove Backup Disk. Remove all the disks, then add them back. Quit System Preferences. Test.
-
Hello,
I would like to ask you about advice.
We have MSSQL 2008 R2, 32 bit. Memory is 4GB, split into 2GB for Windows and 2GB for applications. Database has recovery model simple because we have replicated data into other servers ( 2 ). Contemporary we work with 2 servers. Max memory for MSSQL is 2048
MB.
We set the backup as follows:
USE MSDB
GO
DECLARE @JMENO_ZALOHY VARCHAR(120)
SELECT @JMENO_ZALOHY = 'E:\backup\BackupSQL\1 Pondeli\DAVOSAM_'+ convert( varchar(2), datepart( hh, getdate() ) ) + '00_DEN_DIFF.bak'
SELECT @JMENO_ZALOHY
BACKUP DATABASE [DAVOSAM]
TO DISK = @JMENO_ZALOHY
WITH INIT, DIFFERENTIAL, CHECKSUM, COMPRESSION
GO
Every second or third day in log there is error message: 'There is insufficient system memory in resource pool 'internal' to run this query' Accurate in time of backup. The error is still repeat, majority in working hours.
Today I have found out, that problem is probably in compression of backup. Because if I removed word: compression, a backup normally runs without error.
Question: Is my hypothesis correct that problem is in backup with compression?
Thank you DavidHello, today evening I have ran backup command bellow. All is OK. Probably MSSQL has cleaned memory. Next attempt I will try in peak next week.
Since time I have removed word compression, in error log is not any error.
I have checked memory as soon as memory gets on top, it is about 1.707 GB the MSSQL writes into log this messgages:
2014-03-14 15:00:04.63 spid89 Memory constraints resulted reduced backup/restore buffer sizes. Proceding with 7 buffers of size 64KB.
2014-03-14 15:00:08.74 Backup Database differential changes were backed up. Database: DAVOSAM, creation date(time): 2014/01/12(22:03:10), pages dumped: 16142, first LSN: 1894063:1673:284,
last LSN: 1894063:1792:1, full backup LSN: 1894053:15340:145, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'E:\backup\BackupSQL\5 Patek\DAVOSAM_1500_DEN_DIFF.bak'}). This is an informational message. No user action is required.
2014-03-14 15:00:12.79 spid72 Memory constraints resulted reduced backup/restore buffer sizes. Proceding with 7 buffers of size 64KB.
2014-03-14 15:00:12.88 Backup Database differential changes were backed up. Database: WEBFORM, creation date(time): 2014/02/01(05:22:47), pages dumped: 209, first LSN: 125436:653:48, last
LSN: 125436:674:1, full backup LSN: 125435:689:36, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'E:\backup\BackupSQL\5 Patek\WEBFORM_1500_DEN_DIFF.bak'}). This is an informational message. No user action is required.
After that the MSSQL reduced memory on 1.692.
USE MSDB
GO
DECLARE @JMENO_ZALOHY VARCHAR(120)
SELECT @JMENO_ZALOHY = 'E:\backup\BackupSQL\6 Sobota\DAVOSAM_'+ convert( varchar(2), datepart( hh, getdate() ) ) + '00_DEN_FULL.bak'
SELECT @JMENO_ZALOHY
BACKUP DATABASE [DAVOSAM]
TO DISK = @JMENO_ZALOHY
WITH INIT, CHECKSUM, COMPRESSION, MAXTRANSFERSIZE=65536
GO
E:\backup\BackupSQL\6 Sobota\DAVOSAM_2100_DEN_FULL.bak
(1 row(s) affected)
Processed 467240 pages for database 'DAVOSAM', file 'DavosAM_Data' on file 1.
Processed 2 pages for database 'DAVOSAM', file 'DavosAM_Log' on file 1.
BACKUP DATABASE successfully processed 467242 pages in 24.596 seconds (148.411 MB/sec).
select * from sys.dm_exec_connections
where net_packet_size > 8192
session_id most_recent_session_id connect_time net_transport protocol_type
protocol_version endpoint_id encrypt_option auth_scheme
node_affinity num_reads num_writes last_read last_write net_packet_size client_net_address
client_tcp_port local_net_address local_tcp_port
connection_id parent_connection_id most_recent_sql_handle
(0 row(s) affected)
SELECT SUM (pages_allocated_count * page_size_in_bytes)/1024 as 'KB Used', mo.type, mc.type
FROM sys.dm_os_memory_objects mo
join sys.dm_os_memory_clerks mc on mo.page_allocator_address=mc.page_allocator_address
GROUP BY mo.type, mc.type, mc.type
ORDER BY 1 DESC;
KB Used type type
29392 MEMOBJ_SORTTABLE MEMORYCLERK_SQLSTORENG
9392 MEMOBJ_SOSNODE MEMORYCLERK_SOSNODE
8472 MEMOBJ_SQLTRACE MEMORYCLERK_SQLGENERAL
5480 MEMOBJ_SECOLMETACACHE USERSTORE_SCHEMAMGR
5280 MEMOBJ_RESOURCE MEMORYCLERK_SQLGENERAL
5008 MEMOBJ_CACHEOBJPERM USERSTORE_OBJPERM
4320 MEMOBJ_SOSSCHEDULER MEMORYCLERK_SOSNODE
2864 MEMOBJ_PERDATABASE MEMORYCLERK_SQLSTORENG
2328 MEMOBJ_SQLCLR_CLR_EE MEMORYCLERK_SQLCLR
2288 MEMOBJ_SESCHEMAMGR USERSTORE_SCHEMAMGR
2080 MEMOBJ_SOSDEADLOCKMONITORRINGBUFFER MEMORYCLERK_SQLSTORENG
2008 MEMOBJ_LOCKBLOCKS OBJECTSTORE_LOCK_MANAGER
1584 MEMOBJ_CACHESTORETOKENPERM USERSTORE_TOKENPERM
1184 MEMOBJ_LOCKOWNERS OBJECTSTORE_LOCK_MANAGER
840 MEMOBJ_SNIPACKETOBJECTSTORE OBJECTSTORE_SNI_PACKET
760 MEMOBJ_SOSDEADLOCKMONITOR MEMORYCLERK_SQLSTORENG
752 MEMOBJ_SESCHEMAMGR_PARTITIONED USERSTORE_SCHEMAMGR
688 MEMOBJ_RESOURCEXACT MEMORYCLERK_SQLSTORENG
616 MEMOBJ_SOSWORKER MEMORYCLERK_SOSNODE
552 MEMOBJ_METADATADB MEMORYCLERK_SQLGENERAL
480 MEMOBJ_SRVPROC MEMORYCLERK_SQLCONNECTIONPOOL
424 MEMOBJ_SQLMGR CACHESTORE_SQLCP
400 MEMOBJ_SBOBJECTPOOLS OBJECTSTORE_SERVICE_BROKER
384 MEMOBJ_SUPERLATCH_BLOCK MEMORYCLERK_SQLSTORENG
384 MEMOBJ_RESOURCEDATASESSION MEMORYCLERK_SQLGENERAL
352 MEMOBJ_SOSSCHEDULERMEMOBJPROXY MEMORYCLERK_SOSNODE
328 MEMOBJ_SBMESSAGEDISPATCHER MEMORYCLERK_SQLSERVICEBROKER
320 MEMOBJ_METADATADB USERSTORE_DBMETADATA
296 MEMOBJ_INDEXSTATSMGR MEMORYCLERK_SQLOPTIMIZER
264 MEMOBJ_LBSSCACHE OBJECTSTORE_LBSS
224 MEMOBJ_XE_ENGINE MEMORYCLERK_XE
216 MEMOBJ_GLOBALPMO MEMORYCLERK_SQLGENERAL
208 MEMOBJ_PROCESSRPC USERSTORE_SXC
200 MEMOBJ_SYSTASKSESSION MEMORYCLERK_SQLCONNECTIONPOOL
200 MEMOBJ_REPLICATION MEMORYCLERK_SQLGENERAL
192 MEMOBJ_SOSSCHEDULERTASK MEMORYCLERK_SOSNODE
176 MEMOBJ_SQLCLRHOSTING MEMORYCLERK_SQLCLR
168 MEMOBJ_SYSTEMROWSET CACHESTORE_SYSTEMROWSET
128 MEMOBJ_RESOURCESUBPROCESSDESCRIPTOR MEMORYCLERK_SQLGENERAL
128 MEMOBJ_CACHESTORESQLCP CACHESTORE_SQLCP
128 MEMOBJ_RESOURCESEINTERNALTLS MEMORYCLERK_SQLSTORENG
120 MEMOBJ_BLOBHANDLEFACTORYMAIN MEMORYCLERK_BHF
120 MEMOBJ_SNI MEMORYCLERK_SNI
88 MEMOBJ_QUERYNOTIFICATON MEMORYCLERK_SQLOPTIMIZER
72 MEMOBJ_HOST MEMORYCLERK_HOST
72 MEMOBJ_INDEXRECMGR MEMORYCLERK_SQLOPTIMIZER
64 MEMOBJ_RULETABLEGLOBAL MEMORYCLERK_SQLGENERAL
56 MEMOBJ_SERVICEBROKER MEMORYCLERK_SQLSERVICEBROKER
56 MEMOBJ_REMOTESESSIONCACHE MEMORYCLERK_SQLGENERAL
56 MEMOBJ_PARSE CACHESTORE_PHDR
48 MEMOBJ_CACHESTOREBROKERTBLACS CACHESTORE_BROKERTBLACS
48 MEMOBJ_APPENDONLYSTORAGEUNITMGR MEMORYCLERK_SQLSTORENG
40 MEMOBJ_SBASBMANAGER MEMORYCLERK_SQLSERVICEBROKER
32 MEMOBJ_OPTINFOMGR MEMORYCLERK_SQLOPTIMIZER
32 MEMOBJ_SBTRANSPORT MEMORYCLERK_SQLSERVICEBROKERTRANSPORT
32 MEMOBJ_CACHESTOREBROKERREADONLY CACHESTORE_BROKERREADONLY
32 MEMOBJ_DIAGNOSTIC MEMORYCLERK_SQLGENERAL
32 MEMOBJ_UCS MEMORYCLERK_SQLSERVICEBROKER
24 MEMOBJ_STACKSTORE CACHESTORE_STACKFRAMES
24 MEMOBJ_CACHESTORESXC USERSTORE_SXC
24 MEMOBJ_FULLTEXTGLOBAL MEMORYCLERK_FULLTEXT
24 MEMOBJ_APPLOCKLVB OBJECTSTORE_LOCK_MANAGER
24 MEMOBJ_FULLTEXTSTOPLIST CACHESTORE_FULLTEXTSTOPLIST
24 MEMOBJ_CONVPRI CACHESTORE_CONVPRI
16 MEMOBJ_SQLCLR_VMSPY MEMORYCLERK_SQLCLR
16 MEMOBJ_VIEWDEFINITIONS MEMORYCLERK_SQLOPTIMIZER
16 MEMOBJ_SBACTIVATIONMANAGER MEMORYCLERK_SQLSERVICEBROKER
16 MEMOBJ_AUDIT_EVENT_BUFFER OBJECTSTORE_SECAUDIT_EVENT_BUFFER
16 MEMOBJ_HASHGENERAL MEMORYCLERK_SQLQUERYEXEC
16 MEMOBJ_SBTIMEREVENTCACHE MEMORYCLERK_SQLSERVICEBROKER
16 MEMOBJ_ASYNCHSTATS MEMORYCLERK_SQLGENERAL
16 MEMOBJ_BADPAGELIST MEMORYCLERK_SQLUTILITIES
16 MEMOBJ_QSCANSORTNEW MEMORYCLERK_SQLQUERYEXEC
16 MEMOBJ_SCTCLEANUP MEMORYCLERK_SQLGENERAL
16 MEMOBJ_XP MEMORYCLERK_SQLXP
8 MEMOBJ_SECURITY MEMORYCLERK_SQLGENERAL
8 MEMOBJ_CACHESTOREBROKERRSB CACHESTORE_BROKERRSB
8 MEMOBJ_EXCHANGEXID MEMORYCLERK_SQLGENERAL
8 MEMOBJ_CACHESTOREVENT CACHESTORE_EVENTS
8 MEMOBJ_CACHESTOREXPROC CACHESTORE_XPROC
8 MEMOBJ_DBMIRRORING MEMORYCLERK_SQLUTILITIES
8 MEMOBJ_SERVICEBROKERTRANSOBJ CACHESTORE_BROKERTO
8 MEMOBJ_CACHESTOREOBJCP CACHESTORE_OBJCP
8 MEMOBJ_CACHESTOREXMLDBELEMENT CACHESTORE_XMLDBELEMENT
8 MEMOBJ_ENTITYVERSIONINFO MEMORYCLERK_SQLSTORENG
8 MEMOBJ_AUDIT_MGR MEMORYCLERK_SQLGENERAL
8 MEMOBJ_EXCHANGEPORTS MEMORYCLERK_SQLGENERAL
8 MEMOBJ_DEADLOCKXML MEMORYCLERK_SQLSTORENG
8 MEMOBJ_CACHESTORETEMPTABLE CACHESTORE_TEMPTABLES
8 MEMOBJ_HTTPSNICONTROLLER MEMORYCLERK_SQLHTTP
8 MEMOBJ_CACHESTOREVIEWDEFINITIONS CACHESTORE_VIEWDEFINITIONS
8 MEMOBJ_CACHESTOREPHDR CACHESTORE_PHDR
8 MEMOBJ_CACHESTOREXMLDBTYPE CACHESTORE_XMLDBTYPE
8 MEMOBJ_CACHESTORE_BROKERUSERCERTLOOKUP CACHESTORE_BROKERUSERCERTLOOKUP
8 MEMOBJ_EVENTSUBSYSTEM MEMORYCLERK_SQLGENERAL
8 MEMOBJ_CACHESTOREBROKERDSH CACHESTORE_BROKERDSH
8 MEMOBJ_SOSDEADLOCKMONITORXMLREPORT MEMORYCLERK_SQLSTORENG
8 MEMOBJ_CACHESTOREXMLDBATTRIBUTE CACHESTORE_XMLDBATTRIBUTE
8 MEMOBJ_CACHESTOREBROKERKEK CACHESTORE_BROKERKEK
8 MEMOBJ_QPMEMGRANTINFO MEMORYCLERK_SQLQUERYEXEC
8 MEMOBJ_CACHESTOREQNOTIFMGR CACHESTORE_NOTIF
(101 row(s) affected)
David -
RMAN backup with smallest backup size
Oralce 11g2 on Redhat 5. The diskspace is our tightest resource, and we want to an incremental backup with level0 on Sunday and level 1 every week days and Saturday. I am to use the comamnds to do the job--Sunday
backup incremental level 0 tag 'level_0' database plus archivelog;
--Other days
backup incremental level 1 database plus archivelog delete all input;I do not think this is the best practice nor produce smallest backup files.
What are you comments and opinions. ThanksPavan, Thank you for reply. Here are the info requested
what is size of DB ??
~250GB, including UNDO and TEMP. It is a dev database and not very big. But we have total 800GB disk space. After setting some housekeeoing folders, and allow some space for data growth, it leaves 180GB for flash_recovery_area.
what would be max size of archive logs generated per day ??
Variable from less than 1 GB to 12 GB
Are you taking backups to tape or Disk ??
Disk. In the 180GB flash_recovery_area, Current backup size is 152GB. If a backup fails to delete obsolete files, the next backup will fill the flash_recovery_area.
Provide the Rman configuration information ??
RMAN> show all;
RMAN configuration parameters for database with db_unique_name TDEV2 are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F';
CONFIGURE DEVICE TYPE DISK PARALLELISM 2 BACKUP TYPE TO BACKUPSET;
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 '/u01/app/oracle/product/11.2.0/dbhome_1/dbs/snapcf_tdev2.f'; # default -
Hi,
I have a windows cluster SAP R3 4.7 with oracle 10.2.
I have implemented backup with brtools 7.0 with split copy, using split_cmd command to split filesystem and post_split_cmd to start sap.
Bac
Brbackup finish successfully but with the warning:
"BR0068W SAP system is running or SAP user is connected to database PRD - database cannot be shut down"
We attach the log of brbackup .
Any idea ?
Thanks.
Maurizio Manera
Detail log: beajdpzw.aff
BR0051I BRBACKUP 7.00 (40)
BR0055I Start of database backup: beajdpzw.aff 2009-04-16 01.50.28
BR0484I BRBACKUP log file: Z:\oracle\PRD\sapbackup\beajdpzw.aff
BR0351I Restoring F:\oracle\PRD\102\database\sapPRD.ora
BR0355I from F:\oracle\PRD\102\database\sapPRD.ora ...
BR0477I Oracle pfile F:\oracle\PRD\102\database\initPRD.ora created from spfile F:\oracle\PRD\102\database\spfilePRD.ora
BR0613I Database instance PRD/PRIMARY is shut down
BR0280I BRBACKUP time stamp: 2009-04-16 01.50.29
BR0304I Starting and opening database instance PRD/PRIMARY ...
BR0280I BRBACKUP time stamp: 2009-04-16 01.50.38
BR0305I Start and open of database instance PRD/PRIMARY successful
BR0101I Parameters
Name Value
oracle_sid PRD
oracle_home F:\oracle\PRD\102
oracle_profile F:\oracle\PRD\102\database\initPRD.ora
sapdata_home K:\oracle\PRD
sap_profile f:\splitscripts\PRD\initPRD_ReplicationManager.sap
backup_mode ALL
backup_type offline_split
backup_dev_type util_file
util_par_file F:\splitscripts\PRD\initPRD_ReplicationManager.utl
primary_db PRD
split_cmd F:\splitscripts\PRD\ERM_PRD.cmd > F:\splitscripts\PRD\logs\split_log.txt
resync_cmd NULL
post_split_cmd F:\splitscripts\PRD\start_PRD_sap.cmd > F:\splitscripts\PRD\logs\post_split_log.txt
system_info prdadm SRB44 Windows 5.2 Build 3790 Service Pack 2 AMD64
oracle_info PRD 10.2.0.2.0 8192 24929 2831181212 SRB31 UTF8 UTF8
sap_info 620 SAPPRD PRD S0893011436 R3_ORA 0020174098
make_info NTAMD64 OCI_10201_SHARE Feb 1 2009
command_line brbackup.exe -p f:\splitscripts\PRD\initPRD_ReplicationManager.sap -t offline_split -u system/****** -d util_file -m all -c
BR0116I ARCHIVE LOG LIST before backup for database instance PRD
Parameter Value
Database log mode Archive Mode
Automatic archival Enabled
Archive destination M:\oracle\PRD\oraarch\PRDarch
Archive format ARC%S_%R.%T
Oldest online log sequence 24926
Next log sequence to archive 24929
Current log sequence 24929 SCN: 2831181212
Database block size 8192 Thread: 1
Current system change number 2831210933 ResetId: 633955817
BR0280I BRBACKUP time stamp: 2009-04-16 01.50.44
BR0307I Shutting down database instance PRD/PRIMARY ...
BR0280I BRBACKUP time stamp: 2009-04-16 01.50.45
BR0308I Shutdown of database instance PRD/PRIMARY successful
BR0280I BRBACKUP time stamp: 2009-04-16 01.50.46
BR0295I Splitting mirror disks...
BR0280I BRBACKUP time stamp: 2009-04-16 02.04.56
BR0296I Split of mirror disks successful
BR0280I BRBACKUP time stamp: 2009-04-16 02.04.56
BR0304I Starting and opening database instance PRD/PRIMARY ...
BR0280I BRBACKUP time stamp: 2009-04-16 02.06.28
BR0305I Start and open of database instance PRD/PRIMARY successful
BR0117I ARCHIVE LOG LIST after backup for database instance PRD
Parameter Value
Database log mode Archive Mode
Automatic archival Enabled
Archive destination M:\oracle\PRD\oraarch\PRDarch
Archive format ARC%S_%R.%T
Oldest online log sequence 24926
Next log sequence to archive 24929
Current log sequence 24929 SCN: 2831181212
Database block size 8192 Thread: 1
Current system change number 2831214167 ResetId: 633955817
BR0280I BRBACKUP time stamp: 2009-04-16 02.06.29
BR1374I Executing post-split command...
BR0280I BRBACKUP time stamp: 2009-04-16 02.08.48
BR1375I Post-split command executed successfully
BR0118I Tablespaces and data files
Tablespace TS-Status F-Status File Size Id. Device Link Type MaxSize IncrSize BlkSize
PSAPPRD ONLINE* ONLINE+ J:\ORACLE\PRD\SAPDATA3\PRD_20\PRD.DATA20 10485768192 23 9 NOLINK FILE 10485760000 20971520 8192
BR0120I Control files
File Size Id. Device Link Type
H:\oracle\PRD\origlogA\cntrl\cntrlPRD.dbf 15024128 0 7 NOLINK FILE
K:\oracle\PRD\sapdata1\system_1\cntrl\cntrlPRD.dbf 15024128 0 10 NOLINK FILE
K:\oracle\PRD\saparch\cntrl\cntrlPRD.dbf 15024128 0 10 NOLINK FILE
BR0280I BRBACKUP time stamp: 2009-04-16 02.08.48
BR0057I Backup of database: PRD
BR0058I BRBACKUP action ID: beajdpzw
BR0059I BRBACKUP function ID: aff
BR0110I Backup mode: ALL
BR0077I Database files for backup:
H:\ORACLE\PRD\ORIGLOGA\LOG_G11M1.DBF
H:\ORACLE\PRD\ORIGLOGB\LOG_G12M1.DBF
H:\ORACLE\PRD\ORIGLOGA\LOG_G13M1.DBF
H:\ORACLE\PRD\ORIGLOGB\LOG_G14M1.DBF
H:\oracle\PRD\origlogA\cntrl\cntrlPRD.dbf
BR0061I 89 files found for backup, total size 724314.986 MB
BR0143I Backup type: offline_split
BR0130I Backup device type: util_file
BR0109I Files will be saved by backup utility
BR0126I Unattended mode active - no operator confirmation required
BR0280I BRBACKUP time stamp: 2009-04-16 02.08.48
BR0229I Calling backup utility with function 'backup'...
BR0278I Command output of 'F:\usr\sap\PRD\SYS\exe\run\backint.exe -u PRD -f backup -i Z:\oracle\PRD\sapbackup\.beajdpzw.lst -t file -p F:\splitscripts\PRD\initPRD_ReplicationManager.utl -c':
BR0280I BRBACKUP time stamp: 2009-04-16 02.18.37
#FILE..... J:\ORACLE\PRD\SAPDATA3\PRD_21\PRD.DATA21
#SAVED.... 1239840533
BR0280I BRBACKUP time stamp: 2009-04-16 04.33.11
#FILE..... J:\ORACLE\PRD\SAPDATA3\PRD_57\PRD.DATA57
#SAVED.... 1239848995
BR0280I BRBACKUP time stamp: 2009-04-16 04.33.11
BR0232I 89 of 89 files saved by backup utility
BR0230I Backup utility called successfully
BR0280I BRBACKUP time stamp: 2009-04-16 04.33.14
BR0229I Calling backup utility with function 'backup'...
BR0278I Command output of 'F:\usr\sap\PRD\SYS\exe\run\backint.exe -u PRD -f backup -i Z:\oracle\PRD\sapbackup\.beajdpzw.lst -t file -p F:\splitscripts\PRD\initPRD_ReplicationManager.utl -c':
BR0280I BRBACKUP time stamp: 2009-04-16 04.33.16
#PFLOG.... Z:\oracle\PRD\sapbackup\beajdpzw.aff
#SAVED.... 1239849194
BR0280I BRBACKUP time stamp: 2009-04-16 04.33.17
#PFLOG.... Z:\oracle\PRD\sapbackup\backPRD.log
#SAVED.... 1239849195
BR0280I BRBACKUP time stamp: 2009-04-16 04.33.21
#PFLOG.... F:\oracle\PRD\102\database\initPRD.ora
#SAVED.... 1239849201
BR0280I BRBACKUP time stamp: 2009-04-16 04.33.21
BR0232I 8 of 8 files saved by backup utility
BR0230I Backup utility called successfully
BR0068W SAP system is running or SAP user is connected to database PRD - database cannot be shut down
BR0056I End of database backup: beajdpzw.aff 2009-04-16 04.33.21
BR0280I BRBACKUP time stamp: 2009-04-16 04.33.22
BR0053I BRBACKUP completed successfully with warningsHi,
> BR0068W SAP system is running or SAP user is connected to database PRD - database cannot be shut down
> BR0056I End of database backup: beajdpzw.aff 2009-04-16 04.33.21
> BR0280I BRBACKUP time stamp: 2009-04-16 04.33.22
> BR0053I BRBACKUP completed successfully with warnings.
As it is offline backup via brbackup it seems sap starts automatically after completion of backup.
So it is giving warnings that sap is already running.
You can ignore it.
Regards,
Nitin Salunkhe -
Since updating to Mountain Lion in the last week, an error message keeps popping up. The graphic is the button with 3 stick men holding hands and the message is "There was a problem connecting to the server. URLs with the type "file:" are not supported". Any solutions found?
Open the Time Machine pane in System Preferences. If it shows that Time Machine is ON, click the padlock icon in the lower left corner, if necessary, to unlock it. Scroll to the bottom of the list of backup drives and click Add or Remove Backup Disk. Remove all the disks, then add them back. Quit System Preferences. Test.
-
Replace iDisk backups with Dropbox?
Every day Backup automatically backs up a whole bunch of key files to my iDisk. When I use Finder to look at iDisk's contents, I see it creates a Full Backup Package once a month (as I've asked it to) and then Incremental Packages every day. But even though I've set it for "Backups after 30 days will be recycled", I see that there are several months worth of backups in there. This raises a concern for me.
I'm about to set Dropbox as my daily backup location replacement for iDisk. But if Backup keeps adding a constantly growing amount of backups with no limit, it will eventually fill up my Dropbox space. Is there some way I can get Backup to limit how many GB it sends to Dropbox?You may want to do some comparisons. Type "DropBox vs Wuala" into Google for instance.
http://lifehacker.com/5818908/dropbox-vs-the-alternatives-which-online-syncing-s ervice-is-right-for-you -
Restore incremental backup with rman
Dear Friends
can u tell me how to restore an incremental backup with rman? i backup my rman with statement below :
1. backup full database format '/oracle/PRD/sapbackup/%U';
the results was :
-rw-r----- 1 oraprd dba 19006996480 Jun 10 12:08 0ojiit4n_1_1
-rw-r----- 1 oraprd dba 12746752 Jun 10 12:08 0pjiiu6b_1_1
2. after that i do incremental backup :
backup incremental level 1 cumulative database format '/oracle/PRD/sapbackup/%U';
the results was :
-rw-r----- 1 oraprd dba 173400064 Jun 10 13:44 0ujij2k0_1_1
-rw-r----- 1 oraprd dba 12746752 Jun 10 13:44 0vjij3qc_1_1
what statement i need to run for restore the incremental backup?run{
ALLOCATE CHANNEL c1 DEVICE TYPE DISK;
RESTORE DATABASE;
RECOVER DATABASE;
The above command will restore your database from the last good RMAN backup. Your last backup is incremental level backup as you posted. The above command will fullfill your requirements -
I tried to do an incremental level 0 backup with archivelogs, it failed with the error messages said that can not recognize file C:\ARCHIVE\ORCL\4_1_684433700.ARC, the error code was ORA-19625. So I added "crosscheck archivelog all;" to the backup script and Redo it.
This time it succeeded, but there is still something I'm confused. I set up two folders to store the archivelogs, during the process, the archivelogs in the folders were not deleted synchronously,for example arhivelog a was deleted from one folder while the same file in the other folder was remained. Below is my backup script
RUN {
ALLOCATE CHANNEL ch00 TYPE DISK;
ALLOCATE CHANNEL ch01 TYPE DISK;
BACKUP
incremental level 0
SKIP INACCESSIBLE
TAG hot_db_bk_level0
FILESPERSET 5
# recommended format
FORMAT '\\dell090121\rman_hotbackup\bk_full_%s_%p_%t'
DATABASE;
sql 'alter system archive log current';
RELEASE CHANNEL ch00;
RELEASE CHANNEL ch01;
# backup all archive logs
ALLOCATE CHANNEL ch00 TYPE DISK;
ALLOCATE CHANNEL ch01 TYPE DISK;
BACKUP
filesperset 20
FORMAT '\\dell090121\rman_hotbackup\al_%s_%p_%t'
ARCHIVELOG ALL DELETE INPUT;
RELEASE CHANNEL ch00;
RELEASE CHANNEL ch01;
# Note: During the process of backing up the database, RMAN also backs up the
# control file. This version of the control file does not contain the
# information about the current backup because "nocatalog" has been specified.
# To include the information about the current backup, the control file should
# be backed up as the last step of the RMAN section. This step would not be
# necessary if we were using a recovery catalog.
ALLOCATE CHANNEL ch00 TYPE DISK;
BACKUP
# recommended format
FORMAT '\\dell090121\rman_hotbackup\cntrl_%s_%p_%t'
CURRENT CONTROLFILE;
RELEASE CHANNEL ch00;
}Even if you have two (or more) archivelog destination directories, the "DELETE INPUT" clause in "BACKUP ARCHIVELOG ..." would delete only archivelogs which it reads for the backup. Thus, because the backup could read from dest_1 (for instance), it would archivelogs from dest_1 but not from dest_2. The Backup is free to backup files at either dest location and delete only what it has backed up, by default with "DELETE INPUT".
However if you specify DELETE ALL INPUT, then Oracle deletes all copies of the ArchiveLogs.
Thus your backup command would be
BACKUP ARCHIVELOG ALL DELETE ALL INPUT;where the first "ALL" is "all archived log sequences available, but only 1 copy of each" while the second "ALL" is "all copies of each archived log backed up by the BACKUP"
Maybe you are looking for
-
Dear CRM gurus. When creating business partner in former GUI (ABAP) we have to save the customer before we can assign marketing atributes. The system issues error message "Business partner with GUID *** does not exist". And we loose all data and we h
-
Problem in CACSDESIGN Transaction
As we try to create an design for application by CACSDESIGN transaction, an error message appears: Table / structure XXXXXX_A_TGT_INQ_PORTAL is not registered as a generation template.
-
External activity PR prob.
Dear Experts, I am very new in SAP PS . I created External Activity for procuring some material. This material will be suppose to send outside after receive from supplier .When I create ext. activity then 1 PR item created agai
-
I'm using firefox 6.0.2 It's making problem with Bangla font ONLY on FACEBOOK others bangli website FORNT SIZE are OK. On the FACEBOOK it shows Bangla font in a very / Too small! I change font SIZE in firefox setting but i can't solve. Pls HELP me ..
-
Can I install leopard on the new mac mini A1347 ?