HANA Logs in "Truncated" status

We currently have an issue where all the HANA logs (except the current "active" log) are in "Truncated" status. This is causing new log segments to be created every time a log is filled, instead of cycling through the older logs. The backup logs indicate no failures and show that log backups are completing every few minutes. The only thing unusual that I could find was one instance of a log backup from 4 days ago that appeared to be stuck in "Running" status. All subsequent backups appear to be running normally however. Coincidentally, 4 days ago is roughly when the log segment count started increasing.
Anyone know what could have caused this, and what can be done to reset the log statuses so that they can be written again? We are approaching 85% full on the filesystem and growing.

Okay the requirement is to check a text field to be filled in a specific status with a specific priority. The only way i managed to do that is by allowing a status change only via defined actions. I implemented the badi SOCM_CHECK_CONDITION and did my checks there.
It worked perfectly, except for the fact that the system won't change the user status until the ibase component field is filled. I thought it could be a problem with the condition so i did a fresh copy of the slfn and added just the action for status change. But the problem is still there.
There is no error message and it also says that the specific action has been performed succesfully. But the status will only change if i fill the ibase component field.
I assume that the "hf_check_status" method has been coded for the change request management where you always need an ibase component in you change requests or change documents.
I can do a workaround by filling the ibsae by default and hide it, but it would be nice to know what the problem actually is
regards daniel

Similar Messages

MV logs getting truncated

I am trying to setup Master to Materialized view(Snapshot) replication and Materailzed view logs getting truncated when I create MV at Snapshot site. Is there any way to prevent truncating MV logs at master site while creating MV at sanpshot site?
Here are steps that I perforemd, Initally I made two copy of database one as master and other is Snpshot with unique global name.
At Master site:
1. MV logs created.
2. Some DML happned at Master site, MV logs are populated.
Snapshot(MV) site:
1. MV created using prebuilt table option.
then I checked on Maste site MV logs are truncated but DML that happened in step 2 at Master site that are missing at Snapshot site.
Is there any way to prevent truncating MV logs at master site while creating MV at sanpshot site?
Thanks.
Pravin

This is a restriction of the prebuilt table "At registration time, the table must reflect the materialization of a subquery." Even if you could prevent the snapshot log from getting truncated (i.e. by creating a second snapshot against the same master table), the snapshot you created on prebuilt still will NOT refresh those records. As far as the snapshot log is concerned, once you create the snapshot with prebuilt, it must be consistent. The trick is, you have to keep the users from updating the master table until you have issued the create snapshot command.

Logging event link-status

Is this enabled by default on Cisco IOS switch ports? What logging level will ensure I see link status in the router buffer log?

logging event link-status global (global configuration)
To change the default switch-wide global link-status event messaging settings, use the
logging event link-status global command. Use the no form of this command to disable the link-status event messaging.
logging event link-status global
no logging event link-status global
Syntax Description
This command has no arguments or keywords.
Defaults
The global link-status messaging is disabled.
Command Modes
Global configuration
Command History
Release Modification
12.2(25)SG
Support for this command was introduced on the Catalyst 4500 series switch.
Usage Guidelines
If link-status logging event is not configured at the interface level, this global link-status setting takes effect for each interface.
Examples
This example shows how to globally enable link status message on each interface:
Switch# config terminal
Enter configuration commands, one per line. End with CNTL/Z.
Switch(config)# logging event link-status global
Switch(config)# end
Switch#
Related Commands
logging event link-status global (global configuration)
logging event link-status (interface configuration)
To enable the link-status event messaging on an interface, use the logging event link-status command. Use the no form of this command to disable link-status event messaging. Use the
logging event link-status use-global command to apply the global link-status setting.
logging event link-status
no logging event link-status
logging event link-status use-global
Defaults
Global link-status messaging is enabled.
Command Modes
Interface configuration
Command History
Release Modification
12.2(25)SG
Support for this command was introduced on the Catalyst 4500 series switch.

No logging event link-status on SG300

How can I do it (no logging event link-status) on Cisco Small Business 300 Series Managed Switches (SG300)?

no logging event link-status
This command disables the logs generated when port(s) go down or up.

Logging event trunk-status vs link-status vs bundle-status

Hi
This is not really a query regarding the above interface level commands, but just looking for someone elses view on the differences regardless of however subtle they are.
No links please, like I said I know what they are and do.
Just your real life expereinces why you needed bundle-status for instance will do just fine.
thanks in advance

