carlos.alfaro's Posts

carlos.alfaro's Posts

I have many Data Domain, some DD2200 and other model DD2500, all have a high consumption of RAM, but my backups work very well. Depending on the configuration of Data Domain disks, the system ... See more...
I have many Data Domain, some DD2200 and other model DD2500, all have a high consumption of RAM, but my backups work very well. Depending on the configuration of Data Domain disks, the system contains a certain value of RAM, look at the image: Data Somain Stream Informed Segment Layout (SISL) The foundation for Data Domain’s industry leading performance is the Stream-Informed Segment Layout (SISL) scaling architecture. SISL enables Data Domain systems to perform 99% of the deduplication processing in CPU and RAM, which gives it fantastic performance even with inefficient protocols like CIFS and NFS. SISL means Data Domain systems do not rely on increasing the number of disks to increase performance and therefore are not spindle-bound like other deduplication platforms. This is why Data Domain systems have dramatic increases in performance with each successive generation of Intel processors – every time Intel processors get faster, Data Domain systems get faster. So the server uses a lot of RAM and can use it at any time, but this is to make the backups faster. On servers with low memory the system consumes almost 100%. Data Domain uses a lot of RAM and can use it at any time, but this is to make the backups faster. On DD with low memory the system consumes almost 100%. In short, I suggest you look for another reason to justify the slow performance of your backups. My Data Domain systems: DD2200 - 1 (16 GB): DD2200 - 2 (8 GB): DD2200 - 3 ( 8 GB):
Hi, I use the next connectivity example for iSCSI to VNX or Unity: Without port binding: https://kb.vmware.com/kb/2038869 Use the next example without port binding: VMware Training - ... See more...
Hi, I use the next connectivity example for iSCSI to VNX or Unity: Without port binding: https://kb.vmware.com/kb/2038869 Use the next example without port binding: VMware Training - iSCSI and VMware vSphere 5 - Method 1 - YouTube Is good idea use jumbo frames (9000 MTU)
It seeks to increase the parallelism. Check the properties of the group has Savegrp parallelism >= 10. Verify if your pool and device allow writing in parallel. Create many c... See more...
It seeks to increase the parallelism. Check the properties of the group has Savegrp parallelism >= 10. Verify if your pool and device allow writing in parallel. Create many copies of client SQL within same group, but each client with different SQL data bases, 30 DBs for client is good idea,as Hrvoje Crvelin says. Please review this links: Does the savegrp parallelism value override the client parallelism value? Understanding NetWorker Parallelism and target sessions settings
Hi nrgreen, It is better not touch the original EBR. You must create a new EBR for the vCenter 6 and possibly leave the old vCenter, but failing that you can use "Direct to host recovery (Emergen... See more...
Hi nrgreen, It is better not touch the original EBR. You must create a new EBR for the vCenter 6 and possibly leave the old vCenter, but failing that you can use "Direct to host recovery (Emergency Restore)" witout vCenter. You can use the procedure "Recovery from a secondary site" to restore VMs between vCenters References: Direct to host recovery (Emergency Restore), pag 91 https://support.emc.com/docu57703_NetWorker_8.2_SP1_and_later_VMware_Integration_Guide.pdf?language=en_US Recovery from a secondary site, pag 109 https://support.emc.com/docu57703_NetWorker_8.2_SP1_and_later_VMware_Integration_Guide.pdf?language=en_US Best Regards.
Yes, is normal, same kernel Windows = same name Avamar.
Hi, you try to increase the parallelism of the client, when small databases downtime exists between them, put client parallelism in 8 or higher.
Hello, please review this document: https://support.emc.com/docu59471 Version 7.1.2-21 is a great choice,
You need EMC account, try this: Workaround: Use older web browser. For Example:You can use the older v36 Portable Firefox browser available here: http://ftp.mozilla.org/pub/mozilla.org/fi... See more...
You need EMC account, try this: Workaround: Use older web browser. For Example:You can use the older v36 Portable Firefox browser available here: http://ftp.mozilla.org/pub/mozilla.org/firefox/releases/36.0.4/ Fix: 1. Stop emwebapp emwebapp.sh --stop 2. Back up existing keystore (optional) cp /root/.keystore /root/.keystore.sav 3.List tomcat certificate  - should see one certificate  (optional) /usr/java/latest/bin/keytool -list  -keystore /root/.keystore -storepass changeit -alias tomcat 4. Delete tomcat certificate from keystore /usr/java/latest/bin/keytool -delete -alias tomcat -storepass changeit 5. (Optional) List tomcat certificate again - should return empty /usr/java/latest/bin/keytool -list  -keystore /root/.keystore -storepass changeit -alias tomcat 6. Regenerate certificate using SHA256 /usr/java/latest/bin/keytool -genkeypair -v -alias tomcat -keyalg RSA -sigalg SHA256withRSA -keystore  /root/.keystore -storepass changeit -keypass changeit -validity 3650 -dname "CN=localhost.localdom, OU=Avamar, O=EMC, L=Irvine, S=California, C=US" 7. List tomcat certificate again - should see one certificate (optional) 8. Start emwebapp.sh emwebapp.sh --start Once this is done: Google Chrome version 44.0.2403.155 m or later should work with ebr-configure and flr again URL
Please review the following document: https://www.emc.com/collateral/software/white-papers/h7082-data-domain-replicator-wp.pdf With DDBoost, then you should also be able to... See more...
Please review the following document: https://www.emc.com/collateral/software/white-papers/h7082-data-domain-replicator-wp.pdf With DDBoost, then you should also be able to take advantage of DD Boost replication active in NetBackup and NetWorker.
Try restarting client NetWorker services:   Confirm that the NetWorker Remote Exec daemon, nsrexecd is started:     ps -ef | grep nsr   If the nsrexecd daemon is not started, type: ... See more...
Try restarting client NetWorker services:   Confirm that the NetWorker Remote Exec daemon, nsrexecd is started:     ps -ef | grep nsr   If the nsrexecd daemon is not started, type:     /etc/rc.nsr   Stop the NetWorker daemons:     nsr_shutdown Review the NetWorker daemon.raw log file on NetWorker client – On UNIX, the log file appears in the /nsr/logs directory. Review the hosts file entries on client and on Networker server Restore client from Networker using command https://community.emc.com/blogs/cairo_BRS/2013/05/19/how-to-restore-linux-client-from-networker-using-command