arturo3's Posts

arturo3's Posts

You are right, it is not a normal plugin since it is the DTO export and imports plugins but avtar binary is similar to any avtar running on any Linux system and it can be used to backup DR image ... See more...
You are right, it is not a normal plugin since it is the DTO export and imports plugins but avtar binary is similar to any avtar running on any Linux system and it can be used to backup DR image via command line as I suggested. Rgds
Joe, AER node is running an external avamar agent activated on the external grid so you could use similar previous scripting and replace scp command by avtar command and backup snapshot folder o... See more...
Joe, AER node is running an external avamar agent activated on the external grid so you could use similar previous scripting and replace scp command by avtar command and backup snapshot folder on the external server.
Joe, DR exports can be sent to another machine using scp for example. Procedure steps are documented on this KB: https://support.emc.com/kb/192102 If you don't have access these are ... See more...
Joe, DR exports can be sent to another machine using scp for example. Procedure steps are documented on this KB: https://support.emc.com/kb/192102 If you don't have access these are the steps: • In order to be able to successfully create an AER DR copy we need first to have at least one tape with space, labelled on the Default pool • By default the AER DR copy needs to be run manually using the command below but many customers ask support to configure this to run auto /opt/EMC/avamarer/bin/avamar-er-dr --export --pass=<postgrespassword> •In order to run this command automatically we can use the AER internal Avamar cron crontab –e   •And add a line at the end of the cron tab (with the time and frequency we want it to run) with something like the following as an example 34 12 * * * /root/AERdisasterrecovery.sh •Where “AERdisasterrecovery.sh” is the following script which runs the DR command and does a scp of the snapshot file to an external server in order to keep the DR snapshots safe in the case if we lose the AER server #!/bin/bash PATH=/usr/local/avamar/bin:/sbin:/usr/sbin:/usr/local/avamar/bin:/bin:/usr/bin:/sbin:/usr/sbin:/usr/local/bin:/usr/local/sbin:/usr/local/apache/bin:/usr/local/ssl/bin:/opt/dell/srvadmin/bin:/opt/dell/srvadmin/sbin export PATH SNAPSHOTDIR=/tmp/ER-DR-SNAPSHOT #create DR copy /opt/EMC/avamarer/bin/avamar-er-dr --export --pass=<postgrespassword> #copies the DR snapshot outside the AER server File=`ls -latr /opt/EMC/snapshot | grep -e avamar-er-dr-1.1.0-01-Snapshot.zip | tail -1 | awk '{print $9}'` echo $File cp /opt/EMC/snapshot/$File $SNAPSHOTDIR scp $SNAPSHOTDIR/$File root@<externalserver>:$SNAPSHOTDIR  •This way we can automatically create snapshots of the AER configuration outside the server which will allow us to fully recover the server in the case of loss * note that for a fully server recovery we also need the Networker bootstrap which is also generated with the same command but is saved on the Default tape pool
I would try to list all available clients on that domain to check if client name is correct: mccli client show --domain==/10.137.84.3/VirtualMachines --recursive
You are using Windows VMware Image pluginid (3016) to restore a Linux VM so this is the reason why restore is rejected. Give it a try to pluginid 1016: mccli backup restore --name=/10.136.84.... See more...
You are using Windows VMware Image pluginid (3016) to restore a Linux VM so this is the reason why restore is rejected. Give it a try to pluginid 1016: mccli backup restore --name=/10.136.84.2/VirtualMachines/vropsrh6561-d --labelnum=3 --plugin=1016 --restore-vm-to=original and/or mccli backup restore --name=/10.136.84.2/VirtualMachines/vropsrh6561-d_UBEF80CAvSoTkeHvoLxFGg --labelnum=3 --plugin=1016 --restore-vm-to=original
According to mccli command you are running a restore and not a backup as you mentioned, I suppose it is a typo. 1) On first command: plugin id is wrong and you didn't set restore-vm-to param.... See more...
According to mccli command you are running a restore and not a backup as you mentioned, I suppose it is a typo. 1) On first command: plugin id is wrong and you didn't set restore-vm-to param. 2) On second command: plugin id is wrong and you didn't set restore-vm-to param. What kind of restore do you want to run? to new or original VM? If it is restore to original VM I would try something like: mccli backup restore --name=/10.136.84.2/VirtualMachines/vropsrh6561-d --labelnum=3 --plugin=3016 --restore-vm-to=original or mccli backup restore --name=/10.136.84.2/VirtualMachines/vropsrh6561-d_UBEF80CAvSoTkeHvoLxFGg --labelnum=3 --plugin=3016 --restore-vm-to=original
Required port are documented in Security Guide, latest Avamar 7.1 can be found here: https://support.emc.com/docu53938_Avamar_7.1_Product_Security_Guide.pdf?language=en_US
Joe, Sure, any flag can be injected in dataset using the right syntax:   You can edit the dataset:   Edit Dataset - Options Tab - Click More   Select  the right plugin from drop d... See more...
Joe, Sure, any flag can be injected in dataset using the right syntax:   You can edit the dataset:   Edit Dataset - Options Tab - Click More   Select  the right plugin from drop down   Enter Attribute Section: [avtar]no-query-vols Enter Attribute Value: A:   Click plus button.. Click ok. Keep in mind that "[avtar]" string could be replaced for any other plugin binary where you want to apply some flag. For example: [avsql]sqltimeoutsecs=800
Joe, If you are using 7.1 client you could give it a try to the following flag in avtar.cmd: --no-query-vols=A: If you are running Avamar 7.0 client, please contact support to install a ho... See more...
Joe, If you are using 7.1 client you could give it a try to the following flag in avtar.cmd: --no-query-vols=A: If you are running Avamar 7.0 client, please contact support to install a hotfix since same flag is not included in 7.0 client by default.
./avoracle --browse --debug --verbose But at this point I would suggest you to open a support ticket so we can help you out.
There are a couple of libraries missing: libstdc++.so.6 =>        (file not found) libgcc_s.so.1 =>         (file not found) Could you run the previous find command to search them? find... See more...
There are a couple of libraries missing: libstdc++.so.6 =>        (file not found) libgcc_s.so.1 =>         (file not found) Could you run the previous find command to search them? find / -name libstdc++.so.6 find / -name libgcc_s.so.1
It seems one library is missing: ldd avoracle find / -name  libstdc* Could you also provide Avamar, Solaris and Oracle versions?
Please get avoracle browse command output, oratab file and tnsnames.ora file: ./avoracle --browse
Avamar 7.1 server officially supports 7.1, 7.0 and 6.1 client versions, and unfortunately Windows 2000 support is EOL since it was supported in Avamar 4.1 client so if you want to get support ple... See more...
Avamar 7.1 server officially supports 7.1, 7.0 and 6.1 client versions, and unfortunately Windows 2000 support is EOL since it was supported in Avamar 4.1 client so if you want to get support please contact your account team and get an RPQ submitted and approved to be able to back up those 3 servers.
Joe, Path can be forced on this registry entry: HKLM/Software/Emc/avamar/winfs
The first place to check would be the Avamar Cluster Configuration logs - av_cluster_config_wizard  located in client var folder
cpu-throttle is an avtar flag so it cannot be applied on plugin level. VSS or SQL backups will spawn one or several avtar processes to backup plugin data so this flag has to be applied on avtar l... See more...
cpu-throttle is an avtar flag so it cannot be applied on plugin level. VSS or SQL backups will spawn one or several avtar processes to backup plugin data so this flag has to be applied on avtar level to limit CPU usage. If you want to apply this flag to all kind of backups on client side, you just need to create a file named avtar.cmd on client side Avamar var folder and set cpu-throttle inside. You can also check this KB for further details: https://support.emc.com/kb/106429 I hope it helps, let me know if you need further assistance.
You attached some lines from avagent.log with no errors, just some harmless warnings, could you provide whole avagent log and backup logs? maybe you missed error there. What problem are you tryi... See more...
You attached some lines from avagent.log with no errors, just some harmless warnings, could you provide whole avagent log and backup logs? maybe you missed error there. What problem are you trying to solve?
Jurgen, This error is usually received if the 100 MB system partition is offline. Some VSS providers are known for taking offline any partition with no drive letter. You may need to give the par... See more...
Jurgen, This error is usually received if the 100 MB system partition is offline. Some VSS providers are known for taking offline any partition with no drive letter. You may need to give the partition a drive letter to avoid having it go offline. Solution: Open the command prompt as administrator, and run the commands below: C:\> Diskpart C:\Diskpart> List volume Check if the 100 MB partition is offline C:\Diskpart> Select volume 2 (Considering volume 2 is the 100 MB system partition) C:\Diskpart> Online volume See the following KB for further details: https://support.emc.com/kb/166631 Could you also provide the output of the following vssadmin commands if still fails? vssadmin list writers vssadmin list providers Rgds
Ludwig, It is officially supported on two different scenarios: 1. Support for minimal customer configurations. Some customer sites use a simple VMware topology, comprising a single ESX host, ... See more...
Ludwig, It is officially supported on two different scenarios: 1. Support for minimal customer configurations. Some customer sites use a simple VMware topology, comprising a single ESX host, with one or more virtual machines residing on that ESX host. These sites typically do not implement a vCenter management layer. However, the virtual machines residing on a standalone ESX host still must be backed up in order to protect against data loss. Adding the standalone ESX host as an Avamar vCenter client enables those virtual machines to be backed up with image backup, rather than guest backup. 2. Virtual vCenter disaster recovery. Adding an ESX host as an Avamar vCenter client can be useful when virtual machines residing on a particular ESX host must be restored, but the vCenter is not operational. This is often the case when a virtual vCenter must be recovered from Avamar backups. Adding the standalone ESX host as an Avamar vCenter client enables the vCenter management infrastructure virtual machines to be restored so that the vCenter can be restarted. Yours is the second one, so check VMware guide "Protecting ESX Hosts" for limitations and further information. Rgds