Three different use cases for status notifications.
I'll give you my experience with using these commands and where they are useful.
Logging event trunk-status--this command is particularly useful for tracking security vulnerabilities as well as trunk mismatches when you're relying on DTP for trunk negotiation.
Say you have a trunk uplink on a switch that links to a distribution switch. This trunk carries traffic for multiple VLANs (thus the very definition of a trunk).
Lets say the other side of the link on the distribution switch is for some reason changed from a trunking state (switchport mode trunk, or switchport mode dynamic desirable/auto) to a non-trunking state (switchport mode access). If the uplink on your access layer switch is not hard-coded for trunk-mode (switchport mode trunk and/or switchport nonegotiate), then your uplink interface can potentially be changed from a trunk port to an access port and only carry traffic for a single VLAN. This would leave other clients on the access switch VLANs stranded from the rest of the network. This logging mechanism would let you know that the switchport is no longer an operational trunk, even though the link status would still be up.
Of course, as a best practice, you should never rely on DTP to form trunk links, especially on uplinks.
The second use is for security--if you have an interface that you KNOW should never become a trunk interface (i.e. an access port where clients connect), and for whatever reason the interface becomes a trunk link (due to a compromised switch or an over-reliance on DTP), you could potentially expose VLANs that users should never have access to. This logging mechanism would let you know if that happens.
Logging event link-status--this one is simple--it logs whether the interface is up/down or changes. One thing I find this useful for is on particularly important interfaces--uplink interfaces, routing adjacency interfaces, server interfaces, etc. Use this on any port when you want to absolutely know if it goes down.
Logging event bundle-status--this one is fairly simple as well--it logs whether there is a change in the port-channel. This could be triggered by a member interface leaving or joining. One reason you would want to use this is for guaranteed bandwidth and configuration consistency.
Sometimes port-channel members leave a channel-group because the configuration is changed on one member and not on the other, likely by mistake. This could catch an error like that and cue you on where to look into the issue. As for bandwidth, obviously you don't want to believe you have 20Gbps or 2Gbps on your uplink, then find out that you actually have half (or whatever portion) of that bandwidth missing because a member has left the port-channel. Both situations can be avoided by monitoring the status of your bundle (or port-channel).

WBS Report Showing Change logs - ex: system status

Hi,
I would like to know if there is any report that would show the change log for AVAC for WBS Elements (i.e. change data of system status). I tried running CN60 but it does not give any results.
Thanks!
Vivian

Hi Sarang,
Thanks for your reply.
Would you know if there is any specific report for this instead of having to look up individually?
Also, in order to view the change document for both Project Definition and WBS Element, I understand there is some config that need to be done. Could you confirm if below are complete / correct?
- project profile - tick on change document (OPSA)
- Project Definition and WBS Element status profile (user status profile) - set business transaction to allow "create change document"
Thanks!
Vivian

No Logs in specific status

Hi all,
in a specific status of my support message there are no logs (error messages, warnings etc.) visible. If i change the status i can see them.
It is NOT an authentication problem.
Any help would be much appreciated.
Regards Daniel

Okay the requirement is to check a text field to be filled in a specific status with a specific priority. The only way i managed to do that is by allowing a status change only via defined actions. I implemented the badi SOCM_CHECK_CONDITION and did my checks there.
It worked perfectly, except for the fact that the system won't change the user status until the ibase component field is filled. I thought it could be a problem with the condition so i did a fresh copy of the slfn and added just the action for status change. But the problem is still there.
There is no error message and it also says that the specific action has been performed succesfully. But the status will only change if i fill the ibase component field.
I assume that the "hf_check_status" method has been coded for the change request management where you always need an ibase component in you change requests or change documents.
I can do a workaround by filling the ibsae by default and hide it, but it would be nice to know what the problem actually is
regards daniel

Change log for system status of Building

Dear Experts,
Would like to inquire if there is a tcode that can be used to view logs for change in system status of building in RE-SD
Thanks in advance.
Kathy

Hi Kathy,
when ever there is error we check using
-> BPIA
-> ECATT error log or BC set error log
-> SECATT tcode can be use dfor the purpose
With every Package there is a installation guide which has further information for the things about the package being used.
Have a best day ahead.

SQL Server transaction log not truncating in simple recovery model mode

The transaction log for our SQL Server database is no longer truncating when it gets to the restricted file growth limit set by the autogrowth settings. Previously - as expected - it would reach this limit and then truncate allowing further entries. Now
it stays full and the application using it shuts down. We are using 2008 R2 and the recovery model is set to simple. Is this a known behaviour / fault which can be resolved ? Thanks.

