Hi all,

I'm running a proof of concept environment to trial VM DR and so far having a lot of joy in testing the features however I came across a potential show stopper for prospective users/clients who might be considering using this solution but wanted to run it by you guys/girls to see if there was a way round the problem.

My problem is that some clients might not have large storage arrays to store the backups on the LUNs/RDMs presented to the Recovery Server so would probably look to reducing the retention settings to allow a certain amount of daily/weekly jobs on disk. In addition to this I can foresee customers wanting to back the backup data LUNs to tape to adhere to company policies/laws etc.

So in light of this, if I wanted to backup the datastore/rdm containing the backup data from the vDR server to tape and at a later stage carry out a restore (i.e. a VM/file which has expired beyond the retention set by vDR server); how would I go about importing the files/data back on to the server and then see these backup objects in the vDR server?

Is it possible or a functionality I've missed or is there a work around for this?

Your thoughts and suggestions are always welcome!

Regards

Don

Hi, it is possible to install a backup agent on the vmware datarecovery appliance  to perform file base backup of the backup virtuel machine  ? thank Chist ? 

Hey,

I have a problem with back up my virtual guests over CommVault Simpana 9 SP3. Every time I try to back up a vSphere 5 VM I got following Error from Galaxy Server: Description: Unable to download the VMX file for Virtual Machine [VM].  Please consult http://kb.vmware.com/kb/1019286 for additional information.

I opened a support case some weeks ago but they can't help me till now.

This error happen within an HA Cluster, other vCenter, directly over vSphere Client ... every time. I have no successfull backup since I upgrade or servers to vSphere5.

Is there any solution?

I have a vmdk file tfrom an SMVI backup that i am trying to mount on a different server adn wehn i try to add it and point top that datastore location no files show up so i can't restore my files.  The file is quite larre so i can't move it around too much but tried different locatoins with the same results. The file is called...server_1-flat.vmdk.  Is there any reason this file cannot be mounted.  Any help is appreciated.  thanks

I have a big problem with consolidation VM disks, and with VDR at all.

A few days ago VDR was trying to make backup and remove snapshhoot on mail server (1 TB disk), and result was a new 219 delta disks in one night!

Another result of that was that my connection with vCenter is going doing after few seconds I am connected.

After many hours I realize that connection is going down becouse mail server (with 219 disks) is in inventory, althouh it is not powered on.

I can connet directly on esx host, remove VM from inventory and then I can connet on vCenter with that host.

Automatic consolidation did not work (Cannot allocate memory) so I try to manually clone this disk with vmkfstools but after 52% I get message:

"Failed to clone disk: Cannot allocate memory (786441)."

I tried with thin disk (vmkfstools -i ... -d thin) but nothing.

I tried to set parameter VMFS3.MaxHeapSizeMB in advanced settings on maximum.

I even upgraded esx and vCenter on 5.1 version.

I appreciate any advice.

I'm using Veeam Backup & Recovery version 6.5 with VMware vSphere ESXi 5.1. The VM storage is local to the ESXi server in a RAID5 SAS array. Veeam is running on a separate physical machine and backing up over a 2 Gbps aggregated link, onto an external USB 2.0 hard drive.

Veeam seems to top out at about 22MB/s when performing a backup operation, and indicates that the bottleneck is the source. This seems too slow given the setup, and I'm wondering if I'm missing something. Can anyone shed any light on my situation?

hi guys

I would like to know If I am the only one having this issues where VDP works good some time and all of sudden backups start failing and you find those VMs faling are the ones needing disk consolidation since VDP has made a ton of snapshots which obviously were not properly removed.

This issue has cost some downtime in this Virtual machines one of this power off itseft when trying to vmotion.

this weekend VDP tried to do the backup as usual and tried to consolidate too but it failed and powered off the VM.

I would like to know which is the reason for this? are my VMs too big (500 GB, 300 GB) an VDP is not ready for this?

