Backup and Log reduction scheduling in background

Hi Experts,
We need to schedule backup in weakly and monthly automatically. this is to replace new backup in weakly and monthly.
Weakly is deferential backup and monthly is full backup. and also we need log reduction automatically when it will reach more than 1GB.
please help me for this.
Thanks in Advance
Thanks
J Jana

Hello J Jana,
You just have to select a data/time and select the available actions.
Check the following website for further information:
Setting Up the DBA Planning Calendar (MS SQL Server) (SAP Library - BC R/3 Database Guide: MS SQL Server)
About the log shrink, we don't recommend to run shrinks.
Regards,
Eduardo

Similar Messages

Backup and Log that keep the same size

Hi guys, just a quick question...but once that I ran a backup, the log file should become zero or not? I mean, I ran a backup and before my log file ( I'm getting crazy with it) was 153 GB, after the backup is...153 GB...!?
Any thoughts...

The select return NOTHING, the DBCCOPENTRAN(datawarehose) returns incorrect syntax, I shrinked the log file and now is Filesize 1.00, UsedSpace 0.29, FreeSpace 0.71, Perc 70.67
Now I ran a query before the backup and it took 6.01 min, after the backup it took 3.48 and after the shrink log 3.48 again.
It seems that the performance is improved but I need to test with select more incisive.
Query should be DBCC OPENTRAN(datawarehose) anyways as you said database is in simple recovery no need of full backup it would have no affect on Log shrinking. You can always shrink log when when query returns nothing it means nothing is holding back the
query.
Most important thing dont shrink logs it would cause performance issue because when log grows spave has to be zeroed out first before information can be written which can take time and thus can delay query. You should preallocate log file enough space to
grow before hand instead of being reactive with shrink and then again grow.
if your issue is solved close thread by marking the answer
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
My Technet Articles

Exchange 2013 backup and log truncation question

I have a scenario where I have 5 Exchange mailbox servers as members of a DAG, everything running fine, log truncation is working, but seems to be working differently than I am expecting it to work, as in previous versions of Exchange. I am used to the
logs being truncated immediately after the full backup completes. What is happening is that the server is retaining a weeks worth of logs. Everything older than 7 days gets truncated after a full backup completes. Is this expected behavior? I am running Exchange
2013 CU3 on Server 2012, backup software is HP Data Protector 8 running the latest updates. I am running a VSS backup. The DAG is not a lagged copy of the DB's either.

I will check the HP Data Protector setting, but I do not think that setting is valid or anything configurable.
Here is the contents of some various commands for one of my databases, all of which are configured identically, tell me if you see something set incorrectly. Hopefully I have redacted enough internal stuff:
Get-MailboxDatabaseCopyStatus
RunspaceId                            : 8467f253-8c82-4206-a002-14779e701b0e
Identity                              : DB1\EX2013-MB1
Id                                    : DB1\EX2013-MB1
Name                                  : DB1\EX2013-MB1
DatabaseName                          : DB1
Status                                : Mounted
InstanceStartTime                     : 12/10/2013 7:02:44 PM
LastStatusTransitionTime              :
MailboxServer                         : EX2013-MB1
ActiveDatabaseCopy                    : EX2013-MB1
ActiveCopy                            : True
ActivationPreference                  : 1
StatusRetrievedTime                   : 1/7/2014 12:54:19 PM
WorkerProcessId                       : 10292
ActivationSuspended                   : False
ActionInitiator                       : Unknown
ErrorMessage                          :
ErrorEventId                          :
ExtendedErrorInfo                     :
SuspendComment                        :
RequiredLogsPresent                   :
SinglePageRestore                     : 0
ContentIndexState                     : Healthy
ContentIndexErrorMessage              :
ContentIndexVersion                   : 1
ContentIndexBacklog                   : 0
ContentIndexRetryQueueSize            : 0
ContentIndexMailboxesToCrawl          :
ContentIndexSeedingPercent            :
ContentIndexSeedingSource             :
CopyQueueLength                       : 0
ReplayQueueLength                     : 0
ReplaySuspended                       : False
ResumeBlocked                         : False
ReseedBlocked                         : False
MinimumSupportedDatabaseSchemaVersion : 0.121
MaximumSupportedDatabaseSchemaVersion : 0.126
RequestedDatabaseSchemaVersion        :
LatestAvailableLogTime                :
LastCopyNotificationedLogTime         : 1/7/2014 12:38:09 PM
LastCopiedLogTime                     :
LastInspectedLogTime                  :
LastReplayedLogTime                   :
LastLogGenerated                      : 3510
LastLogCopyNotified                   : 3510
LastLogCopied                         : 0
LastLogInspected                      : 0
LastLogReplayed                       : 0
LowestLogPresent                      : 2875
LastLogInfoIsStale                    : False
LastLogInfoFromCopierTime             : 1/7/2014 12:54:19 PM
LastLogInfoFromClusterTime            : 1/7/2014 12:54:16 PM
LastLogInfoFromClusterGen             : 3510
LogsReplayedSinceInstanceStart        : 0
LogsCopiedSinceInstanceStart          : 0
LatestFullBackupTime                  : 12/9/2013 10:31:32 PM
LatestIncrementalBackupTime           :
LatestDifferentialBackupTime          :
LatestCopyBackupTime                  :
SnapshotBackup                        : True
SnapshotLatestFullBackup              : True
SnapshotLatestIncrementalBackup       :
SnapshotLatestDifferentialBackup      :
SnapshotLatestCopyBackup              :
LogReplayQueueIncreasing              : False
LogCopyQueueIncreasing                : False
ReplayLagStatus                       : Enabled:False; PlayDownReason:None; Percentage:0; Configured:00:00:00; Actual:00:00:00
DatabaseSeedStatus                    :
OutstandingDumpsterRequests           : {}
OutgoingConnections                   : {}
IncomingLogCopyingNetwork             :
SeedingNetwork                        :
DiskFreeSpacePercent                  : 99
DiskFreeSpace                         : 4.365 TB (4,798,945,292,288 bytes)
DiskTotalSpace                        : 4.366 TB (4,800,702,836,736 bytes)
ExchangeVolumeMountPoint              :
DatabaseVolumeMountPoint              : C:\Disks\DB1\
DatabaseVolumeName                    : \\?\Volume{b95c7aa2-2cd9-430e-ab75-ea4b0efba659}\
DatabasePathIsOnMountedFolder         : True
LogVolumeMountPoint                   : C:\Disks\DB1\
LogVolumeName                         : \\?\Volume{b95c7aa2-2cd9-430e-ab75-ea4b0efba659}\
LogPathIsOnMountedFolder              : True
LastDatabaseVolumeName                :
LastDatabaseVolumeNameTransitionTime :
VolumeInfoError                       :
IsValid                               : True
ObjectState                           : Unchanged
[PS] C:\Windows\system32>Get-MailboxDatabase -Identity db1 |fl
RunspaceId                                   : 8467f253-8c82-4206-a002-14779e701b0e
JournalRecipient                             :
MailboxRetention                             : 30.00:00:00
OfflineAddressBook                           : \Default Offline Address Book
OriginalDatabase                             :
PublicFolderDatabase                         : CMBS1CC\CMBS1PF\CMBS1PF
ProhibitSendReceiveQuota                     : Unlimited
ProhibitSendQuota                            : 2 GB (2,147,483,648 bytes)
RecoverableItemsQuota                        : 30 GB (32,212,254,720 bytes)
RecoverableItemsWarningQuota                 : 20 GB (21,474,836,480 bytes)
CalendarLoggingQuota                         : 6 GB (6,442,450,944 bytes)
IndexEnabled                                 : True
IsExcludedFromProvisioning                   : False
IsExcludedFromInitialProvisioning            : False
IsSuspendedFromProvisioning                  : False
IsExcludedFromProvisioningBySpaceMonitoring : False
DumpsterStatistics                           :
DumpsterServersNotAvailable                  :
ReplicationType                              : Remote
AdminDisplayVersion                          : Version 15.0 (Build 775.38)
AdministrativeGroup                          : Exchange Administrative Group (FYDIBOHF23SPDLT)
AllowFileRestore                             : False
BackgroundDatabaseMaintenance                : True
ReplayBackgroundDatabaseMaintenance          :
BackgroundDatabaseMaintenanceSerialization   :
BackgroundDatabaseMaintenanceDelay           :
ReplayBackgroundDatabaseMaintenanceDelay     :
MimimumBackgroundDatabaseMaintenanceInterval :
MaximumBackgroundDatabaseMaintenanceInterval :
BackupInProgress                             :
DatabaseCreated                              : True
Description                                  :
EdbFilePath                                  : C:\Disks\DB1\DB\DB1.edb
ExchangeLegacyDN                             : /o=%%%%%/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=EX2013-MB1/cn=Microsoft
Private MDB
DatabaseCopies                               : {DB1\EX2013-MB1, DB1\EX2013-MB2, DB1\EX2013-MB3, DB1\EX2013-MB1-DR,
DB1\EX2013-MB2-DR}
InvalidDatabaseCopies                        : {}
AllDatabaseCopies                            : {DB1\EX2013-MB1, DB1\EX2013-MB2, DB1\EX2013-MB3, DB1\EX2013-MB1-DR, DB1\EX2013-MB2-DR}
Servers                                      : {EX2013-MB1, EX2013-MB2,
EX2013-MB3, EX2013-MB1-DR, EX2013-MB2-DR}
ActivationPreference                         : {[EX2013-MB1, 1], [EX2013-MB2, 2], [EX2013-MB3, 3], [EX2013-MB1-DR, 4], [EX2013-MB2-DR, 5]}
ReplayLagTimes                               : {[EX2013-MB1, 00:00:00], [EX2013-MB2, 00:00:00], [EX2013-MB3,
00:00:00], [EX2013-MB1-DR, 00:00:00], [EX2013-MB2-DR, 00:00:00]}
TruncationLagTimes                           : {[EX2013-MB1, 00:00:00], [EX2013-MB2, 00:00:00], [EX2013-MB3, 00:00:00], [EX2013-MB1-DR,
00:00:00], [EX2013-MB2-DR, 00:00:00]}
RpcClientAccessServer                        : EX2013-MB1.%%%%%%.local
MountedOnServer                              :
DeletedItemRetention                         : 60.00:00:00
SnapshotLastFullBackup                       :
SnapshotLastIncrementalBackup                :
SnapshotLastDifferentialBackup               :
SnapshotLastCopyBackup                       :
LastFullBackup                               :
LastIncrementalBackup                        :
LastDifferentialBackup                       :
LastCopyBackup                               :
DatabaseSize                                 :
AvailableNewMailboxSpace                     :
MaintenanceSchedule                          : {Sun.1:00 AM-Sun.5:00 AM, Mon.1:00 AM-Mon.5:00 AM, Tue.1:00 AM-Tue.5:00 AM, Wed.1:00
AM-Wed.5:00 AM, Thu.1:00 AM-Thu.5:00 AM, Fri.1:00 AM-Fri.5:00 AM, Sat.1:00 AM-Sat.5:00 AM}
MountAtStartup                               : True
Mounted                                      :
Organization                                 : %%%%%%%
QuotaNotificationSchedule                    : {Sun.1:00 AM-Sun.1:15 AM, Mon.1:00 AM-Mon.1:15 AM, Tue.1:00 AM-Tue.1:15 AM, Wed.1:00 AM-Wed.1:15 AM, Thu.1:00 AM-Thu.1:15
AM, Fri.1:00 AM-Fri.1:15 AM, Sat.1:00 AM-Sat.1:15 AM}
Recovery                                     : False
RetainDeletedItemsUntilBackup                : False
Server                                       : EX2013-MB1
MasterServerOrAvailabilityGroup              : DAG1
WorkerProcessId                              :
CurrentSchemaVersion                         :
RequestedSchemaVersion                       :
AutoDagExcludeFromMonitoring                 : False
AutoDatabaseMountDial                        : GoodAvailability
DatabaseGroup                                :
MasterType                                   : DatabaseAvailabilityGroup
ServerName                                   : EX2013-MB1
IssueWarningQuota                            : 1.9 GB (2,040,110,080 bytes)
EventHistoryRetentionPeriod                  : 7.00:00:00
Name                                         : DB1
LogFolderPath                                : C:\Disks\DB1\LOGS
TemporaryDataFolderPath                      :
CircularLoggingEnabled                       : False
LogFilePrefix                                : E01
LogFileSize                                  : 1024
LogBuffers                                   :
MaximumOpenTables                            :
MaximumTemporaryTables                       :
MaximumCursors                               :
MaximumSessions                              :
MaximumVersionStorePages                     :
PreferredVersionStorePages                   :
DatabaseExtensionSize                        :
LogCheckpointDepth                           :
ReplayCheckpointDepth                        :
CachedClosedTables                           :
CachePriority                                :
ReplayCachePriority                          :
MaximumPreReadPages                          :
MaximumReplayPreReadPages                    :
DataMoveReplicationConstraint                : SecondCopy
IsMailboxDatabase                            : True
IsPublicFolderDatabase                       : False
MailboxProvisioningAttributes                :
AdminDisplayName                             : DB1
ExchangeVersion                              : 0.10 (14.0.100.0)
DistinguishedName                            : CN=DB1,CN=Databases,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative
Groups,CN=%%%%%,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=%%%%%%,DC=%%%
Identity                                     : DB1
Guid                                         : 765d01d0-4468-43fd-a1e8-ad205b25c8ee
ObjectCategory                               : %%%%%%.%%%/Configuration/Schema/ms-Exch-Private-MDB
ObjectClass                                  : {top, msExchMDB, msExchPrivateMDB}
WhenChanged                                  : 12/10/2013 7:02:44 PM
WhenCreated                                  : 11/13/2013 11:00:58 AM
WhenChangedUTC                               : 12/11/2013 12:02:44 AM
WhenCreatedUTC                               : 11/13/2013 4:00:58 PM
OrganizationId                               :
OriginatingServer                            : %%%%%-DC4.%%%%%.%%%
IsValid                                      : True
ObjectState                                  : Changed
[PS] C:\Windows\system32>Get-MailboxDatabase -Status | ft Name,Server,LastF*Backup,LastI*Backup,LastD*Backup -AutoSize
Name       Server        LastFullBackup       LastIncrementalBackup LastDifferentialBackup
MB1-DB0    EX2013-MB1    1/6/2014 11:30:46 PM
DB1        EX2013-MB1    1/6/2014 11:30:46 PM
DB2        EX2013-MB1    1/6/2014 11:30:46 PM
MB3-DB0    EX2013-MB3    1/6/2014 10:45:44 PM
DB5        EX2013-MB3    1/6/2014 10:45:44 PM
DB6        EX2013-MB3    1/6/2014 10:45:44 PM
MB2-DB0    EX2013-MB2    1/6/2014 10:15:39 PM
DB3        EX2013-MB2    1/6/2014 10:15:39 PM
DB4        EX2013-MB2    1/6/2014 10:15:39 PM
MB1-DR-DB0 EX2013-MB1-DR 1/6/2014 8:00:23 PM
MB2-DR-DB0 EX2013-MB2-DR 1/6/2014 8:15:22 PM

APO Livecache DB Backup and Livecache Auto Log Backup

Hi Guys,
Could you please help me here which tranaction code we use to check APO Livecache DB Backup and Livecache Auto Log Backup
Thank you

Hi,
Livecache DB and log back up looks like can not be accessed from SAP. Database Manager GUI is used.
Please check the below link for helpful information.
http://help.sap.com/saphelp_nw04/helpdata/en/f7/499e3c1fbe8c15e10000000a114084/content.htm
Regards,
Saravanan V

Create Scheduled in Background and Output as excel

Hi All,
I have already created an Adhoc Query, and I would like to run it every Sunday and save it as an Excel File automatically. I have already known how to set schedule in background. but I don't know how to set the output format and save it into specific folder. I would like to collect all the file for data warehouse processes.
Please kindly assist me... (help help help)
Thanks
MWidodo

Hi,
You can use the following code
types: begin ot ty_string,
           a type string,
           end of ty_string.
data: it_string type table of ty_string,
         wa_string type ty_string,
         tab type c value cl_abap_char_utilities=>horizontal_tab.
loop at itab(internal table that contains data fetched from database tables for your requirement).
concatenate itab-a itab-b into wa_string separateb by tab.
append wa_string to it_string.
endloop.
Use FM GUI_DOWNLOAD to download it_string to excel sheet.
Regards
Dande

In FCP x backup process is constantly running in background even though its done which results into slow working of FCP x. any idea to resolve the issue. I am using 10.1.3 and facing the problem ever since i have updated my FCP x to 10.1.3

in FCP x backup process is constantly running in background even though its done which results into slow working of FCP x. any idea to resolve the issue? I am using 10.1.3 and facing the problem ever since i have updated my FCP x to 10.1.3

Go into preferences and under playback turn off background render. That helped speed things for me when working with large files.

Backup and restore full and transaction log in nonrecovery mode failed due to LSN

In SQL 2012 SP1 enterprise, when taking a full backup and followed up a transaction log backup immediately, the transaction log backup starts with an earlier LSN than the ending LSN of the full backup. As a result, I cannot restore
the transaction log backup after the full backup both as nonrecovery on another machine. I was trying to make the two machine in sync for mirroring purpose. An example is as follows.
full backup: first 1121000022679500037, last 1121000022681200001
transaction log: first 1121000022679000001, last 1121000022682000001
--- SQL Scripts used
BACKUP DATABASE xxx TO DISK = xxx WITH FORMAT
go
backup log xxx to disk = xxx
--- When restore, I tried the
restore log BarraOneArchive from disk=xxx WITH STOPATMARK = 'lsn:1121000022682000001', NORECOVERY
Also tried StopBeforeMark, did not work either. Complained about the LSN too early to apply to the database

I think that what I am saying is correct .I said in sync mirroring ( i was not talking about witness) if network goes for few minutes or some longer time may be 20 mins ( more than that is reare scenario IS team has backup for that) logs on Principal will
continue to grow as they wont be able to commit because there connection with mirror is gone so commit from mirror is not coming.After network comes online Mirror will replay all logs and will soon try to come up with principal
Books Online says this: This is achieved by waiting to commit a transaction on the principal database, until the principal server receives a message from the mirror server stating that it has hardened the transaction's log to disk. That is,
if the remote server would go away in a way so that the primary does not notice, transactions would not commit and the primary would also be stalled.
In practice it does not work that way. When a timeout expires, the principal will consider the mirror to be gone, and Books Online says about this case
If the mirror server instance goes down, the principal server instance is unaffected and runs exposed (that is without mirroring the data). In this section, BOL does not discussion transaction logs, but it appear reasonable that the log records are
retained so that the mirror can resync once it is back.
In Async Mirroring Transaction log is sent to Mirror but it does not waits for Acknowledgement from mirror and commits the transaction.
But I would expect that the principal still gets acknowledgement that the log records have been consumed, or else your mirroring could start failing f you backup the log too frequently. That is, I would not expect any major difference between sync and async
mirroring in this regard. (Where it matters is when you fail over. With async mirroring, you are prepared to accept some data loss in case of a failover.)
These are theories that could be fairly easily tested if you have a mirroring environment set up in a lab, but I don't.
Erland Sommarskog, SQL Server MVP, [email protected]

Backup and restore logs, quarantines cisco ironport c170

Hello,
Is there anyway to backup and restore logs and quarantine to another ironport c170?
Thanks in advance.
Alexandre

Hello Alexandre,
logs can easily be downloaded via FTP or SCP, there is a folder per logs subscription, i.e.
/mail_logs
/system_logs
/error_logs
Each folder contains multiple logs, thos e are with extention .s are the ones that have rolled over, while .c and .current are the ones currently written to. I would not recommend to upload them to another appliance, as this may cause problems or at least confusion. Quarantines cannot be backed up, that functionality is limited to SMAs (M-series).
Hope that helps,
Andreas

Is RMAN only way to take backup and delete Archive Logs?

On primary db:
===============
OS: Windows 2003 server 32-bit
Oracle: Oracle 10g (10.2.0.1.0) R2 32-bit
On Physical standby db:
===============
OS: Windows 2003 server 32-bit
Oracle: Oracle 10g (10.2.0.1.0) R2 32-bit
Data Guard just configured. Archive Logs are properly being shipped to standby db. Is RMAN only way to take backup and delete Archive Logs from both primary and standby db? What other command can be used?
Thanks

No, but anything else is way more work. Without using RMAN you would have to find another way to keep track of applied logs.
RMAN make this very simple :
RMAN> CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;Using another method would be like using the handle of your screwdriver as a hammer.
See "RMAN Recipes for Oracle Database 11g" ISBN 978-1-5959-851-1
Best Regards
mseberg

Differencial backup, Log backup and restore

Hi Team,
A scenario: If I have backups as below.
FullBackup1
LogBackup1
LogBackup2
DiffBackup1
LogBackup3
LogBackup4
If our database crash after logBackup4, Is it really required the DiffBackup1 to recover the db? or will it be possible to recover using the first Full backup and all the 4 log backups? Here I did not considered tail of log.
Thanks,
Ashru
MCTS, http://asharafaliptb.wordpress.com

You do not need all backups. A database can be recovered to a point in time as long as a complete chain is present.
A full backup will not break the log chain.
A differential will not break the log chain.
A snapshot will not break your log chain unless you revert it, where by it will rebuild the log.
Full01
Tran01
Diff01 (Based on Full01)
Tran02
Diff02 (Based on Full01)
Tran03
Full02
Diff03 (Based on Full02)
Tran04
Diff04 (Based on Full02)
Tran05
Full03
Diff05 (Based on Full03)
Tran06
Diff06 (Based on Full03)
Tran07
A. Starting from any full backup, then apply all transaction logs.
b. Starting from any full backup, then apply any differential based on that full, then apply all transaction logs post that differential.
Note a differential is tied to the full backup that preceded it. That is to say Diff06 can not be used with Full02.
Also only one differential would be applied, you could choose either Diff05 or Diff06 to apply to Full03.
Jon

Backup and Recovery from Archive Log

Dear all,
I implemented hot backup with oracle9i and
Can anybody suggest me how to backup and recovery archive log ?
Thanks for advance.
Chara

assuming you are using RMAN for backup -
backup ( archivelog all );
backup ( archivelog all delete input ); - to delete from file system.
If you are not using RMAN but backup using a script which puts the tablespaces in hot backup mode then you just need to backup archive log directory.
The archive logs are required when you need to do a database recovery. You don't recover archive log files.
rgds

RMAN BACKUPS AND ARCHIVED LOG ISSUES

제품 : RMAN
작성날짜 : 2004-02-17
RMAN BACKUPS AND ARCHIVED LOG ISSUES
=====================================
Scenario #1:
1)RMAN이 모든 archived log들을 삭제할 때 실패하는 경우.
database는 두 개의 archive destination에 archive file을 생성한다.
다음과 같은 스크립트를 수행하여 백업후에 archived redo logfile을 삭제한다.
run {
allocate channel c1 type 'sbt_tape';
backup database;
backup archivelog all delete input;
Archived redo logfile 삭제 유무를 확인하기 위해 CROSSCHECK 수행시 다음과
같은 메시지가 발생함.
RMAN> change archivelog all crosscheck;
RMAN-03022: compiling command: change
RMAN-06158: validation succeeded for archived log
RMAN-08514: archivelog filename=
/oracle/arch/dest2/arcr_1_964.arc recid=19 stamp=368726072
2) 원인분석
이 문제는 에러가 아니다. RMAN은 여러 개의 arhive directory중 하나의
directoy안에 있는 archived file들만 삭제한다. 그래서 나머지 directory안의
archived log file들은 삭제되지 않고 남게 되는 것이다.
3) 해결책
RMAN이 강제로 모든 directory안의 archived log file들을 삭제하게 하기 위해서는
여러 개의 채널을 할당하여 각 채널이 각 archive destination안의 archived file을
백업하고 삭제하도록 해야 한다.
이것은 아래와 같이 구현될 수 있다.
run {
allocate channel t1 type 'sbt_tape';
allocate channel t2 type 'sbt_tape';
backup
archivelog like '/oracle/arch/dest1/%' channel t1 delete input
archivelog like '/oracle/arch/dest2/%' channel t2 delete input;
Scenario #2:
1)RMAN이 archived log를 찾을 수 없어 백업이 실패하는 경우.
이 시나리오에서 database를 incremental backup한다고 가정한다.
이 경우 RMAN은 recover시 archived redo log대신에 incremental backup을 사용할
수 있기 때문에 백업 후 모든 archived redo log를 삭제하기 위해 OS utility를 사용한다.
그러나 다음 번 backup시 다음과 같은 Error를 만나게 된다.
RMAN-6089: archive log NAME not found or out of sync with catalog
2) 원인분석
이 문제는 OS 명령을 사용하여 archived log를 삭제하였을 경우 발생한다. 이때 RMAN은
archived log가 삭제되었다는 것을 알지 못한다. RMAN-6089는 RMAN이 OS 명령에 의해
삭제된 archived log가 여전히 존재하다고 생각하고 백업하려고 시도하였을 때 발생하게 된다.
3) 해결책
가장 쉬운 해결책은 archived log를 백업할 때 DELETE INPUT option을 사용하는 것이다.
예를 들면
run {
allocate channel c1 type 'sbt_tape';
backup archivelog all delete input;
두 번째로 가장 쉬운 해결책은 OS utility를 사용하여 archived log를 삭제한 후에
다음과 같은 명령어를 RMAN prompt상에서 수행하는 것이다.
RMAN>allocate channel for maintenance type disk;
RMAN>change archivelog all crosscheck;
Oracle 8.0:
RMAN> change archivelog '/disk/path/archivelog_name' validate;
Oracle 8i:
RMAN> change archivelog all crosscheck ;
Oracle 9i:
RMAN> crosscheck archivelog all ;
catalog의 COMPATIBLE 파라미터가 8.1.5이하로 설정되어 있으면 RMAN은 찾을 수 없는
모든 archived log의 status를 "DELETED" 로 셋팅한다. 만약에 COMPATIBLE이 8.1.6이상으로
설정되어 있으면 RMAN은 Repository에서 record를 삭제한다.

Very strange, I issue following command in RMAN on both primary and standby machine, but it they don't delete the 1_55_758646076.dbf, I find in v$archived_log, this "/home/oracle/app/oracle/dataguard/1_55_758646076.dbf" had already been applied.
RMAN> connect target /
RMAN> CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;
old RMAN configuration parameters:
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;
new RMAN configuration parameters:
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;
new RMAN configuration parameters are successfully stored
RMAN>
----------------------------------------------------------------------------------

Rman backup and restore noarchive log

Hi,
We are changing our backup tools from exp to rman. For this I am trying to do
restoration in test server of oracle db running on 9.2 noarchive log.
Step 1. Taken complete backup with rman with nocatalog and include controlfile
nput datafile fno=00008 name=D:\ORACLE\ORADATA\TOTO\TOOLS01.DBF
channel ORA_DISK_1: starting piece 1 at 09-MAR-06
channel ORA_DISK_1: finished piece 1 at 09-MAR-06
piece handle=D:\DBBACKUPS\T1.BKP comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:01:15
Finished backup at 09-MAR-06
Step 2. Deleted database files and control files from database directory.
Step 3. Restore controlfiles
RMAN> restore controlfile from 'd:\dbbackups\t1.bkp';
Starting restore at 09-MAR-06
using channel ORA_DISK_1
channel ORA_DISK_1: restoring controlfile
channel ORA_DISK_1: restore complete
replicating controlfile
input filename=D:\ORACLE\ORADATA\TOTO\CONTROL01.CTL
output filename=D:\ORACLE\ORADATA\TOTO\CONTROL02.CTL
output filename=D:\ORACLE\ORADATA\TOTO\CONTROL03.CTL
Finished restore at 09-MAR-06
Step 3. after database mount, try to restore datafiles, which is failed
restoring datafile 00024 to D:\ORACLE\ORADATA\TOTO\DIN36\TESTUNV1.ORA
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 03/09/2006 17:24:25
ORA-19505: failed to identify file "D:\DBBACKUPS\TOTOBKP.RMAN"
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.
Why it is looking old backup totobkp.rman which is not existing on disk ? My
backup name is t1.bkp.
Will you pl tell me where I have gone wrong ? Secondly what are the correct
steps to be followed for taking cold backup and restoration.
thanks & regards
pjp

Okay let us ponder this for a moment:-
DB NOARCHIVELOG
It does not matter when you take the backup of controlfile because the database is in mount state and no changes are allowed to the db ( Checkpoints etc. )
DB ARCHIVELOG
It does not matter when you take the backup of controlfile because the database is continuously writing to the archivelog's.
End result should not be significantly different as to worry about whether to take backup of control file before or after backup.
Thanks
Gopal

Question about full backup and Transaction Log file

I had a query will taking full backup daily won't allow my log file to grow as after taking the full backup I still see the some of the VLF in status 2. It went away when I manually took the backup of log file. I am bit confused shall I
perform backup of transaction log and full database backup daily to avoid such things in future also until I run shrinkfile the storage space from server won't get reduced right.

yes, full backup does not clear log file only log backup does. once the log backup is taken, it will set the inactive vlfs in the log file to 0.
you should perform log backup as the per your business SLA in data loss.
Go ahead and ask this to yourself:
If a disaster strikes and your database server is lost and your only option is restore it from backup,
how much data loss can your business handle??
the answer to this question is how frequently your log backup should be?
if the answer is 10 mins, you should have log backups every 10 mins atleast.
if the answer is 30 mins, you should have log backups every 30 mins atleast.
if the answer is 90 mins, you should have log backups every 90 mins atleast.
so, when you restore, you will restore latest fullbackup+differential(latest one taken after restored fullback)
and all the logbackups taken since the latest(restored full or differential backup).
there several resources on web,inculding youtube videos, that explain these concepts clearly.i advice you to look at them.
to release the file space to OS, you should the shrink the file. log file shrink happens from the end upto the point it reaches an active vlf.
if there are no inactive vlf's in the end,despite how many inactive vlf's the log file has in the begining, the log file is not shrinkable
Hope it Helps!!

How to Schedule SAP background job at OS Level

Hi All,
Can Anyone tell me how to Schedule SAP background job at OS Level (unix).
Regards,
Anil

Hi Anil,
I donu2019t know your requirements, anyway itu2019s possible to setup your SAP job in order to start after an event, and after that you can get the event triggered from the Operating System in the following way:
- log into you Operating System with the SIDadm user id (at the Operating System level) and go to directory /usr/sap/SID/SYS/exe/run
- Run the SAPEVT executable as follows:
sapevt YOUR_EVENT -t pf=/usr/sap/SID/SYS/profile/DEV_DVEBMGS00_server001 nr=01
This will raise the event, and cause the job scheduled within SAP to execute.
You can periodically execute this job with crontab.
Thanks,
Federico Biavati

Backup and Log reduction scheduling in background

Similar Messages

Maybe you are looking for