As already suggested check wait type in log_reuse_wait_desc from sys.databases and open transaction on the database.
Also, check long running SPIDs are waiting for from sys.sysprocesses from wait_type column
0 = Nothing - What it sounds like.. Shouldn't be waiting
1 = Checkpoint - Waiting for a checkpoint to occur. This should happen and you should be fine - but there are some cases to look for here for later answers or edits.
2 = Log backup - You are waiting for a log backup to occur. Either you have them scheduled and it will happen soon, or you have the first problem described here and you now know how to fix it
3 = Active backup or restore - A backup or restore operation is running on the database
4 = Active transaction - * There is an active transaction that needs to complete (either way -
ROLLBACK or COMMIT) before the log can be backed up. This is the second reason described in this answer.
5 = Database mirroring Either a mirror is getting behind or under some latency in a high performance mirroring situation or mirroring is paused for some reason
6 = Replication - There can be issues with replication that would cause this - like a log reader agent not running, a database thinking it is marked for replication that no longer is and various other reasons. You can also see this reason and it is
perfectly normal because you are looking at just the right time, just as transactions are being consumed by the log reader
7 = Database snapshot creation You are creating a database snapshot, you'll see this if you look at just the right moment as a snapshot is being created
8 = Log Scan I have yet to encounter an issue with this running along forever. If you look long enough and frequently enough you can see this happen, but it shouldn't be a cause of excessive transaction log growth, that I've seen.
9 = An AlwaysOn Availability Groups secondary replica is applying transaction log records of this database to a corresponding secondary database
Please click the Mark as answer button and vote as helpful if this reply solves your problem

Logging and Audit Statuses

Present Situation:
1. Currently running combination of PL/SQL and OWB ETL
2. Separate frameworks for logging process status and errors used.
Question:
Is there a common logging framework in OWB in both our home-grown PL/SQL ETL, OWB mappings, and user-defined transformations written as either functions, procedures, or packages. We are interested in calling these common APIs from Java, and Unix shell scripts.

Hi Sybrand Bakker,
Hot backup means your db should be in archive mode.
How a db can be in noarchive mode when you are using the hot backup ?
My question is on data consistency when you taking the backup using OS Command " alter database begin backup" or RMAN .
When backup is using the hotbackup , its always incosistent and we need to recover from archive log.
For the create table as select , Alter index there is no logging by default. If you are going to fire such command and that corresponds DB file (Only one) is already backed up , so from where you will get that data since data will not be written to the redo logs.
Next is RMAN enough smart to consider this change ?
I hope I am clear now.
Either my question is not clear or You have misinterpret it.
REgards
Sourabh GUpta

Whether t-logs are truncated in DB's particpating in High Availability. SQLAlways On 2012

Hi,
How the transaction logs are cleared for DB's participating in SQL AlwaysOn.I have a DB participating in HA.Now in order to use alwaysON DB recovery model should be set to full. NOw with this recovery model my transaction logs will grow continuously.
How t-logs can be cleared for the DB's participating in AG. Is there any recommendation?
Thanks
Manish

Hello,
Have you scheduled log backup on primary.Secondary replica might be applying transaction log records of this database to a corresponding secondary database.
Whats does below query returns
select name,log_resuse_wait_desc from sys.databases where name='db_name'
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

Logging off changes status to online or "away"

When I go offline my skype account shows me online or "away" to my friends, any suggestions?
It would be nice if we could finally get this issue addressed. More examples from other users:
http://community.skype.com/t5/Windows-desktop-client/Skype-status-changes-to-Away-when-I-sign-out/td...

Here's a workaround that worked for me.Download version 7.7 from the link provided by @ruwim below (http://download.skype.com/msi/SkypeSetup_7.7.0.103.msi) (thanks @ruwim!)Download jsMSIx from JSWare (http://www.jsware.net/jsware/zips/jsmsix418a.zip)Unzip it to a folder of your choice.Run jsMSIx.exe to extract the contents of the Skype msi file you previously downloaded.Make sure Skype is NOT running, then...Copy Skype.exe from the extracted folder (it was "F:\tmp\S77\ProgramFilesFolder\Skype\Phone\Skype.exe" for me) to the Skype\Phone folder where Skype is installed, overwriting the version which is there.Restart Skype. Like I said, it worked for me, but it might not work for you. It might also wreck you Skype installation, your computer, your life, and bring about the end of the world - so try it at your own risk

PerformanceLogsToBeProcessed Logs not truncating

hi there,
On my Exchange servers, all is ok however my Diagnostics folder these logs are always filling up, where can I check retention thresholds??
\PerformanceLogsToBeProcessed
Thanks
pjmartins