or my VMs are IO Intensive and VDP is not ready for this?

but the way I don't have the latest version that came out in November I think but I have the previous version for VDP 5.5, I think it 5.5.1

thanks a lot guys

Hi Team,

I've been searching the net for info. on CPU ready time on ESX host, I'm already aware for VM's the recommended is 5% CPU ready time anything higher than that the VM would is performing quite poorly.

But what I want to know is ESX host ready such that I can measure at host level the CPU's are over committed resulting in insufficient CPU resource allocation for the VM's but I haven't managed to find any specifics - can anyone shed some light on this or point me in the right direction

Hi vSphere community,

Curious what people are doing to backup up physical ESXi servers?   We have IBM TSM, but I'm not sure it can backup an ESX Host.

Strictly looking at ESX host backups at the moment and not virtual machines.

Any suggestions or advice?

Thanks!

I accidentally deleted a folder while browsing datastore thru VSphere Client containing the VM on ESXi 5.5. Can I recover it, I am new to this, can someone please help me.

Hallo VMware Community,

we are running VSA Backup of CommVault SIMPANA. We are using a VSA Proxy. To the Proxy the VMFS-5 LUNs are mapped read-only so that we can use SAN as transport mode for the VMs which are located on that datastores.

We have testet many things but always still getting the error message "Failure Reason:Could not read data from the virtual disk" and the Job failed. At the beginning we started with one Subclient for all the VMs but now we switched to one Subclient per VM so that the jobs are running sequentially step by step but the error still occurs.

Error Code (at SIMPANA Console):

Description: Unable to read the disk [] for virtual machine [xxx] on Host [xxx]. [Beim Verarbeiten der Anfrage ist mindestens ein Fehler aufgetreten., Failed to ReadCurrVmdkFile (W32.774)]

Source: xxx, Process: vsbkp    

8340  1b88  01/25 00:33:11 89467 stat- ID [readdisk], Bytes [26381910425], Time [133.847090] Sec(s), Average Speed [187.973832] MB/Sec

8340  1b88  01/25 00:33:11 89467 CVMDiskInfo::DecrementMaxNDBHandlesAllowed() - Max allowed NBD Open handles for backup are now [0]

8340  1b88  01/25 00:33:11 89467 CVMDiskInfo::IncrementMaxNDBHandlesAllowed() - Max allowed NBD Open handles for backup are now [1]

8340  1b88  01/25 00:33:11 89467 VSBkpWorker::BackupVMDisk() - Using default extent size

8340  1b88  01/25 00:33:11 89467 VSBkpWorker::BackupVMDisk() - Disabling CRC Processing as change Id [52 47 9b 90 ff f5 be 24-37 6c f9 43 a2 89 58 e3/57] is supplied

8340  1b88  01/25 00:33:11 89467 VSBkpChangeIdFile::ReadChangeID() - Not using a Change ID

8340  6     01/25 00:33:11 89467 ### GetService --- Reopening connection

8340  6     01/25 00:33:12 89467 ### CVIWrapper::_GetDiskInfoArr --- Updating disk label from [Festplatte 1] to [Hard disk 1]

8340  6     01/25 00:33:13 89467 ### CVIWrapper::_GetDiskInfoArr --- Updating disk label from [Festplatte 2] to [Hard disk 2]

8340  1b88  01/25 00:33:13 89467 There are 6 entries in the allocated extent table for xxx.vmdk

8340  1b88  01/25 00:33:13 89467 VSBkpWorker::BackupVMDisk() - Extent Size [262144] bytes [512] sectors [512] bytes per sector

8340  1b88  01/25 00:33:13 89467 VSBkpWorker::BackupVMDisk() - Sending File Header Path:[\501de18e-3138-67f9-2514-daffc1b51880\scsi0-1-xxx_1.vmdk] with size:[450971566080]

