I need a solution
Hello,
I use System recovery 2013 r2 and I can't create a the recovery disk.
Classic option is not avalaible.
Windows save and backup is working correctly.
Thanks for your help
↧
Can create a recovery Disck
↧
Imposible de créer le disque de recupération
I need a solution
Bonjour,
Je n'arrive pas à creer le disque de recupération. l'otption "classique" n'est pas disponible alors que la sauvegarde windows fonctionne parfaitement.
J'utilise system recovery 2013 r2
Merci pour vore aide
↧
↧
SSR 2013 R2 Desktop Edition
I need a solution
I am currently using SSR2013R2 Desktop Edition on Windows 8.1 64-bit and have used this product on various Windows operating systems for a number of years.
Microsoft have annouced on Monday (1st June) that Windows 10 will be released on 29th July 2015. The platform will be made available across the globe in 190 markets as a free upgrade from Windows 7 and Windows 8.1. Customers who are still sporting Windows 8 will need to upgrade to Windows 8.1 first before getting on the Windows 10 bandwagon.
I would like to know if SSR2013 supports Windows 10 now and if not when it is likely to?
Regards.
↧
Will there be an update to support Windows 10 before transition to Veritas?
I do not need a solution (just sharing information)
Just heard that our beloved (!) SSR 2013 R2 will transition to become a Veritas product.
Was wondering if we will see any new build (to support Windows 10) before this happens....
↧
Excessive Backup Time
I need a solution
I am using SSR 2013 on a Win XP system. I have installed all the components that were specified prior to SSR 2013 installation (WIN & .Net 4). Installation went smoothly with no errors reported. However, when I try to perform the initial backup, what usually takes 15 - 20 minutes is now taking 5 hours. This is being backed up on a local hard drive, NOT over the intranet. I would welcome any and all suggestions on how to correct this issue.
Thank you
↧
↧
SSR 2013 Error: E7D1000E "Unable to open '/WINDOWS/system32/config/SYSTEM'. It does not exist." when restoring v2i files.
I need a solution
I used SSR 2013 to backup an existing laptop.
I am trying to image a new workstation with those .v2i files and getting the error message above.
Any assistance is appreciated.
↧
Data Base query
I need a solution
Can multiple data base servers point to single enforce console
↧
SSR iso image 64 bits Windows
I need a solution
Hi,
I have seen that there are many entries about this problem. I have used the links provided in those but I have dowload the SSR 2013 but not an iso file for the recovery disc. I really need the 64 bits ISO for a Windows Server 2008 installation.
Thanks in advanced.
↧
Dismiss old notification server and register new one
I need a solution
I had to replace the old server running SSR 2013 R2 management solution with a new one. Toghether with this, I also moved the SQL database from an old 2008R2 server to a new sql 2012 server. These servers when down, so I was restoring the database by extracting it from a BACKUP made with SSR2013. I didn't want to restore the full backups because I also wanted to migrate to windows 2012 r2 (from 2008r2) and to sql 2012.
To do this I followed some discussions i found in this forum.
1)Installed SQL server 2012 on SQLNEW
2)restored the database from the backup into the DATA folder of mysql server on SQLNEW
3)imported the database in sql 2012
4)installed SIM on NOTIFICATIONSERVERNEW
5)started SSR 2013 install on NOTIFICATIONSERVERNEW, SIM added Symantec managements platform 7.5 SP1 automatically
6)In the install procedure I select the SQLNEW as new server, and i select to use existing database
7)I wait for the installation, the configuration takes a lot of time as expected
8)In Altiris management console on NOTIFICATIONSERVERNEW, I went to Manage->Filters->Computer Filters->All computers and removed the old dismissed servers, except NOTIFICATIONSERVEROLD that has no delete option
then i navigate to Manage->Filters->Notification Server Filters->Notification Server and Manage->Filters->Notification Server Filters->Site Server.
In the first, only NOTIFICATIONSERVEROLD is listed.
QUESTION1) How can i add NOTIFICATIONSERVERNEW and remove NOTIFICATIONSERVEROLD from this list?
In the second, both servers are listed
QUESTION2)How can i remove NOTIFICATIONSERVEROLD from this list?
↧
↧
Symantec LiveState 2013 R2 & ESXI Free -> VM-Based and/or Cold Image Possible?
I need a solution
Hello,
We have inherited a Server running ESXI Free and a single VM with Server 2012R2
-Recognizing the limitations inherent in the Free Edition in terms of protecting the ESXI, is at least possible to install 2013R2 w/in the Virtual Machine and successfully back it up to external storage for DR Consideration?
-Model would be if total server failure at least 2012 Server can be saved and restored to different machine via V2P
-Apparently VM does have standard Backup Exec on it currently that running - did not know if this would extend to 2013 R2
-Additionally to get an entire image of the machine can the entire Drive be imaged via Cold Boot with new version of SRD
Thank you very much
↧
trouble removing old backup destination from SSR 2013 R2 management solution
I need a solution
I have followed this guide
https://support.symantec.com/en_US/article.TECH153...
to remove old backup destinations.
Unfortunately I didn't read the note at the end:
NOTE: Please be aware of the following side effects of using the above steps:
- Client machines may lose their association with the backup policy
- Client machines may go into a 'Not Installed' state (seen via 'Manage Tasks' / 'Computers' view)
Despite the above side effects, over a period of time (impossible to say how long as it depends on size of environment and what the Symantec Management Agent 'configuration' interval is set to), the client machines will regain their association to the backup policy and also regain their correct status (when the policy 'cleanup' is complete).
It happened that 4 clients have undergon exactly the issues cited here. Even more, they completely disappeared from the management solution, like they had been deleted (but I didn't delete them, I just followed the guide and deleted their old backup destinations associations). After clicking "update" in the managament agent settings tab, they appeared again in the management solution, going to "not installed state". After rebooting them one time, they changed their state to SAFE/AT RISK depending on what was their state before. BUT! They have lost their associtation with all client polices, included backup policies.
What should I do? I have waited 24 h and reboteed them 5 times. Should I wait even more? or should I start to add them back manually to the policies? Why this happened? My suspect is that the policies have not been restore because in the above procedure not only their backup destinations, but also their records had been deleted from the database...
↧
Windows 10? New software update for Symantec System Recovery 2013 Desktop Edition?
I need a solution
I am currently using Symantec System Recovery 2013 R2 with my Windows 8.1 based desktop PC. I am planning on upgrading to Windows 10 on July 29, 2015 when Windows 10 is released. I've been relying on Norton Ghost and SSR 2013 to do full system images for years.
Is Symantec currently working on software for Symantec System Recovery 2013 so that it will be compatible with Windows 10?
Will Symantec be offering a FREE update patch to Symantec System Recovery 2013 that will make it compatible with Windows 10? Will it be called Symantec System Recovery 2013 R3 or something else like Symantec System Recovery 2015?
I would like to see SSR 2013 tested and certified as compatible with Windows 10 as soon as possible. I would prefer not to have switch to another vendor's system image backup software like Acronis. Their website is saying that you can get a free software update for Windows 10 compatibility for Acronis True Image 2015.
↧
Agent not communicating on server with domain controller
I need a solution
Hello. I have several 2003R2 servers that I'm looking to backup with SSR 2013R2 Server. I have one main server that contains SSR and have installed the agent to multiple servers on the network with no issues being able to comunicate back and forth to them. I'm having an issue with one of them though. It's our DR domain controller server. I'm able to deploy the agent to the server with no issues. After the server reboots, I can no longer connect via SSR. I can see it in the list of computers and it shows the agent is installed in SSR computer search but I can't do anything else with it. Any ideas??
Thanks
↧
↧
SSR recovery failed: no OS
I need a solution
Hi, our customer's SSR is SSR 2013 R2. We are helping them testing SSR recovery of a Windows client (Windows Server 2008 R2 SP1). After boot from SSR recovery CD, in the recovery point page, we saw individual disks (C drive, D drive and E drive) under Date or System instead of one recovery point that contains all drives.
May I know why we cannot see one recovery point with all drives? And in this case, how to recover the full system? Shall we recovery the drives one by one?
Thanks in advance.
↧
Symantec System Recovery 2013 R2: Error EBAB03F1
I need a solution
Hi all,
I'm evaluating Symantec System Recovery 2013 R2; when I try to get a "One Time Backup" I receive the following error on screen:
-Snapshot error %1.
--Error EBAB03F1: Following Operating System error occurred while performing requested operation: 'OS error 2147754996.'
(UMI:V-281-187-181)
And this via email:
Description: Error EC8F17B7: Cannot create recovery points for job: Drive Backup of Riservato per il sistema (*:\), DISK_C (C:\), DISK_D (D:\), DISK_E (E:\).
Error E0BB00B5: Snapshot error Error EBAB03F1: Following Operating System error occurred while performing requested operation: 'OS error 2147754996.'.
Details: 0xE0BB00B5
I tried to reboot but the same error; I deeply checked the hard disk using the manufacturer's utility but no error on the disk.
The error occurs at the end of the process (after about 4 hours).
Any suggestion?
Thank you
↧
Symantec SR Backup fails 0xE4F3000F - VSS Error
I need a solution
Hi all,
we are using a SBS 2011 Standard with System Recovery 2013 R2. We have used Backup Exec 2010 R3 before and had trouble with that too. The VSS Microsoft Exchange Writer gets into state 9 (timed out).
Backup protocol says:
Fehler E4F3000F: Unexpected VSS writer error. Check the application event log for writer specific error. Failed VSS writers: Microsoft Exchange Writer.
Details: 0xE4F3000F
I can reboot the server or the service but it will occur after 1-2 days again. We can't do any full or incremental backups in that time.
Writer name: "Microsoft Exchange Writer"
Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
Writer Instance Id: {9b6d5bed-27f5-4409-8257-dea8f2450938}
State: [9] Failed
Last error: Timed out
I've been searching for a solution for days but no luck yet. Any help is appreciated.
Many thanks in advance
Stef
↧
Administrator doesn't have permission to restore Users Directory to New Server
I need a solution
We have a folderRedirect for all Users and they are the explicit owner of the folder. I am restoring the entire directory to a new folder on a completely different Server and it will NOT copy the files over. I mounted the directory and tried to use Xcopy to copy them over and I get a "permissions" error. I don't want to go through and use icacls to take ownership and grant rights to Administrator. Which Symantec tool should copy over the files with permissions in tact? Since I nor the Symantec Service account (domain admins) don't have access "Granular Restore" tool is not working. It only restore a few folders that Domain Admin is the CO-OWNER of.
The new folder has Administrator with full rights (Do I need to remove that?)
Thanks for your assistance!
Bodnice
↧
↧
Recovery Disk for Multiple Devices Unable to Load Network Adaptor
I need a solution
Good morning,
I've been trying to set up a recovery disk for a small number of computers here at work using SSR2013 R2. We planned on storing the disk on a single USB-connected hard drive. I've gone around to each of our computers and used the Customize Recovery Disk option to add their drivers. We use an NAS for storing backups, so at the very least I need each computer's network drivers. However, after getting all of the drivers, I now can't access our network in the recovery environment of a computer that was able to connect previously (it gives the unable to find network adaptor error).
To perhaps clarify, the USB drive does not just contain iso files, it is itself the recovery disk.
Is there any way I can ensure the correct drivers are loaded for each computer? Could it have something to do with multiple versions of the same driver being on the recovery disk?
Thanks for your help!
↧
changing backup settings to allow new hard drives
I need a solution
Our current setup:
Windows Small Business Server 2011 (which is actually Server 2008 R2)
Symantec System Recovery 2013
Logical drives are C:, D: and E:. We back these up on a weeknightly basis (Monday, Tuesday, Wednesday, Thursday, and Friday). It also backs up the System Reserved drive. It is a recovery point set that run a complete backup each night to an external USB drive. Before the backup runs, we delete out the previous recovery backups from the week before. Ex: on a Tuesday night, we plug in the USB drive labeled "Tuesday". In Windows explorer, we delete out the backup files that are there from last Tuesday's backup. This leaves the hard drive blank, allowing that night's backup to run, which completely copies over the C:, D: and E: drives to the Tuesday USB hard drive (in the case of someone accidently leaving the previous week's backup files on the USB drive, the job creates a differential backup of the logical drives to the USB drive).
-We are using a recovery point set job description. Every day, the job shows up as scheduled with the destination drive labeled according to the day of the week: [Monday]\, [Tuesday]\, etc.
-Each hard drive has a recovery point set limit of 1.
-All the USB hard drives are identical.
The problem is that one of the hard drives has failed and we are replacing it with a different, higher capacity USB hard drive. Now the scheduled jobs do not run on that drive. When we run the scheduled backup job manually, it backups successfully to the new USB hard drive.
I do not have any error messages right now, unfortunately.
What changes do I need to make to my scheduled backup job to allow it to backup to different models of hard drive? We are not using offsite backup features.
↧
Splitting hairs
I need a solution
At time updates don't make sense. This seems to be one of those times. Can someone point me to the What's New article about the differences in SSR 2013 and SSR2013 R2? Or is it so minor someone can tell me? Thanks
↧