File Dynamics: A New Product Addressing the Expanding Requirements of Data Management

buckgashler

“Data really powers everything we do. It has been called the “raw material” of business. That is why proper data management is so important. However, the term “data management” is one that is continuously evolving. Today, a variety of factors including the overwhelming growth of data, compliance to data-specific industry and government regulations, and…

+read more

The post File Dynamics: A New Product Addressing the Expanding Requirements of Data Management appeared first on Cool Solutions. buckgashler

Related:

  • No Related Posts

Re: Avamar managed file replication failing with error Replication failed: could not open connection to dest DDR

My issue was related to an avamar backup image that was written to DD but was corrupted. So when Avamar instructs DD to replicate that backup image/file, it errors out with that code.

It is difficult to narrow down the exact backup image that is corrupt, but there’s two options here: 1) comb through the logs to find what client’s backups are being replicated at time of faillure, note the name, remove the client from the replication scope, rerun replication, if it fails again, repeat the procedure and keep a running list of clients that fail until the replication job succeeds. Then create a separate replication job that just has the failed servers, and narrow the data range of the replication scope until you find the backup image that is causing the issue. Likely, if there are multiple servers with this issue, the failures will trace back to the same date/time. Once you have the Avamar backup images identified, you can delete it from Avamar. I’m not entirely sure if that removes the image from DD, so if the backup image is sizable, you may want to engage EMC support to dig into the array to remove the file.

Related:

Re: SNMP Trap when failure recovered

Hello guys,

I’m testing SNMP function of Scaleio Gateway software(v2.0.0.2) with 3node cluster.

According to User Guide document(p.530), Scaleio gateway sends a SNMP trap when system failure has been fixed.

>Open and closing alerts will consist of the same code and issue number, with the

>exception of the first digit (0 or 1) in the <ISSUE> section. For example:

> SIOXX.XX.0XXXXXX indicates that the alert is active

> SIOXX.XX.1XXXXXX indicates that the alert has been closed

I’ve rebooted Secondary MDM to test the function above.

I had expected the trap contains “SIO02.01.1000001″ would be send by gateway after cluster recovered, but it wasn’t.

Is it normal behavior? If so, do I have to any setting or configuring to activate the function to send trap after failure recovered?

#please see packet capture log below:

————————————

tcpdump -i eth0 -T snmp -s 0 “(dst port 162) or (src port 161) or (dst port161)”

[Before reboot MDM2]

10:41:23.734093 IP [SIO-GATEWAY].38650 > [SNMP-RCV].snmptrap: V2Trap(188) system.sysUpTime.0=222765000 S:1.1.4.1.0=E:1139.101.1 E:1139.101.1.1=3 E:1139.101.1.2=”System.License.Trial_License_Used” E:1139.101.1.3=”[MDM1-id]” E:1139.101.1.4=”SIO01.02.0000003″

[After MDM2 shutdown]

10:41:53.734020 IP [SIO-GATEWAY].36025 > [SNMP-RCV].snmptrap: V2Trap(188) system.sysUpTime.0=222768000 S:1.1.4.1.0=E:1139.101.1 E:1139.101.1.1=3 E:1139.101.1.2=”System.License.Trial_License_Used” E:1139.101.1.3=”[MDM1-id]” E:1139.101.1.4=”SIO01.02.0000003″

10:41:53.734251 IP [SIO-GATEWAY].36025 > [SNMP-RCV].snmptrap: V2Trap(188) system.sysUpTime.0=222768000 S:1.1.4.1.0=E:1139.101.1 E:1139.101.1.1=5 E:1139.101.1.2=”MDM.MDM_Cluster.MDM_Not_Clustered” E:1139.101.1.3=”[MDM1-id]” E:1139.101.1.4=”SIO02.01.0000001″

[During MDM2 rebooting]

10:45:23.733943 IP [SIO-GATEWAY].59254 > [SNMP-RCV].snmptrap: V2Trap(188) system.sysUpTime.0=222789000 S:1.1.4.1.0=E:1139.101.1 E:1139.101.1.1=3 E:1139.101.1.2=”System.License.Trial_License_Used” E:1139.101.1.3=”[MDM1-id]” E:1139.101.1.4=”SIO01.02.0000003″