8340  1b88  01/25 00:33:13 89467 VSBkpWorker::AddVMMetadataFile() - Adding metadata file [D:\Program Files\CommVault\Simpana\iDataAgent\JobResults\CV_JobResults\iDataAgent\VirtualServerAgent\2\375\VolHdr(501de18e-3138-67f9-2514-daffc1b51880_scsi0-1-xxx_1.vmdk).imf] to list to be uploaded to index cache

8340  1b88  01/25 00:33:13 89467 VSBkpWorker::BackupVMDisk() - Backing up disk/volume [xxx_1.vmdk]

8340  1b88  01/25 00:33:13 89467 VSBkpWorker::BackupVMDisk() - Using Fixed Length Extent Names

8340  234c  01/25 00:33:13 89467 VSBkpWorker::ArchiveExtentProcessor() - Send volume or disk data to MA thread

8340  2134  01/25 00:34:35 89467 VSBkpCoordinator::OnIdle_Running() - Waiting for [1] VMs to be processed.  [xxx]

8340  2134  01/25 00:34:35 89467 VSBkpCoordinator::DumpStreamInfo() - StreamId = 1, RCID = 189844, ReservationId = 137886, MediaAgent = s190a0010, Agent = s190a0010  []

8340  1b88  01/25 00:34:50 89467 CVMDiskInfo::ReadDisk() - VixDiskLib_Read failed Err=3e80 One of the parameters supplied is invalid

8340  1b88  01/25 00:34:50 89467 VSBkpWorker::BackupVMDisk() - Failed to read from virtual disk [xxx_1.vmdk],  [0x80070306:{..\..\..\CommClient\VirtualServer\VMInfo\ArchiveVirtualDiskFile.cpp[CArchiveVirtualDiskFile::GetNextBlock(535)]} + {..\..\..\CommClient\VirtualServer\VMInfo\VmdkVcb4ExtentReader.cpp[CVmdkVcb4ExtentReader::ReadBlock(664)]/W32.774.(Beim Verarbeiten der Anfrage ist mindestens ein Fehler aufgetreten.)-Failed to ReadCurrVmdkFile}]

We are running the latest version of VMware ESXi and also the latest version of the vSphere Server.

Maybe someone of you is also using VSA backup of SIMPANA and can help us to resolve this issue.

Thanks a lot

Best Regards

Philipp

Hi there,

I consider not renewing my Veeam B&R license this time because I want to try if the latest version of DP gives me what I need.

I need to replicate all VMs on two hosts on site A via a fibre link to a third host at a second location (site B) . The Veeam B&R software managed that excellently.  One replication each night that left complete ready-to-run VM replicas at the remote site.  No backup history, just one fresh copy of each VM each night.  No Exchange, SQL Server nor SharePoint.

I have only one VCenter server with one DP 6.1.1 appliance connected.  Can I use this setup to replicate VMs to site B in the same manner?  Do I need a DP proxy at site B?

Do I still have to restore the replicated VMs using DP in order to start / use them?  Why is it so difficult for VMWare to just snapshot and replicate the VM files in folders as Veeam does?  I'd like a replication solution that creates ready-to-run VMs at the remote site.  Do I need Veeam to achieve that..?

Comments are welcome :-)

greetings

btor

Hello,

Is there any way I can perform backup of a VM having physical RDM. As physical RDM isn't allow snapshots to create so I am not able to perform any backup.

Is there anyway I can perform excluding RDM disk and take backup of OS disk only?

I am using HPE Data Protector as a backup software.

Regards,

Hi - I hope someone will be able to point me in the right direction to resolve this.

I am trying to deploy the standard 2GB VDP 5.8.4 into a 5.5 environment.

The .ova deploys without issue and powers on.

I log into the suggested web page and am able to confirm the network details and run through the rest of the set up wizard, linking to my chosen VC and adding storage. The wizard completes works for a few mins to add the storage and then reboots the appliance and then the appliance comes up and steps through the configuration until it returns to the standard blue logon screen. Subsequent reboots are just reboots.

