How often do you create a new recovery point set (base)?
When defining a new backup job, the default is "Start a new recovery point set the first time the backup is run in a new month". On my servers (Exchange, files, Sharepoint, and 2 DCs) I have chagned this default to "Start a new recovery point set the first time the backup is run in a new week". Which is better in your opinion? What are the pros and cons of each configuration?
Hot Swap - Lost disk format?
In my desktop PC I have an hot swap adapter. This allow me to have two or more hard drives with the same drive letter say "E:" Most of the time I use the hot swap for different groups of files (Movies on one drive, Books on a different) and the drive letter is "E:" which is the default letter that is assigned by the PC since it is the need letter not use by my internal hard drives. I back up my OS and Data with SSR to my 3 Tb internal hard drive that is assigned the letter "V:". Over the last few days, my V drive has been showing signs of getting "sick". So I purchased a second 3Tb drive. I removed the V drive from inside the computer. I placed my new 3Tb drive in the hot swap adapter and change the label to "Second BackUP- V2" and assigned it the drive letter "V:". It was my intention to rotate the two V drive as one does external USB drives. Since drives in the hot swap adapter are not on the USB port, the USB option is grayed out when I creat a new backup job. The SSR backup appeared to be running OK until at the very end, I receive an error. When I looked at the new V2 drive with Windows Disk Manager it was (1) unlable and (2) looked as if it was un-formated. I then put the original V drive in the hot swap adapter to make a backup before I attempted to find out what was wrong. SSR could not find the original V drive. When I looked at the original V drive it also appears to have "lost its format". Before, I attempt to take any other action, I am asking for your help. It appears that SSR does not like two disk with the same name. I did notice that SSR "identify" each backup location. Could this be the problem? Any quick solution to restore my backup copies without using a file recover software?
Dismiss old notification server and register new one
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?