Hi,
Please follow these steps to set Maximum root path size for ExchangeDiagnosticsPerformanceLog under \PerformanceLogsToBeProcessed folder.
In Administrative Tools, open Performance Monitor. Expand Data Collector Sets and click
User Defined .
In the console pane, right-click ExchangeDiagnosticsPerformanceLog and click
Data Manager.
On the Data Manager tab, choose Maximum root path size
and set the size you want to configure.
Click OK.
Maximum root path size: The maximum size of the data directory for the Data Collector Set, including all subfolders. If selected, this maximum path size overrides the Minimum free disk and Maximum folders limits, and previous data will be deleted according
to the Resource policy that you choose when the limit is reached.
For more information, please refer to this document
https://technet.microsoft.com/en-us/library/cc765998.aspx
Best Regards.

Transaction Log Truncate not working on Sql Server 2012 High Availability Groups

Hi Everyone
Firstly I have tried to search the forum for similar issues but can't seem to find any that match our situation.
We have a SQL Server 2012 High Availability Group with 2 Nodes
Node 1 = Primary
Node 2 = Secondary
Backup Schedule as follows
Full Database Backup @ 00:00
Transaction Log Backup every 30 minutes from 00:30:00 till 23:59:59.
These backups are run by Maintenance Jobs, but we have also tried doing direct backups in SSMS using Backup Database and Backup Log commands.
Before we configured the High Availability group the transaction log backups worked fine.
After we configured the High Availability group we performed a Full Backup and the T-Log schedule did the T-Log backup. The 1st T-log backup truncated the log (Used space Decreased) as expected.
However subsequent T-Log backups do not truncate the T-Log.
This happens both in our acceptance and Live environments. This also happens when running the backups as a Backup operator and sysadmin, this does not seem to be a permissions issue at all.
We have tried running the Backup on the Primary and Secondary Replica.
What about High Availability groups could stop Transaction Log Backups from not truncating the log?
Thanks
James

Hi Sean
Thank you for your reply, please see the output of the sys.databases query below, and some others which you may find usefull.
Query: select database_id,recovery_model_desc, log_reuse_wait, log_reuse_wait_desc from sys.databases
where database_id = 5
Result: database_id   recovery_model_desc   log_reuse_wait   log_reuse_wait_desc
                 5