I believe the next step is to go into the VDP Node in the webclient, select the appliance from the drop down and click 'Connect' - when I do this the interface 'grey's out and the clock timer symbol appears... and that's it... no failure message, nothing until the client times out or I manually refresh.

All the DNS entries are in place and resolve in both directions, the account I used to join the appliance to VC has full permissions.

I have trawled the KBs looing for something similar but the articles I have found do not appear to apply to these symptoms - I will raise a case if necessary but I'm hoping someone has seen this before and can help me out.

I did a data domain restore because we were updating from VDP 6.0 to 6.1.2 and the migration utility will not work currently, so in order to do a migration you need to do a Data Domain Checkpoint Restore, we followed it very closely in the documentation and we I also looked at this link, which describes what we did. But that problem that I am having is that we don't see any of our existing back up jobs nor restores. And we restarted VDP logged out of web client log back in, checked the plugin the new plug in is there we did a integrity check and still nothing coming up, what am I missing?

Hi All,

I've been struggling with another issue in my home lab.  I upgraded to vCenter 6.5 last week and, at the same time, deployed a new vDP 6.1.3 appliance.  Try as I might, I can't seem to get the plug-in to appear anywhere within vCenter.

I have gone into the extensions section of http://<vcenter>/mob and only see config.vmware.vdp2.config.  I can't seem to get config.vmware.vdp2 to show up, even if I delete the .config entry and restart/re-register the vDP appliance.

I have also done the workaround where you log into the vCenter server and add the .war and .jar file manually into the vsphere-client directory, with no luck.

Anyone else seeing this issue?

Thanks,

Dave

Hello,

I have a small lab where I am testing VDP 6.1.3. This appliance is backing up some VM successfully. I have installed SQL server agent in a server with Windows Server 2016 and SQL Server 2016. I get This error:

2017-02-27 20:00:16 avsql Info <5008>: Logging to C:\Program Files\avp\var\XutiLabSQL-XutiLabSQL-1488222002981-3006-SQL.log

2017-02-27 20:00:18 avsql Info <6673>: CTL listening on port 57495

2017-02-27 20:00:18 avsql Info <10684>: Setting ctl message version to 3 (from 1)

2017-02-27 20:00:18 avsql Info <16136>: Setting ctl max message size to 268435456

2017-02-27 20:00:18 avsql Info <17376>: Working on stand alone environment.

2017-02-27 20:00:18 avsql Info <7838>: - Adding user exclude "*/tempdb"

2017-02-27 20:00:18 avsql Info <18482>: Adding SQL Database '*/tempdb' to EXCLUDE list

2017-02-27 20:00:18 avsql Info <19484>: ===> sqlconnectimpl::check_smo_version

2017-02-27 20:00:18 avsql Info <19484>: ===> sqlconnectimpl::get_smo_version

2017-02-27 20:00:18 avsql Info <19482>: Found assembly: 'Microsoft.SqlServer.Smo,fileVersion="12.0.2000.8",version="12.0.0.0000",culture="neutral",publicKeyToken="89845DCD8080CC91",processorArchitecture="MSIL"'

2017-02-27 20:00:18 avsql Info <19483>: Returning from SMO version check with value: 16

2017-02-27 20:00:18 avsql Info <0000>: <=== sqlconnectimpl::get_smo_version

2017-02-27 20:00:18 avsql Info <19484>: ===> sqlconnectimpl::get_smo_version

2017-02-27 20:00:18 avsql Info <19482>: Found assembly: 'Microsoft.SqlServer.Smo,fileVersion="12.0.2000.8",version="12.0.0.0000",culture="neutral",publicKeyToken="89845DCD8080CC91",processorArchitecture="MSIL"'

2017-02-27 20:00:18 avsql Info <19483>: Returning from SMO version check with value: 16

