Monitor Appliance Health & Performance 24x7
Today’s businesses require access to their information on a 24x7 basis, not to mention the ability to protect that data in the event of unplanned interruptions which leads to complexities in their IT infrastructure. For many IT leaders, moving to Symantec appliances for their backup issues to protect data means reducing cost, complexity and operational risks in their IT environment. Symantec understands that a properly planned out data protection strategy enables customers continuous access to their information. To that end, Symantec has gone a step further to simplify, automate and enhance the support experiences for its appliance customers with its latest functionality in appliances, Symantec AutoSupport. Symantec AutoSupport proactively identifies issues, automates support, and enables faster resolution with the aim of lowering customer’s total cost of ownership of their appliance environment. As a result, appliance downtime is minimized, product reliability and serviceability is enhanced, storage capacity planning and management is simplified, and who doesn’t want their issues resolved before the customer is aware of any problems. To find out how Symantec AutoSupport can help, check out this video http://bit.ly/EnableAutoSupportQuestion : Regards backup exec 10d
Issue is Server was carashed re-built a new server with same hardware and trying to restore the backup from old server to a new server Getting error : Invalid physical volume library media identifier. Customer want to know if this is related to hardware issue or software issue ? I found a KB link : "Invalid Physical Volume Library Media Identifier" (a0008105 HEX or e00008105 HEX) is reported when a restore job fails. Please let me know If the above KB link will be helpfull ?Server Agent out of date
I started seeing LiveUpdate Information About the agent for windows on at least one server does not have the most recent updates? To Install the most recent updates, on the Backup and restore tab, right click the remote computer that is out of date, and then select Update. 1.There is no indication on what server agent is out of date 2.After right clicking on each server on some I can see Update is grayed out and on some its clickable 3.Does this mean they are out of date and need to be updated? 4.What happen if I update the server will I have to reboot? 5.The server is Windows 2003 with exchange 2003 running on a cluster serves with 2 nodes 6.It seem each node might need the upgrade and the cluster seems to need 7.I am assuming after I update the active node the cluster will be up-to-date 8.Should I manually run LiveUpdate on the backup Exec server monthly and after an update I should update the clients?
New Symantec Desktop & Laptop. NEW?!!
Version 7 is just a value. I've recently had the chance to test the "new" Symantec Desktop and Laptop, formerly the well known product named D&L...Option. Really there's nothing new and the product is only available as separate software and it has mantained the same old graphic style (since 2004 when it was linked to NBU 5.x). After all when it was linked as option to BE something new in aspect of icons and menus was changed! Now the engine/console is available for Windows 64bit paltform too but I've measured no improvements in 64bit services versus the traditional 32 bit ones. After all the database repository of D&L is the same: on a SQL Express instance locally setup together with the server/console or on an external SQL 2005/2008. Some improvement has been made on PST backup with a real "delta" incremental transfer of only the changed part of the PST but this requires the presence of the local desktop area of the DLO backed up files. Do not forget that this product can "ideologically" conflict with Enterprise Vault that would remove the PST (or NSF too) from desktop at all ;-) Technologically there's nothing new...again! The "engine" is the same version 3 of the formerly NBU 6.x/BE 2010 option and the things it can do are basically the same. After all nothing is changed on the users' desktop to justify new features and locally saved data (including PST) are the same! Same policies, some user profiling and so on. Simple question: I can understand the installation of LiveUpdate software in the console server but why the setup push LiveUpdate on the client too? This can cause issues. Some really negative note: . browsing of PC is always done using Netbios (no W7 client detected) . DLO agent on client is always started using the Programs/Startup folder and not a service linked on registry of the current user .I've got several issue pushing the agent on client with several errors (the vxpush is the same old one...) while when pushed using the BE2010 console there were no issues forcing me to manually install or to use a GPO . .the error code are the same old one V-xxx-yyyy from Veritas paleolithic era ;-) and, worst, most of the Internet link to the current support site are broken with no result!!! .automatic user assignment using AD or LDAP does not work on 64bit version!