FULL   0
NOTHING
I also ran the following
select database_id, truncation_lsn, last_received_lsn, last_commit_lsn, last_hardened_lsn, last_redone_lsn,*
from sys.dm_hadr_database_replica_states
go
database_id
truncation_lsn
last_received_lsn
last_commit_lsn
last_hardened_lsn
last_redone_lsn
database_id
group_id
replica_id
group_database_id
is_local
synchronization_state
synchronization_state_desc
is_commit_participant
synchronization_health
synchronization_health_desc
database_state
database_state_desc
is_suspended
suspend_reason
suspend_reason_desc
recovery_lsn
truncation_lsn
last_sent_lsn
last_sent_time
last_received_lsn
last_received_time
last_hardened_lsn
last_hardened_time
last_redone_lsn
last_redone_time
log_send_queue_size
log_send_rate
redo_queue_size
redo_rate
filestream_send_rate
end_of_log_lsn
last_commit_lsn
last_commit_time
low_water_mark_for_ghosts
5
1231833000417170000000
1231833000418880000000
1231833000418880000000
1231833000418890000000
1231833000418880000000
5
1391A499-3F9A-47D5-BCE0-70BC204E2A5B
7E8BFC2E-363F-4C48-86F0-C276D3E0C8D9
0581E17A-6B7B-4B8F-9288-BF765BFBCE77
0
2
SYNCHRONIZED
1
2
HEALTHY
NULL
NULL
0
NULL
NULL
4294967295429490000000000
1231833000417170000000
1
41863
1231833000418880000000
41863
1231833000418890000000
41863
1231833000418880000000
41863
0
25541
0
84404
75304
1231833000418880000000
1231833000418880000000
41863
441019861
5
1231833000417170000000
NULL
1231833000418880000000
1231833000418890000000
NULL
5
1391A499-3F9A-47D5-BCE0-70BC204E2A5B
83B9F00E-D63F-4AC0-98FC-35E48FFA2C6F
0581E17A-6B7B-4B8F-9288-BF765BFBCE77
1
2
SYNCHRONIZED
1
2
HEALTHY
0
ONLINE
0
NULL
NULL
4294967295429490000000000
1231833000417170000000
NULL
NULL
NULL
NULL
1231833000418890000000
NULL
NULL
NULL
NULL
NULL
NULL
NULL
NULL
1231833000418880000000
1231833000418880000000
41863
441019861
And
dbcc loginfo
go
RecoveryUnitId
FileId
FileSize
StartOffset
FSeqNo
Status
Parity
CreateLSN
0
2
458752
8192
1231828
0
128
0
0
2
458752
466944
1231829
0
128
0
0
2
458752
925696
1231830
0
128
0
0
2
712704
1384448
1231831
0
128
0
0
2
19398656
2097152
1231832
0
128
1229654000000040000000
0
2
10199171072
21495808
1231833
2
128
1229656000000010000000
0
2
10199171072
10220666880
0
0
64
1229656000000010000000
0
2
10199171072
20419837952
1231827
0
64
1229656000000010000000
0
2
10199171072
30619009024
0
0
128
1229656000000010000000
0
2
10199171072
40818180096
0
0
128
1229656000000010000000
0
2
10199171072
51017351168
0
0
128
1229656000000010000000
0
2
10199171072
61216522240
0
0
128
1229656000000010000000
0
2
10199171072
71415693312
0
0
128
1229656000000010000000
0
2
10199171072
81614864384
0
0
128
1229656000000010000000
0
2
536870912
91814035456
0
0
64
1229989001661260000000
0
2
536870912
92350906368
0
0
64
1229989001661260000000
0
2
536870912
92887777280
0
0
64
1229989001661260000000
0
2
536870912
93424648192
0
0
64
1229989001661260000000
0
2
536870912
93961519104
0
0
64
1229989001661260000000
0
2
536870912
94498390016
0
0
64
1229989001661260000000
0
2
536870912
95035260928
0
0
64
1229989001661260000000
0
2
536870912
95572131840
0
0
64
1229989001661260000000
0
2
536870912
96109002752
0
0
64
1229989001661260000000
0
2
536870912
96645873664
0
0
64
1229989001661260000000
0
2
536870912
97182744576
0
0
64
1229989001661260000000
0
2
536870912
97719615488
0
0
64
1229989001661260000000
0
2
536870912
98256486400
0
0
64
1229989001661260000000
0
2
536870912
98793357312
0
0
64
1229989001661260000000
0
2
536870912
99330228224
0
0
64
1229989001661260000000
0
2
536870912
99867099136
0
0
64
1229989001661260000000
0
2
536870912
100403970048
0
0
64
1229995000058520000000
0
2
536870912
100940840960
0
0
64
1229995000058520000000
0
2
536870912
101477711872
0
0
64
1229995000058520000000
0
2
536870912
102014582784
0
0
64
1229995000058520000000
0
2
536870912
102551453696
0
0
64
1229995000058520000000
0
2
536870912
103088324608
0
0
64
1229995000058520000000
0
2
536870912
103625195520
0
0
64
1229995000058520000000
0
2
536870912
104162066432
0
0
64
1229995000058520000000
0
2
536870912
104698937344
0
0
64
1229995000058520000000
0
2
536870912
105235808256
0
0
64
1229995000058520000000
0
2
536870912
105772679168
0
0
64
1229995000058520000000
0
2
536870912
106309550080
0
0
64
1229995000058520000000
0
2
536870912
106846420992
0
0
64
1229995000058520000000
0
2
536870912
107383291904
0
0
64
1229995000058520000000
0
2
536870912
107920162816
0
0
64
1229995000058520000000
0
2
536870912
108457033728
0
0
64
1229995000058520000000
0
2
536870912
108993904640
0
0
64
1230004000028400000000
0
2
536870912
109530775552
0
0
64
1230004000028400000000
0
2
536870912
110067646464
0
0
64
1230004000028400000000
0
2
536870912
110604517376
0
0
64
1230004000028400000000
0
2
536870912
111141388288
0
0
64
1230004000028400000000
0
2
536870912
111678259200
0
0
64
1230004000028400000000
0
2
536870912
112215130112
0
0
64
1230004000028400000000
0
2
536870912
112752001024
0
0
64
1230004000028400000000
0
2
536870912
113288871936
0
0
64
1230004000028400000000
0
2
536870912
113825742848
0
0
64
1230004000028400000000
0
2
536870912
114362613760
0
0
64
1230004000028400000000
0
2
536870912
114899484672
0
0
64
1230004000028400000000
0
2
536870912
115436355584
0
0
64
1230004000028400000000
0
2
536870912
115973226496
0
0
64
1230004000028400000000
0
2
536870912
116510097408
0
0
64
1230004000028400000000
0
2
536870912
117046968320
0
0
64
1230004000028400000000
0
2
536870912
117583839232
0
0
64
1230012000103140000000
0
2
536870912
118120710144
0
0
64
1230012000103140000000
0
2
536870912
118657581056
0
0
64
1230012000103140000000
0
2
536870912
119194451968
0
0
64
1230012000103140000000
0
2
536870912
119731322880
0
0
64
1230012000103140000000
0
2
536870912
120268193792
0
0
64
1230012000103140000000
0
2
536870912
120805064704
0
0
64
1230012000103140000000
0
2
536870912
121341935616
0
0
64
1230012000103140000000
0
2
536870912
121878806528
0
0
64
1230012000103140000000
0
2
536870912
122415677440
0
0
64
1230012000103140000000
0
2
536870912
122952548352
0
0
64
1230012000103140000000
0
2
536870912
123489419264
0
0
64
1230012000103140000000
0
2
536870912
124026290176
0
0
64
1230012000103140000000
0
2
536870912
124563161088
0
0
64
1230012000103140000000
0
2
536870912
125100032000
0
0
64
1230012000103140000000
0
2
536870912
125636902912
0
0
64
1230012000103140000000
0
2
536870912
126173773824
0
0
128
1230338000973820000000
0
2
536870912
126710644736
0
0
128
1230338000973820000000
0
2
536870912
127247515648
0
0
128
1230338000973820000000
0
2
536870912
127784386560
0
0
128
1230338000973820000000
0
2
536870912
128321257472
0
0
128
1230338000973820000000
0
2
536870912
128858128384
0
0
128
1230338000973820000000
0
2
536870912
129394999296
0
0
128
1230338000973820000000
0
2
536870912
129931870208
0
0
128
1230338000973820000000
0
2
536870912
130468741120
0
0
128
1230338000973820000000
0
2
536870912
131005612032
0
0
128
1230338000973820000000
0
2
536870912
131542482944
0
0
128
1230338000973820000000
0
2
536870912
132079353856
0
0
128
1230338000973820000000
0
2
536870912
132616224768
0
0
128
1230338000973820000000
0
2
536870912
133153095680
0
0
128
1230338000973820000000
0
2
536870912
133689966592
0
0
128
1230338000973820000000
0
2
536870912
134226837504
0
0
128
1230338000973820000000
0
2
536870912
134763708416
0
0
128
1230338001901440000000
0
2
536870912
135300579328
0
0
128
1230338001901440000000
0
2
536870912
135837450240
0
0
128
1230338001901440000000
0
2
536870912
136374321152
0
0
128
1230338001901440000000
0
2
536870912
136911192064
0
0
128
1230338001901440000000
0
2
536870912
137448062976
0
0
128
1230338001901440000000
0
2
536870912
137984933888
0
0
128
1230338001901440000000
0
2
536870912
138521804800
0
0
128
1230338001901440000000
0
2
536870912
139058675712
0
0
128
1230338001901440000000
0
2
536870912
139595546624
0
0
128
1230338001901440000000
0
2
536870912
140132417536
0
0
128
1230338001901440000000
0
2
536870912
140669288448
0
0
128
1230338001901440000000
0
2
536870912
141206159360
0
0
128
1230338001901440000000
0
2
536870912
141743030272
0
0
128
1230338001901440000000
0
2
536870912
142279901184
0
0
128
1230338001901440000000
0
2
536870912
142816772096
0
0
128
1230338001901440000000
0
2
536870912
143353643008
0
0
128
1230346000103040000000
0
2
536870912
143890513920
0
0
128
1230346000103040000000
0
2
536870912
144427384832
0
0
128
1230346000103040000000
0
2
536870912
144964255744
0
0
128
1230346000103040000000
0
2
536870912
145501126656
0
0
128
1230346000103040000000
0
2
536870912
146037997568
0
0
128
1230346000103040000000
0
2
536870912
146574868480
0
0
128
1230346000103040000000
0
2
536870912
147111739392
0
0
128
1230346000103040000000
0
2
536870912
147648610304
0
0
128
1230346000103040000000
0
2
536870912
148185481216
0
0
128
1230346000103040000000
0
2
536870912
148722352128
0
0
128
1230346000103040000000
0
2
536870912
149259223040
0
0
128
1230346000103040000000
0
2
536870912
149796093952
0
0
128
1230346000103040000000
0
2
536870912
150332964864
0
0
128
1230346000103040000000
0
2
536870912
150869835776
0
0
128
1230346000103040000000
0
2
536870912
151406706688
0
0
128
1230346000103040000000
0
2
536870912
151943577600
0
0
128
1230355000086930000000
0
2
536870912
152480448512
0
0
128
1230355000086930000000
0
2
536870912
153017319424
0
0
128
1230355000086930000000
0
2
536870912
153554190336
0
0
128
1230355000086930000000
0
2
536870912
154091061248
0
0
128
1230355000086930000000
0
2
536870912
154627932160
0
0
128
1230355000086930000000
0
2
536870912
155164803072
0
0
128
1230355000086930000000
0
2
536870912
155701673984
0
0
128
1230355000086930000000
0
2
536870912
156238544896
0
0
128
1230355000086930000000
0
2
536870912
156775415808
0
0
128
1230355000086930000000
0
2
536870912
157312286720
0
0
128
1230355000086930000000
0
2
536870912
157849157632
0
0
128
1230355000086930000000
0
2
536870912
158386028544
0
0
128
1230355000086930000000
0
2
536870912
158922899456
0
0
128
1230355000086930000000
0
2
536870912
159459770368
0
0
128
1230355000086930000000
0
2
536870912
159996641280
0
0
128
1230355000086930000000
0
2
536870912
160533512192
0
0
128
1230364000070870000000
0
2
536870912
161070383104
0
0
128
1230364000070870000000
0
2
536870912
161607254016
0
0
128
1230364000070870000000
0
2
536870912
162144124928
0
0
128
1230364000070870000000
0
2
536870912
162680995840
0
0
128
1230364000070870000000
0
2
536870912
163217866752
0
0
128
1230364000070870000000
0
2
536870912
163754737664
0
0
128
1230364000070870000000
0
2
536870912
164291608576
0
0
128
1230364000070870000000
0
2
536870912
164828479488
0
0
128
1230364000070870000000
0
2
536870912
165365350400
0
0
128
1230364000070870000000
0
2
536870912
165902221312
0
0
128
1230364000070870000000
0
2
536870912
166439092224
0
0
128
1230364000070870000000
0
2
536870912
166975963136
0
0
128
1230364000070870000000
0
2
536870912
167512834048
0
0
128
1230364000070870000000
0
2
536870912
168049704960
0
0
128
1230364000070870000000
0
2
536870912
168586575872
0
0
128
1230364000070870000000
0
2
536870912
169123446784
0
0
128
1230373000054750000000
0
2
536870912
169660317696
0
0
128
1230373000054750000000
0
2
536870912
170197188608
0
0
128
1230373000054750000000
0
2
536870912
170734059520
0
0
128
1230373000054750000000
0
2
536870912
171270930432
0
0
128
1230373000054750000000
0
2
536870912
171807801344
0
0
128
1230373000054750000000
0
2
536870912
172344672256
0
0
128
1230373000054750000000
0
2
536870912
172881543168
0
0
128
1230373000054750000000
0
2
536870912
173418414080
0
0
128
1230373000054750000000
0
2
536870912
173955284992
0
0
128
1230373000054750000000
0
2
536870912
174492155904
0
0
128
1230373000054750000000
0
2
536870912
175029026816
0
0
128
1230373000054750000000
0
2
536870912
175565897728
0
0
128
1230373000054750000000
0
2
536870912
176102768640
0
0
128
1230373000054750000000
0
2
536870912
176639639552
0
0
128
1230373000054750000000
0
2
536870912
177176510464
0
0
128
1230373000054750000000
0
2
536870912
177713381376
0
0
128
1230382000038660000000
0
2
536870912
178250252288
0
0
128
1230382000038660000000
0
2
536870912
178787123200
0
0
128
1230382000038660000000
0
2
536870912
179323994112
0
0
128
1230382000038660000000
0
2
536870912
179860865024
0
0
128
1230382000038660000000
0
2
536870912
180397735936
0
0
128
1230382000038660000000
0
2
536870912
180934606848
0
0
128
1230382000038660000000
0
2
536870912
181471477760
0
0
128
1230382000038660000000
0
2
536870912
182008348672
0
0
128
1230382000038660000000
0
2
536870912
182545219584
0
0
128
1230382000038660000000
0
2
536870912
183082090496
0
0
128
1230382000038660000000
0
2
536870912
183618961408
0
0
128
1230382000038660000000
0
2
536870912
184155832320
0
0
128
1230382000038660000000
0
2
536870912
184692703232
0
0
128
1230382000038660000000
0
2
536870912
185229574144
0
0
128
1230382000038660000000
0
2
536870912
185766445056
0
0
128
1230382000038660000000
The create LSN column seems to have been truncated so here is is again, sorry for the bulky reply.
CreateLSN
0
0
0
0
1229654000000041600001
1229656000000012000001
1229656000000012000001
1229656000000012000001
1229656000000012000001
1229656000000012000001
1229656000000012000001
1229656000000012000001
1229656000000012000001
1229656000000012000001
1229989001661260800316
1229989001661260800316
1229989001661260800316
1229989001661260800316
1229989001661260800316
1229989001661260800316
1229989001661260800316
1229989001661260800316
1229989001661260800316
1229989001661260800316
1229989001661260800316
1229989001661260800316
1229989001661260800316
1229989001661260800316
1229989001661260800316
1229989001661260800316
1229995000058525600316
1229995000058525600316
1229995000058525600316
1229995000058525600316
1229995000058525600316
1229995000058525600316
1229995000058525600316
1229995000058525600316
1229995000058525600316
1229995000058525600316
1229995000058525600316
1229995000058525600316
1229995000058525600316
1229995000058525600316
1229995000058525600316
1229995000058525600316
1230004000028405600295
1230004000028405600295
1230004000028405600295
1230004000028405600295
1230004000028405600295
1230004000028405600295
1230004000028405600295
1230004000028405600295
1230004000028405600295
1230004000028405600295
1230004000028405600295
1230004000028405600295
1230004000028405600295
1230004000028405600295
1230004000028405600295
1230004000028405600295
1230012000103148800147
1230012000103148800147
1230012000103148800147
1230012000103148800147
1230012000103148800147
1230012000103148800147
1230012000103148800147
1230012000103148800147
1230012000103148800147
1230012000103148800147
1230012000103148800147
1230012000103148800147
1230012000103148800147
1230012000103148800147
1230012000103148800147
1230012000103148800147
1230338000973824800555
1230338000973824800555
1230338000973824800555
1230338000973824800555
1230338000973824800555
1230338000973824800555
1230338000973824800555
1230338000973824800555
1230338000973824800555
1230338000973824800555
1230338000973824800555
1230338000973824800555
1230338000973824800555
1230338000973824800555
1230338000973824800555
1230338000973824800555
1230338001901449600555
1230338001901449600555
1230338001901449600555
1230338001901449600555
1230338001901449600555
1230338001901449600555
1230338001901449600555
1230338001901449600555
1230338001901449600555
1230338001901449600555
1230338001901449600555
1230338001901449600555
1230338001901449600555
1230338001901449600555
1230338001901449600555
1230338001901449600555
1230346000103044000554
1230346000103044000554
1230346000103044000554
1230346000103044000554
1230346000103044000554
1230346000103044000554
1230346000103044000554
1230346000103044000554
1230346000103044000554
1230346000103044000554
1230346000103044000554
1230346000103044000554
1230346000103044000554
1230346000103044000554
1230346000103044000554
1230346000103044000554
1230355000086934400510
1230355000086934400510
1230355000086934400510
1230355000086934400510
1230355000086934400510
1230355000086934400510
1230355000086934400510
1230355000086934400510
1230355000086934400510
1230355000086934400510
1230355000086934400510
1230355000086934400510
1230355000086934400510
1230355000086934400510
1230355000086934400510
1230355000086934400510
1230364000070872800554
1230364000070872800554
1230364000070872800554
1230364000070872800554
1230364000070872800554
1230364000070872800554
1230364000070872800554
1230364000070872800554
1230364000070872800554
1230364000070872800554
1230364000070872800554
1230364000070872800554
1230364000070872800554
1230364000070872800554
1230364000070872800554
1230364000070872800554
1230373000054757600431
1230373000054757600431
1230373000054757600431
1230373000054757600431
1230373000054757600431
1230373000054757600431
1230373000054757600431
1230373000054757600431
1230373000054757600431
1230373000054757600431
1230373000054757600431
1230373000054757600431
1230373000054757600431
1230373000054757600431
1230373000054757600431
1230373000054757600431
1230382000038664800234
1230382000038664800234
1230382000038664800234
1230382000038664800234
1230382000038664800234
1230382000038664800234
1230382000038664800234
1230382000038664800234
1230382000038664800234
1230382000038664800234
1230382000038664800234
1230382000038664800234
1230382000038664800234
1230382000038664800234
1230382000038664800234
1230382000038664800234
Thanks
James

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

HANA Logs in "Truncated" status

Similar Messages

Maybe you are looking for