2017-02-27 20:00:18 avsql Info <0000>: <=== sqlconnectimpl::get_smo_version

2017-02-27 20:00:18 avsql Info <0000>: <=== sqlconnectimpl::check_smo_version

2017-02-27 20:00:18 avsql Info <19487>: Start checking for SMO DLL version 12...

2017-02-27 20:00:18 avsql Info <19484>: ===> sqlconnectimpl::is_SqlServ_2014

2017-02-27 20:00:18 avsql Info <19484>: ===> sqlconnectimpl::get_SqlServers_ver

2017-02-27 20:00:18 avsql Info <19468>: Connected to ROOT\CIMV2 WMI namespace.

2017-02-27 20:00:41 avsql Info <19475>: Detected version: 13.0.1601.5

2017-02-27 20:00:41 avsql Info <19476>: Add (13) to major version list.

2017-02-27 20:00:41 avsql Info <19475>: Detected version: 13.0.1601.5

2017-02-27 20:00:41 avsql Info <19471>: Reach the end of wmi qurery enumerator object.

2017-02-27 20:00:41 avsql Info <0000>: <=== sqlconnectimpl::get_SqlServers_ver

2017-02-27 20:00:41 avsql Info <0000>: <=== sqlconnectimpl::is_SqlServ_2014

2017-02-27 20:00:41 avsql Info <19494>: Start checking for SMO DLL version 10...

2017-02-27 20:00:41 avsql Info <19484>: ===> sqlconnectimpl::is_SqlServ_2008

2017-02-27 20:00:41 avsql Info <19484>: ===> sqlconnectimpl::get_SqlServers_ver

2017-02-27 20:00:41 avsql Info <19468>: Connected to ROOT\CIMV2 WMI namespace.

2017-02-27 20:00:44 avsql Info <19475>: Detected version: 13.0.1601.5

2017-02-27 20:00:44 avsql Info <19476>: Add (13) to major version list.

2017-02-27 20:00:44 avsql Info <19475>: Detected version: 13.0.1601.5

2017-02-27 20:00:44 avsql Info <19471>: Reach the end of wmi qurery enumerator object.

2017-02-27 20:00:44 avsql Info <0000>: <=== sqlconnectimpl::get_SqlServers_ver

2017-02-27 20:00:44 avsql Info <0000>: <=== sqlconnectimpl::is_SqlServ_2008

2017-02-27 20:00:44 avsql Error <19498>: Unable to load any of SMO managed DLL files.

2017-02-27 20:00:44 avsql Error <15744>: Unable to load SMO managed DLL: (symbol SMO_New not found)

2017-02-27 20:00:44 avsql Error <15760>: No targets after expansion!

2017-02-27 20:00:44 avsql Error <15760>: No targets after expansion!

2017-02-27 20:00:44 avsql Info <7271>: Final summary generated subwork 0, cancelled/aborted 0, snapview 0, exitcode 536870919

2017-02-27 20:00:49 avsql Info <6451>: avsql returning with exitcode 536870919

Is VDP 6.1.3 compatible with SQL Server 2016?

Thank you.

I am attempting to deploy a new VDP 6.1.4 appliance in our vCenter Server 6.5 environment. I am able to deploy and configure the appliance without issue, all services are running, and I am able to ssh to said appliance. When I attempt to connect to the appliance from vCenter I receive the following error:

Unable to connect to the requested VDP Appliance.

Would you like to be directed to the VDP Configuration utility to troubleshoot the issue?

I have deleted the appliance from disk and tried this a second time with the same results.

I have gone through the vCenter registration in the Configuration a few times, trying local accounts and SSO/AD accounts with the same results.

I have NTP servers configured in my ESXi hosts, set the time zone in the VDP appliance and verified that the date and time are correct.

Another thread led me to check the mcserver.out info as there is a known issue in an earlier version with vCenter Server 5.5. While there seems to be warnings and exceptions I am not sure I can make heads or tails as to what they are.