10:45:23.734308 IP [SIO-GATEWAY].59254 > [SNMP-RCV].snmptrap: V2Trap(188) system.sysUpTime.0=222789000 S:1.1.4.1.0=E:1139.101.1 E:1139.101.1.1=5 E:1139.101.1.2=”MDM.MDM_Cluster.MDM_Not_Clustered” E:1139.101.1.3=”[MDM1-id]” E:1139.101.1.4=”SIO02.01.0000001″

[After MDM2 rebooted]

10:45:53.734101 IP [SIO-GATEWAY].57034 > [SNMP-RCV].snmptrap: V2Trap(188) system.sysUpTime.0=222792000 S:1.1.4.1.0=E:1139.101.1 E:1139.101.1.1=3 E:1139.101.1.2=”System.License.Trial_License_Used” E:1139.101.1.3=”[MDM1-id]” E:1139.101.1.4=”SIO01.02.0000003″

10:46:23.734032 IP [SIO-GATEWAY].52960 > [SNMP-RCV].snmptrap: V2Trap(188) system.sysUpTime.0=222795000 S:1.1.4.1.0=E:1139.101.1 E:1139.101.1.1=3 E:1139.101.1.2=”System.License.Trial_License_Used” E:1139.101.1.3=”[MDM1-id]” E:1139.101.1.4=”SIO01.02.0000003″

————————————

*: “…” means repeating.

Regards,

Ichiro

Related:

  • No Related Posts

Netscaler VPX 1000 – Azure – Slowness getting through Netscaler.


With 12.0 builds, we have changed default yield behavior for PE vCPUs. vCPU will not yield to hypervisor, even though if there is less/moderate traffic in 12.0 build, which was not the case for 11.1 builds. That’s the reason, VPX vCPU is always 100% on hypervisor. However, vCPU is allocated to management core might not be 100%.

NetScaler yields PE vCPUs to hypervisor in sparse/moderate traffic cases. Since we have observed Tx overflow/congestion, it’s somewhat related to scheduling, we thought not yielding vCPU helps in improving the situation.

– set ns vpxparam -cpuyield NO

Upgrade to 12.0.53.X+

Related:

  • No Related Posts

How to Use the Authentication Feature of a NetScaler Appliance with a Load Balancing or Content Switching VServer on the Appliance

This article describes how to use the authentication feature of a NetScaler appliance with a Load Balancing or Content Switching virtual server on the appliance.

Requirements

To complete this task, the NetScaler appliance must have license for the Load Balancing, Content Switching, and Authentication, Authorization, and Auditing (AAA – Application Traffic) features.

Related:

  • No Related Posts

Upgrade SourceOne 6.8 to 7.2

Hello,

We are currently running SourceOne Email Management v 6.8 (no service packs) and would like to upgrade to the latest and greatest – 7.2 sp6. I am seeing mixed things regarding an upgrade path – I was initially told by EMC that I need to upgrade to v6.8 sp4, then v7.0, then v7.2 sp6. However, the release notes for v7.1 say you can upgrade from v6.8 sp1 (I can’t find the release notes for v7.2).

I have also been reading thru the v7.1 install guide and do not see any mention of upgrading from v6.8. Any special requirements or procedures? Also, wondering about licensing – do I need to acquire a new license key/file? (not a problem, we do have support).

Can anyone please offer any insight?

Thank you.

Related:

  • No Related Posts

Symantec DLP real-time scan for uploaded SharePoint documents?

I need a solution

Is there a way to integrate Symantec DLP with SharePoint to have a real-time document scan during upload and download of documents?

How could I tell SharePoint to send uploded documents to the Symantec DLP Detection REST API?

I see that the Symantec Protection product integrates with SharePoint and has this real-time scan feature, but only for Malware. Would be nice to connect Symantec Protection and Symantec DLP Detection…

0

Related:

  • No Related Posts