=== BEGIN === check.mcs (prestart)
check.mcs                        passed
=== PASS === check.mcs PASSED OVERALL (prestart)
Starting Administrator Server at: Tue Apr 18 07:33:44 MDT 2017
Starting Administrator Server...
Warning: org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser: Property 'http://www.oracle.com/xml/jaxp/properties/entityExpansionLimit' is not recognized.
Compiler warnings:
  WARNING:  'org.apache.xerces.jaxp.SAXParserImpl: Property 'http://javax.xml.XMLConstants/property/accessExternalDTD' is not recognized.'
Started
Clone started
Clone started
Clone started
Clone started
Initiated VC: /pic-vc01.corp.pingidentity.com. (Total time - 10421 ms)
VmwareService is ready. (Total time - 10422 ms)

2017-04-18 07:34:17.540:INFO::Logging to STDERR via org.mortbay.log.StdErrLog
2017-04-18 07:34:17.642:INFO::jetty-6.1.23
2017-04-18 07:34:17.669:INFO::Extract lib/mcsdk-axis2.war to /usr/local/avamar/var/mc/server_tmp/Jetty_0_0_0_0_9443_mcsdk.axis2.war____.xz4n3v/webapp
2017-04-18 07:34:25.927:INFO::Started TlsSocketConnector@0.0.0.0:9443
2017-04-18 07:34:26.146:INFO::jetty-6.1.23
2017-04-18 07:34:26.310:INFO::Extract lib/mcebms.war to /usr/local/avamar/var/mc/server_tmp/Jetty_0_0_0_0_9090_mcebms.war____i3qqxk/webapp
2017-04-18 07:34:27.075:INFO:/:Initializing Spring root WebApplicationContext
2017-04-18 07:34:28.219:INFO::Started TlsSocketConnector@0.0.0.0:9090
Administrator Server started.
Started
Ended VMWare
Ended VMWare
Started
Exception in thread "VmwareEventsMonitor for VC /pic-vc01.corp.xxxxxxxxxxx.com" java.lang.LinkageError: loader (instance of  sun/misc/Launcher$AppClassLoader): attempted  duplicate class definition for name: "org/apache/axis/message/SOAPFaultCodeBuilder"
        at java.lang.ClassLoader.defineClass1(Native Method)
        at java.lang.ClassLoader.defineClass(Unknown Source)
        at java.security.SecureClassLoader.defineClass(Unknown Source)
        at java.net.URLClassLoader.defineClass(Unknown Source)
        at java.net.URLClassLoader.access$100(Unknown Source)
        at java.net.URLClassLoader$1.run(Unknown Source)
        at java.net.URLClassLoader$1.run(Unknown Source)
        at java.security.AccessController.doPrivileged(Native Method)
        at java.net.URLClassLoader.findClass(Unknown Source)
        at java.lang.ClassLoader.loadClass(Unknown Source)
        at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source)
        at java.lang.ClassLoader.loadClass(Unknown Source)
        at org.apache.axis.message.BodyBuilder.onStartChild(BodyBuilder.java:160)
        at org.apache.axis.encoding.DeserializationContext.startElement(DeserializationContext.java:1035)
        at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
        at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
        at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
        at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
        at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
        at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
        at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
        at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
        at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
        at org.apache.xerces.jaxp.SAXParserImpl.parse(Unknown Source)
        at org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227)
        at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)
        at org.apache.axis.Message.getSOAPEnvelope(Message.java:435)
        at org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:62)
        at org.apache.axis.client.AxisClient.invoke(AxisClient.java:206)
        at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
        at org.apache.axis.client.Call.invoke(Call.java:2767)
        at org.apache.axis.client.Call.invoke(Call.java:2443)
        at org.apache.axis.client.Call.invoke(Call.java:2366)
        at org.apache.axis.client.Call.invoke(Call.java:1812)
        at com.vmware.vim25.VimBindingStub.waitForUpdates(VimBindingStub.java:49497)
        at com.avamar.mc.vmware.VmwareEventsMonitor.run(VmwareEventsMonitor.java:334)
Clone started
Clone started
Clone started
Clone started

I'm using VDP 6.1 in ESXi 6 environment cluster to backup virtual machines and I noted the same Windows guest OS has different kind of backup:

Crash Consistent or application consistent backup

E.g. the same job for Windows 2008 sometimes gets Crash Consistent backup and it sometimes get application consistent backup?

So logs show for some day "application consistent backup and for other days "Crash Consistent backup"

What is the reason to get different types of backup for the same job? In this server there is no database.

thanks

is there any way to reduce the log-spam of the VDP appliance

fresh deployment of vSphereDataProtection-6.1.5.ova at 2016-12-06 and until tody 280 such 25 MB files
since the appliance itself is thin-provisioned on NFS that thing grows useless and 50-75 MB per day is way too much

what makes this also bad is that on NFS UNMAp don't work and we copy the whole appliance regulary to a USB3 harddisk with "cp -R --sparse=always"
at the bottom a log-sample - frankly if something goes wrong i prefer re-deploy anyways

[root@vmware-recovery:/etc/cron.daily]$ cat /usr/local/bin/remove-gsan-logs.sh

#!/bin/bash

/usr/bin/find /data01/ -mtime +3 -type f -regex ".*\/gsan\.log\.[0-9][0-9].*" -exec /bin/ls -lh {} \;

/usr/bin/find /data01/ -mtime +3 -type f -regex ".*\/gsan\.log\.[0-9][0-9].*" -exec /bin/rm -f {} \;

/usr/bin/find /data02/ -mtime +3 -type f -regex ".*\/gsan\.log\.[0-9][0-9].*" -exec /bin/ls -lh {} \;

/usr/bin/find /data02/ -mtime +3 -type f -regex ".*\/gsan\.log\.[0-9][0-9].*" -exec /bin/rm -f {} \;

/usr/bin/find /data03/ -mtime +3 -type f -regex ".*\/gsan\.log\.[0-9][0-9].*" -exec /bin/ls -lh {} \;

/usr/bin/find /data03/ -mtime +3 -type f -regex ".*\/gsan\.log\.[0-9][0-9].*" -exec /bin/rm -f {} \;

[harry@srv-rhsoft:/downloads]$ cat remove-gsan-logs.log | wc -l

280

part of the delete-log:

-r--r----- 4 admin admin 25M Dec 29 00:33 /data01/cur/gsan.log.014

-r--r----- 4 admin admin 25M Dec 28 12:53 /data01/cur/gsan.log.015

-r--r----- 4 admin admin 25M Dec 28 03:49 /data01/cur/gsan.log.016

-r--r----- 4 admin admin 25M Dec 27 20:29 /data01/cur/gsan.log.017

-r--r----- 4 admin admin 25M Dec 27 08:51 /data01/cur/gsan.log.018

-r--r----- 4 admin admin 25M Dec 27 00:36 /data01/cur/gsan.log.019

-r--r----- 4 admin admin 25M Dec 26 12:59 /data01/cur/gsan.log.020

-r--r----- 4 admin admin 25M Dec 26 03:53 /data01/cur/gsan.log.021

-r--r----- 4 admin admin 25M Dec 25 17:10 /data01/cur/gsan.log.022

-r--r----- 4 admin admin 25M Dec 25 07:05 /data01/cur/gsan.log.023

-r--r----- 4 admin admin 25M Dec 24 21:17 /data01/cur/gsan.log.024

-r--r----- 4 admin admin 25M Dec 24 09:42 /data01/cur/gsan.log.025

-r--r----- 4 admin admin 25M Dec 24 01:20 /data01/cur/gsan.log.026

-r--r----- 4 admin admin 25M Dec 23 14:07 /data01/cur/gsan.log.027

-r--r----- 4 admin admin 25M Dec 23 05:00 /data01/cur/gsan.log.028

-r--r----- 4 admin admin 25M Dec 22 18:36 /data01/cur/gsan.log.029

-r--r----- 4 admin admin 25M Dec 22 07:53 /data01/cur/gsan.log.030

-r--r----- 4 admin admin 25M Dec 21 23:45 /data01/cur/gsan.log.031

-r--r----- 4 admin admin 25M Dec 21 11:05 /data01/cur/gsan.log.032

-r--r----- 4 admin admin 25M Dec 21 01:34 /data01/cur/gsan.log.033
......................

[root@vmware-recovery:/data01/cp.20180101051643]$ tail -n 10 gsan.log.010

2017/12/29-07:59:26.78420 {0.0} [srvm-14292621#srv:2729]  servloop::acctrequest login username=root

2017/12/29-07:59:26.78507 {0.0} [srvm-14292621#srv:104]  syslog: msg=[/usr/local/avamar/bin/avmaint --flagfile=/usr/local/avamar/etc/usersettings.cfg --password=**************** --vardir=/usr/local/avamar/var --server=vmware-recovery --id=root --bindir=/usr/local/avamar/bin getclientmsgs --server=vmware-recovery.thelounge.net --hfsport=27000 --conntimeout=120 --timeout=120 --vardir=/usr/local/avamar/var --startoffset=22188496] host=[vmware-recovery] time=[Fri Dec 29 08:59:26 2017 CEST] build=[version=7.2.80-133 date=Jul 13 2017 08:07:49 msg=13-10 SSL=TLSv1   OpenSSL 1.0.2a-fips 19 Mar 2015 Zlib=1.2.7 LZO=1.08 Jul 12 2002 platform=Linux OS=SLES-64 Processor=x86_64]

2017/12/29-07:59:26.78872 {0.0} [srvm-14292621#0x8ea22b0 clientaddr=192.168.196.114:57533 ismaint=1 type=avmaint access=uname=root uid=0 priv=enabled,create,read,backup,access,move,delete,maint,manage,fullmanage,noticketrequired,superuser,ignoreacls,readdir,mclogin,opt1,opt2 avail=modes=00pu:3179]  servmain::dispatcherloop end

2017/12/29-07:59:26.78882 {0.0} [srvm-14292621#0x8ea22b0 clientaddr=192.168.196.114:57533 ismaint=1 type=avmaint access=uname=root uid=0 priv=enabled,create,read,backup,access,move,delete,maint,manage,fullmanage,noticketrequired,superuser,ignoreacls,readdir,mclogin,opt1,opt2 avail=modes=00pu:3179]  servmain::execute end

2017/12/29-07:59:27.03422 {0.0} [acpt0-27000-192.168.196.114]  Socket buffer size (recv) requested 131072, was set to 131072

2017/12/29-07:59:27.03425 {0.0} [acpt0-27000-192.168.196.114]  Socket buffer size (send) requested 131072, was set to 131072

2017/12/29-07:59:27.03457 {0.0} [srvm-14292637#0x8ea22b0 clientaddr=192.168.196.114:51043 ismaint=1 type=unknown access=<noaccess> avail=<noavail>:3358]  servmain::execute start

2017/12/29-07:59:27.03459 {0.0} [srvm-14292637#0x8ea22b0 clientaddr=192.168.196.114:51043 ismaint=1 type=unknown access=<noaccess> avail=modes=0000:3358]  servmain::dispatcherloop start

2017/12/29-07:59:27.03484 {0.0} [srvm-14292637#srv:078]  servloop::handle_getserverconnection 192.168.196.114:27000 -> 192.168.196.114:27000

2017/12/29-07:59:27.03666 {0.0} [srvm-14292637#srv:872]  servloop::acctrequest login username=root